RFC 7315 Updates
draft-holmberg-dispatch-rfc7315-updates-04
The information below is for an old version of the document.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Christer Holmberg , Nevenka Biondic , Gonzalo Salgueiro | ||
| Last updated | 2016-02-04 (Latest revision 2016-01-07) | ||
| Stream | (None) | ||
| Formats | plain text xml htmlized pdfized bibtex | ||
| Reviews |
SECDIR Last Call review
(of
-07)
Has Nits
GENART Last Call review
(of
-07)
Ready with Nits
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Jean Mahoney" <mahoney@nostrum.com> |
draft-holmberg-dispatch-rfc7315-updates-04
Network Working Group C. Holmberg
Internet-Draft N. Biondic
Updates: 7315 (if approved) Ericsson
Intended status: Informational G. Salgueiro
Expires: July 10, 2016 Cisco
January 7, 2016
RFC 7315 Updates
draft-holmberg-dispatch-rfc7315-updates-04
Abstract
The 3rd-Generation Partnership Project 3GPP has identified cases
where different SIP private header extensions referred to as P-
header fields, defined in RFC 7315, need to be included in SIP
requests and responses currently not allowed according to RFC 7315.
This document updates RFC 7315, in order to allow inclusion of the
affected P- header fields in such requests and responses.
In order to get a complete picture, this document also contains a set
of errata that are to be filed against RFC 7315, in order to fix
misalignments that occurred when RFC 3455 was updated and obsoleted
by RFC 7315.
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 July 10, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
Holmberg, et al. Expires July 10, 2016 [Page 1]
Internet-Draft 7315 Updates January 2016
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Errata to RFC 7315 . . . . . . . . . . . . . . . . . . . . . 3
3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Correction to section 5.7 of RFC 7315 . . . . . . . . . . 3
4. Update to RFC 7315 . . . . . . . . . . . . . . . . . . . . . 4
4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. 3GPP Use-cases . . . . . . . . . . . . . . . . . . . . . 5
4.2.1. P-Access-Network-Info . . . . . . . . . . . . . . . . 5
4.2.2. P-Charging-Vector . . . . . . . . . . . . . . . . . . 6
4.3. Updates to section 5.7 of RFC 7315 . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
The 3rd-Generation Partnership Project (3GPP) has identified cases
where different Session Initiation Protocol (SIP) [RFC3261] private
header extensions referred to as P- header fields, defined in RFC
7315 [RFC7315], need to be included in SIP requests and responses
currently not allowed according to RFC 7315. This document updates
RFC 7315, in order to allow inclusion of the affected P- header
fields in such requests and responses.
In order to get a complete picture, this document also contains a set
of errata that are to be filed against RFC 7315, in order to fix
misalignments that occurred when RFC 3455 [RFC3455] was updated and
obsoleted by RFC 7315.
Holmberg, et al. Expires July 10, 2016 [Page 2]
Internet-Draft 7315 Updates January 2016
This document updates RFC 7315 [RFC7315], by allowing the insertion
of the P-Access-Network-Info header field in SIP ACK requests.
As the P- header fields are mainly used in (and in most cases, only
defined for) networks defined by the 3rd-Generation Partnership
Project (3GPP), where the updates defined in this document are
already defined [TS.3GPP.24.229], the updates are not seen to cause
backward compatibility concerns.
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Errata to RFC 7315
3.1. General
RFC 7315 contains contradicting statements regarding the usage of SIP
P- header fields in SIP requests and responses, which leave the
presence of the SIP P- header fields in the SIP requests and
responses open to interpretation, and different implementations.
Statements in section 5.7 are not aligned with the definitions and
usage of the SIP P- header fields specified in section 4.
This section defines the errata that is to be submitted against RFC
7315. The scope of the errata is only alignment between RFC 3455 and
RFC 7315.
NOTE: In the case of the P-Called-Party-ID header field, allowing it
in PUBLISH requests was deliberately done in RFC 7315. It will
therefore not be impacted by the errata.
3.2. Correction to section 5.7 of RFC 7315
The errata makes the following changes:
o P-Associated-URI: Remove statement that the header field can
appear in the SIP REGISTER method.
o P-Called-Party-ID: Delete statement that the header field can
appear in SIP responses. Add statement that the P-Called-Party-ID
header field can appear in the SIP REFER method.
o P-Visited-Network-ID: Delete statement that the header field can
appear in SIP responses. Add statement that the P-Visited-
Holmberg, et al. Expires July 10, 2016 [Page 3]
Internet-Draft 7315 Updates January 2016
Network-ID header field cannot appear in the SIP NOTIFY, PRACK,
INFO and UPDATE methods.
o P-Access-Network-Info: Add statement that header field can appear
in SIP responses.
o P-Charging-Vector: Add statement that the header field can appear
in SIP responses. Add statement that the header field can not
appear in the SIP ACK method.
o P-Charging-Function-Addresses: Add statement that the P-Charging-
Function-Addresses header field can appear in SIP responses.
Old text:
The P-Associated-URI header field can appear in SIP REGISTER method
and 2xx resonses. The P-Called-Party-ID header field can appear in
SIP INVITE, OPTIONS, PUBLISH, SUBSCRIBE, and MESSAGE methods and all
responses. The P-Visited-Network-ID header field can appear in all
SIP methods except ACK, BYE, and CANCEL and all responses. The
P-Access-Network-Info header field can appear in all SIP methods
except ACK and CANCEL. The P-Charging-Vector header field can appear
in all SIP methods except CANCEL. The P-Charging-Function-Addresses
header field can appear in all SIP methods except ACK and CANCEL.
New text:
The P-Associated-URI header field can appear in SIP REGISTER
2xx responses. The P-Called-Party-ID header field can appear in
SIP INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods.
The P-Visited-Network-ID header field can appear in all SIP methods
except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO and UPDATE. The
P-Access-Network-Info header field can appear in all SIP methods
and responses, except in ACK and CANCEL methods and CANCEL responses.
The P-Charging-Vector header field can appear in all SIP methods and
responses, except in ACK and CANCEL methods and CANCEL responses.
The P-Charging-Function-Addresses header field can appear in all
SIP methods and responses, except in ACK and CANCEL methods and
CANCEL responses.
4. Update to RFC 7315
Holmberg, et al. Expires July 10, 2016 [Page 4]
Internet-Draft 7315 Updates January 2016
4.1. General
This section updates section 5.7 of RFC 7315, based on requirements
from 3GPP. This section contains the 3GPP use-cases behind the
updates, and the suggested changes.
4.2. 3GPP Use-cases
4.2.1. P-Access-Network-Info
The P-Access-Network-Info header field may contain the Network
provided Location information (NPLI). The Network Provided Location
Information (NPLI) is described in 3GPP TS 23.228.
A proxy in possession of appropriate information about the access
technology might insert a P-Access-Network-Info header field with its
own values. Such values are identified by the string "network-
provided" defined in RFC 7315. Based on operator policy and/or
roaming agreement, local time of visited network may be included.
The CDRs generated within IMS have to contain the NPLI in order to
guarantee correct billing. When an IMS Session is modified the NPLI
also needs to be stored as the location of the user at the time when
the session is modified may generate a charging event. In case of a
session modification event at IMS, the NPLI needs to be provided:
o when the bearer establishment is triggered, or
o at session release when the bearer deactivation is triggered, or
o when the bearer modification is triggered e.g. QoS modification
for the use of newly negotiated codec.
In some scenarios, the bearer modification may be triggered by the
proxy upon reception of an SDP answer within SIP 2xx response to the
SIP INVITE request. In such case the NPLI needs to be provided
within the SIP ACK request. However, RFC 7315 does not allow the
usage of the P-Access-Network-Info header field in SIP ACK request.
Upon reception of the SDP answer within SIP 2xx response on the SIP
INVITE request a proxy may initiate procedures to obtain the NPLI and
MAY include the P-Access-Network-Info header field with the NPLI in
the SIP ACK request.
The P-Access-Network-Info header field shall not be included in SIP
ACK requests triggered by a 3xx-6xx response.
Holmberg, et al. Expires July 10, 2016 [Page 5]
Internet-Draft 7315 Updates January 2016
4.2.2. P-Charging-Vector
RFC 7315 defines an Inter Operator Identifier (IOI) to enable
different operators involved in a SIP dialog or a transaction outside
a dialog to identify each other by exchanging operator identification
information within the P-Charging-Vector header field.
In the interconnection scenarios in multi operator environments,
where one or more transit operators are between the originating and
terminating operator, the identities of the involved transit
operators are represented by a transit-ioi parameter of the P-
Charging-Vector header field.
Transit operators can be selected independently for each SIP method
and direction of request. A transit network will only have knowledge
of an individual SIP request and transit network selection will be an
independent decision for each request and could be made based on
load, cost, percentage, time of day, and more. For this reason, it
is necessary that the P-Charging-Vector header field, which carries
the transit IOI information, is included in each SIP request and
response. However, RFC 7315 does not allow the usage of the
P-Charging- Vector header field in SIP ACK request.
A SIP proxy that supports this extension and receives the SIP ACK
request MAY include a P-Charging-Vector header field in the SIP ACK
request.
The P-Charging-Vector header field shall not be included in SIP ACK
requests triggered by a 3xx-6xx response.
4.3. Updates to section 5.7 of RFC 7315
Note that the old text incorporates the fixes done by the errata
described above.
The following updates are done:
o P-Access-Network-Info: Add statement that the header field can
appear in the SIP ACK method.
o P-Charging-Vector: Add statement that the header field can appear
in the SIP ACK method.
Holmberg, et al. Expires July 10, 2016 [Page 6]
Internet-Draft 7315 Updates January 2016
Old text:
The P-Associated-URI header field can appear in SIP REGISTER
2xx responses. The P-Called-Party-ID header field can appear in
SIP INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods.
The P-Visited-Network-ID header field can appear in all SIP methods
except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO and UPDATE. The
P-Access-Network-Info header field can appear in all SIP methods
and responses, except in ACK and CANCEL methods and CANCEL responses.
The P-Charging-Vector header field can appear in all SIP methods and
responses, except in ACK and CANCEL methods and CANCEL responses.
The P-Charging-Function-Addresses header field can appear in all
SIP methods and responses, except in ACK and CANCEL methods and
CANCEL responses.
New text:
The P-Associated-URI header field can appear in SIP REGISTER
2xx responses. The P-Called-Party-ID header field can appear in
SIP INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods.
The P-Visited-Network-ID header field can appear in all SIP methods
except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO and UPDATE. The
P-Access-Network-Info header field can appear in all SIP methods
and responses, except in CANCEL methods and CANCEL responses.
The P-Charging-Vector header field can appear in all SIP methods and
responses, except in CANCEL methods and CANCEL responses. The
P-Charging-Function-Addresses header field can appear in all
SIP methods and responses, except in ACK and CANCEL methods
and CANCEL responses.
5. Security Considerations
The security considerations for the P-Access-Network-Info header
field are defined in [RFC7315]. The update defined in this document
does not impact the security considerations.
6. IANA Considerations
This document makes no requests from IANA.
7. Acknowledgments
TBD
Holmberg, et al. Expires July 10, 2016 [Page 7]
Internet-Draft 7315 Updates January 2016
8. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-holmberg-dispatch-rfc7315-updates-03
o - Minor editorial corrections.
Changes from draft-holmberg-dispatch-rfc7315-updates-02
o - Justification text for P-Charging-Vector update added.
Changes from draft-holmberg-dispatch-rfc7315-updates-01
o - Justification text for P-Access-Network-Info update added.
Changes from draft-holmberg-dispatch-rfc7315-updates-00
o - Title corrected.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>.
[RFC7315] Jesske, R., Drage, K., and C. Holmberg, "Private Header
(P-Header) Extensions to the Session Initiation Protocol
(SIP) for the 3GPP", RFC 7315, DOI 10.17487/RFC7315, July
2014, <http://www.rfc-editor.org/info/rfc7315>.
[TS.3GPP.24.229]
3GPP, "IP multimedia call control protocol based on
Session Initiation Protocol (SIP) and Session Description
Protocol (SDP);Stage 3", 3GPP TS 24.229 13.3.1, September
2015.
Holmberg, et al. Expires July 10, 2016 [Page 8]
Internet-Draft 7315 Updates January 2016
9.2. Informative References
[RFC3455] Garcia-Martin, M., Henrikson, E., and D. Mills, "Private
Header (P-Header) Extensions to the Session Initiation
Protocol (SIP) for the 3rd-Generation Partnership Project
(3GPP)", RFC 3455, DOI 10.17487/RFC3455, January 2003,
<http://www.rfc-editor.org/info/rfc3455>.
Authors' Addresses
Christer Holmberg
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
Email: christer.holmberg@ericsson.com
Nevenka Biondic
Ericsson
Krapinska 45
Zagreb 10002
Croatia
Email: nevenka.biondic@ericsson.com
Gonzalo Salgueiro
Cisco Systems, Inc.
7200-12 Kit Creek Road
Research Triangle Park, NC 27709
US
Email: gsalguei@cisco.com
Holmberg, et al. Expires July 10, 2016 [Page 9]