Hi
Refer ETSI TS 124 229 V6.6.0 (2005-03) for your answers. Excerpts: 5.1.1.2 Initial registration The initial registration procedure consists of the UE sending an unprotected REGISTER request and, upon being challenged, sending the integrity protected REGISTER request. The UE can register a public user identity with its contact address at any time after it has aquired an IP address, discovered a P-CSCF, and established an IP-CAN bearer that can be used for SIP signalling. .. .. On sending a REGISTER request, the UE shall populate the header fields as follows: a) an Authorization header, with: - the username directive, set to the value of the private user identity; - the realm directive, set to the domain name of the home network; - the uri directive, set to the SIP URI of the domain name of the home network; - the nonce directive, set to an empty value; and - the response directive, set to an empty value; Regards, Tarun Aricent -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of cool goose Sent: Tuesday, March 10, 2009 11:38 AM To: [email protected] Subject: [Sip-implementors] REGISTER request with Authorization header field Hi All, In RFC 2617 in Section 1.2 Access Authentication Framework states the below mentioned: " A user agent that wishes to authenticate itself with an origin server--usually, but not necessarily, after receiving a 401 (Unauthorized)--MAY do so by including an Authorization header field with the request. " Does this mean that a UAC can originate a REGISTER request with Authorization header before it receives 401 Un authorized? If so, what would be the contents of such REGISTER request? What would be the value of nonce field? Since the nonce value is provided by UAC or registrar in 401 Un authorized, if UAC wishes to authenticate itself before receiving 401, what should it use for the nonce value for computing the digest response? Thanks in Advance, CoolGoose. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
