End-to-End Session Identification in IP-Based Multimedia Communication Networks
draft-ietf-insipid-session-id-05

The information below is for an old version of the document
Document Type Active Internet-Draft (insipid WG)
Authors Paul Jones  , Chris Pearce  , James Polk  , Gonzalo Salgueiro 
Last updated 2014-02-13
Replaces draft-jones-insipid-session-id
Stream IETF
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Keith Drage
Shepherd write-up Show (last changed 2013-09-10)
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD Richard Barnes
Send notices to insipid-chairs@tools.ietf.org, draft-ietf-insipid-session-id@tools.ietf.org
Network Working Group                                     P. Jones (Ed.)
Internet Draft                                                 C. Pearce
Intended status: Standards Track                           J. Polk (Ed.)
Expires: August 14, 2014                                    G. Salgueiro
                                                           Cisco Systems
                                                       February 14, 2014

         End-to-End Session Identification in IP-Based Multimedia
                          Communication Networks
                     draft-ietf-insipid-session-id-05

Abstract

   This document describes an end-to-end Session Identifier for use in
   IP-based multimedia communication systems that enables endpoints,
   intermediate devices, and management systems to identify a session
   end-to-end, associate multiple endpoints with a given multipoint
   conference, track communication sessions when they are redirected,
   and associate one or more media flows with a given communication
   session.

   This document also describes a backwards compatibility mechanism for
   an existing "in the wild" session identifier implementation that is
   sufficiently different from the procedures defined in this document.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on August 14, 2014.

Jones, et al.          Expires August 14, 2014                  [Page 1]
Internet-Draft          End-To-End Session ID              February 2014

Copyright Notice

   Copyright (c) 2014 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.

Table of Contents

   1. Introduction...................................................3
   2. Conventions used in this document..............................3
   3. Session Identifier Requirements and Use Cases..................4
   4. Constructing and Conveying the Session Identifier..............4
      4.1. Constructing the Session Identifier.......................4
      4.2. Conveying the Session Identifier..........................4
   5. Transmitting the Session Identifier in SIP.....................6
   6. Endpoint Behavior..............................................7
   7. Processing by Intermediaries...................................8
   8. Associating Endpoints in a Multipoint Conference...............9
   9. Various Call Flow Operations Utilizing the Session ID.........10
      9.1. Basic Session ID Construction with 2 UUIDs...............10
      9.2. Basic Call Transfer using REFER..........................11
      9.3. Basic Call Transfer using reINVITE.......................13
      9.4. Single Focus Conferencing................................14
      9.5. Single Focus Conferencing using WebEx....................16
      9.6. Cascading Conference Bridge Support for the Session ID...17
         9.6.1. Calling into Cascaded Conference Bridge for the Session
         ID.........................................................18
      9.7. Basic 3PCC for two UAs...................................19
      9.8. Session ID Handling in 100 Trying SIP Response and CANCEL
      Request.......................................................20
         9.8.1. Session ID Handling in a 100 Trying SIP Response....20
         9.8.2. Session ID in a CANCEL SIP Request..................21
      9.9. Session ID in an out-of-dialog REFER Transaction.........22
   10. Compatibility with a Previous Implementation.................23
   11. Security Considerations......................................24
   12. IANA Considerations..........................................25
Show full document text