Clarifications for When to Use the name-addr Production in SIP Messages

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 6
Abstract: RFC 3261 constrained several SIP header fields whose grammar contains the "name-addr / addr-spec" alternative to use name-addr when certain characters appear. Unfortunately, it expressed the constraints with prose copied into each header field definition, and at least one header field was missed. Further, the constraint has not been copied into documents defining extension headers whose grammar contains the alternative. This document updates RFC 3261 to state the constraint generically and clarifies that the constraint applies to all SIP header fields where there is a choice between using name-addr or addr-spec. It also updates the RFCs that define extension SIP header fields using the alternative to clarify that the constraint applies (RFCs 3325, 3515, 3892, 4508, 5002, 5318, 5360, and 5502).
Publication Date: 2017-08-01
Status Note: Proposed Standard
DOI: 10.17487/RFC8217
Link: https://doi.org/10.17487/RFC8217
Author(s): Robert Sparks

Latest version of IETF RFC 8217

Document Versions — IETF RFC 8217

▶ IETF RFC 8217 (2017-08-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 3261 [Active*]
IETF RFC 3325 [Active*]
IETF RFC 3515 [Active*]
IETF RFC 3892 [Active*]
IETF RFC 4508 [Active*]
IETF RFC 5002 [Active*]
IETF RFC 5234 [Active, Amended*]
RFC5318 — RFC5318 EXTERNAL
RFC5360 — RFC5360 EXTERNAL
RFC5502 — RFC5502 EXTERNAL
IETF RFC 8174 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC8217.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 8217, Clarifications for When to Use the name-addr Production in SIP Messages. Available at https://doi.org/10.17487/RFC8217

Snippet:

IETF RFC 8217, Clarifications for When to Use the name-addr Production in SIP Messages. Available at https://doi.org/10.17487/RFC8217

HTML (ISO 690 compliant)

Preview:

IETF RFC 8217, Clarifications for When to Use the name-addr Production in SIP Messages. Available at https://doi.org/10.17487/RFC8217

Snippet:

<span class="citation"><cite>IETF RFC 8217</cite>, Clarifications for When to Use the name-addr Production in SIP Messages. Available at <a href="https://doi.org/10.17487/RFC8217" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8217</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 8217, Clarifications for When to Use the name-addr Production in SIP Messages
doi: 10.17487/RFC8217
url: https://doi.org/10.17487/RFC8217

Snippet:

<li>
<cite id="bib-rfc8217">IETF RFC 8217</cite>, Clarifications for When to Use the name-addr Production in SIP Messages
<span class="doi">10.17487/RFC8217</span>
</li>