True, though why not still use this XML structure and the "RetrievalMethod" element within the XRDS so that can then point to a remote "KeyInfo" element in another XML document?
--David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grant Monroe Sent: Friday, January 05, 2007 8:31 AM To: Recordon, David Cc: Carl Howells; specs@openid.net Subject: Re: Key Discovery In DTP Draft 3 On 1/4/07, Recordon, David <[EMAIL PROTECTED]> wrote: > Hey guys, > Was looking at > http://openid.net/specs/openid-service-key-discovery-1_0-01.html > tonight and curious why the decision was made to define the <PublicKey > /> element which contains a link to the RSA key or X.509 certificate > versus embedding the key in the XRDS file? I believe the rational was that KeyInfo objects can be quite large. Especially if you have multiple services using them. We were concerned about XRDSs getting really large. It doesn't make a whole lot of sense to download a key for a service entry you aren't even interested in. -- Grant Monroe JanRain, Inc. _______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
