--- 1/draft-ietf-sipcore-content-id-08.txt 2017-09-01 03:13:09.981831535 -0700 +++ 2/draft-ietf-sipcore-content-id-09.txt 2017-09-01 03:13:10.009832207 -0700 @@ -1,19 +1,19 @@ SIPCORE Working Group C. Holmberg Internet-Draft I. Sedlacek Updates: 5621, 5368, 6442 (if approved) Ericsson -Intended status: Standards Track August 31, 2017 -Expires: March 4, 2018 +Intended status: Standards Track September 1, 2017 +Expires: March 5, 2018 Content-ID header field in Session Initiation Protocol (SIP) - draft-ietf-sipcore-content-id-08 + draft-ietf-sipcore-content-id-09 Abstract This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). The document also updates RFC 5621, which only allows a Content-ID URL to reference a body part that is part of a multipart message-body. This update enables a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. @@ -28,21 +28,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 March 4, 2018. + This Internet-Draft will expire on March 5, 2018. 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 @@ -278,25 +278,25 @@ and o Updates [RFC5621], to enable a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. o Updates [RFC5368] and [RFC6442] by adding explicit text saying that a SIP Content-ID header field can be used. 1.6. Backward compatibility - If an existing specification explicitly defines the usage of a - multipart message-body for carrying a single body part, that - specification MUST be updated in order to allow usage of a non- - multipart message-body for carrying the MIME entity, and for - referencing the whole message-body using a Content-ID URL. + If an existing specification only defines the usage of a multipart + message-body for carrying a single body part to be referenced by a + Content-ID URL, implementations MUST NOT carry the MIME entity in a + non-multipart message-body unless the specification is updated to + explicitly allow it. 2. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Content-ID header field 3.1. Introduction @@ -510,20 +510,24 @@ Header Name: Content-ID compact: Reference: RFCXXXX 9. Change log [RFC EDITOR NOTE: Please remove this section when publishing] + Changes from draft-ietf-sipcore-content-id-08 + + o Editorial change based on comment from Ben Campbell. + Changes from draft-ietf-sipcore-content-id-07 o Updates to affected RFCs. o Editorial changes and clarifications based on IESG review. Changes from draft-ietf-sipcore-content-id-06 o Editorial changes and clarifications based on Gen-ART review from Elwyn Davies.