From vkg@bell-labs.com Thu Sep 5 07:37:40 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7CE11E80EC for ; Thu, 5 Sep 2013 07:37:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.304 X-Spam-Level: X-Spam-Status: No, score=-110.304 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ly5RSCWPTBKO for ; Thu, 5 Sep 2013 07:37:30 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id D006D11E81A6 for ; Thu, 5 Sep 2013 07:37:29 -0700 (PDT) Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r85EbRfK018787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Sep 2013 09:37:28 -0500 (CDT) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r85EbR4F025626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Sep 2013 09:37:27 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r85EbPGa003294; Thu, 5 Sep 2013 09:37:27 -0500 (CDT) Message-ID: <5228984A.1090106@bell-labs.com> Date: Thu, 05 Sep 2013 09:42:18 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" References: <5213751E.8060006@bell-labs.com> In-Reply-To: <5213751E.8060006@bell-labs.com> X-Forwarded-Message-Id: <5213751E.8060006@bell-labs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11 Cc: cuss@ietf.org Subject: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2013 14:37:40 -0000 Authors of CUSS ISDN Service draft, please advise on the matter below regarding the availability of a new version. Thanks, -------- Original Message -------- Subject: Re: [cuss] To "isdn-network" or not Date: Tue, 20 Aug 2013 08:54:38 -0500 From: Vijay K. Gurbani Organization: Bell Laboratories, Alcatel-Lucent To: R.Jesske@telekom.de CC: cuss@ietf.org On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: [...] > Could we agree on counting who is OK with this Note? > Or can we have an alternative proposal? Roland: While not an actual count, I would note that all the people who expressed an opinion on this --- except for Paul's observation [1] --- supported the addition of the note with the understanding in [2]. As such, Enrico and I would exhort the authors of the draft to chime in on the mailing list with their acquiescence (or questions) and close this issue by producing a revision as soon as possible. Authors? [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.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 From atle.monrad@ericsson.com Tue Sep 10 07:00:16 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24E721F8201 for ; Tue, 10 Sep 2013 07:00:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtPhNbpdkdj2 for ; Tue, 10 Sep 2013 07:00:11 -0700 (PDT) Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 66A9821E80E0 for ; Tue, 10 Sep 2013 06:59:57 -0700 (PDT) X-AuditID: c1b4fb30-b7f9a8e000005620-4b-522f25d3207b Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 0A.01.22048.3D52F225; Tue, 10 Sep 2013 15:59:48 +0200 (CEST) Received: from ESESSMB203.ericsson.se ([169.254.3.129]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.02.0328.009; Tue, 10 Sep 2013 15:59:47 +0200 From: Atle Monrad To: "Vijay K. Gurbani" , "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV7ZwWF4R1aYk+DerYESMEiWJm/BQXQ Date: Tue, 10 Sep 2013 13:59:46 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C19AFDE@ESESSMB203.ericsson.se> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> In-Reply-To: <5228984A.1090106@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.148] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+Jvje4VVf0ggx9rWS1utL9gtjh+dRWL RcMaOQdmj77LLh5Llvxk8vhy+TNbAHMUl01Kak5mWWqRvl0CV8bSl5+ZCjpFKo69287UwHhb oIuRg0NCwERiwxufLkZOIFNM4sK99WxdjFwcQgKHGSVOfH8A5SxhlHg0bT07SBWbgI7EuZ93 WEESIgLdjEAtP1lBEswCyhIv/rWygkwVFjCTmNjpAGKKCJhLfLweBlIhImAksf/uDSYQm0VA VWLbvNVgNq+At8SiC61gU4QEfCXuft8AZnMK6EocO9LIDDKGUUBWYm4TL8QicYlbT+YzQdws ILFkz3lmCFtU4uXjf6wQtpJE45InUIfpSCzY/YkNwtaWWLbwNTPEWkGJkzOfsExgFJuFZOws JC2zkLTMQtKygJFlFSN7bmJmTnq5+SZGYLwc3PLbYAfjpvtihxilOViUxHk3650JFBJITyxJ zU5NLUgtii8qzUktPsTIxMEp1cAoymWdY8iga1Hxncm0ccXu3ZPrrzhIS3bsyjDYrvGm10yy 44O3puhV0/Cu4zFnct9/0Y36s1DCbqLvyZz4GfueXWBJZbFb+Ng6I2LrtgCn3r9TL0i5lm6f cUeNP/TF488vbq/oyYqXk0icbGFV4Lunz+Gw6Ls9xm/nz3349PnVrLsbkzy19y5WYinOSDTU Yi4qTgQA0zQEyWUCAAA= Cc: "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 14:00:17 -0000 Vijay I'm not one of the draft authors, but as stated before=20 I would like to support moving along with text in line with previous discus= sions (i.e. the already identified Note) and not reopen old discussions. We= 'll never be able to complete the draft otherwise. I would also like to ask the authors of cuss-sip-uui & cuss-sip-uui-isdn to= kindly find a timeslot to wrap up the remaining topics and complete the dr= afts. thanks /atle ________________________________=20 Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation=20 Ericsson -----Original Message----- From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf Of Vij= ay K. Gurbani Sent: 5. september 2013 15:42 To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org Cc: cuss@ietf.org Subject: [cuss] Fwd: Re: To "isdn-network" or not Authors of CUSS ISDN Service draft, please advise on the matter below regar= ding the availability of a new version. Thanks, -------- Original Message -------- Subject: Re: [cuss] To "isdn-network" or not Date: Tue, 20 Aug 2013 08:54:38 -0500 From: Vijay K. Gurbani Organization: Bell Laboratories, Alcatel-Lucent To: R.Jesske@telekom.de CC: cuss@ietf.org On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: [...] > Could we agree on counting who is OK with this Note? > Or can we have an alternative proposal? Roland: While not an actual count, I would note that all the people who exp= ressed an opinion on this --- except for Paul's observation [1] --- supported the addition of the note with the understanding in [2]. As such, Enrico and I would exhort the authors of the draft to chime in on = the mailing list with their acquiescence (or questions) and close this issu= e by producing a revision as soon as possible. Authors? [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.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 From keith.drage@alcatel-lucent.com Tue Sep 10 08:05:00 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F7A21E8123 for ; Tue, 10 Sep 2013 08:04:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vDL6jT+ldnM for ; Tue, 10 Sep 2013 08:04:52 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 38F5921E813D for ; Tue, 10 Sep 2013 08:04:37 -0700 (PDT) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r8AF4TI6006878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 10 Sep 2013 10:04:30 -0500 (CDT) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r8AF4R1b010596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Sep 2013 17:04:28 +0200 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 10 Sep 2013 17:04:27 +0200 From: "DRAGE, Keith (Keith)" To: "Gurbani, Vijay K (Vijay)" , "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkWFMWiaHadTGUCf5NicWzP73Jm/GUXw Date: Tue, 10 Sep 2013 15:04:27 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> In-Reply-To: <5228984A.1090106@bell-labs.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] 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.39 Cc: "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 15:05:00 -0000 All these mails keep referring to a proposed note. However statements from the same source stated they wanted it normative. Either it is normative, and not a note, or it is informative and we'll put = it in a note. Can you please clarify which it is. Regards Keith > -----Original Message----- > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf Of > Vijay K. Gurbani > Sent: 05 September 2013 15:42 > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc: cuss@ietf.org > Subject: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Authors of CUSS ISDN Service draft, please advise on the matter below > regarding the availability of a new version. >=20 > Thanks, >=20 > -------- Original Message -------- > Subject: Re: [cuss] To "isdn-network" or not > Date: Tue, 20 Aug 2013 08:54:38 -0500 > From: Vijay K. Gurbani > Organization: Bell Laboratories, Alcatel-Lucent > To: R.Jesske@telekom.de > CC: cuss@ietf.org >=20 > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > [...] > > Could we agree on counting who is OK with this Note? > > Or can we have an alternative proposal? >=20 > Roland: While not an actual count, I would note that all the people > who expressed an opinion on this --- except for Paul's observation [1] > --- supported the addition of the note with the understanding in [2]. >=20 > As such, Enrico and I would exhort the authors of the draft to chime > in on the mailing list with their acquiescence (or questions) and > close this issue by producing a revision as soon as possible. >=20 > Authors? >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html >=20 > Thanks, >=20 > - 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 >=20 >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss From celine.serrutvalette@orange.com Tue Sep 10 09:01:21 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8520E21F9AD8 for ; Tue, 10 Sep 2013 09:01:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KiErFVPEW8oP for ; Tue, 10 Sep 2013 09:01:12 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id BB2AE11E81C6 for ; Tue, 10 Sep 2013 08:57:53 -0700 (PDT) Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id D34132AC6BB; Tue, 10 Sep 2013 17:57:50 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id AE2FE15805B; Tue, 10 Sep 2013 17:57:50 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 10 Sep 2013 17:57:50 +0200 From: To: "DRAGE, Keith (Keith)" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV84n4L5xZAfEGxPwbtNNvX2Jm++AOAgAAu8bA= Date: Tue, 10 Sep 2013 15:57:49 +0000 Message-ID: <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.27.82422 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "Gurbani, Vijay K \(Vijay\)" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 16:01:21 -0000 Hello, Our preference would be that it is normative. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part de D= RAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0=A0: Gurbani, Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.o= rg Cc=A0: cuss@ietf.org Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not All these mails keep referring to a proposed note. However statements from the same source stated they wanted it normative. Either it is normative, and not a note, or it is informative and we'll put = it in a note. Can you please clarify which it is. Regards Keith > -----Original Message----- > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf=20 > Of Vijay K. Gurbani > Sent: 05 September 2013 15:42 > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc: cuss@ietf.org > Subject: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Authors of CUSS ISDN Service draft, please advise on the matter below=20 > regarding the availability of a new version. >=20 > Thanks, >=20 > -------- Original Message -------- > Subject: Re: [cuss] To "isdn-network" or not > Date: Tue, 20 Aug 2013 08:54:38 -0500 > From: Vijay K. Gurbani > Organization: Bell Laboratories, Alcatel-Lucent > To: R.Jesske@telekom.de > CC: cuss@ietf.org >=20 > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > [...] > > Could we agree on counting who is OK with this Note? > > Or can we have an alternative proposal? >=20 > Roland: While not an actual count, I would note that all the people=20 > who expressed an opinion on this --- except for Paul's observation [1] > --- supported the addition of the note with the understanding in [2]. >=20 > As such, Enrico and I would exhort the authors of the draft to chime=20 > in on the mailing list with their acquiescence (or questions) and=20 > close this issue by producing a revision as soon as possible. >=20 > Authors? >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html >=20 > Thanks, >=20 > - 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:=20 > http://goo.gl/x3Ogq _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 >=20 > _______________________________________________ > 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 ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From R.Jesske@telekom.de Tue Sep 10 22:30:23 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24A6411E8159 for ; Tue, 10 Sep 2013 22:30:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WuwyxpJdQ35s for ; Tue, 10 Sep 2013 22:30:19 -0700 (PDT) Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id EE0B611E8118 for ; Tue, 10 Sep 2013 22:30:17 -0700 (PDT) Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 11 Sep 2013 07:30:15 +0200 Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 11 Sep 2013 07:30:15 +0200 From: To: , Date: Wed, 11 Sep 2013 07:30:14 +0200 Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV84n4L5xZAfEGxPwbtNNvX2Jm++AOAgAAu8bCAAOQvYA== Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org, vijay.gurbani@alcatel-lucent.com, cuss@ietf.org Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2013 05:30:23 -0000 Hello, >From my understanding we had the agreement that we keep it in a Note. Best Regards Roalnd -----Urspr=FCngliche Nachricht----- Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag von ce= line.serrutvalette@orange.com Gesendet: Dienstag, 10. September 2013 17:58 An: DRAGE, Keith (Keith) Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay); = cuss@ietf.org Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not Hello, Our preference would be that it is normative. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part de D= RAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0=A0: Gurb= ani, Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.org Cc=A0: cuss@ietf.org Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not All these mails keep referring to a proposed note. However statements from the same source stated they wanted it normative. Either it is normative, and not a note, or it is informative and we'll put = it in a note. Can you please clarify which it is. Regards Keith > -----Original Message----- > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf=20 > Of Vijay K. Gurbani > Sent: 05 September 2013 15:42 > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc: cuss@ietf.org > Subject: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Authors of CUSS ISDN Service draft, please advise on the matter below=20 > regarding the availability of a new version. >=20 > Thanks, >=20 > -------- Original Message -------- > Subject: Re: [cuss] To "isdn-network" or not > Date: Tue, 20 Aug 2013 08:54:38 -0500 > From: Vijay K. Gurbani > Organization: Bell Laboratories, Alcatel-Lucent > To: R.Jesske@telekom.de > CC: cuss@ietf.org >=20 > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > [...] > > Could we agree on counting who is OK with this Note? > > Or can we have an alternative proposal? >=20 > Roland: While not an actual count, I would note that all the people=20 > who expressed an opinion on this --- except for Paul's observation [1] > --- supported the addition of the note with the understanding in [2]. >=20 > As such, Enrico and I would exhort the authors of the draft to chime=20 > in on the mailing list with their acquiescence (or questions) and=20 > close this issue by producing a revision as soon as possible. >=20 > Authors? >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html >=20 > Thanks, >=20 > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane,=20 > 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:=20 > http://goo.gl/x3Ogq _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 >=20 > _______________________________________________ > 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 ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou = copies sans autorisation. Si vous avez recu ce message par erreur, veuillez= le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le= s messages electroniques etant susceptibles d'alteration, Orange decline to= ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used= or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From keith.drage@alcatel-lucent.com Wed Sep 11 05:18:19 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E21311E8229 for ; Wed, 11 Sep 2013 05:18:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ds+LIcHqAMhU for ; Wed, 11 Sep 2013 05:18:14 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 7342B11E821B for ; Wed, 11 Sep 2013 05:18:14 -0700 (PDT) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r8BCI9Pd006397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 11 Sep 2013 07:18:10 -0500 (CDT) Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r8BCI6ud000683 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Sep 2013 14:18:08 +0200 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 11 Sep 2013 14:18:07 +0200 From: "DRAGE, Keith (Keith)" To: "R.Jesske@telekom.de" , "celine.serrutvalette@orange.com" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkWFMWiaHadTGUCf5NicWzP73Jm/GUXw///tp4CAAOL9AIAAeK/g Date: Wed, 11 Sep 2013 12:18:06 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> In-Reply-To: <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.41] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "Gurbani, Vijay K \(Vijay\)" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2013 12:18:19 -0000 As in informative? I.e. no uppercase MUST or SHOULD? Keith > -----Original Message----- > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > Sent: 11 September 2013 06:30 > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay)= ; > cuss@ietf.org > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, > From my understanding we had the agreement that we keep it in a Note. >=20 > Best Regards >=20 > Roalnd >=20 > -----Urspr=FCngliche Nachricht----- > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag von > celine.serrutvalette@orange.com > Gesendet: Dienstag, 10. September 2013 17:58 > An: DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay)= ; > cuss@ietf.org > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > Our preference would be that it is normative. > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part de > DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0=A0: G= urbani, > Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc=A0: cuss@ietf.org > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > All these mails keep referring to a proposed note. >=20 > However statements from the same source stated they wanted it normative. >=20 > Either it is normative, and not a note, or it is informative and we'll pu= t > it in a note. >=20 > Can you please clarify which it is. >=20 > Regards >=20 > Keith >=20 > > -----Original Message----- > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf > > Of Vijay K. Gurbani > > Sent: 05 September 2013 15:42 > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc: cuss@ietf.org > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > Authors of CUSS ISDN Service draft, please advise on the matter below > > regarding the availability of a new version. > > > > Thanks, > > > > -------- Original Message -------- > > Subject: Re: [cuss] To "isdn-network" or not > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > From: Vijay K. Gurbani > > Organization: Bell Laboratories, Alcatel-Lucent > > To: R.Jesske@telekom.de > > CC: cuss@ietf.org > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > [...] > > > Could we agree on counting who is OK with this Note? > > > Or can we have an alternative proposal? > > > > Roland: While not an actual count, I would note that all the people > > who expressed an opinion on this --- except for Paul's observation [1] > > --- supported the addition of the note with the understanding in [2]. > > > > As such, Enrico and I would exhort the authors of the draft to chime > > in on the mailing list with their acquiescence (or questions) and > > close this issue by producing a revision as soon as possible. > > > > Authors? > > > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.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 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 > _________________________________________________________________________= _ > _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > exploites ou copies sans autorisation. Si vous avez recu ce message par > erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les > pieces jointes. Les messages electroniques etant susceptibles d'alteratio= n, > Orange decline toute responsabilite si ce message a ete altere, deforme o= u > falsifie. Merci. >=20 > This message and its attachments may contain confidential or privileged > information that may be protected by law; they should not be distributed, > used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have bee= n > modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss From celine.serrutvalette@orange.com Thu Sep 12 06:01:27 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A847F11E8113 for ; Thu, 12 Sep 2013 06:01:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PqljjJA0i6y for ; Thu, 12 Sep 2013 06:01:23 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 7396611E820D for ; Thu, 12 Sep 2013 06:01:23 -0700 (PDT) Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 466132AC40E; Thu, 12 Sep 2013 15:01:22 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 19BF5180075; Thu, 12 Sep 2013 15:01:22 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Thu, 12 Sep 2013 15:01:21 +0200 From: To: "DRAGE, Keith (Keith)" , "R.Jesske@telekom.de" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV84n4L5xZAfEGxPwbtNNvX2Jm++AOAgAAu8bCAAOQvYIAAULsAgAG/pgA= Date: Thu, 12 Sep 2013 13:01:21 +0000 Message-ID: <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.5] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.27.82422 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "Gurbani, Vijay K \(Vijay\)" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:01:27 -0000 Hello, As done in our proposition of July 2012, we would like to use the term of "= RECOMMENDED" as defined in RFC 2119 and it seems to us that nothing forbids= its usage in a Note. It is for instance used in this way in draft-ietf-bfc= pbis-rfc4583bis-07 in section 6: Note: In [15] 'm-stream' was erroneously used in Section 10. Although the e= xample was non-normative, it is implemented by some vendors and occurs in c= ases where the endpoint is willing to act as an server. Therefore, it is R= ECOMMENDED to support parsing and interpreting 'm-stream' the same way as '= mstrm' when receiving. Our proposed note (same as in July 2012) following this approach:=20 Note: 'isdn-interwork' value for purpose parameter was used in Internet-Dra= fts that have led to the publication of the present RFC. Although these doc= uments had not other status than "work in progress", it is implemented by s= ome vendors. Therefore, it is RECOMMENDED to support parsing and interpreti= ng 'isdn-interwork' the same way as 'isdn-uui' when receiving. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]=20 Envoy=E9=A0: mercredi 11 septembre 2013 14:18 =C0=A0: R.Jesske@telekom.de; SERRUT-VALETTE Celine IMT/OLN Cc=A0: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay= ); cuss@ietf.org Objet=A0: RE: [cuss] Fwd: Re: To "isdn-network" or not As in informative? I.e. no uppercase MUST or SHOULD? Keith > -----Original Message----- > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > Sent: 11 September 2013 06:30 > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, > From my understanding we had the agreement that we keep it in a Note. >=20 > Best Regards >=20 > Roalnd >=20 > -----Urspr=FCngliche Nachricht----- > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag=20 > von celine.serrutvalette@orange.com > Gesendet: Dienstag, 10. September 2013 17:58 > An: DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > Our preference would be that it is normative. > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part=20 > de DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0=A0= :=20 > Gurbani, Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc=A0: cuss@ietf.org > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > All these mails keep referring to a proposed note. >=20 > However statements from the same source stated they wanted it normative. >=20 > Either it is normative, and not a note, or it is informative and we'll=20 > put it in a note. >=20 > Can you please clarify which it is. >=20 > Regards >=20 > Keith >=20 > > -----Original Message----- > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf=20 > > Of Vijay K. Gurbani > > Sent: 05 September 2013 15:42 > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc: cuss@ietf.org > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > Authors of CUSS ISDN Service draft, please advise on the matter=20 > > below regarding the availability of a new version. > > > > Thanks, > > > > -------- Original Message -------- > > Subject: Re: [cuss] To "isdn-network" or not > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > From: Vijay K. Gurbani > > Organization: Bell Laboratories, Alcatel-Lucent > > To: R.Jesske@telekom.de > > CC: cuss@ietf.org > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > [...] > > > Could we agree on counting who is OK with this Note? > > > Or can we have an alternative proposal? > > > > Roland: While not an actual count, I would note that all the people=20 > > who expressed an opinion on this --- except for Paul's observation=20 > > [1] > > --- supported the addition of the note with the understanding in [2]. > > > > As such, Enrico and I would exhort the authors of the draft to chime=20 > > in on the mailing list with their acquiescence (or questions) and=20 > > close this issue by producing a revision as soon as possible. > > > > Authors? > > > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html > > > > Thanks, > > > > - vijay > > -- > > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent=20 > > Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > > Email: vkg@{bell-labs.com,acm.org} /=20 > > 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 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 > ______________________________________________________________________ > ____ _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations=20 > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20 > exploites ou copies sans autorisation. Si vous avez recu ce message=20 > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi=20 > que les pieces jointes. Les messages electroniques etant susceptibles=20 > d'alteration, Orange decline toute responsabilite si ce message a ete=20 > altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or=20 > privileged information that may be protected by law; they should not=20 > be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and=20 > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have=20 > been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From R.Jesske@telekom.de Thu Sep 12 06:15:52 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3CC21E80FC for ; Thu, 12 Sep 2013 06:15:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-A+E8+AZFpc for ; Thu, 12 Sep 2013 06:15:49 -0700 (PDT) Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 6772C21E80D3 for ; Thu, 12 Sep 2013 06:15:43 -0700 (PDT) Received: from he113657.emea1.cds.t-internal.com ([10.134.99.17]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 12 Sep 2013 15:15:30 +0200 Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113657.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 12 Sep 2013 15:15:30 +0200 From: To: , Date: Thu, 12 Sep 2013 15:15:29 +0200 Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV84n4L5xZAfEGxPwbtNNvX2Jm++AOAgAAu8bCAAOQvYIAAULsAgAG/pgCAAAP9AA== Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0FA57@HE113667.emea1.cds.t-internal.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org, vijay.gurbani@alcatel-lucent.com, cuss@ietf.org Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:15:52 -0000 Full Support. Thank you. Best Regards Roland -----Urspr=FCngliche Nachricht----- Von: celine.serrutvalette@orange.com [mailto:celine.serrutvalette@orange.co= m]=20 Gesendet: Donnerstag, 12. September 2013 15:01 An: DRAGE, Keith (Keith); Jesske, Roland Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay); = cuss@ietf.org Betreff: RE: [cuss] Fwd: Re: To "isdn-network" or not Hello, As done in our proposition of July 2012, we would like to use the term of "= RECOMMENDED" as defined in RFC 2119 and it seems to us that nothing forbids= its usage in a Note. It is for instance used in this way in draft-ietf-bfc= pbis-rfc4583bis-07 in section 6: Note: In [15] 'm-stream' was erroneously used in Section 10. Although the e= xample was non-normative, it is implemented by some vendors and occurs in c= ases where the endpoint is willing to act as an server. Therefore, it is R= ECOMMENDED to support parsing and interpreting 'm-stream' the same way as '= mstrm' when receiving. Our proposed note (same as in July 2012) following this approach:=20 Note: 'isdn-interwork' value for purpose parameter was used in Internet-Dra= fts that have led to the publication of the present RFC. Although these doc= uments had not other status than "work in progress", it is implemented by s= ome vendors. Therefore, it is RECOMMENDED to support parsing and interpreti= ng 'isdn-interwork' the same way as 'isdn-uui' when receiving. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] Envoy=E9=A0: mercredi 11 septembre 2013 14:18 =C0=A0: R.Jesske@telekom.de; = SERRUT-VALETTE Celine IMT/OLN Cc=A0: draft-ietf-cuss-sip-uui-isdn@tools.iet= f.org; Gurbani, Vijay K (Vijay); cuss@ietf.org Objet=A0: RE: [cuss] Fwd: Re= : To "isdn-network" or not As in informative? I.e. no uppercase MUST or SHOULD? Keith > -----Original Message----- > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > Sent: 11 September 2013 06:30 > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, > From my understanding we had the agreement that we keep it in a Note. >=20 > Best Regards >=20 > Roalnd >=20 > -----Urspr=FCngliche Nachricht----- > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag=20 > von celine.serrutvalette@orange.com > Gesendet: Dienstag, 10. September 2013 17:58 > An: DRAGE, Keith (Keith) > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > Our preference would be that it is normative. > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part=20 > de DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0=A0= : > Gurbani, Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > Cc=A0: cuss@ietf.org > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not >=20 > All these mails keep referring to a proposed note. >=20 > However statements from the same source stated they wanted it normative. >=20 > Either it is normative, and not a note, or it is informative and we'll=20 > put it in a note. >=20 > Can you please clarify which it is. >=20 > Regards >=20 > Keith >=20 > > -----Original Message----- > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf=20 > > Of Vijay K. Gurbani > > Sent: 05 September 2013 15:42 > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc: cuss@ietf.org > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > Authors of CUSS ISDN Service draft, please advise on the matter=20 > > below regarding the availability of a new version. > > > > Thanks, > > > > -------- Original Message -------- > > Subject: Re: [cuss] To "isdn-network" or not > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > From: Vijay K. Gurbani > > Organization: Bell Laboratories, Alcatel-Lucent > > To: R.Jesske@telekom.de > > CC: cuss@ietf.org > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > [...] > > > Could we agree on counting who is OK with this Note? > > > Or can we have an alternative proposal? > > > > Roland: While not an actual count, I would note that all the people=20 > > who expressed an opinion on this --- except for Paul's observation=20 > > [1] > > --- supported the addition of the note with the understanding in [2]. > > > > As such, Enrico and I would exhort the authors of the draft to chime=20 > > in on the mailing list with their acquiescence (or questions) and=20 > > close this issue by producing a revision as soon as possible. > > > > Authors? > > > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html > > > > Thanks, > > > > - vijay > > -- > > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent=20 > > Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > > Email: vkg@{bell-labs.com,acm.org} /=20 > > 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 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 > ______________________________________________________________________ > ____ _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations=20 > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20 > exploites ou copies sans autorisation. Si vous avez recu ce message=20 > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi=20 > que les pieces jointes. Les messages electroniques etant susceptibles=20 > d'alteration, Orange decline toute responsabilite si ce message a ete=20 > altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or=20 > privileged information that may be protected by law; they should not=20 > be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and=20 > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have=20 > been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou = copies sans autorisation. Si vous avez recu ce message par erreur, veuillez= le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le= s messages electroniques etant susceptibles d'alteration, Orange decline to= ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used= or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From keith.drage@alcatel-lucent.com Thu Sep 12 06:21:08 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2179A21E8098 for ; Thu, 12 Sep 2013 06:21:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AuBmjD1RVboj for ; Thu, 12 Sep 2013 06:21:00 -0700 (PDT) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A740221E80B7 for ; Thu, 12 Sep 2013 06:21:00 -0700 (PDT) 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 r8CDKs8u008696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Sep 2013 08:20:55 -0500 (CDT) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r8CDKr3m004544 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Sep 2013 15:20:53 +0200 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Thu, 12 Sep 2013 15:20:53 +0200 From: "DRAGE, Keith (Keith)" To: "celine.serrutvalette@orange.com" , "R.Jesske@telekom.de" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkWFMWiaHadTGUCf5NicWzP73Jm/GUXw///tp4CAAOL9AIAAeK/ggAGXsICAACaqUA== Date: Thu, 12 Sep 2013 13:20:52 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "Gurbani, Vijay K \(Vijay\)" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:21:08 -0000 If we are going to do that, then I would suggest we delete the word "Note."= =20 Its presence implies there are two levels of meaning of the word "RECOMMEND= ED", those that are included in Notes and those that are not. Keith > -----Original Message----- > From: celine.serrutvalette@orange.com > [mailto:celine.serrutvalette@orange.com] > Sent: 12 September 2013 14:01 > To: DRAGE, Keith (Keith); R.Jesske@telekom.de > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay)= ; > cuss@ietf.org > Subject: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > As done in our proposition of July 2012, we would like to use the term of > "RECOMMENDED" as defined in RFC 2119 and it seems to us that nothing > forbids its usage in a Note. It is for instance used in this way in draft= - > ietf-bfcpbis-rfc4583bis-07 in section 6: >=20 > Note: In [15] 'm-stream' was erroneously used in Section 10. Although the > example was non-normative, it is implemented by some vendors and occurs i= n > cases where the endpoint is willing to act as an server. Therefore, it i= s > RECOMMENDED to support parsing and interpreting 'm-stream' the same way a= s > 'mstrm' when receiving. >=20 > Our proposed note (same as in July 2012) following this approach: > Note: 'isdn-interwork' value for purpose parameter was used in Internet- > Drafts that have led to the publication of the present RFC. Although thes= e > documents had not other status than "work in progress", it is implemented > by some vendors. Therefore, it is RECOMMENDED to support parsing and > interpreting 'isdn-interwork' the same way as 'isdn-uui' when receiving. >=20 > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] > Envoy=E9=A0: mercredi 11 septembre 2013 14:18 > =C0=A0: R.Jesske@telekom.de; SERRUT-VALETTE Celine IMT/OLN > Cc=A0: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K > (Vijay); cuss@ietf.org > Objet=A0: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > As in informative? >=20 > I.e. no uppercase MUST or SHOULD? >=20 > Keith >=20 > > -----Original Message----- > > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > > Sent: 11 September 2013 06:30 > > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K > > (Vijay); cuss@ietf.org > > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > From my understanding we had the agreement that we keep it in a Note. > > > > Best Regards > > > > Roalnd > > > > -----Urspr=FCngliche Nachricht----- > > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag > > von celine.serrutvalette@orange.com > > Gesendet: Dienstag, 10. September 2013 17:58 > > An: DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K > > (Vijay); cuss@ietf.org > > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > > > Our preference would be that it is normative. > > Regards, > > > > Celine Serrut-Valette > > Orange Labs > > > > -----Message d'origine----- > > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part > > de DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0= =A0: > > Gurbani, Vijay K (Vijay); draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc=A0: cuss@ietf.org > > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > All these mails keep referring to a proposed note. > > > > However statements from the same source stated they wanted it normative= . > > > > Either it is normative, and not a note, or it is informative and we'll > > put it in a note. > > > > Can you please clarify which it is. > > > > Regards > > > > Keith > > > > > -----Original Message----- > > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf > > > Of Vijay K. Gurbani > > > Sent: 05 September 2013 15:42 > > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > > Cc: cuss@ietf.org > > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > > > Authors of CUSS ISDN Service draft, please advise on the matter > > > below regarding the availability of a new version. > > > > > > Thanks, > > > > > > -------- Original Message -------- > > > Subject: Re: [cuss] To "isdn-network" or not > > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > > From: Vijay K. Gurbani > > > Organization: Bell Laboratories, Alcatel-Lucent > > > To: R.Jesske@telekom.de > > > CC: cuss@ietf.org > > > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > > [...] > > > > Could we agree on counting who is OK with this Note? > > > > Or can we have an alternative proposal? > > > > > > Roland: While not an actual count, I would note that all the people > > > who expressed an opinion on this --- except for Paul's observation > > > [1] > > > --- supported the addition of the note with the understanding in [2]. > > > > > > As such, Enrico and I would exhort the authors of the draft to chime > > > in on the mailing list with their acquiescence (or questions) and > > > close this issue by producing a revision as soon as possible. > > > > > > Authors? > > > > > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00487.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 > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss > > > > ______________________________________________________________________ > > ____ _______________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > > exploites ou copies sans autorisation. Si vous avez recu ce message > > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi > > que les pieces jointes. Les messages electroniques etant susceptibles > > d'alteration, Orange decline toute responsabilite si ce message a ete > > altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or > > privileged information that may be protected by law; they should not > > be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and > > delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have > > been modified, changed or falsified. > > Thank you. > > > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss >=20 > _________________________________________________________________________= _ > _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme o= u > falsifie. Merci. >=20 > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have bee= n > modified, changed or falsified. > Thank you. From vkg@bell-labs.com Thu Sep 12 06:31:46 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69AFA21E80DA for ; Thu, 12 Sep 2013 06:31:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrGxH0DpiVzc for ; Thu, 12 Sep 2013 06:31:40 -0700 (PDT) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 88D0821E80B7 for ; Thu, 12 Sep 2013 06:31:40 -0700 (PDT) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r8CDVXBl006002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Sep 2013 08:31:34 -0500 (CDT) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r8CDVWaK014161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 12 Sep 2013 08:31:33 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r8CDVIVR026090; Thu, 12 Sep 2013 08:31:18 -0500 (CDT) Message-ID: <5231C34E.2000300@bell-labs.com> Date: Thu, 12 Sep 2013 08:36:14 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: "DRAGE, Keith (Keith)" References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:31:47 -0000 On 09/12/2013 08:20 AM, DRAGE, Keith (Keith) wrote: > If we are going to do that, then I would suggest we delete the word > "Note." > > Its presence implies there are two levels of meaning of the word > "RECOMMENDED", those that are included in Notes and those that are > not. I think the group had also agreed to add that implementations conformant to the RFC-to-be MUST NOT generate 'isdn-network' when sending requests. 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 From celine.serrutvalette@orange.com Thu Sep 12 06:39:53 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52FB11E819D for ; Thu, 12 Sep 2013 06:39:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8FeAeZuG9Dz for ; Thu, 12 Sep 2013 06:39:49 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 207E211E8185 for ; Thu, 12 Sep 2013 06:39:46 -0700 (PDT) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 3E2452640E2; Thu, 12 Sep 2013 15:39:46 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A901327C046; Thu, 12 Sep 2013 15:39:31 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Thu, 12 Sep 2013 15:39:31 +0200 From: To: "Vijay K. Gurbani" Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkV84n4L5xZAfEGxPwbtNNvX2Jm++AOAgAAu8bCAAOQvYIAAULsAgAG/pgD//+Q4AIAABEsAgAAh6DA= Date: Thu, 12 Sep 2013 13:39:30 +0000 Message-ID: <22229_1378993186_5231C413_22229_3966_1_F8BE5641EC3C954DA088A8350BDDFA480D2A24@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> <5231C34E.2000300@bell-labs.com> In-Reply-To: <5231C34E.2000300@bell-labs.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.5] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.9.12.113015 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:39:54 -0000 No, I don't think so, we did not agree to add such statement. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: Vijay K. Gurbani [mailto:vkg@bell-labs.com]=20 Envoy=E9=A0: jeudi 12 septembre 2013 15:36 =C0=A0: DRAGE, Keith (Keith) Cc=A0: SERRUT-VALETTE Celine IMT/OLN; R.Jesske@telekom.de; draft-ietf-cuss-= sip-uui-isdn@tools.ietf.org; cuss@ietf.org Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not On 09/12/2013 08:20 AM, DRAGE, Keith (Keith) wrote: > If we are going to do that, then I would suggest we delete the word=20 > "Note." > > Its presence implies there are two levels of meaning of the word=20 > "RECOMMENDED", those that are included in Notes and those that are=20 > not. I think the group had also agreed to add that implementations conformant to= the RFC-to-be MUST NOT generate 'isdn-network' when sending requests. 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 ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From vkg@bell-labs.com Thu Sep 12 06:52:32 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0BA21F9FB7 for ; Thu, 12 Sep 2013 06:52:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsnQfTWiGbqu for ; Thu, 12 Sep 2013 06:52:22 -0700 (PDT) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8466B11E8185 for ; Thu, 12 Sep 2013 06:52:19 -0700 (PDT) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r8CDqFYL006589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Sep 2013 08:52:15 -0500 (CDT) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r8CDqEYd014357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 12 Sep 2013 08:52:14 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r8CDpiQX010326; Thu, 12 Sep 2013 08:51:44 -0500 (CDT) Message-ID: <5231C818.2020108@bell-labs.com> Date: Thu, 12 Sep 2013 08:56:40 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 MIME-Version: 1.0 To: celine.serrutvalette@orange.com References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> <5231C34E.2000300@bell-labs.com> <22229_1378993186_5231C413_22229_3966_1_F8BE5641EC3C954DA088A8350BDDFA480D2A24@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <22229_1378993186_5231C413_22229_3966_1_F8BE5641EC3C954DA088A8350BDDFA480D2A24@PEXCVZYM13.corporate.adroot.infra.ftgroup> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "cuss@ietf.org" Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 13:52:32 -0000 On 09/12/2013 08:39 AM, celine.serrutvalette@orange.com wrote: > No, I don't think so, we did not agree to add such statement. Celine: Never mind; it looks like I really should not read emails and post responses while being on a conference call. Cheers, - 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 From R.Jesske@telekom.de Thu Sep 12 23:05:42 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935DB11E8144 for ; Thu, 12 Sep 2013 23:05:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rdjq5Ccze3Ob for ; Thu, 12 Sep 2013 23:05:38 -0700 (PDT) Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id 3960811E811A for ; Thu, 12 Sep 2013 23:05:37 -0700 (PDT) Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 13 Sep 2013 08:05:35 +0200 Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 13 Sep 2013 08:05:34 +0200 From: To: , Date: Fri, 13 Sep 2013 08:05:31 +0200 Thread-Topic: [cuss] Fwd: Re: To "isdn-network" or not Thread-Index: AQHOqkWFMWiaHadTGUCf5NicWzP73Jm/GUXw///tp4CAAOL9AIAAeK/ggAGXsICAACaqUIABEqXw Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0FC0A@HE113667.emea1.cds.t-internal.com> References: <5213751E.8060006@bell-labs.com> <5228984A.1090106@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0A1FB5@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8934_1378828670_522F417E_8934_2004_1_F8BE5641EC3C954DA088A8350BDDFA480D281D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0EF52@HE113667.emea1.cds.t-internal.com> <949EF20990823C4C85C18D59AA11AD8B0A2BF2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <21167_1378990882_5231BB22_21167_193_7_F8BE5641EC3C954DA088A8350BDDFA480D29E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0A38E0@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org, vijay.gurbani@alcatel-lucent.com, cuss@ietf.org Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 06:05:43 -0000 Even that there are no rules in IETF what is allowed in a note to write and= what is not allowed I can agree on your proposal. So the text is then: 'isdn-interwork' value for purpose parameter was used in=20 Internet- Drafts that have led to the publication of the present RFC.=20 Although these documents had not other status than "work in progress",=20 it is implemented by some vendors. Therefore, it is RECOMMENDED to=20 support parsing and interpreting 'isdn-interwork' the same way as 'isdn-uui= ' when receiving. Best Regards Roland -----Urspr=FCngliche Nachricht----- Von: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]=20 Gesendet: Donnerstag, 12. September 2013 15:21 An: celine.serrutvalette@orange.com; Jesske, Roland Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay); = cuss@ietf.org Betreff: RE: [cuss] Fwd: Re: To "isdn-network" or not If we are going to do that, then I would suggest we delete the word "Note."= =20 Its presence implies there are two levels of meaning of the word "RECOMMEND= ED", those that are included in Notes and those that are not. Keith > -----Original Message----- > From: celine.serrutvalette@orange.com > [mailto:celine.serrutvalette@orange.com] > Sent: 12 September 2013 14:01 > To: DRAGE, Keith (Keith); R.Jesske@telekom.de > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Subject: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > As done in our proposition of July 2012, we would like to use the term=20 > of "RECOMMENDED" as defined in RFC 2119 and it seems to us that=20 > nothing forbids its usage in a Note. It is for instance used in this=20 > way in draft- > ietf-bfcpbis-rfc4583bis-07 in section 6: >=20 > Note: In [15] 'm-stream' was erroneously used in Section 10. Although=20 > the example was non-normative, it is implemented by some vendors and=20 > occurs in cases where the endpoint is willing to act as an server. =20 > Therefore, it is RECOMMENDED to support parsing and interpreting=20 > 'm-stream' the same way as 'mstrm' when receiving. >=20 > Our proposed note (same as in July 2012) following this approach: > Note: 'isdn-interwork' value for purpose parameter was used in=20 > Internet- Drafts that have led to the publication of the present RFC.=20 > Although these documents had not other status than "work in progress",=20 > it is implemented by some vendors. Therefore, it is RECOMMENDED to=20 > support parsing and interpreting 'isdn-interwork' the same way as 'isdn-u= ui' when receiving. >=20 > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] > Envoy=E9=A0: mercredi 11 septembre 2013 14:18 =C0=A0: R.Jesske@telekom.de= ;=20 > SERRUT-VALETTE Celine IMT/OLN Cc=A0:=20 > draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay);=20 > cuss@ietf.org Objet=A0: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > As in informative? >=20 > I.e. no uppercase MUST or SHOULD? >=20 > Keith >=20 > > -----Original Message----- > > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > > Sent: 11 September 2013 06:30 > > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > > (Vijay); cuss@ietf.org > > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > From my understanding we had the agreement that we keep it in a Note. > > > > Best Regards > > > > Roalnd > > > > -----Urspr=FCngliche Nachricht----- > > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag=20 > > von celine.serrutvalette@orange.com > > Gesendet: Dienstag, 10. September 2013 17:58 > > An: DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > > (Vijay); cuss@ietf.org > > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > > > Our preference would be that it is normative. > > Regards, > > > > Celine Serrut-Valette > > Orange Labs > > > > -----Message d'origine----- > > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part= =20 > > de DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0= =A0: > > Gurbani, Vijay K (Vijay);=20 > > draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc=A0: cuss@ietf.org > > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > All these mails keep referring to a proposed note. > > > > However statements from the same source stated they wanted it normative= . > > > > Either it is normative, and not a note, or it is informative and=20 > > we'll put it in a note. > > > > Can you please clarify which it is. > > > > Regards > > > > Keith > > > > > -----Original Message----- > > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On=20 > > > Behalf Of Vijay K. Gurbani > > > Sent: 05 September 2013 15:42 > > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > > Cc: cuss@ietf.org > > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > > > Authors of CUSS ISDN Service draft, please advise on the matter=20 > > > below regarding the availability of a new version. > > > > > > Thanks, > > > > > > -------- Original Message -------- > > > Subject: Re: [cuss] To "isdn-network" or not > > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > > From: Vijay K. Gurbani > > > Organization: Bell Laboratories, Alcatel-Lucent > > > To: R.Jesske@telekom.de > > > CC: cuss@ietf.org > > > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > > [...] > > > > Could we agree on counting who is OK with this Note? > > > > Or can we have an alternative proposal? > > > > > > Roland: While not an actual count, I would note that all the=20 > > > people who expressed an opinion on this --- except for Paul's=20 > > > observation [1] > > > --- supported the addition of the note with the understanding in [2]. > > > > > > As such, Enrico and I would exhort the authors of the draft to=20 > > > chime in on the mailing list with their acquiescence (or=20 > > > questions) and close this issue by producing a revision as soon as po= ssible. > > > > > > Authors? > > > > > > [1]=20 > > > http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > > [2]=20 > > > http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html > > > > > > Thanks, > > > > > > - vijay > > > -- > > > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent=20 > > > Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > > > Email: vkg@{bell-labs.com,acm.org} /=20 > > > vijay.gurbani@alcatel-lucent.com > > > Web: http://ect.bell-labs.com/who/vkg/ | Calendar: > > > http://goo.gl/x3Ogq=20 > > > _______________________________________________ > > > 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 > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss > > > > ____________________________________________________________________ > > __ ____ _______________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations=20 > > confidentielles ou privilegiees et ne doivent donc pas etre=20 > > diffuses, exploites ou copies sans autorisation. Si vous avez recu=20 > > ce message par erreur, veuillez le signaler a l'expediteur et le=20 > > detruire ainsi que les pieces jointes. Les messages electroniques=20 > > etant susceptibles d'alteration, Orange decline toute responsabilite=20 > > si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or=20 > > privileged information that may be protected by law; they should not=20 > > be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender=20 > > and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that=20 > > have been modified, changed or falsified. > > Thank you. > > > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss >=20 > ______________________________________________________________________ > ____ _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations=20 > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20 > exploites ou copies sans autorisation. Si vous avez recu ce message=20 > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi=20 > que les pieces jointes. Les messages electroniques etant susceptibles=20 > d'alteration, Orange decline toute responsabilite si ce message a ete=20 > altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or=20 > privileged information that may be protected by law; they should not=20 > be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and=20 > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have=20 > been modified, changed or falsified. > Thank you. From atle.monrad@ericsson.com Wed Sep 25 08:16:08 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B1F21F8416 for ; Wed, 25 Sep 2013 08:16:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.884 X-Spam-Level: X-Spam-Status: No, score=-5.884 tagged_above=-999 required=5 tests=[AWL=0.365, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bINGTRCbqN2x for ; Wed, 25 Sep 2013 08:16:03 -0700 (PDT) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 454EC21F9F08 for ; Wed, 25 Sep 2013 08:16:02 -0700 (PDT) X-AuditID: c1b4fb25-b7eff8e000000eda-0e-5242fe31ebe8 Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id EE.45.03802.13EF2425; Wed, 25 Sep 2013 17:16:01 +0200 (CEST) Received: from ESESSMB203.ericsson.se ([169.254.3.129]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0328.009; Wed, 25 Sep 2013 17:16:00 +0200 From: Atle Monrad To: "R.Jesske@telekom.de" , "keith.drage@alcatel-lucent.com" , "celine.serrutvalette@orange.com" Thread-Topic: [cuss] progress and completion of draft-ietf-cuss-sip-uui and draft-ietf-cuss-sip-uui-isdn Thread-Index: Ac66AXKen7sKLRLyQZ25rYCtD/m/cQ== Date: Wed, 25 Sep 2013 15:16:00 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C1A4FC5@ESESSMB203.ericsson.se> Accept-Language: nb-NO, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.148] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+Jvra7hP6cggxtv+Sw2TDzHZnGj/QWz xfGrq1gsnjaeZbRoutPFZrHp3Dp2BzaP1md7WT2WLPnJ5NHy7CSbR9tLBY8vlz+zBbBGcdmk pOZklqUW6dslcGWc/bmGseBXSMXT1c+YGhj3uXYxcnJICJhIzJwwkQ3CFpO4cG89kM3FISRw mFFiQvNSFghnCaPE+t7fTCBVbAI6Eud+3mEFSYgI7GaUWP2mGcxhFjjLKHF2+UZ2kCphgVSJ S5tegNkiAlkSizcuZYWw9SSmfVnN2MXIwcEioCpx53IUiMkr4C2x/5MniMkoICsxt4kXpJhZ QFzi1pP5TBDHCUgs2XOeGcIWlXj5+B8rhK0k0bjkCStEvZ7EjalT2CBsbYllC1+D1fMKCEqc nPmEZQKjyCwkY2chaZmFpGUWkpYFjCyrGNlzEzNz0suNNjEC4+bglt+qOxjvnBM5xCjNwaIk zrtZ70ygkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkZewd9/XoY4+c1Jf3XTykzr3uVTua5V Utx81/xYmA6U1v6I2BX+zGXX4dimN0t7TTeUG7AwFK8XXGn/w+RAY7LsOZ6jT0rO6yya5/dF oM1xU/z/XzxHplld2z6Bm9UwX/BGbrBQ67v0hNaOzdMytA2FGI4Hul5KvXhkzlQGOeWQmAdO 2n8i65VYijMSDbWYi4oTAYajvpdpAgAA Cc: "draft-ietf-cuss-sip-uui-isdn@tools.ietf.org" , "vijay.gurbani@alcatel-lucent.com" , "cuss@ietf.org" Subject: [cuss] progress and completion of draft-ietf-cuss-sip-uui and draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2013 15:16:08 -0000 All Would it be possible to get some commitment from the authors to do the fina= l work and complete the drafts progress and completion of draft-ietf-cuss-s= ip-uui and draft-ietf-cuss-sip-uui-isdn ?? The final mile for these drafts does not look that long, and it would be ap= preciated to complete the outstanding work now. It would be appreciated to be able to mark these drafts as completed before= end-of-2013. Or am I too optimistic ?? Have a nice day /atle ________________________________=20 Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation=20 Ericsson -----Original Message----- From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf Of R.J= esske@telekom.de Sent: 13. september 2013 08:06 To: keith.drage@alcatel-lucent.com; celine.serrutvalette@orange.com Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; vijay.gurbani@alcatel-luce= nt.com; cuss@ietf.org Subject: Re: [cuss] Fwd: Re: To "isdn-network" or not Even that there are no rules in IETF what is allowed in a note to write and= what is not allowed I can agree on your proposal. So the text is then: 'isdn-interwork' value for purpose parameter was used in Internet- Drafts that have led to the publication of the present RFC.=20 Although these documents had not other status than "work in progress", it i= s implemented by some vendors. Therefore, it is RECOMMENDED to support pars= ing and interpreting 'isdn-interwork' the same way as 'isdn-uui' when recei= ving. Best Regards Roland -----Urspr=FCngliche Nachricht----- Von: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] Gesendet: Donnerstag, 12. September 2013 15:21 An: celine.serrutvalette@orange.com; Jesske, Roland Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay); = cuss@ietf.org Betreff: RE: [cuss] Fwd: Re: To "isdn-network" or not If we are going to do that, then I would suggest we delete the word "Note."= =20 Its presence implies there are two levels of meaning of the word "RECOMMEND= ED", those that are included in Notes and those that are not. Keith > -----Original Message----- > From: celine.serrutvalette@orange.com > [mailto:celine.serrutvalette@orange.com] > Sent: 12 September 2013 14:01 > To: DRAGE, Keith (Keith); R.Jesske@telekom.de > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > (Vijay); cuss@ietf.org > Subject: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > Hello, >=20 > As done in our proposition of July 2012, we would like to use the term=20 > of "RECOMMENDED" as defined in RFC 2119 and it seems to us that=20 > nothing forbids its usage in a Note. It is for instance used in this=20 > way in draft- > ietf-bfcpbis-rfc4583bis-07 in section 6: >=20 > Note: In [15] 'm-stream' was erroneously used in Section 10. Although=20 > the example was non-normative, it is implemented by some vendors and=20 > occurs in cases where the endpoint is willing to act as an server. > Therefore, it is RECOMMENDED to support parsing and interpreting=20 > 'm-stream' the same way as 'mstrm' when receiving. >=20 > Our proposed note (same as in July 2012) following this approach: > Note: 'isdn-interwork' value for purpose parameter was used in > Internet- Drafts that have led to the publication of the present RFC.=20 > Although these documents had not other status than "work in progress",=20 > it is implemented by some vendors. Therefore, it is RECOMMENDED to=20 > support parsing and interpreting 'isdn-interwork' the same way as 'isdn-u= ui' when receiving. >=20 > Regards, >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] > Envoy=E9=A0: mercredi 11 septembre 2013 14:18 =C0=A0: R.Jesske@telekom.de= ;=20 > SERRUT-VALETTE Celine IMT/OLN Cc=A0: > draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K (Vijay);=20 > cuss@ietf.org Objet=A0: RE: [cuss] Fwd: Re: To "isdn-network" or not >=20 > As in informative? >=20 > I.e. no uppercase MUST or SHOULD? >=20 > Keith >=20 > > -----Original Message----- > > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de] > > Sent: 11 September 2013 06:30 > > To: celine.serrutvalette@orange.com; DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > > (Vijay); cuss@ietf.org > > Subject: AW: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > From my understanding we had the agreement that we keep it in a Note. > > > > Best Regards > > > > Roalnd > > > > -----Urspr=FCngliche Nachricht----- > > Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag=20 > > von celine.serrutvalette@orange.com > > Gesendet: Dienstag, 10. September 2013 17:58 > > An: DRAGE, Keith (Keith) > > Cc: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org; Gurbani, Vijay K=20 > > (Vijay); cuss@ietf.org > > Betreff: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > Hello, > > > > Our preference would be that it is normative. > > Regards, > > > > Celine Serrut-Valette > > Orange Labs > > > > -----Message d'origine----- > > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part= =20 > > de DRAGE, Keith (Keith) Envoy=E9=A0: mardi 10 septembre 2013 17:04 =C0= =A0: > > Gurbani, Vijay K (Vijay); > > draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > Cc=A0: cuss@ietf.org > > Objet=A0: Re: [cuss] Fwd: Re: To "isdn-network" or not > > > > All these mails keep referring to a proposed note. > > > > However statements from the same source stated they wanted it normative= . > > > > Either it is normative, and not a note, or it is informative and=20 > > we'll put it in a note. > > > > Can you please clarify which it is. > > > > Regards > > > > Keith > > > > > -----Original Message----- > > > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On=20 > > > Behalf Of Vijay K. Gurbani > > > Sent: 05 September 2013 15:42 > > > To: draft-ietf-cuss-sip-uui-isdn@tools.ietf.org > > > Cc: cuss@ietf.org > > > Subject: [cuss] Fwd: Re: To "isdn-network" or not > > > > > > Authors of CUSS ISDN Service draft, please advise on the matter=20 > > > below regarding the availability of a new version. > > > > > > Thanks, > > > > > > -------- Original Message -------- > > > Subject: Re: [cuss] To "isdn-network" or not > > > Date: Tue, 20 Aug 2013 08:54:38 -0500 > > > From: Vijay K. Gurbani > > > Organization: Bell Laboratories, Alcatel-Lucent > > > To: R.Jesske@telekom.de > > > CC: cuss@ietf.org > > > > > > On 08/20/2013 06:13 AM, R.Jesske@telekom.de wrote: > > > [...] > > > > Could we agree on counting who is OK with this Note? > > > > Or can we have an alternative proposal? > > > > > > Roland: While not an actual count, I would note that all the=20 > > > people who expressed an opinion on this --- except for Paul's=20 > > > observation [1] > > > --- supported the addition of the note with the understanding in [2]. > > > > > > As such, Enrico and I would exhort the authors of the draft to=20 > > > chime in on the mailing list with their acquiescence (or > > > questions) and close this issue by producing a revision as soon as po= ssible. > > > > > > Authors? > > > > > > [1] > > > http://www.ietf.org/mail-archive/web/cuss/current/msg00484.html > > > [2] > > > http://www.ietf.org/mail-archive/web/cuss/current/msg00487.html > > > > > > Thanks, > > > > > > - vijay > > > -- > > > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent=20 > > > Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > > > Email: vkg@{bell-labs.com,acm.org} /=20 > > > 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 > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss > > > > ____________________________________________________________________ > > __ ____ _______________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations=20 > > confidentielles ou privilegiees et ne doivent donc pas etre=20 > > diffuses, exploites ou copies sans autorisation. Si vous avez recu=20 > > ce message par erreur, veuillez le signaler a l'expediteur et le=20 > > detruire ainsi que les pieces jointes. Les messages electroniques=20 > > etant susceptibles d'alteration, Orange decline toute responsabilite=20 > > si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or=20 > > privileged information that may be protected by law; they should not=20 > > be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender=20 > > and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that=20 > > have been modified, changed or falsified. > > Thank you. > > > > _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss >=20 > ______________________________________________________________________ > ____ _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations=20 > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20 > exploites ou copies sans autorisation. Si vous avez recu ce message=20 > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi=20 > que les pieces jointes. Les messages electroniques etant susceptibles=20 > d'alteration, Orange decline toute responsabilite si ce message a ete=20 > altere, deforme ou falsifie. Merci. >=20 > This message and its attachments may contain confidential or=20 > privileged information that may be protected by law; they should not=20 > be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and=20 > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have=20 > been modified, changed or falsified. > Thank you. _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss