rfc-8217
Clarifications for When to Use the name-addr Production in SIP Messages
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).
updates
- rfc-3261 — SIP: Session Initiation Protocol
- rfc-3325 — Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
- rfc-3515 — The Session Initiation Protocol (SIP) Refer Method
- rfc-3892 — The Session Initiation Protocol (SIP) Referred-By Mechanism
- rfc-4508 — Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method
- rfc-5002 — The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
- rfc-5318 — The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
- rfc-5360 — A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
- rfc-5502 — The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem