draft-ietf-cuss-sip-uui-isdn-04.txt   draft-ietf-cuss-sip-uui-isdn-05.txt 
Network Working Group K. Drage, Ed. Network Working Group K. Drage, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track A. Johnston Intended status: Standards Track A. Johnston
Expires: November 5, 2012 Avaya Expires: February 5, 2014 Avaya
May 4, 2012 August 4, 2013
Interworking ISDN Call Control User Information with SIP Interworking ISDN Call Control User Information with SIP
draft-ietf-cuss-sip-uui-isdn-04 draft-ietf-cuss-sip-uui-isdn-05
Abstract Abstract
The motivation and use cases for interworking and transporting ITU-T The motivation and use cases for interworking and transporting ITU-T
DSS1 User-user information element data in SIP are described in the DSS1 User-user information element data in SIP are described in the
"Problem Statement and Requirements for Transporting User to User "Problem Statement and Requirements for Transporting User to User
Call Control Information in SIP" document. As networks move to SIP Call Control Information in SIP" document. As networks move to SIP
it is important that applications requiring this data can continue to it is important that applications requiring this data can continue to
function in SIP networks as well as the ability to interwork with function in SIP networks as well as the ability to interwork with
this ISDN service for end-to- end transparency. This document this ISDN service for end-to- end transparency. This document
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 http://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 5, 2012. This Internet-Draft will expire on February 5, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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 (http://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 37 skipping to change at page 2, line 37
7. UAC requirements . . . . . . . . . . . . . . . . . . . . . . . 8 7. UAC requirements . . . . . . . . . . . . . . . . . . . . . . . 8
8. UAS requirements . . . . . . . . . . . . . . . . . . . . . . . 9 8. UAS requirements . . . . . . . . . . . . . . . . . . . . . . . 9
9. UUI contents . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. UUI contents . . . . . . . . . . . . . . . . . . . . . . . . . 10
10. Considerations for ISDN interworking gateways . . . . . . . . 11 10. Considerations for ISDN interworking gateways . . . . . . . . 11
11. Coding requirements . . . . . . . . . . . . . . . . . . . . . 11 11. Coding requirements . . . . . . . . . . . . . . . . . . . . . 11
12. Media Feature Tag . . . . . . . . . . . . . . . . . . . . . . 12 12. Media Feature Tag . . . . . . . . . . . . . . . . . . . . . . 12
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
14. Security Considerations . . . . . . . . . . . . . . . . . . . 13 14. Security Considerations . . . . . . . . . . . . . . . . . . . 13
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
16. Changes since previous versions . . . . . . . . . . . . . . . 14 16. Changes since previous versions . . . . . . . . . . . . . . . 14
17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
17.1. Normative References . . . . . . . . . . . . . . . . . . . 17 17.1. Normative References . . . . . . . . . . . . . . . . . . . 18
17.2. Informative References . . . . . . . . . . . . . . . . . . 18 17.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Terminology 1. 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 BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
2. Overview 2. Overview
skipping to change at page 4, line 30 skipping to change at page 4, line 30
CONNECT messages, within DSS1 USER INFORMATION messages; and CONNECT messages, within DSS1 USER INFORMATION messages; and
UUS3: User-to-user information exchanged while a call is in the UUS3: User-to-user information exchanged while a call is in the
Active state, within DSS1 USER INFORMATION messages. Active state, within DSS1 USER INFORMATION messages.
The service is always requested by the calling user. The service is always requested by the calling user.
This document defines only the provision of the ISDN UUS1 implicit This document defines only the provision of the ISDN UUS1 implicit
supplementary service to interworking scenarios, this being the most supplementary service to interworking scenarios, this being the most
widely deployed and used of the various ISDN user-to-user services, widely deployed and used of the various ISDN user-to-user services,
and indeed the one that matches the requirements specified in and indeed the one that matches the requirements specified in RFC
draft-ietf-cuss-sip-uui-reqs [I-D.ietf-cuss-sip-uui-reqs]. 6567 [RFC6567].
The above come from the ISDN specifications defined for public The above come from the ISDN specifications defined for public
networks. There are a parallel set of ISDN specifications defined networks. There are a parallel set of ISDN specifications defined
for private networks (QSIG}. These specifications do not define a for private networks (QSIG}. These specifications do not define a
UUS1 implicit supplementary service. However, implementation of such UUS1 implicit supplementary service. However, implementation of such
a UUS1 implicit supplementary service for private networks can a UUS1 implicit supplementary service for private networks can
readily be constructed in a proprietary fashion based on the readily be constructed in a proprietary fashion based on the
specifications for public networks, and evidence suggests that some specifications for public networks, and evidence suggests that some
vendors have done so. On this basis, there is no reason why this vendors have done so. On this basis, there is no reason why this
package cannot also be used to support interworking with such a package cannot also be used to support interworking with such a
skipping to change at page 12, line 4 skipping to change at page 12, line 4
[I-D.ietf-cuss-sip-uui] defines a "uui" option tag for use with the [I-D.ietf-cuss-sip-uui] defines a "uui" option tag for use with the
UUI mechanism extension. The option tag is not interworked at an UUI mechanism extension. The option tag is not interworked at an
ISDN interworking gateway. The ISDN interworking gateways MUST NOT ISDN interworking gateway. The ISDN interworking gateways MUST NOT
take the omission of the "uui" option tag in a received INVITE take the omission of the "uui" option tag in a received INVITE
request to indicate that interworking of a received header field is request to indicate that interworking of a received header field is
not to be performed. not to be performed.
11. Coding requirements 11. Coding requirements
This document defines "isdn-uui" as a new value of the User-to-User This document defines "isdn-uui" as a new value of the User-to-User
"purpose" header field parameter. "purpose" header field parameter. The following ABNF adds to the
production in [I-D.ietf-cuss-sip-uui]
pkg-param-value =/ "isdn-uui"
This document defines "isdn-uui" as a new value of the User-to-User This document defines "isdn-uui" as a new value of the User-to-User
"content" header field parameter. A content value of "isdn-uui" "content" header field parameter. A content value of "isdn-uui"
indicates that the contents have a first octet that is a protocol indicates that the contents have a first octet that is a protocol
discriminator (see table 4-26 of ITU-T Recommendation Q.931) [Q931] discriminator (see table 4-26 of ITU-T Recommendation Q.931) [Q931]
followed by uui-data that can be subject to a length limitation followed by uui-data that can be subject to a length limitation
(before encoding or after decoding) that is generally 128 octets. (before encoding or after decoding) that is generally 128 octets.
The following ABNF adds to the production in [I-D.ietf-cuss-sip-uui]
cont-param-value =/ "isdn-uui"
12. Media Feature Tag 12. Media Feature Tag
This document defines a new media feature tag "sip.uui-isdn". This This document defines a new media feature tag "sip.uui-isdn". This
feature tag indicates that this UUI package is supported by the feature tag indicates that this UUI package is supported by the
sender, and its usage is entirely in accordance with RFC 3840 sender, and its usage is entirely in accordance with RFC 3840
[RFC3840]. This document makes no additional provisions for the use [RFC3840]. This document makes no additional provisions for the use
of this feature tag. of this feature tag.
13. IANA Considerations 13. IANA Considerations
skipping to change at page 14, line 30 skipping to change at page 14, line 40
thank Francois Audet, Denis Alexeitsev, Paul Kyzivat, Cullen thank Francois Audet, Denis Alexeitsev, Paul Kyzivat, Cullen
Jennings, Mahalingam Mani and Celine Serrut-Valette for their Jennings, Mahalingam Mani and Celine Serrut-Valette for their
comments. comments.
16. Changes since previous versions 16. Changes since previous versions
Note to RFC editor: This section is to be deleted before final Note to RFC editor: This section is to be deleted before final
publication. publication.
Changes since made in the creation of the Changes since made in the creation of the
draft-ietf-cuss-sip-uui-isdn-05 version from the
draft-ietf-cuss-sip-uui-isdn-04 version.
ABNF provided for definition of values of package and content to
correspond to ABNF in current version of [I-D.ietf-cuss-sip-uui]
Changes since made in the creation of the
draft-ietf-cuss-sip-uui-isdn-04 version from the draft-ietf-cuss-sip-uui-isdn-04 version from the
draft-ietf-cuss-sip-uui-isdn-03 version. draft-ietf-cuss-sip-uui-isdn-03 version.
Change of the "package" header field parameter back to the Change of the "package" header field parameter back to the
"purpose" header field parameter in alignment with change in "purpose" header field parameter in alignment with change in
draft-ietf-cuss-sip-uui. draft-ietf-cuss-sip-uui.
Identification of the package name in the abstract. Identification of the package name in the abstract.
Minor change to IANA registration of "content" header field Minor change to IANA registration of "content" header field
skipping to change at page 18, line 6 skipping to change at page 18, line 25
for Telephones (SIP-T): Context and Architectures", for Telephones (SIP-T): Context and Architectures",
BCP 63, RFC 3372, September 2002. BCP 63, RFC 3372, September 2002.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
[I-D.ietf-cuss-sip-uui] [I-D.ietf-cuss-sip-uui]
Johnston, A. and J. Rafferty, "A Mechanism for Johnston, A. and J. Rafferty, "A Mechanism for
Transporting User to User Call Control Information in Transporting User to User Call Control Information in
SIP", draft-ietf-cuss-sip-uui-06 (work in progress), SIP", draft-ietf-cuss-sip-uui-10 (work in progress),
May 2012. April 2013.
[Q931] "ITU-T Recommendation Q.931: Digital subscriber Signalling [Q931] "ITU-T Recommendation Q.931: Digital subscriber Signalling
System No. 1 - Network layer; ISDN user-network interface System No. 1 - Network layer; ISDN user-network interface
layer 3 specification for basic call control", layer 3 specification for basic call control",
http://www.itu.int/rec/T-REC-Q.931-199805-I/en . http://www.itu.int/rec/T-REC-Q.931-199805-I/en .
17.2. Informative References 17.2. Informative References
[I-D.ietf-cuss-sip-uui-reqs] [RFC6567] Johnston, A. and L. Liess, "Problem Statement and
Johnston, A. and L. Liess, "Problem Statement and Requirements for Transporting User-to-User Call Control
Requirements for Transporting User to User Call Control Information in SIP", RFC 6567, April 2012.
Information in SIP", draft-ietf-cuss-sip-uui-reqs-09 (work
in progress), January 2012.
[Q957.1] "ITU-T Recommendation Q.957.1: Digital subscriber [Q957.1] "ITU-T Recommendation Q.957.1: Digital subscriber
Signalling System No. 1 - Stage 3 description for Signalling System No. 1 - Stage 3 description for
supplementary services using DSS 1; Stage 3 description supplementary services using DSS 1; Stage 3 description
for additional information transfer supplementary services for additional information transfer supplementary services
using DSS 1: User-to-User Signalling (UUS)", using DSS 1: User-to-User Signalling (UUS)",
http://www.itu.int/rec/T-REC-Q.957.1-199607-I . http://www.itu.int/rec/T-REC-Q.957.1-199607-I .
[Q763] "ITU-T Q.763 Signaling System No. 7 - ISDN user part [Q763] "ITU-T Q.763 Signaling System No. 7 - ISDN user part
formats and codes", formats and codes",
 End of changes. 12 change blocks. 
18 lines changed or deleted 29 lines changed or added

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