3GPP SIP URI Inter-Operator Traffic Leg Parameter (RFC7549)
Original Publication Date: 2015-May-01
Included in the Prior Art Database: 2015-May-20
Internet Society Requests For Comment (RFCs)
C. Holmberg: AUTHOR [+4]
In a 3GPP network, an end-user device can be attached (e.g., using a radio access network) to its own operator network (home network) [TS.3GPP.24.229] or to another operator's network (visited network) [TS.3GPP.24.229]. In the latter case, the user is referred to as a roaming user.
Internet Engineering Task Force (IETF) C. Holmberg Request for Comments: 7549 J. Holm Category: Standards Track Ericsson ISSN: 2070-1721 R. Jesske Deutsche Telekom M. Dolly AT&T May 2015
3GPP SIP URI Inter-Operator Traffic Leg Parameter
In 3GPP networks, the signaling path between a calling user and a called user can be partitioned into segments, referred to as traffic legs. Each traffic leg may span networks belonging to different operators and will have its own characteristics that can be different from other traffic legs in the same call. A traffic leg might be associated with multiple SIP dialogs, e.g., in case a Back-to-Back User Agent (B2BUA) that modifies the SIP dialog identifier is located within the traffic leg.
This document defines a new SIP URI parameter, 'iotl' (an abbreviation for Inter-Operator Traffic Leg). The parameter can be used in a SIP URI to indicate that the entity associated with the address, or an entity responsible for the host part of the address, represents the end of a specific traffic leg (or multiple traffic legs).
The SIP URI 'iotl' parameter defined in this document has known uses in 3GPP networks. Usage in other networks is also possible.
Status of This Memo
This is an Internet Standards Track document.
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). Further information on Internet Standards is available in 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/rfc7549.
al. Standards Track [Page 1]
RFC 7549 3GPP 'iotl' May 2015
Copyright (c) 2015 IET...