Thanks for clarifying this. BTW, could someone clarify as to why Authentication-Info header is explicitly mentioned as being permitted in SIP, w.a. Proxy-Authentication-Info is not ? Although this header also only gets a fleeting description (in sec. 3.6 of RFC2617).
regards, bd -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Tate Sent: Tuesday, September 20, 2005 6:35 PM To: 'Sip-Implementors' Subject: RE: [Sip-implementors] WWW-Authenticate header,need for .domain. parameter > RFC2617 talks about the .domain. parameter for WWW-Authenticate > header. > Is this relevant in case of SIP ? No. RFC 3261 section 22.4 number 5 mentions that the caching mechanism of RFC 2617 does not apply to SIP. RFC 3261 section 22 presents the SIP caching mechanism. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
