draft-ietf-sipcore-reason-q850-loc-02.txt   draft-ietf-sipcore-reason-q850-loc-03.txt 
Sipcore R. Jesske Sipcore R. Jesske
Internet-Draft Deutsche Telekom Internet-Draft Deutsche Telekom
Updates: RFC3326 (if approved) January 19, 2018 Updates: RFC3326 (if approved) February 12, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: July 23, 2018 Expires: August 16, 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-02.txt draft-ietf-sipcore-reason-q850-loc-03.txt
Abstract Abstract
The SIP Reason header field is defined for carrying ISUP cause values The SIP Reason header field is defined for carrying ISDN User Part
as well as SIP response codes. Some services in SIP networks may (ISUP) cause values as well as SIP response codes. Some services in
need to know the ISUP location where the call was released in the SIP networks may need to know the ISUP location where the call was
PSTN network to correctly interpret the reason of release. released in the 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 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 July 23, 2018. This Internet-Draft will expire on August 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 2, line 15 skipping to change at page 2, line 17
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 location Parameter for Reason header
header field . . . . . . . . . . . . . . . . . . . . . . 5 field . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 10. Normative References . . . . . . . . . . . . . . . . . . . . 5
10.1. Normative 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 2, line 47 skipping to change at page 2, line 47
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Rationale 3. Rationale
The primary intent of the parameter defined in this specification is The primary intent of the parameter defined in this specification is
for use in IMS networks defined by 3GPP but also open to be used by for use in IMS (IP Multimedia Subsystem) networks defined by 3GPP but
any other network. The purpose of this parameter is to transport the also open to be used by any other network. The purpose of this
location of call release from the originating PSTN entity to the SIP parameter is to transport the location of call release from the
entity receiving the response or BYE message containing the location originating PSTN entity to the SIP entity receiving the response or
of the call release. The ISDN location is defined in [Q.850]. BYE message containing the location of the call release. The ISDN
location is defined in [Q.850].
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
skipping to change at page 3, line 39 skipping to change at page 3, line 41
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 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 location
cause-location when setting up the Reason header field with a [Q.850] parameter 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 The use of the location parameter is restricted to Q850 cause values
other cases the location, if present, MUST be silently discarted. in other cases the location, if present, MUST be silently ignored.
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
SIP/2.0 404 Not Found SIP/2.0 404 Not Found
From: Alice <sips:alice@atlanta.example.com>;tag=1234567 From: Alice <sips:alice@atlanta.example.com>;tag=1234567
To: Bob <sips:bob@biloxi.example.com>;tag=765432 To: Bob <sips:bob@biloxi.example.com>;tag=765432
Call-ID: 12345600@atlanta.example.com Call-ID: 12345600@atlanta.example.com
CSeq: 1 INVITE CSeq: 1 INVITE
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"; Reason: Q.850;cause=1;text="Unallocated (unassigned) number";
location=LN location=LN
Content-Length: 0 Content-Length: 0
Figure 2: Example Location in Reason header field. Figure 2: Example Location in Reason header field.
6. Privacy Considerations 6. Privacy Considerations
This document doesn't change any of the privacy considerations This document doesn't change any of the privacy considerations
described in [RFC3326]. While the addition of the isup-cause- described in [RFC3326]. While the addition of the location parameter
location parameter does provide an indicator of the entity that added does provide an indicator of the entity that added the location in
the location in the signaling path this provides little more exposure the signaling path this provides little more exposure than the
than the [Q.850] cause itself. [Q.850] cause itself.
7. Security Considerations 7. Security Considerations
This document doesn't change any of the security considerations This document doesn't change any of the security considerations
described in [RFC3326]. The addition of the isup-cause-location described in [RFC3326]. The addition of the location parameter does
parameter does provide an indicator of the [Q.850] location where the provide an indicator of the [Q.850] location where the call was
call was released within the PSTN. This information may be used for released within the PSTN. This information may be used for specific
specific location driven services but does not create any additional location driven services but does not create any additional security
security constrains. But since the [Q.850] location is very constrains. But since the [Q.850] location is very imprecise the
imprecise the [Q.850] location value itself will not add any major [Q.850] location value itself will not add any major security
security constrain. The use of this parameter is not restricted to a constraint. 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 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 [RFC3968], which will be added to Header as per the guidelines in [RFC3968], which will be added to Header
Field Parameters sub-registry under http://www.iana.org/assignments/ Field Parameters sub-registry under http://www.iana.org/assignments/
sip-parameters. sip-parameters.
Header Field: Reason Header Field: Reason
Parameter Name: location Parameter Name: location
9. Acknowledgments 9. Acknowledgments
Thanks to Michael Kreipl, Thoams Belling, Marianne Mohali, Peter Thanks to Michael Kreipl, Thoams Belling, Marianne Mohali, Peter
Daws, Paul Kyzivat, Dale Worley, Yehoshua Gev, Keith Drage for the Daws, Paul Kyzivat, Dale Worley, Yehoshua Gev, Keith Drage for the
comments and review. comments and review.
10. References 10. Normative References
10.1. Normative References [Q.850] INTERNATIONAL TELECOMMUNICATION UNION, "Usage of cause and
location in the Digital Subscriber Signalling System No. 1
and the Signalling System No. 7 ISDN User Part", Q 850,
May 1998.
[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>.
[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,
skipping to change at page 6, line 10 skipping to change at page 6, line 10
(IANA) Header Field Parameter Registry for the Session (IANA) Header Field Parameter Registry for the Session
Initiation Protocol (SIP)", BCP 98, RFC 3968, Initiation Protocol (SIP)", BCP 98, RFC 3968,
DOI 10.17487/RFC3968, December 2004, DOI 10.17487/RFC3968, December 2004,
<https://www.rfc-editor.org/info/rfc3968>. <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
[Q.850] INTERNATIONAL TELECOMMUNICATION UNION, "Usage of cause and
location in the Digital Subscriber Signalling System No. 1
and the Signalling System No. 7 ISDN User Part", Q 850,
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. 19 change blocks. 
48 lines changed or deleted 41 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/