Content-ID header field in Session Initiation Protocol (SIP)
draft-ietf-sipcore-content-id-10

Document Type Active Internet-Draft (sipcore WG)
Last updated 2017-09-08 (latest revision 2017-09-02)
Replaces draft-holmberg-sipcore-content-id
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: May 2017 - Request publication ... )
Document shepherd Jean Mahoney
Shepherd write-up Show (last changed 2017-05-10)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to Jean Mahoney <mahoney@nostrum.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
SIPCORE Working Group                                        C. Holmberg
Internet-Draft                                               I. Sedlacek
Updates: 5621, 5368, 6442 (if approved)                         Ericsson
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-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.

   This document updates RFC 5368 and RFC 6442, by clarifying their
   usage of the SIP Content-ID header field.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

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

Holmberg & Sedlacek       Expires March 6, 2018                 [Page 1]
Internet-Draft              Content-ID in SIP             September 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Identifying a body part . . . . . . . . . . . . . . . . .   2
     1.2.  Referencing a body part . . . . . . . . . . . . . . . . .   3
     1.3.  Problem statement . . . . . . . . . . . . . . . . . . . .   3
     1.4.  Consequences  . . . . . . . . . . . . . . . . . . . . . .   4
       1.4.1.  Example 1 . . . . . . . . . . . . . . . . . . . . . .   4
       1.4.2.  Example 2 . . . . . . . . . . . . . . . . . . . . . .   5
     1.5.  Solution  . . . . . . . . . . . . . . . . . . . . . . . .   6
     1.6.  Backward compatibility  . . . . . . . . . . . . . . . . .   7
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Content-ID header field . . . . . . . . . . . . . . . . . . .   7
     3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Semantics . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   8
       3.4.1.  User Agent (UA) procedures  . . . . . . . . . . . . .   8
       3.4.2.  Proxy procedures  . . . . . . . . . . . . . . . . . .   9
       3.4.3.  Example . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Update to RFC 5368  . . . . . . . . . . . . . . . . . . . . .  10
   5.  Update to RFC 5621  . . . . . . . . . . . . . . . . . . . . .  10
   6.  Update to RFC 6442  . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security considerations . . . . . . . . . . . . . . . . . . .  12
   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Header field  . . . . . . . . . . . . . . . . . . . . . .  13
   9.  Change log  . . . . . . . . . . . . . . . . . . . . . . . . .  13
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     10.1.  Normative references . . . . . . . . . . . . . . . . . .  14
     10.2.  Informative references . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

1.1.  Identifying a body part

   A SIP message consists of a start-line, one or more header fields, an
Show full document text