The Reason Header Field for the Session Initiation Protocol (SIP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- The REGISTER function is used in a Session Initiation Protocol (SIP) system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a Uniform Resource Identifier (URI), such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP User Agent (UA). The problem is that network topology may have one or more SIP proxies between the UA and the registrar, such that any request traveling from the user's home network to the registered UA must traverse these proxies. The REGISTER method does not give us a mechanism to discover and record this sequence of proxies in the registrar for future use. This document defines an extension header field, "Path" which provides such a mechanism. [STANDARDS-TRACK]
- Publication Date
- 2002-12-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3326- Link
- https://doi.org/10.17487/RFC3326
- Author(s)
- Henning SchulzrinneDavid R. OranGonzalo Camarillo
- Keyword(s)
- SIP, Heterogeneous Error Response Forking Problem
Latest version of IETF RFC 3326
Document Versions — IETF RFC 3326
-
▶ IETF RFC 3326 (2002-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3261 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3326.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3326, The Reason Header Field for the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3326
Snippet:
IETF RFC 3326, The Reason Header Field for the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3326
HTML (ISO 690 compliant)
Preview:
IETF RFC 3326, The Reason Header Field for the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3326
Snippet:
<span class="citation"><cite>IETF RFC 3326</cite>, The Reason Header Field for the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC3326" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3326</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3326, The Reason Header Field for the Session Initiation Protocol (SIP)
doi: 10.17487/RFC3326
url: https://doi.org/10.17487/RFC3326
doi: 10.17487/RFC3326
url: https://doi.org/10.17487/RFC3326
Snippet:
<li> <cite id="bib-rfc3326">IETF RFC 3326</cite>, The Reason Header Field for the Session Initiation Protocol (SIP) <span class="doi">10.17487/RFC3326</span> </li>
Referenced By
- IETF RFC 3725 [Active*]
- IETF RFC 4244 [Superseded*]
- IETF RFC 4964 [Active*]
- IETF RFC 7044 [Active*]
- IETF RFC 8606 [Active*]
- IETF RFC 9366 [Active*]