Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks
RFC 7206
Internet Engineering Task Force (IETF) P. Jones
Request for Comments: 7206 G. Salgueiro
Category: Informational J. Polk
ISSN: 2070-1721 Cisco Systems
L. Liess
Deutsche Telekom
H. Kaplan
Oracle
May 2014
Requirements for an End-to-End Session Identifier
in IP-Based Multimedia Communication Networks
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 document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7206.
Jones, et al. Informational [Page 1]
RFC 7206 Requirements for End-to-End Session ID May 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. Terminology .....................................................4
3.1. What Does the Session Identifier Identify? .................4
3.2. Communication Session ......................................5
3.3. End-to-End .................................................6
4. Session Identifier Use Cases ....................................6
4.1. End-to-End Identification of a Communication Session .......6
4.2. Protocol Interworking ......................................6
4.3. Traffic Monitoring .........................................7
4.4. Tracking Transferred Sessions ..............................7
4.5. Session Signal Logging .....................................8
4.6. Identifier Syntax ..........................................8
4.7. 3PCC Use Case ..............................................9
5. Requirements for the End-to-End Session Identifier ..............9
6. Related Work in Other Standards Organizations ..................10
6.1. Coordination with the ITU-T ...............................10
6.2. Requirements within 3GPP ..................................11
7. Security Considerations ........................................11
8. Acknowledgments ................................................12
9. Contributors ...................................................12
10. References ....................................................12
10.1. Normative References .....................................12
10.2. Informative References ...................................12
Jones, et al. Informational [Page 2]
RFC 7206 Requirements for End-to-End Session ID May 2014
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
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 mean that the
Show full document text