Inline ... >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Thursday, July 26, 2007 12:04 AM >To: Sanjay Sinha (sanjsinh) >Cc: Jeroen van Bemmel; sip-implementors@lists.cs.columbia.edu >Subject: Re: [Sip-implementors] B2BUA Problem when processing 401/407 > > > >Sanjay Sinha (sanjsinh) wrote: >> I think the RFC is pretty clear on what the behavior should be. Here >> is the quote from sec. 22.2: >> >> When a UAC resubmits a request with its credentials after >receiving a >> 401 (Unauthorized) or 407 (Proxy Authentication Required) >response, >> it MUST increment the CSeq header field value as it would normally >> when sending an updated request. >> >> Since it is asking the UAC to increment the Cseq number, it is >> implicit that the Call-Id + from-tag must not change from >the initial request. >> So the UAC side of your B2BUA needs to follow this rule too. >> >> Sanjay >> >> >> >I agree that the recommended behavior is clear. But the point I want >to raise is I found a valid reason to deviate and since it's a >SHOULD, I >did not break any rule. It almost sounds as if you are telling me to >NOT bother about the SHOULD and treat every SHOULD as a MUST. > >Lets reverse the table for a while. Let's say I am the implementor of >the far-end UAS and not the B2BUA. I got a resend of the >credentials >with a different call-id, is there anything in 3261 stating >this as an error condition? What's the error response I should use?
As Scott mentioned in this thread, you should expect lots of failures from UAS particularly if the implementation uses call-id value to construct the nonce so that the nonce is specific to the call. I expect lots of 401 responses from UAS and maybe finally a 403. But as a UAC you need to follow the text mentioned in sec. 22.2, it is not a SHOULD, it is a MUST. So there is no ambiguity about it Sanjay _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
