3GPP SIP URI Inter-Operator Traffic Leg Parameter
RFC 7549
| Document | Type |
RFC - Proposed Standard
(May 2015; No errata)
Was draft-holmberg-dispatch-iotl (individual)
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Gonzalo Salgueiro | ||
| Shepherd write-up | Show (last changed 2014-10-23) | ||
| IESG | IESG state | RFC 7549 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Richard Barnes | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
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
Abstract
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.
Holmberg, et al. Standards Track [Page 1]
RFC 7549 3GPP 'iotl' May 2015
Copyright Notice
Copyright (c) 2015 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.
Holmberg, et al. Standards Track [Page 2]
RFC 7549 3GPP 'iotl' May 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Traffic Leg Examples . . . . . . . . . . . . . . . . . . . . 6
4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Originating Roaming Call . . . . . . . . . . . . . . . . 6
4.3. Terminating Roaming Call . . . . . . . . . . . . . . . . 7
4.4. Call from Originating Home to Terminating Home . . . . . 7
5. 'iotl' SIP URI Parameter . . . . . . . . . . . . . . . . . . 7
5.1. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Parameter Values . . . . . . . . . . . . . . . . . . . . 8
5.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 8
5.2.2. homea-homeb . . . . . . . . . . . . . . . . . . . . . 8
5.2.3. homeb-visitedb . . . . . . . . . . . . . . . . . . . 8
5.2.4. visiteda-homea . . . . . . . . . . . . . . . . . . . 9
5.2.5. homea-visiteda . . . . . . . . . . . . . . . . . . . 9
5.2.6. visiteda-homeb . . . . . . . . . . . . . . . . . . . 9
6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.2. ABNF . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11
Show full document text