metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3326: The Reason Header Field for the Session Initiation Protocol (SIP)

Still current, but amended. Parts of this document are changed or extended by RFC 8606, RFC 9366. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3326
Published
December 2002
Authors
H. Schulzrinne; D. Oran; G. Camarillo
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
8
Also known as
—
Updated by:
RFC 8606, RFC 9366

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3326-the-reason-header-field-for-the-session-initiation-protocol-sip