> As per 3GPP spec 33.203, server adds Authentication-Info header
> in REGISTER response, Proxy-Authentication-Info header in
> Non-REGISTER response.
>
> 1. Can server add Authentication-Info header in non-REGISTER
> response and Proxy-Authentication-Info header in REGISTER
> response?
>
> 2. If yes for query#1,
> i. Should client process both Authentication-Info and
> Proxy-Authentication-Info header are same?
As far as I know, the IETF has never defined Proxy-Authentication-Info for use
within SIP. There were some discussions concerning the header during the
rfc2543bis process ("Open Issue #164: Proxy-Authentication-Info") and within
http://tools.ietf.org/id/draft-dotson-sip-mutual-auth-03.txt
However, the header is not registered with IANA (with reference to the document
that defines it). I'm not sure if 3GPP or anyone will finally get it
registered/documented for use.
http://www.iana.org/assignments/sip-parameters
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
