Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Fri, 13 December 2013 17:54 UTC

Return-Path: <keith.drage@alcatel-lucent.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 0F38F1AE0F4 for <cuss@ietfa.amsl.com>; Fri, 13 Dec 2013 09:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 S3FLFgkHQJI5 for <cuss@ietfa.amsl.com>; Fri, 13 Dec 2013 09:54:53 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9465D1ADF9E for <cuss@ietf.org>; Fri, 13 Dec 2013 09:54:53 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBDHshbu021017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Dec 2013 11:54:45 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBDHsh4U000849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Dec 2013 18:54:43 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 13 Dec 2013 18:54:43 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Atle Monrad <atle.monrad@ericsson.com>, "Gurbani, Vijay K (Vijay)" <vijay.gurbani@alcatel-lucent.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn
Thread-Index: AQHO4KQz6m0bJAR+y0uBhOtWswz/6ZoxmTqAgCD8RzA=
Date: Fri, 13 Dec 2013 17:54:43 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F90F4@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <5283CECB.8050804@bell-labs.com> <7D2F7D7ADBA812449F25F4A69922881C209216@ESESSMB203.ericsson.se>
In-Reply-To: <7D2F7D7ADBA812449F25F4A69922881C209216@ESESSMB203.ericsson.se>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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, 13 Dec 2013 17:54:56 -0000

As below:

Keith 

> -----Original Message-----
> From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Atle Monrad
> Sent: 22 November 2013 19:04
> To: Gurbani, Vijay K (Vijay); cuss@ietf.org
> Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn
> 
> 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.
> 
Done - seems to be something xml2rfc does that I was not expecting - hopefully changed the source so it does not happen.

> 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've added the colon. New lines is beyond my xml2rfc capabilities.

> ----
> 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 mailing list
> cuss@ietf.org
> https://www.ietf.org/mailman/listinfo/cuss
>