Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn
Atle Monrad <atle.monrad@ericsson.com> Fri, 22 November 2013 19:04 UTC
Return-Path: <atle.monrad@ericsson.com>
X-Original-To: cuss@ietfa.amsl.com
Delivered-To: cuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 878C11AE1E6 for <cuss@ietfa.amsl.com>; Fri, 22 Nov 2013 11:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYjHs2xxe8mm for <cuss@ietfa.amsl.com>; Fri, 22 Nov 2013 11:04:26 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 103CC1ADF7C for <cuss@ietf.org>; Fri, 22 Nov 2013 11:04:25 -0800 (PST)
X-AuditID: c1b4fb30-b7f228e000003e6c-b8-528faab1573d
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 01.54.15980.1BAAF825; Fri, 22 Nov 2013 20:04:17 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.134]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0328.009; Fri, 22 Nov 2013 20:04:17 +0100
From: Atle Monrad <atle.monrad@ericsson.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn
Thread-Index: AQHO4KQjqvmSckbl8USYrsZxBrS5apoxok3A
Date: Fri, 22 Nov 2013 19:04:15 +0000
Message-ID: <7D2F7D7ADBA812449F25F4A69922881C209216@ESESSMB203.ericsson.se>
References: <5283CECB.8050804@bell-labs.com>
In-Reply-To: <5283CECB.8050804@bell-labs.com>
Accept-Language: nb-NO, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyM+Jvre7GVf1BBp826VvcaH/BbNGwRs6B yaPvsovHkiU/mQKYorhsUlJzMstSi/TtErgyNnxYy1bQrVKxa+UalgbG99JdjJwcEgImEp0X ZzBB2GISF+6tZ+ti5OIQEjjEKHGm+zUzhLOEUeLlgQfsIFVsAjoS537eYQWxRQS8JaY+/Q9m CwtYSsw7+JQFIm4l8ezOKyYI20jiyIYpYL0sAqoSR29OZQOxeYF6H3+bwwxiCwHNPPBhGVgv p4CuxLqP34BsDg5GAVmJuU28IGFmAXGJW0/mQx0qILFkz3lmCFtU4uXjf6wQtpLE2sPbWSDq dSQW7P7EBmFrSyxb+JoZYq2gxMmZT1gmMIrOQjJ2FpKWWUhaZiFpWcDIsoqRPTcxMye93HwT IzAODm75bbCDcdN9sUOM0hwsSuK8H946BwkJpCeWpGanphakFsUXleakFh9iZOLglGpgFFVY 80GmZH/aessVv6qUjrBpxa1wm8A77Yj3FRtBkQ75CK1/d3f/n1/hyJEV4lSmFLf5oujnLrcL 1kLKPaYXb30KsJqYxmStNeeA+J7Iwu7Lb5LD9tv+MjZ8I8VUx3Z5zt7zJ1cwLXNvTG/0EY4y U59z++PDE+rXQpdLhEsJHF2atKqptXq3EktxRqKhFnNRcSIAvR4p0FECAAA=
Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn
X-BeenThere: cuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" <cuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cuss>, <mailto:cuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cuss/>
List-Post: <mailto:cuss@ietf.org>
List-Help: <mailto:cuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cuss>, <mailto:cuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2013 19:04:28 -0000
G'day I have reviewed the draft again and have a couple of nits. 1. Abstract The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in the "Problem Statement and Requirements for Transporting User to User Call Control Information in SIP" document. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to- end transparency. Remove space: this ISDN service for end-to-end transparency. 2. 3.2. Impacts of the ISDN service on SIP operation The ISDN service has the following impacts that need to be understood within the SIP environment. Call transfer ISDN call transfer cancels all user-to-user supplementary services. In the ISDN, if user-to-user data is required after call transfer, then UUS3 has to be renegotiated, which is not provided by this SIP extension. The impact of this restriction on the SIP environment is that UUI header fields cannot be exchanged in transactions clearing down the SIP dialog after call transfer has occurred. Conference ISDN conferencing allows the user to still exchange user- to-user data after the conference is created. As far as UUS1 is concerned, it is not permitted. The ISDN three-party supplementary service is similar in many ways to conferencing, but is signalled using a different mechanism. This means that on clearing, the controller using UUS1 implicit does have the choice of sending data to either or both remote users. Because SIP conferencing cannot completely emulate the ISDN three-party supplementary service at the served user, UUS1 implicit is not possible. Diversion When ISDN diversion occurs, any UUS1 user-to-user data is sent to the forwarded-to-user (assuming that the call meets requirements for providing the service - this is impacted by the explicit service only). If the type of diversion is such that the call is also delivered to the forwarding user, they will also receive any UUS1 user-to-user data. Would it make sense to add some NLs and/or :s after the three "ISDN SSs" to split the text and improve readability?? e.g. like Call transfer: ISDN call transfer cancels all user-to-user supplementary services. In the ISDN, if user-to-user data is required after call transfer, then UUS3 has to be renegotiated, which is not provided by this SIP extension. The impact of this restriction on the SIP environment is that UUI header fields cannot be exchanged in transactions clearing down the SIP dialog after call transfer has occurred. Or Call transfer: ISDN call transfer cancels all user-to-user supplementary services. In the ISDN, if user-to-user data is required after call transfer, then UUS3 has to be renegotiated, which is not provided by this SIP extension. The impact of this restriction on the SIP environment is that UUI header fields cannot be exchanged in transactions clearing down the SIP dialog after call transfer has occurred. ---- I hope the draft can progress soon Cheers /atle ________________________________ Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation Ericsson -----Original Message----- From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K. Gurbani Sent: 13. november 2013 20:11 To: cuss@ietf.org Subject: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Folks: Enrico and I will like to announce a WGLC for the ISDN draft [1]. The WGLC will run from Wed, Nov 13 2013 to Fri, Nov 29 2013. We will appreciate your comments on the draft, posted to the list. All comments are appreciated, even if it is a simple one-liner saying that you believe the draft is ready, or conversely, that it is not ready (and why). As you review the draft, as part of your WGLC review, please identify any issues that may exist in regard to compatibility with draft-ietf-cuss-uui (the mechanism draft). Thank you. [1] http://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ Vijay K. Gurbani and Enrico Marocco _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss
- [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Vijay K. Gurbani
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Atle Monrad
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn DRAGE, Keith (Keith)
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn R.Jesske
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn DRAGE, Keith (Keith)
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn DRAGE, Keith (Keith)
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Atle Monrad
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Vijay K. Gurbani
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Atle Monrad
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Vijay K. Gurbani
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn DRAGE, Keith (Keith)
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn R.Jesske
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn celine.serrutvalette
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Vijay K. Gurbani
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Atle Monrad
- Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn DRAGE, Keith (Keith)