Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps

Atle Monrad <atle.monrad@ericsson.com> Tue, 03 December 2013 07:42 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 A98EB1AE080 for <cuss@ietfa.amsl.com>; Mon, 2 Dec 2013 23:42:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 QbeQA4Roh_Ev for <cuss@ietfa.amsl.com>; Mon, 2 Dec 2013 23:42:09 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id A1AF01AE045 for <cuss@ietf.org>; Mon, 2 Dec 2013 23:42:08 -0800 (PST)
X-AuditID: c1b4fb38-b7f2c8e000006d25-b4-529d8b4d57ab
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id FD.08.27941.D4B8D925; Tue, 3 Dec 2013 08:42:05 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.134]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 08:42:04 +0100
From: Atle Monrad <atle.monrad@ericsson.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "Gurbani, Vijay K (Vijay)" <vijay.gurbani@alcatel-lucent.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
Thread-Index: AQHO73F+QurHFH6wtESVPvq1tc09QJpCB8EggAAMBbA=
Date: Tue, 3 Dec 2013 07:42:04 +0000
Message-ID: <7D2F7D7ADBA812449F25F4A69922881C22FCD0@ESESSMB203.ericsson.se>
References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.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.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvra5v99wgg7nz1SxutL9gtnjaeJbR YtO5dewOzB6tz/ayeixZ8pMpgCmKyyYlNSezLLVI3y6BK2N121K2gtkKFftO9jI3MC6V6mLk 5JAQMJG4sHINE4QtJnHh3nq2LkYuDiGBI4wSje8aWSGcxYwS39sWM4JUsQnoSJz7eQcsISIw n1Hi06VfbCAJYQEviX+bv4DZIgLeEv+fzmWBsK0krk26wA5iswioSNy+ug2shheo5vLVo2Bx IYFaiZ2nv4DVcwpES2yb0gQU5+BgFJCVmNvECxJmFhCXuPVkPtSlAhJL9pxnhrBFJV4+/scK YStJrNh+iRGiXkdiwe5PbBC2tsSyha+ZIdYKSpyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsY OYpTi5Ny040MNjECI+Pglt8WOxgv/7U5xCjNwaIkzvvxrXOQkEB6YklqdmpqQWpRfFFpTmrx IUYmDk6pBkaDU8fC2LXdBHsznxYkhV3c/98kxHmj52bZ4uRk61n+KbJ7bc80LUn10/m6fPG9 7tOWTQfWiV29vWduyI5telbtDi+r+JPeC8Tf2vjlg+Q+NZHMl6c3/zfIy/2ivUEn3n2NyMW3 SR6p37JV/mZnvDstbvjJ4LXT6gIzMwYfu+QjhRH90RMT8pRYijMSDbWYi4oTAT/xRq5aAgAA
Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
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: Tue, 03 Dec 2013 07:42:11 -0000

Keith

Thanks for a quick reply and an alternative phrase that at least to me also clearly identify the point in an informative way.

Good to hear that your target for completion is end-of-this-week.

cheers
/atle

________________________________ 


Atle Monrad
3GPP CT Chairman

Group Function Technology - Standardization and Technical Regulation 
Ericsson



-----Original Message-----
From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith)
Sent: 3. desember 2013 15:56
To: Gurbani, Vijay K (Vijay); cuss@ietf.org
Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps

In terms of the text added, I have a preference for not using lower case forms of RFC 2119 language if we can avoid it. The reasoning is that it leads to questions as to whether the upper case form was meant, both in final review, publication, and by developers. If we can find therefore some other wording that expresses the same intent.

I am having trouble thinking of some suitable wording, but my suggestion might be:

"The 'isdn-interwork' value for purpose parameter was used in Internet-Drafts that have led to the publication of the present RFC. Although these documents had no other status than "work in progress", this value is implemented by some vendors. While not defined by this document, implementations could find it useful for interoperability purposes to support parsing and interpreting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages."

I will work through the other comments and respond hopefully later this week.

Keith

> -----Original Message-----
> From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K. 
> Gurbani
> Sent: 02 December 2013 15:16
> To: cuss@ietf.org
> Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps
> 
> Folks:
> 
> The WGLC for draft-ietf-cuss-sip-uui-isdn is now over.
> 
> Below is my personal interpretation of where the matter stands, i.e., 
> what I write below is not written as a co-chair but rather to 
> determine if the WG agree that this is where matters now stand.  
> Please comment if I deviate from what you all agree.
> 
> - "isdn-network" is tacitly supported, but not overtly so.
> 
> - More specifically, "isdn-network" is not IANA registered, and all
>    text related to it is not normative.
> 
> - The addition of the Note uses non-normative language, i.e.,
> 
>       "The 'isdn-interwork' value for purpose parameter was used
>       in Internet-Drafts that have led to the publication of the
>       present RFC. Although these documents had no other status than
>       "work in progress", this value is implemented by some vendors.
>       Therefore, it is recommended to support parsing and interpreting
>       'isdn-interwork' the same way as 'isdn-uui' when receiving
>       messages."
> 
> Is this an accurate representation?
> 
> Now back with the co-chair hat on ...
> 
> There has been reviews of the draft [1,2,3] by key WG members.  Can 
> the draft authors please comment on next steps with respect to 
> revising the draft.  Enrico and I will start the shepherding step in 
> parallel to the revision to be submitted.
> 
> [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html
> [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html
> [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html
> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, 
> Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: 
> http://goo.gl/x3Ogq _______________________________________________
> 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