--- 1/draft-ietf-sipcore-content-id-03.txt 2017-05-08 13:13:09.282398413 -0700 +++ 2/draft-ietf-sipcore-content-id-04.txt 2017-05-08 13:13:09.298398797 -0700 @@ -1,19 +1,19 @@ SIPCORE Working Group C. Holmberg Internet-Draft I. Sedlacek Updates: 5621 (if approved) Ericsson -Intended status: Standards Track April 28, 2017 -Expires: October 30, 2017 +Intended status: Standards Track May 8, 2017 +Expires: November 9, 2017 Content-ID header field in Session Initiation Protocol (SIP) - draft-ietf-sipcore-content-id-03 + draft-ietf-sipcore-content-id-04 Abstract This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). The document also updates RFC 5621, to enable a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. Status of This Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on October 30, 2017. + This Internet-Draft will expire on November 9, 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -57,21 +57,21 @@ 1.4.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 3 1.4.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 4 1.5. Solution . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Content-ID header field . . . . . . . . . . . . . . . . . . . 4 3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Semantics . . . . . . . . . . . . . . . . . . . . . . . . 5 3.4. Procedures . . . . . . . . . . . . . . . . . . . . . . . 5 3.4.1. UA procedures . . . . . . . . . . . . . . . . . . . . 5 - 3.4.2. Proxy procedures . . . . . . . . . . . . . . . . . . 5 + 3.4.2. Proxy procedures . . . . . . . . . . . . . . . . . . 6 4. Update to RFC 5621 . . . . . . . . . . . . . . . . . . . . . 6 5. Security considerations . . . . . . . . . . . . . . . . . . . 6 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 6 6.1. Header field . . . . . . . . . . . . . . . . . . . . . . 7 7. Change log . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Normative references . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction @@ -123,36 +123,36 @@ 1.4. Consequences The examples below shows the consequences of the problem described above. 1.4.1. Example 1 If a UAC sends an INVITE request conveying location as specified in [RFC6442], if the UAC decides not to include an SDP offer, and if the - location is conveyed by value, then the UAC needs to include one - content only in the INVITE request. This content can be e.g. of the + location is conveyed by value, then the UAC needs to include only one + MIME entity in the INVITE request. This content can be e.g. of the application/pidf+xml MIME type. However, due to [RFC6442] requiring inclusion of a Geolocation header field referencing the body part with the location information, the UAC includes a multipart message-body with single body part in the INVITE request, and includes the location information of application/ pidf+xml MIME type and an associated Content-ID header field in the body part. 1.4.2. Example 2 If a UAC sends an REFER request including a list of targets as - specified in [RFC5368], then the UAC needs to include one content - only in the REFER request. This content is of the application/ + specified in [RFC5368], then the UAC needs to include only one MIME + entity in the REFER request. This content is of the application/ resource-lists+xml MIME type. However, due to [RFC5368] requiring inclusion of a Refer-To header field referencing the body part containing the list of targets, the UAC includes a multipart message-body with single body part in the REFER request, and includes the list of targets of application/ resource-lists+xml MIME type and an associated Content-ID header field in the body part. 1.5. Solution @@ -180,27 +180,28 @@ 3. Content-ID header field 3.1. Introduction This section defines the usage of the Content-ID header field for SIP. 3.2. Syntax - The ABNF for the Content-ID header fields is: + The ABNF [RFC5234] for the Content-ID header field is: Content-ID = "Content-ID" HCOLON msg-id msg-id = "<" id-left "@" id-right ">" - NOTE: id-left and id-right are specified in [RFC5322]. + NOTE: id-left and id-right are specified in [RFC5322]. HCOLON is + defined in [RFC3261]. NOTE: When used in a SIP header field, the msg-id syntax has been simplified compared to the syntax in [RFC5322]. 3.3. Semantics The Content-ID header field included in the header fields of a SIP message identifies the message-body of the SIP message, and the metadata provided by: @@ -210,25 +211,25 @@ header field itself) included in the header fields of the SIP message. The Content-ID header field can be included in any SIP message which is allowed to contain a message-body. 3.4. Procedures 3.4.1. UA procedures - A UA MAY include a Content-ID header field in any SIP message which - is allowed to contain a message-body. + A UA MAY include a Content-ID header field in any SIP message that is + allowed to contain a message-body. A UA MUST NOT include a Content-ID header field in any SIP message - which is not allowed to contain a message-body. + that is not allowed to contain a message-body. The UA MUST set the value of the Content-ID header field to a globally unique value. 3.4.2. Proxy procedures A proxy MUST NOT add a Content-ID header field in a SIP message. A proxy MUST NOT modify a Content-ID header field included in a SIP message. @@ -266,33 +267,43 @@ encrypted body, it MUST NOT be possible to derive a key that can be used to decrypt the body from the Content-ID header field value. 6. IANA considerations This specification registers a new SIP header field according to the procedures in [RFC3261]. 6.1. Header field + The header field described in Section 3 has been registered in the + "Header Fields" sub-registry of the "Session Initiation Protocol + (SIP) Parameters" registry by adding a row with these values: + [RFC EDITOR NOTE: Please replace XXXX with the RFC number of this document when publishing] - RFC Number: RFC XXXX + Header Name: Content-ID - Header Field Name: Content-ID + compact: - Compact Form: none + Reference: RFCXXXX 7. Change log [RFC EDITOR NOTE: Please remove this section when publishing] + Changes from draft-ietf-sipcore-content-id-03 + + o Changes based on doc shepard review: + o - Reference to RFC 5234 added. + o - Editorial changes. + Changes from draft-ietf-sipcore-content-id-02 o Editorial changes based on comments from Paul Kyzivat. Changes from draft-ietf-sipcore-content-id-01 o Update to RFC 5621 added. o Editorial changes. 8. Normative references @@ -304,20 +315,25 @@ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998, . + [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax + Specifications: ABNF", STD 68, RFC 5234, + DOI 10.17487/RFC5234, January 2008, + . + [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, . [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002, .