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

Received changes through RFC Editor sync (changed abstract to '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).')

Received changes through RFC Editor sync (created alias RFC 8217, changed title to 'Clarifications for When to Use the name-addr Production in SIP Messages', changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-08-02, changed IESG state to RFC Published, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 3261, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 3325, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 3515, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 3892, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 4508, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 5002, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 5318, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 5360, created updates relation between draft-ietf-sipcore-name-addr-guidance and RFC 5502)