draft-ietf-sipcore-reason-q850-loc-00.txt   draft-ietf-sipcore-reason-q850-loc-01.txt 
Sipcore R. Jesske Sipcore R. Jesske
Internet-Draft Deutsche Telekom Internet-Draft Deutsche Telekom
Updates: RFC6442 (if approved) May 16, 2017 Updates: RFC6442 (if approved) September 29, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: November 17, 2017 Expires: April 2, 2018
ISUP Cause Location Parameter for the SIP Reason Header Field ISUP Cause Location Parameter for the SIP Reason Header Field
draft-ietf-sipcore-reason-q850-loc-00.txt draft-ietf-sipcore-reason-q850-loc-01
Abstract Abstract
The SIP Reason header field is defined for carrying ISUP cause values The SIP Reason header field is defined for carrying ISUP cause values
as well as SIP response codes. Some services in SIP networks may as well as SIP response codes. Some services in SIP networks may
need to know the ISUP location where the call was released in the need to know the ISUP location where the call was released in the
PSTN network to correctly interpret the reason of release. PSTN network to correctly interpret the reason of release.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 17, 2017. This Internet-Draft will expire on April 2, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8.1. Registration of isup-cause-location Parameter for reason 8.1. Registration of isup-cause-location Parameter for reason
header field . . . . . . . . . . . . . . . . . . . . . . 4 header field . . . . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
10.1. Normative References . . . . . . . . . . . . . . . . . . 5 10.1. Normative References . . . . . . . . . . . . . . . . . . 5
10.2. Informative References . . . . . . . . . . . . . . . . . 5 10.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The SIP Reason header field specification [RFC3326] describes a SIP The SIP Reason header field specification [RFC3326] describes a SIP
header field that is used to indicate that a SIP request is carrying header field that is used to indicate that a SIP request is carrying
the reason of release. It may be an SIP response or ISUP release the reason of release. It may be an SIP response or ISUP release
cause as specified within [Q.850]. [RFC3326] does specify that a cause as specified within [Q.850]. [RFC3326] does specify that a
ISUP [Q.850] cause code can be carried within a SIP response. The ISUP [Q.850] cause code can be carried within a SIP response. The
[Q.850] location information identifies the part of the ISUP network [Q.850] location information identifies the part of the ISUP network
where the call was released. where the call was released.
skipping to change at page 3, line 15 skipping to change at page 3, line 15
4. Mechanism 4. Mechanism
As defined by [RFC3326] a Reason header field MAY appear in any As defined by [RFC3326] a Reason header field MAY appear in any
request in a dialog, in any CANCEL request and in any response whose request in a dialog, in any CANCEL request and in any response whose
status code explicitly allows the presence of this header field. The status code explicitly allows the presence of this header field. The
syntax of the header field follows the standard SIP parameter syntax. syntax of the header field follows the standard SIP parameter syntax.
The mechanism employed adds a parameter with the ISUP location value The mechanism employed adds a parameter with the ISUP location value
defined in [Q.850] to the Reason header field that identifies the defined in [Q.850] to the Reason header field that identifies the
[Q.850] location of the call release in ISUP as defined in [Q.850] . [Q.850] location of the call release in ISUP as defined in [Q.850] .
The Augmented BNF (ABNF) [RFC5234] for this parameter is shown in The location is a 4 bit value which reflects the possible locations
Figure 1. where an ISUP call is released. Some values are spare or reserved
for national use. The Augmented BNF (ABNF) [RFC5234] for this
parameter is shown in Figure 1.
reason-extension =/ isup-cause-location reason-extension =/ isup-cause-location
isup-cause-location = "location" EQUAL string isup-cause-location = "location" EQUAL string
The following values shall be used as location: The following values shall be used as location:
U for user U for 0 0 0 0 user
LPN for private network serving the local user LPN for 0 0 0 1 private network serving the local user
LN for public network serving the local user LN for 0 0 1 0 public network serving the local user
TN for transit network TN for 0 0 1 1 transit network
RLN for public network serving the remote user RLN for 0 1 0 0 public network serving the remote user
RPN for private network serving the remote user RPN for 0 1 0 1 private network serving the remote user
INTL for international network LOC-6 for 0 1 1 0 spare
BI for network beyond interworking point INTL for 0 1 1 1 international network
LOC-8 for 1 0 0 0 spare
LOC-9 for 1 0 0 1 spare
BI for 1 0 1 0 network beyond interworking point
LOC-11 for 1 0 1 1 spare
LOC-12 for 1 1 0 0 reserved for national use
LOC-13 for 1 1 0 1 reserved for national use
LOC-14 for 1 1 1 0 reserved for national use
LOC-15 for 1 1 1 1 reserved for national use
Figure 1: isup-cause-location Figure 1: isup-cause-location
Note: These are the values defined within [Q.850] as location. Thus Note: These are the values defined within [Q.850] as location. Thus
other values are not within the scope of this document. other values are not within the scope of this document.
Depending on the direction the UAC or UAS shall include the isup- Depending on the direction the UAC or UAS shall include the isup-
cause-location when setting up the Reason header field with a [Q.850] cause-location when setting up the Reason header field with a [Q.850]
cause. This approach is only valid in cases when the ISUP [Q.850] cause. This approach is only valid in cases when the ISUP [Q.850]
location is available. location is available.
skipping to change at page 5, line 7 skipping to change at page 5, line 20
This document calls for IANA to register a new SIP header parameter This document calls for IANA to register a new SIP header parameter
as per the guidelines in [RFC3261], which will be added to header as per the guidelines in [RFC3261], which will be added to header
sub-registry under http://www.iana.org/assignments/sip-parameters. sub-registry under http://www.iana.org/assignments/sip-parameters.
Header Field: Reason Header Field: Reason
Parameter Name: isup-cause-location Parameter Name: isup-cause-location
9. Acknowledgments 9. Acknowledgments
Thanks to Michael Kreipl, Thoams Belling, Marianne Mohali, Peter Thanks to Michael Kreipl, Thomas Belling, Marianne Mohali, Peter
Daws, Paul Kyzivat for the comments and review. Dawes, Paul Kyzivat and Dale Worley for the comments and review.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason [RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason
Header Field for the Session Initiation Protocol (SIP)", Header Field for the Session Initiation Protocol (SIP)",
RFC 3326, DOI 10.17487/RFC3326, December 2002, RFC 3326, DOI 10.17487/RFC3326, December 2002,
<http://www.rfc-editor.org/info/rfc3326>. <https://www.rfc-editor.org/info/rfc3326>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
10.2. Informative References 10.2. Informative References
[Q.850] INTERNATIONAL TELECOMMUNICATION UNION, "Usage of cause and [Q.850] INTERNATIONAL TELECOMMUNICATION UNION, "Usage of cause and
location in the Digital Subscriber Signalling System No. 1 location in the Digital Subscriber Signalling System No. 1
and the Signalling System No. 7 ISDN User Part", Q 850, and the Signalling System No. 7 ISDN User Part", Q 850,
May 1998. May 1998.
Author's Address Author's Address
Roland Jesske Roland Jesske
Deutsche Telekom Deutsche Telekom
Heinrich-Hertz Str, 3-7 Heinrich-Hertz Str. 3-7
Darmstadt 64295 Darmstadt 64295
Germany Germany
Email: r.jesske@telekom.de Email: r.jesske@telekom.de
URI: www.telekom.de URI: www.telekom.de
 End of changes. 18 change blocks. 
27 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/