--- 1/draft-ietf-sipcore-content-id-04.txt	2017-05-09 00:13:27.721386525 -0700
+++ 2/draft-ietf-sipcore-content-id-05.txt	2017-05-09 00:13:27.741387003 -0700
@@ -1,19 +1,19 @@
 
 SIPCORE Working Group                                        C. Holmberg
 Internet-Draft                                               I. Sedlacek
 Updates: 5621 (if approved)                                     Ericsson
-Intended status: Standards Track                             May 8, 2017
-Expires: November 9, 2017
+Intended status: Standards Track                             May 9, 2017
+Expires: November 10, 2017
 
       Content-ID header field in Session Initiation Protocol (SIP)
-                    draft-ietf-sipcore-content-id-04
+                    draft-ietf-sipcore-content-id-05
 
 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 November 9, 2017.
+   This Internet-Draft will expire on November 10, 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
@@ -124,35 +124,35 @@
 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 only one
-   MIME entity in the INVITE request.  This content can be e.g. of the
-   application/pidf+xml MIME type.
+   MIME entity in the INVITE request.  This MIME entity 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 only one MIME
-   entity in the REFER request.  This content is of the application/
+   entity in the REFER request.  This MIME entity 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
@@ -284,20 +284,24 @@
       Header Name:  Content-ID
 
       compact:
 
       Reference:  RFCXXXX
 
 7.  Change log
 
    [RFC EDITOR NOTE: Please remove this section when publishing]
 
+   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  - 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.