Then why are RFC 3665 we have proxy authentication for some ack and not for others see call flow f2
On 19 Dec 2016 22:45, "Tarun Gupta" <[email protected]> wrote: > Hi > > Proxy-Authorization header is optional for ACK - see Table 3 in RFC 3261. > > Also Section 22 of RFC 3261 states the following (which should answer your > question): > > Under an authentication scheme that uses responses to carry values > used to compute nonces (such as Digest), some problems come up for > any requests that take no response, including ACK. For this reason, > any credentials in the INVITE that were accepted by a server MUST be > accepted by that server for the ACK. UACs creating an ACK message > will duplicate all of the Authorization and Proxy-Authorization > header field values that appeared in the INVITE to which the ACK > corresponds. Servers MUST NOT attempt to challenge an ACK. > > Hope this helps. > > Regards > Tarun Gupta > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of sairam > pokkunuri > Sent: Monday, December 19, 2016 3:42 PM > To: [email protected] > Subject: [Sip-implementors] Regarding UAC behaviour for ACK with > proxy-authentication > > Hi > > As per RFC 3665 there are two call flows where in UAC sends ACK message > with proxy-authentication > > Is Proxy-Authorization mandatory or optional for ack > > What is the use of Proxy-Authorization header at ACK ? > As far as I understand "Proxy-Authorization" should be there for all > upcoming requests post 407/401 Please clarify > > Page 30 RFC 3665 > > > CSeq: 2 ACK > Proxy-Authorization: Digest username="alice", > realm="atlanta.example.com", > nonce="wf84f1ceczx41ae6cbe5aea9c8e88d359", opaque="", > uri="sip:[email protected]", > response="42ce3cef44b22f50c6a6071bc8" > Content-Length: 0 > > > > Regards > > Sai > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
