I agree with Bob; however the branch would need to change if it starts with the magic cookie.
Additionally RFC3665 currently shows the tag changing instead of following the rfc3261 section 8.1.3.5 SHOULD text. Thus RFC3665 potentially should be corrected via errata or bugzilla. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Bob Penfield > Sent: Thursday, May 18, 2006 7:53 PM > To: Szilagyi, Mike; [email protected] > Subject: Re: [Sip-implementors] From-tag on Registration attempt > > > It is referring to the entire From header, including the tag. > The only > difference in the request should be the CSeq (increased by > 1), and the > addition of credentials (WWW-Authenticate or Proxy-Authenticate). > > cheers, > (-:bob > > Robert F. Penfield > Chief Software Architect > Acme Packet, Inc. > 71 Third Avenue > Burlington, MA 01803 > [EMAIL PROTECTED] > > > ----- Original Message ----- > From: "Szilagyi, Mike" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Thursday, May 18, 2006 7:11 PM > Subject: [Sip-implementors] From-tag on Registration attempt > > > > When a UAS or proxy challenges a REGISTER request, should > the UAC use > > the From-tag from the original request in the second > REGISTER attempt. > > > > RFC3261 says it should have the same From header but does not > > explicitly mention the tag value. > > > > Regards. > > _______________________________________________ > > Sip-implementors mailing list [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
