datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks
draft-ietf-insipid-session-id-reqts-11

Document type: Active Internet-Draft (insipid WG)
Document stream: IETF
Last updated: 2014-02-11 (latest revision 2014-02-08)
Intended RFC status: Informational
Other versions: plain text, pdf, html

IETF State: WG Document Mar 2014
Consensus: Unknown
Document shepherd: Keith Drage
Shepherd Write-Up: Last changed 2013-07-31

IESG State: RFC Ed Queue
IANA Action State: No IC
RFC Editor State: AUTH48
Responsible AD: Richard Barnes
Send notices to: insipid-chairs@tools.ietf.org, draft-ietf-insipid-session-id-reqts@tools.ietf.org

Network Working Group                                      Paul E. Jones
Internet Draft                                         Gonzalo Salgueiro
Intended status: Informational                                James Polk
Expires: August 8, 2014                                    Cisco Systems
                                                             Laura Liess
                                                        Deutsche Telekom
                                                          Hadriel Kaplan
                                                                  Oracle
                                                        February 8, 2014

         Requirements for an End-to-End Session Identification in
                IP-Based Multimedia Communication Networks
                draft-ietf-insipid-session-id-reqts-11.txt

Abstract

   This document specifies the requirements for an end-to-end session
   identifier in IP-based multimedia communication networks.  This
   identifier would enable endpoints, intermediate devices, and
   management and monitoring systems to identify a session end-to-end
   across multiple SIP devices, hops, and administrative domains.

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 August 8, 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

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

   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. Terminology....................................................3
      3.1. What does the Session Identifier Identify?................3
      3.2. Communication Session.....................................4
      3.3. End-to-End................................................5
   4. Session Identifier Use Cases...................................5
      4.1. End-to-end identification of a communication session......5
      4.2. Protocol Interworking.....................................6
      4.3. Traffic Monitoring........................................6
      4.4. Tracking transferred sessions.............................6
      4.5. Session Signal Logging....................................7
      4.6. Identifier Syntax.........................................7
      4.7. 3PCC Use Case.............................................7
   5. Requirements for the End-to-End Session Identifier.............8
   6. Related Work in other Standards Organizations..................9
      6.1. Coordination with the ITU-T...............................9
      6.2. Requirements within 3GPP..................................9
   7. Security Considerations........................................9
   8. IANA Considerations...........................................10
   9. Acknowledgments...............................................10
   10. Contributors.................................................10
   11. References...................................................10
      11.1. Normative References....................................10
      11.2. Informative References..................................10
   Author's Addresses...............................................12

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
   identifier is intended to represent an end-to-end communication

[include full document text]