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

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 2013-03-12
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           P. Jones
Internet Draft                                                 C. Pearce
Intended status: Standards Track                                 J. Polk
Expires: September 12, 2013                                 G. Salgueiro
                                                           Cisco Systems
                                                          March 12, 2013

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

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.

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 September 12, 2013.

Jones, et al.         Expires September 12, 2013                [Page 1]
Internet-Draft          End-To-End Session ID                 March 2013

Copyright Notice

   Copyright (c) 2013 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...................................................2
   2. Conventions used in this document..............................3
   3. Session Identifier Requirements and Use Cases..................3
   4. Constructing the Session Identifier............................4
   5. Transmitting the Session Identifier in SIP.....................5
   6. Endpoint Behavior..............................................5
   7. Processing by Intermediaries...................................6
   8. Associating Endpoints in a Multipoint Conference...............7
   9. Various Call Flow Operations Utilizing the Session ID..........7
      9.1. Basic Session-ID Construction with 2 UUIDs................8
      9.2. Basic Call Transfer using REFER...........................9
      9.3. Basic Call Transfer using reINVITE.......................10
      9.4. Single Focus Conferencing................................11
      9.5. Single Focus Conferencing using WebEx....................13
      9.6. Cascading Conference Bridge Support for the Session-ID...14
      9.7. Basic 3PCC for two UAs...................................15
   10. Compatibility with a Previous Implementation.................16
   11. Security Considerations......................................17
   12. IANA Considerations..........................................18
      12.1. Registration of the "Session-ID" Header Field...........18
      12.2. Registration of the "remote" Parameter..................18
   13. Acknowledgments..............................................18
   14. References...................................................18
      14.1. Normative References....................................18
      14.2. Informative References..................................19
   Author's Addresses...............................................20

1. Introduction

   IP-based multimedia communication systems like SIP [1] and H.323 [2]
   have the concept of a "call identifier" that is globally unique.  The

Jones, et al.         Expires September 12, 2013               [Page 2]
Internet-Draft          End-To-End Session ID                 March 2013

   identifier is intended to represent an end-to-end communication
Show full document text