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.…

Read RFC 8217 on the RFC Editor

Outgoing relationships (9 related RFCs)

Updates — RFC 3261: SIP: Session Initiation Protocol
Updates — RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
Updates — RFC 3515: The Session Initiation Protocol (SIP) Refer Method
Updates — RFC 3892: The Session Initiation Protocol (SIP) Referred-By Mechanism
Updates — RFC 5360: A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
Updates — RFC 4508: Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method
Updates — RFC 5002: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)
Updates — RFC 5318: The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
Updates — RFC 5502: The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem

Incoming relationships (1 related RFC)

Normatively referenced by — RFC 8496: P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)