RFC 7315 Updates
draft-holmberg-dispatch-rfc7315-updates-01
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 | 2015-12-08 | ||
| 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 | (None) |
draft-holmberg-dispatch-rfc7315-updates-01
Network Working Group C. Holmberg
Internet-Draft N. Biondic
Updates: 7315 (if approved) Ericsson
Intended status: Informational G. Salgueiro
Expires: June 10, 2016 Cisco
December 8, 2015
RFC 7315 Updates
draft-holmberg-dispatch-rfc7315-updates-01
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 June 10, 2016.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
Holmberg, et al. Expires June 10, 2016 [Page 1]
Internet-Draft 7315 Updates December 2015
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
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
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.
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
Holmberg, et al. Expires June 10, 2016 [Page 2]
Internet-Draft 7315 Updates December 2015
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-
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.
Holmberg, et al. Expires June 10, 2016 [Page 3]
Internet-Draft 7315 Updates December 2015
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:
5.7. New Headers
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:
5.7. New Headers
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
This section updates section 5.7 of RFC 7315.
Note that the old text incorporates the fixes done by the errata
described above.
Holmberg, et al. Expires June 10, 2016 [Page 4]
Internet-Draft 7315 Updates December 2015
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.
Old text:
5.7. New Headers
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:
5.7. New Headers
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.
Holmberg, et al. Expires June 10, 2016 [Page 5]
Internet-Draft 7315 Updates December 2015
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
8. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing]
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 June 10, 2016 [Page 6]
Internet-Draft 7315 Updates December 2015
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 June 10, 2016 [Page 7]