Network Working Group Paul E. Jones
Internet Draft Gonzalo Salgueiro
Intended status: Informational James Polk
Expires: August 25, 2013 Cisco Systems
Laura Liess
Deutsche Telekom
Hadriel Kaplan
Acme Packet
February 25, 2013
Requirements for an End-to-End Session Identification in
IP-Based Multimedia Communication Networks
draft-ietf-insipid-session-id-reqts-05.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 25, 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
Jones, et al. Expires August 25, 2013 [Page 1]
Internet-Draft Requirements for End-To-End Session ID February 2013
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. Terminology....................................................3
4. Session Identifier Use Cases...................................5
4.1. End-to-end identification of a communication session......5
4.2. Protocol Interworking.....................................5
4.3. Traffic Monitoring........................................5
4.4. Tracking transferred sessions.............................6
4.5. Session Signal Logging....................................6
4.6. Identifier Syntax.........................................6
4.7. 3PCC Use Case.............................................6
5. Requirements for the End-to-End Session Identifier.............7
6. Related Work in other Standards Organizations..................8
6.1. Coordination with the ITU-T...............................8
6.2. Requirements within 3GPP..................................8
7. Security Considerations........................................9
8. IANA Considerations............................................9
9. Acknowledgments................................................9
10. Contributors..................................................9
11. References....................................................9
11.1. Normative References.....................................9
11.2. Informative References..................................10
Author's Addresses...............................................11
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 represents an end-to-end communication
session from the originating device to the terminating device. Such
an identifier is useful for troubleshooting, session tracking, and so
forth.
Unfortunately, there are a number of factors that contribute to the
datatracker.ietf.org