Two points on this list of response code definitions: 1) Instead of using "It is used when..." and defining the sender condition, can we write it if a form of the semantics the receiver should understand from receiving it. The sender conditions should be covered by normative statements along the lines of "If <condition> then the UAS MUST/SHOULD send a 4xx (xxx) response" elsewhere in the document.
2) A question to which I do not have an answer. This defines 3 new response codes. Are these allocated in sufficiently generic a form. For example the first could be just "Assertion required of Identity header" and the fact that it is a SAML assertion contained in a new header field. I would like at some point to see some list discussion on this. Regards Keith > -----Original Message----- > From: Hannes Tschofenig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 11, 2007 10:03 AM > To: IETF SIP List > Subject: [Sip] SIP SAML IANA Consideration Sction > > I compiled a first version of the IANA consideration section. > Please find it here: http://www.tschofenig.com:8080/saml-sip/issue22 > > Ciao > Hannes > > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
