draft-ietf-cuss-sip-uui-isdn-07.txt   draft-ietf-cuss-sip-uui-isdn-08.txt 
CUSS K. Drage, Ed. CUSS K. Drage, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track A. Johnston Intended status: Standards Track A. Johnston
Expires: August 18, 2014 Avaya Expires: September 6, 2014 Avaya
February 14, 2014 March 5, 2014
Interworking ISDN Call Control User Information with SIP Interworking ISDN Call Control User Information with SIP
draft-ietf-cuss-sip-uui-isdn-07 draft-ietf-cuss-sip-uui-isdn-08
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 defines this ISDN service for end-to-end transparency. This document defines
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 August 18, 2014. This Internet-Draft will expire on September 6, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 8, line 44 skipping to change at page 8, line 44
When sending UUI for the ISDN package, if the "purpose" header field When sending UUI for the ISDN package, if the "purpose" header field
is included, the UAC MUST set the User-to-User "purpose" header field is included, the UAC MUST set the User-to-User "purpose" header field
parameter to "isdn-uui". The UAC MUST NOT include more than one parameter to "isdn-uui". The UAC MUST NOT include more than one
User-to-User header field for this package in any SIP request or User-to-User header field for this package in any SIP request or
response. response.
When receiving UUI, when multiple User-to-User header fields are When receiving UUI, when multiple User-to-User header fields are
received in the same response with the "purpose" header field received in the same response with the "purpose" header field
parameter to "isdn-uui", or with no "purpose" header field parameter, parameter to "isdn-uui", or with no "purpose" header field parameter,
or with some combination of these, the UAS MUST discard all these or with some combination of these, the UAC MUST discard all these
header fields. There are no mechanisms for determining which was the header fields. There are no mechanisms for determining which was the
intended data packet so all are discarded. intended data packet so all are discarded.
The application designer will need to take into account the ISDN The application designer will need to take into account the ISDN
service restrictions; failure to do so can result in information service restrictions; failure to do so can result in information
being discarded at any interworking point with the ISDN. This being discarded at any interworking point with the ISDN. This
document makes no further normative requirements based on those document makes no further normative requirements based on those
constraints, because those constraints may vary from one ISDN to constraints, because those constraints may vary from one ISDN to
another. It is reasonable to expect that a limitation of 128 octets another. It is reasonable to expect that a limitation of 128 octets
(plus a protocol discriminator) can be imposed by the ISDN, and (plus a protocol discriminator) can be imposed by the ISDN, and
skipping to change at page 15, line 7 skipping to change at page 15, line 7
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-08 version from the
draft-ietf-cuss-sip-uui-isdn-07 version.
In section 7, one instance of UAS corrected to UAC.
Changes since made in the creation of the
draft-ietf-cuss-sip-uui-isdn-07 version from the draft-ietf-cuss-sip-uui-isdn-07 version from the
draft-ietf-cuss-sip-uui-isdn-06 version. draft-ietf-cuss-sip-uui-isdn-06 version.
In the UAS requirements section, a new requirement has been added In the UAS requirements section, a new requirement has been added
to set the purpose parameter to "uui-isdn" if it is included. to set the purpose parameter to "uui-isdn" if it is included.
This matches an equivalent requirement for the UAC. This matches an equivalent requirement for the UAC.
In the UAS requirements section, two instances of UAC have been In the UAS requirements section, two instances of UAC have been
corrected to UAS. corrected to UAS.
skipping to change at page 19, line 10 skipping to change at page 19, line 13
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-12 (work in progress), SIP", draft-ietf-cuss-sip-uui-13 (work in progress),
January 2014. March 2014.
[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
[RFC6567] Johnston, A. and L. Liess, "Problem Statement and [RFC6567] Johnston, A. and L. Liess, "Problem Statement and
Requirements for Transporting User-to-User Call Control Requirements for Transporting User-to-User Call Control
 End of changes. 6 change blocks. 
7 lines changed or deleted 13 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/