[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [security-services] Proposed Text and Location for HolderOfKe yand SenderVouches (NOTE commentary at start)
You are quite right, will fix this to say: A <ds:KeyInfo> element MUST be present within the <SubjectConfirmation> element. >>-----Original Message----- >>From: Scott Cantor [mailto:cantor.2@osu.edu] >>Sent: Friday, April 05, 2002 5:48 PM >>To: 'Mishra, Prateek'; security-services@lists.oasis-open.org >>Subject: RE: [security-services] Proposed Text and Location for >>HolderOfKey and SenderVouches (NOTE commentary at start) >> >> >>>5.1.1 Holder Of Key >>> >>>URI: >>>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key >>>The element <SubjectConfirmationData> value MUST be a <ds:KeyInfo> >>>element. >> >>Just one note...aren't there still two elements in that bucket, one >>called SubjectConfirmationData, the other a literal ds:KeyInfo? I >>thought the intent was to use the KeyInfo element when "holder of key" >>was meant, and use SubjectConfirmationData when KeyInfo >>didn't apply. Or >>did I misunderstand on the last call? >> >>The proposed text suggests to me this usage: >> >><SubjectConfirmationData> >> <ds:KeyInfo/> >></SubjectConfirmationData> >> >>I'm not sure if that's the intent or not. >> >>-- Scott >>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC