--- 1/draft-ietf-sipcore-content-id-09.txt	2017-09-02 12:13:13.232036314 -0700
+++ 2/draft-ietf-sipcore-content-id-10.txt	2017-09-02 12:13:13.260036988 -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                       September 1, 2017
-Expires: March 5, 2018
+Intended status: Standards Track                       September 2, 2017
+Expires: March 6, 2018
 
       Content-ID header field in Session Initiation Protocol (SIP)
-                    draft-ietf-sipcore-content-id-09
+                    draft-ietf-sipcore-content-id-10
 
 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 5, 2018.
+   This Internet-Draft will expire on March 6, 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
@@ -129,24 +129,28 @@
 
 1.3.  Problem statement
 
    It is currently not specified how to uniquely identify a complete
    message-body of a SIP message using a Content-ID header field, and
    how to reference a complete message-body using a Content-ID URL.
 
    NOTE: In [RFC5621], the Content-ID URL references a specific body
    part only.
 
-   Some existing specifications, for example [RFC5368], contain examples
+   Some existing specifications, such as [RFC5368], contain examples
    that show usage of a SIP Content-ID header field referencing a
    complete message-body, eventhough such usage has never been
-   specified.
+   specified.  Many implementors have interpreted these examples to
+   indicate that such usage is allowed by the corresponding
+   specification, despite the absence of language allowing it.  This
+   document updates the normative language in the affected documents to
+   explicitly allow such usage.
 
 1.4.  Consequences
 
    The examples below shows the consequences of the problem described
    above.
 
 1.4.1.  Example 1
 
    If a User Agent Client (UAC) sends an INVITE request conveying
    location as specified in [RFC6442], if the UAC decides not to include
@@ -510,50 +514,52 @@
       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-09
+
+   o  Editorial change based on comment from Adam Roach.
+
    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.
 
    Changes from draft-ietf-sipcore-content-id-05
 
-   o  Changes based on AD comments from Ben Campell:
+   o  Changes based on AD comments from Ben Campbell:
    o  - Clarifying that Content-ID header field value is unique within
       the scope of a SIP message.
 
    Changes from draft-ietf-sipcore-content-id-04
 
    o  Minor editorial fix.
 
    Changes from draft-ietf-sipcore-content-id-03
-
-   o  Changes based on doc shepard review:
+   o  Changes based on doc shepherd review:
    o  - Reference to RFC 5234 added.
    o  - SIP message example 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.