RE: [security-services] ISSUE: Format attribute for Issuer also

[Irving Reid <Irving.Reid@baltimore.com>]

> From: RL 'Bob' Morgan [mailto:rlmorgan@washington.edu]
> 
> I think the reasoning that justifies the "Format" attribute 
> for Subject
> NameIdentifier applies equally well to Issuer, since Issuer names also
> will come in the same several standard formats as well as non-standard
> ones, and it would be useful for RPs to be able to 
> distinguish these.  I
> note that this is consistent with RFC 2459, which specifies the use of
> GeneralName syntax for IssuerAltName too.
> 
> So I suggest (as an ISSUE) that the schema for Issuer be modified to
> permit the inclusion of the "Format" attribute for it too 
> (sorry my schema
> skills are limited, so I can't suggest the mod).

I disagree. As it stands, the <Issuer> element refers to a pre-defined
relationship between the asserting party and the relying party. The only
reasonable thing to do with this field is for the relying party to look it
up in a table - there should be no need to parse it in any way.

 - irving -


-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.