draft-ietf-sipcore-reason-q850-loc-01.txt   draft-ietf-sipcore-reason-q850-loc-02.txt 
Sipcore R. Jesske Sipcore R. Jesske
Internet-Draft Deutsche Telekom Internet-Draft Deutsche Telekom
Updates: RFC6442 (if approved) September 29, 2017 Updates: RFC3326 (if approved) January 19, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: April 2, 2018 Expires: July 23, 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-01 draft-ietf-sipcore-reason-q850-loc-02.txt
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 https://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 April 2, 2018. This Internet-Draft will expire on July 23, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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
skipping to change at page 2, line 20 skipping to change at page 2, line 20
4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 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
skipping to change at page 3, line 39 skipping to change at page 3, line 39
RPN for 0 1 0 1 private network serving the remote user RPN for 0 1 0 1 private network serving the remote user
LOC-6 for 0 1 1 0 spare LOC-6 for 0 1 1 0 spare
INTL for 0 1 1 1 international network INTL for 0 1 1 1 international network
LOC-8 for 1 0 0 0 spare LOC-8 for 1 0 0 0 spare
LOC-9 for 1 0 0 1 spare LOC-9 for 1 0 0 1 spare
BI for 1 0 1 0 network beyond interworking point BI for 1 0 1 0 network beyond interworking point
LOC-11 for 1 0 1 1 spare LOC-11 for 1 0 1 1 spare
LOC-12 for 1 1 0 0 reserved for national use LOC-12 for 1 1 0 0 reserved for national use
LOC-13 for 1 1 0 1 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-14 for 1 1 1 0 reserved for national use
LOC-15 for 1 1 1 1 reserved for national use LOC-15 for 1 1 1 0 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.
The use of the location header is restricted to Q850 cause values in
other cases the location, if present, MUST be silently discarted.
5. Example 5. Example
The following example shows a SIP 404 response message containing a The following example shows a SIP 404 response message containing a
Reason header field with a [Q.850] cause value and a isup-cause- Reason header field with a [Q.850] cause value and a isup-cause-
location value. The 404 Response will be set up when a gateway location value. The 404 Response will be set up when a gateway
receives an ISUP Release with a [Q.850] cause set to 1 meaning receives an ISUP Release with a [Q.850] cause set to 1 meaning
"Unallocated (unassigned) number", i.e. the number is not known in "Unallocated (unassigned) number", i.e. the number is not known in
the PSTN. the PSTN.
404 Not Found 404 Not Found
skipping to change at page 5, line 11 skipping to change at page 5, line 11
imprecise the [Q.850] location value itself will not add any major imprecise the [Q.850] location value itself will not add any major
security constrain. The use of this parameter is not restricted to a security constrain. The use of this parameter is not restricted to a
specific architecture. specific architecture.
8. IANA Considerations 8. IANA Considerations
8.1. Registration of isup-cause-location Parameter for reason header 8.1. Registration of isup-cause-location Parameter for reason header
field field
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 [RFC3968], which will be added to Header
sub-registry under http://www.iana.org/assignments/sip-parameters. Field Parameters sub-registry under http://www.iana.org/assignments/
sip-parameters.
Header Field: Reason Header Field: Reason
Parameter Name: isup-cause-location Parameter Name: location
9. Acknowledgments 9. Acknowledgments
Thanks to Michael Kreipl, Thomas Belling, Marianne Mohali, Peter Thanks to Michael Kreipl, Thoams Belling, Marianne Mohali, Peter
Dawes, Paul Kyzivat and Dale Worley for the comments and review. Daws, Paul Kyzivat, Dale Worley, Yehoshua Gev, Keith Drage 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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 5, line 43 skipping to change at page 5, line 45
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,
<https://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,
<https://www.rfc-editor.org/info/rfc3326>. <https://www.rfc-editor.org/info/rfc3326>.
[RFC3968] Camarillo, G., "The Internet Assigned Number Authority
(IANA) Header Field Parameter Registry for the Session
Initiation Protocol (SIP)", BCP 98, RFC 3968,
DOI 10.17487/RFC3968, December 2004,
<https://www.rfc-editor.org/info/rfc3968>.
[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,
<https://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. 13 change blocks. 
13 lines changed or deleted 24 lines changed or added

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