[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [security-services] proposed change to POST profile: send Response instead of Assertion
> From: RL 'Bob' Morgan [mailto:rlmorgan@washington.edu] > Subject: [security-services] proposed change to POST profile: send > Response instead of Assertion > > (i) The proposed Response is not issued in response to a > Request. This > doesn't seem like much of an argument to me. If the > structure is useful, > let's use it; I think there are lots of existing protocols where > "unsolicited responses" exist for this same sort of reason. One specific nit here: the Response has a mandatory element InResponseTo (core25, line 1059) that MUST contain the RequestID. This would need to be tweaked slightly to support unsolicited responses. - 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC