Browse Prior Art Database

Clarifications for When to Use the name-addr Production in SIP Messages (RFC8217) Disclosure Number: IPCOM000250560D
Original Publication Date: 2017-Aug-01
Included in the Prior Art Database: 2017-Aug-03
Document File: 12 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Sparks: AUTHOR


[RFC3261] defines several header fields that contain URIs to allow both a form that contains the bare URI (addr-spec) and one that provides a name and the URI (name-addr). This subset, taken from the ABNF [RFC5234] specified in [RFC3261], shows the relevant part of the definition of the syntax of the "From" header field:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 21% of the total text.

Internet Engineering Task Force (IETF)                         R. Sparks Request for Comments: 8217                                        Oracle Updates: 3261, 3325, 3515, 3892, 4508,                       August 2017          5002, 5318, 5360, 5502 Category: Standards Track ISSN: 2070-1721

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

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Sparks                       Standards Track                    [Page 1]
 RFC 8217                name-addr Clarifications             August 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents

   ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . ....