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

Document Type Active Internet-Draft (sipcore WG)
Last updated 2017-03-23 (latest revision 2017-03-08)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
On Agenda sipcore at IETF-98
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
SIPCORE Working Group                                        C. Holmberg
Internet-Draft                                               I. Sedlacek
Intended status: Standards Track                                Ericsson
Expires: September 9, 2017                                 March 8, 2017

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

Abstract

   This document specifies the Content-ID header field for usage in the
   Session Initiation Protocol (SIP).

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

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Setting up ID value uniquely identifying body . . . . . .   2
     1.2.  Referencing the ID value uniquely identifying body  . . .   3
     1.3.  Problem statement . . . . . . . . . . . . . . . . . . . .   3
     1.4.  Examples of the problem . . . . . . . . . . . . . . . . .   3
       1.4.1.  Example 1 . . . . . . . . . . . . . . . . . . . . . .   3
       1.4.2.  Example 2 . . . . . . . . . . . . . . . . . . . . . .   4
     1.5.  Solution  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Content-ID header field . . . . . . . . . . . . . . . . . . .   5
     3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Semantic  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   6
       3.4.1.  UA procedures . . . . . . . . . . . . . . . . . . . .   6
       3.4.2.  Proxy procedures  . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Header Field  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

1.1.  Setting up ID value uniquely identifying body

   A SIP message consists of a start-line, one or more header fields, an
   empty line indicating the end of the header fields, and an optional
   message-body, as specified in [RFC3261].

   A message-body of the SIP message can contain one body only or can
   contain several body parts, as specified in [RFC3261] and [RFC5621].

   A body part encoded using [RFC2045] can contain a Content-ID header
   field with an ID value uniquely identifying the body part, as
   specified in [RFC2045].

   However, when the message-body of the SIP message contains one body
   only, there is no body part specified.  Thus, there is also no
   defined method how to convey an ID value uniquely identifying the
   body part.

Holmberg & Sedlacek     Expires September 9, 2017               [Page 2]
Internet-Draft              Content-ID-in-SIP                 March 2017

1.2.  Referencing the ID value uniquely identifying body
Show full document text