RE: [security-services] Changes for Core 26

["Hallam-Baker, Phillip" <pbaker@verisign.com>]

The canonical form in 2396 is pretty robust and the rules are very
straightforward,

Essentially the only place where case insensitivity comes in is in the part
of a URI that is a DNS name.

Even if the file is located on a Windows or VMS machine http://foo.com/Fred
is not equivalent to http://foo.com/FRED or http://foo.com/fred

	Phill

Phillip Hallam-Baker FBCS C.Eng.
Principal Scientist
VeriSign Inc.
pbaker@verisign.com
781 245 6996 x227


> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu]
> Sent: Friday, February 08, 2002 1:13 PM
> To: stephen.farrell@baltimore.ie
> Cc: 'Security-Services (E-mail)'
> Subject: RE: [security-services] Changes for Core 26
> 
> 
> > All URIs contained in SAML elements (whether as element or attribute
> > values) MUST be compared as specified in [RFC2396]. In 
> particular this
> > means that "http://foo.com/go/to/the/pub/" represents the same
> resource
> > as "HTTP://FoO.CoM:80/go/../go/to/the/pub". 
> 
> Stephen, do you (or anyone else) know if this is the rule specified by
> the relevant XML standards for comparing namespace URIs?
> 
> I'm specifically curious about that in the context of using URIs as
> identifiers for things like confirmation methods or audience
> restrictions.
> 
> -- Scott
> 
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>

Phillip Hallam-Baker (E-mail).vcf