From vkg@bell-labs.com Mon Dec 2 07:16:18 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B871AE08D for ; Mon, 2 Dec 2013 07:16:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.001 X-Spam-Level: X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpK8GyF0xRF3 for ; Mon, 2 Dec 2013 07:16:16 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id E2B9D1A1F65 for ; Mon, 2 Dec 2013 07:16:05 -0800 (PST) Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rB2FG3bw013994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 2 Dec 2013 09:16:03 -0600 (CST) 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 rB2FG2TH024755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 2 Dec 2013 09:16:03 -0600 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 rB2FG2o9011360 for ; Mon, 2 Dec 2013 09:16:02 -0600 (CST) Message-ID: <529CA43D.3090900@bell-labs.com> Date: Mon, 02 Dec 2013 09:16:13 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: cuss@ietf.org 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.11 Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 15:16:18 -0000 Folks: The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. Below is my personal interpretation of where the matter stands, i.e., what I write below is not written as a co-chair but rather to determine if the WG agree that this is where matters now stand. Please comment if I deviate from what you all agree. - "isdn-network" is tacitly supported, but not overtly so. - More specifically, "isdn-network" is not IANA registered, and all text related to it is not normative. - The addition of the Note uses non-normative language, i.e., "The 'isdn-interwork' value for purpose parameter was used in Internet-Drafts that have led to the publication of the present RFC. Although these documents had no other status than "work in progress", this value is implemented by some vendors. Therefore, it is recommended to support parsing and interpreting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages." Is this an accurate representation? Now back with the co-chair hat on ... There has been reviews of the draft [1,2,3] by key WG members. Can the draft authors please comment on next steps with respect to revising the draft. Enrico and I will start the shepherding step in parallel to the revision to be submitted. [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq From aallen@blackberry.com Mon Dec 2 08:28:02 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4611AC499 for ; Mon, 2 Dec 2013 08:28:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c9JiqlJYxkY9 for ; Mon, 2 Dec 2013 08:27:59 -0800 (PST) Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id 8FBE71A8032 for ; Mon, 2 Dec 2013 08:27:59 -0800 (PST) Received: from xct101ads.rim.net ([10.67.111.42]) by mhs212cnc.rim.net with ESMTP/TLS/AES128-SHA; 02 Dec 2013 11:27:53 -0500 Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT101ADS.rim.net ([fe80::2c7e:1215:d554:35b5%20]) with mapi id 14.03.0158.001; Mon, 2 Dec 2013 10:27:53 -0600 From: Andrew Allen To: "vkg@bell-labs.com" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F92zk1+07b8Ee86abct8exYJpBGAEw Date: Mon, 2 Dec 2013 16:27:51 +0000 Message-ID: In-Reply-To: <529CA43D.3090900@bell-labs.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.67.110.253] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 16:28:02 -0000 I think it might be wise to indicate in the IANA registry that the value "i= sdn-network" is reserved for historical reasons and its use has been deprec= ated. ----- Original Message ----- From: Vijay K. Gurbani [mailto:vkg@bell-labs.com] Sent: Monday, December 02, 2013 10:16 AM Eastern Standard Time To: cuss@ietf.org Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Folks: The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. Below is my personal interpretation of where the matter stands, i.e., what I write below is not written as a co-chair but rather to determine if the WG agree that this is where matters now stand. Please comment if I deviate from what you all agree. - "isdn-network" is tacitly supported, but not overtly so. - More specifically, "isdn-network" is not IANA registered, and all text related to it is not normative. - The addition of the Note uses non-normative language, i.e., "The 'isdn-interwork' value for purpose parameter was used in Internet-Drafts that have led to the publication of the present RFC. Although these documents had no other status than "work in progress", this value is implemented by some vendors. Therefore, it is recommended to support parsing and interpreting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages." Is this an accurate representation? Now back with the co-chair hat on ... There has been reviews of the draft [1,2,3] by key WG members. Can the draft authors please comment on next steps with respect to revising the draft. Enrico and I will start the shepherding step in parallel to the revision to be submitted. [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html Thanks, - vijay -- = Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful. From atle.monrad@ericsson.com Mon Dec 2 22:53:52 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8121AE069 for ; Mon, 2 Dec 2013 22:53:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q93erOfm4FVI for ; Mon, 2 Dec 2013 22:53:50 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id D147D1AE066 for ; Mon, 2 Dec 2013 22:53:49 -0800 (PST) X-AuditID: c1b4fb38-b7f2c8e000006d25-bb-529d7ffa1dd0 Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id A9.F1.27941.AFF7D925; Tue, 3 Dec 2013 07:53:46 +0100 (CET) Received: from ESESSMB203.ericsson.se ([169.254.3.134]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 07:53:46 +0100 From: Atle Monrad To: Andrew Allen , "vkg@bell-labs.com" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F9QurHFH6wtESVPvq1tc09QJpBBz2AgAD0qhA= Date: Tue, 3 Dec 2013 06:53:45 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C22FC60@ESESSMB203.ericsson.se> References: <529CA43D.3090900@bell-labs.com> In-Reply-To: Accept-Language: nb-NO, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.150] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyM+Jvre6v+rlBBldXyVvcn7eV0eJG+wtm i4Y1cg7MHn2XXTxmNaxl91iy5CdTAHMUl01Kak5mWWqRvl0CV0br6tksBbdUKz6f3sHawNgi 38XIySEhYCKxfeJRFghbTOLCvfVsXYxcHEICRxglLp68zQrhLGaUeH35KjNIFZuAjsS5n3dY QWwRgRKJLZ+eMoLYwgJeEv82f2GDiHtL/H86lwXCtpKYdXguUJyDg0VAReLTqhqQMC9QyaJX a1lBwkIC2RJnjgWBmJwCnhKHZ2WDmIwCshJzm3hBipkFxCVuPZnPBHGlgMSSPeeZIWxRiZeP /7FC2EoSK7ZfYoSo15FYsPsTG4StLbFs4WtmiKWCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEj yypGjuLU4qTcdCODTYzAuDi45bfFDsbLf20OMUpzsCiJ83586xwkJJCeWJKanZpakFoUX1Sa k1p8iJGJg1OqgZFzjc9MPX/L+ydeWG75WWS/SfhZSnBKo9mdJ3KWWX9NfteoRMevvsNw4IDz xYVWR32T4nVK/LfeUPj24q7ixptbtp4+PU3adh/vifZcL8ELbVu3FdnbMR1y52aeYDHX3ej8 IgvpJyek/N/fiW92YGzh1Dur75PgHDtDPIR7fqPniZeyL2c2syixFGckGmoxFxUnAgAa11Da WQIAAA== Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 06:53:52 -0000 Folks When I came to Vancouver to discuss how to complete the draft, it was also = my understanding that the involved parties could live with an informative n= ote, thus I support Vijays conclusion.=20 I'd like to add that while [1] and [3] are easy nits, on [2] http://www.iet= f.org/mail-archive/web/cuss/current/msg00539.html, there are some further c= omments from Keith + the fact that we have moved to an informative note, th= us I'm not that sure how much that is left of this comment. Note also that if the current authors cannot find time to complete the work= rather soon, I still have the backup author - Roland Jesske. I assume that= Vijay will contact him if necessary. I would hope that 3GPP does not need = to wait for too long for completion. I'd propose to give people time until = end-of-the-week to revise the draft. __________ On the IANA-registry, I have nothing against this as long as it is formally= correct with the current phrased note by Vijay and doesn't cause more work= to the draft and/or delay the completion process. However, IMHO we shouldn= 't restart the debate if IANA-registries isn't possible without normative s= tatements in the drafts. thanks /atle ________________________________=20 Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation=20 Ericsson -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Andrew Allen Sent: 3. desember 2013 01:28 To: vkg@bell-labs.com; cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps I think it might be wise to indicate in the IANA registry that the value "i= sdn-network" is reserved for historical reasons and its use has been deprec= ated. ----- Original Message ----- From: Vijay K. Gurbani [mailto:vkg@bell-labs.com] Sent: Monday, December 02, 2013 10:16 AM Eastern Standard Time To: cuss@ietf.org Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Folks: The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. Below is my personal interpretation of where the matter stands, i.e., what = I write below is not written as a co-chair but rather to determine if the W= G agree that this is where matters now stand. Please comment if I deviate = from what you all agree. - "isdn-network" is tacitly supported, but not overtly so. - More specifically, "isdn-network" is not IANA registered, and all text related to it is not normative. - The addition of the Note uses non-normative language, i.e., "The 'isdn-interwork' value for purpose parameter was used in Internet-Drafts that have led to the publication of the present RFC. Although these documents had no other status than "work in progress", this value is implemented by some vendors. Therefore, it is recommended to support parsing and interpreting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages." Is this an accurate representation? Now back with the co-chair hat on ... There has been reviews of the draft [1,2,3] by key WG members. Can the dra= ft authors please comment on next steps with respect to revising the draft.= Enrico and I will start the shepherding step in parallel to the revision = to be submitted. [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq ___= ____________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful. _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From keith.drage@alcatel-lucent.com Mon Dec 2 22:55:55 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD741AE06A for ; Mon, 2 Dec 2013 22:55:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEpViQ13HRH8 for ; Mon, 2 Dec 2013 22:55:53 -0800 (PST) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 229BC1AE069 for ; Mon, 2 Dec 2013 22:55:53 -0800 (PST) Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rB36tklY009453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 3 Dec 2013 00:55:48 -0600 (CST) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rB36tki1024530 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Dec 2013 07:55:46 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 3 Dec 2013 07:55:46 +0100 From: "DRAGE, Keith (Keith)" To: "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F+vpEt5zUJT0eVzda+GLp/QZpCB8Eg Date: Tue, 3 Dec 2013 06:55:46 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <529CA43D.3090900@bell-labs.com> In-Reply-To: <529CA43D.3090900@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.40] 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 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 06:55:55 -0000 In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay=20 > K. Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter=20 > stands, i.e., what I write below is not written as a co-chair=20 > but rather to determine if the WG agree that this is where=20 > matters now stand. Please comment if I deviate from what you=20 > all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG=20 > members. Can the draft authors please comment on next steps=20 > with respect to revising the draft. Enrico and I will start=20 > the shepherding step in parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=20 > Thanks, >=20 > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960=20 > 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 > = From atle.monrad@ericsson.com Mon Dec 2 23:42:11 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98EB1AE080 for ; Mon, 2 Dec 2013 23:42:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbeQA4Roh_Ev for ; Mon, 2 Dec 2013 23:42:09 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id A1AF01AE045 for ; Mon, 2 Dec 2013 23:42:08 -0800 (PST) X-AuditID: c1b4fb38-b7f2c8e000006d25-b4-529d8b4d57ab Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id FD.08.27941.D4B8D925; Tue, 3 Dec 2013 08:42:05 +0100 (CET) Received: from ESESSMB203.ericsson.se ([169.254.3.134]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 08:42:04 +0100 From: Atle Monrad To: "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F+QurHFH6wtESVPvq1tc09QJpCB8EggAAMBbA= Date: Tue, 3 Dec 2013 07:42:04 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C22FCD0@ESESSMB203.ericsson.se> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: nb-NO, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.150] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvra5v99wgg7nz1SxutL9gtnjaeJbR YtO5dewOzB6tz/ayeixZ8pMpgCmKyyYlNSezLLVI3y6BK2N121K2gtkKFftO9jI3MC6V6mLk 5JAQMJG4sHINE4QtJnHh3nq2LkYuDiGBI4wSje8aWSGcxYwS39sWM4JUsQnoSJz7eQcsISIw n1Hi06VfbCAJYQEviX+bv4DZIgLeEv+fzmWBsK0krk26wA5iswioSNy+ug2shheo5vLVo2Bx IYFaiZ2nv4DVcwpES2yb0gQU5+BgFJCVmNvECxJmFhCXuPVkPtSlAhJL9pxnhrBFJV4+/scK YStJrNh+iRGiXkdiwe5PbBC2tsSyha+ZIdYKSpyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsY OYpTi5Ny040MNjECI+Pglt8WOxgv/7U5xCjNwaIkzvvxrXOQkEB6YklqdmpqQWpRfFFpTmrx IUYmDk6pBkaDU8fC2LXdBHsznxYkhV3c/98kxHmj52bZ4uRk61n+KbJ7bc80LUn10/m6fPG9 7tOWTQfWiV29vWduyI5telbtDi+r+JPeC8Tf2vjlg+Q+NZHMl6c3/zfIy/2ivUEn3n2NyMW3 SR6p37JV/mZnvDstbvjJ4LXT6gIzMwYfu+QjhRH90RMT8pRYijMSDbWYi4oTAT/xRq5aAgAA Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 07:42:11 -0000 Keith Thanks for a quick reply and an alternative phrase that at least to me also= clearly identify the point in an informative way. Good to hear that your target for completion is end-of-this-week. cheers /atle ________________________________=20 Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation=20 Ericsson -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. desember 2013 15:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter stands, i.e.,=20 > what I write below is not written as a co-chair but rather to=20 > determine if the WG agree that this is where matters now stand. =20 > Please comment if I deviate from what you all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > the draft authors please comment on next steps with respect to=20 > revising the draft. Enrico and I will start the shepherding step in=20 > parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=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 _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From christer.holmberg@ericsson.com Tue Dec 3 00:32:01 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26F981ADF9E for ; Tue, 3 Dec 2013 00:32:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nbEV3MPU_m2g for ; Tue, 3 Dec 2013 00:31:59 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id A9C351ADF7C for ; Tue, 3 Dec 2013 00:31:58 -0800 (PST) X-AuditID: c1b4fb38-b7f2c8e000006d25-98-529d96fbbeef Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 71.2F.27941.BF69D925; Tue, 3 Dec 2013 09:31:55 +0100 (CET) Received: from ESESSMB209.ericsson.se ([169.254.9.73]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 09:31:55 +0100 From: Christer Holmberg To: "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F9nOA+MwfHek6IkARSlNiZA5pB+bsAgAAreBA= Date: Tue, 3 Dec 2013 08:31:54 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.20] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUyM+Jvre7vaXODDI4eV7W40f6C2eJp41lG i03n1rE7MHu0PtvL6rFkyU+mAKYoLpuU1JzMstQifbsEroxtc9ewFbyQrWhrD2lgXCvRxcjJ ISFgIrHoYhsbhC0mceHeeiCbi0NI4AijxJ51nawQziJGifmn7gBlODjYBCwkuv9pg8RFBOYz Sny69AusW1jAS+Lf5i9gtoiAt8T/p3NZIGwriS2T3jOD2CwCKhKdHZdYQebwCvhKPFsuChIW EqiV2Hn6C1g5p0C0xLYpTewgNiPQQd9PrWECsZkFxCVuPZnPBHGogMSSPeeZIWxRiZeP/7FC 2IoSV6cvh6rXkViw+xMbhK0tsWzha7B6XgFBiZMzn7BMYBSdhWTsLCQts5C0zELSsoCRZRUj R3FqcVJuupHBJkZgVBzc8ttiB+PlvzaHGKU5WJTEeT++dQ4SEkhPLEnNTk0tSC2KLyrNSS0+ xMjEwSnVwKjgxveX+Qx3us3xme7287qKYttyf0qfNuDSC/23W3lKN0/Tg5C6B1cfbvRwq255 efZUzgSTU78zttXP/vGxt5Ff+Abbdsm43i/JHf+fdciGcuz+ui1N6ojmGZPnjHctD62IZkq4 mm9zulR/U6L1RN30N++Dl2X/vHRjWcFF0eYv306EZVyauU2JpTgj0VCLuag4EQBJ+5TSWAIA AA== Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 08:32:01 -0000 Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter stands, i.e.,=20 > what I write below is not written as a co-chair but rather to=20 > determine if the WG agree that this is where matters now stand. =20 > Please comment if I deviate from what you all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > the draft authors please comment on next steps with respect to=20 > revising the draft. Enrico and I will start the shepherding step in=20 > parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=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 _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From thomas.belling@nsn.com Tue Dec 3 01:41:08 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9B21AE099 for ; Tue, 3 Dec 2013 01:41:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-SspyNcdFaB for ; Tue, 3 Dec 2013 01:41:07 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0D81AE067 for ; Tue, 3 Dec 2013 01:41:06 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rB39f1ln000769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 3 Dec 2013 10:41:01 +0100 Received: from DEMUHTC004.nsn-intra.net ([10.159.42.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rB39f1aX013437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Dec 2013 10:41:01 +0100 Received: from DEMUHTC010.nsn-intra.net (10.159.42.41) by DEMUHTC004.nsn-intra.net (10.159.42.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 3 Dec 2013 10:41:00 +0100 Received: from DEMUMBX001.nsn-intra.net ([169.254.1.100]) by DEMUHTC010.nsn-intra.net ([10.159.42.41]) with mapi id 14.03.0123.003; Tue, 3 Dec 2013 10:41:00 +0100 From: "Belling, Thomas (NSN - DE/Munich)" To: ext Christer Holmberg , "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F+fllfx2NHFUOThp/SElEVt5pB+bsAgAAa3ACAACPiYA== Date: Tue, 3 Dec 2013 09:41:00 +0000 Message-ID: References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.42.104] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 4241 X-purgate-ID: 151667::1386063661-00006154-D9FD95AA/0-0/0-0 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 09:41:09 -0000 +1 -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of ext Christer Holmber= g Sent: Tuesday, December 03, 2013 9:32 AM To: DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter stands, i.e.,=20 > what I write below is not written as a co-chair but rather to=20 > determine if the WG agree that this is where matters now stand. > Please comment if I deviate from what you all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > the draft authors please comment on next steps with respect to=20 > revising the draft. Enrico and I will start the shepherding step in=20 > parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=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 _______________________________________________ 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 R.Jesske@telekom.de Tue Dec 3 02:46:22 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 439181AE102 for ; Tue, 3 Dec 2013 02:46:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.251 X-Spam-Level: X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USjZV84ftVTR for ; Tue, 3 Dec 2013 02:46:19 -0800 (PST) Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 6253A1AE0FA for ; Tue, 3 Dec 2013 02:46:19 -0800 (PST) Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 03 Dec 2013 11:46:15 +0100 Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 3 Dec 2013 11:46:15 +0100 From: To: , , , Date: Tue, 3 Dec 2013 11:46:14 +0100 Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F9nOA+MwfHek6IkARSlNiZA5pB+bsAgAAreBCAACWjsA== Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DF27DB88D8@HE113667.emea1.cds.t-internal.com> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> 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 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 10:46:22 -0000 +1 Roland -----Urspr=FCngliche Nachricht----- Von: cuss [mailto:cuss-bounces@ietf.org] Im Auftrag von Christer Holmberg Gesendet: Dienstag, 3. Dezember 2013 09:32 An: DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); cuss@ietf.org Betreff: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter stands, i.e.,=20 > what I write below is not written as a co-chair but rather to=20 > determine if the WG agree that this is where matters now stand. > Please comment if I deviate from what you all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > the draft authors please comment on next steps with respect to=20 > revising the draft. Enrico and I will start the shepherding step in=20 > parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=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 _______________________________________________ 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 jan.van.geel@belgacom.be Tue Dec 3 03:18:39 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C4A1AE0A0 for ; Tue, 3 Dec 2013 03:18:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6nwfmDdpBGhX for ; Tue, 3 Dec 2013 03:18:35 -0800 (PST) Received: from mx23.belgacom.be (mx23.belgacom.be [213.181.45.233]) by ietfa.amsl.com (Postfix) with ESMTP id 61D5A1AE04E for ; Tue, 3 Dec 2013 03:18:34 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.93,817,1378850400"; d="scan'208";a="41185579" Received: from a05193.bgc.net ([10.121.129.141]) by mx23.belgacom.be with ESMTP; 03 Dec 2013 12:18:05 +0100 X-TM-IMSS-Message-ID: <1d3e5930000c1ea1@belgacom.be> Received: from A04024.BGC.NET ([10.120.135.25]) by belgacom.be ([10.121.129.141]) with ESMTP (TREND IMSS SMTP Service 7.1; TLSv1/SSLv3 AES128-SHA (128/128)) id 1d3e5930000c1ea1 ; Tue, 3 Dec 2013 12:18:05 +0100 Received: from A04067.BGC.NET ([10.121.135.38]) by A04024.BGC.NET ([10.120.135.25]) with mapi id 14.02.0347.000; Tue, 3 Dec 2013 12:18:04 +0100 From: "VAN GEEL Jan (CIS/SCC)" To: "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73GGHaeOy+cHL023XsTlT4YwTJpB+bsAgAAa3ACAACWIAIAAGZfg Date: Tue, 3 Dec 2013 11:18:03 +0000 Message-ID: <1E97FFD1485F1142BC075FF145A53A1E3B794A@A04067.BGC.NET> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> <058CE00BD4D6B94FAD033A2439EA1E4B01DF27DB88D8@HE113667.emea1.cds.t-internal.com> In-Reply-To: <058CE00BD4D6B94FAD033A2439EA1E4B01DF27DB88D8@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: [10.115.28.59] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 11:18:39 -0000 +1 Jan Van Geel IT and Network Specialist Belgacom CIS/SCC/FVC Tel: +32 2 202 1035 Tel: +32 2 207 9032 Email : jan.van.geel@belgacom.be -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of R.Jesske@telekom.de Sent: Tuesday 3 December 2013 11:46 To: christer.holmberg@ericsson.com; keith.drage@alcatel-lucent.com; vijay.g= urbani@alcatel-lucent.com; cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps +1 Roland -----Urspr=FCngliche Nachricht----- Von: cuss [mailto:cuss-bounces@ietf.org] Im Auftrag von Christer Holmberg Gesendet: Dienstag, 3. Dezember 2013 09:32 An: DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); cuss@ietf.org Betreff: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K. > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps > > Folks: > > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. > > Below is my personal interpretation of where the matter stands, i.e., > what I write below is not written as a co-chair but rather to > determine if the WG agree that this is where matters now stand. > Please comment if I deviate from what you all agree. > > - "isdn-network" is tacitly supported, but not overtly so. > > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. > > - The addition of the Note uses non-normative language, i.e., > > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." > > Is this an accurate representation? > > Now back with the co-chair hat on ... > > There has been reviews of the draft [1,2,3] by key WG members. Can > the draft authors please comment on next steps with respect to > revising the draft. Enrico and I will start the shepherding step in > parallel to the revision to be submitted. > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html > > Thanks, > > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, > Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com > Web: http://ect.bell-labs.com/who/vkg/ | Calendar: > http://goo.gl/x3Ogq _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss _______________________________________________ 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 ________________________________ ***** Disclaimer ***** http://www.belgacom.be/maildisclaimer From aallen@blackberry.com Tue Dec 3 18:49:02 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 573381AD8F2 for ; Tue, 3 Dec 2013 18:49:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fi1Tf-CcCgeb for ; Tue, 3 Dec 2013 18:49:00 -0800 (PST) Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id EC2251ADEC8 for ; Tue, 3 Dec 2013 18:48:59 -0800 (PST) Received: from xct105ads.rim.net ([10.67.111.46]) by mhs212cnc.rim.net with ESMTP/TLS/AES128-SHA; 03 Dec 2013 21:48:53 -0500 Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.03.0158.001; Tue, 3 Dec 2013 20:48:52 -0600 From: Andrew Allen To: Christer Holmberg , "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F92zk1+07b8Ee86abct8exYJpCbxQAgAAa3ACAAM3V8A== Date: Wed, 4 Dec 2013 02:48:52 +0000 Message-ID: References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.67.110.251] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 02:49:02 -0000 I am also OK with Keith's proposal -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Tuesday, December 03, 2013 3:32 AM To: DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K. = > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps > = > Folks: > = > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. > = > Below is my personal interpretation of where the matter stands, i.e., = > what I write below is not written as a co-chair but rather to = > determine if the WG agree that this is where matters now stand. > Please comment if I deviate from what you all agree. > = > - "isdn-network" is tacitly supported, but not overtly so. > = > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. > = > - The addition of the Note uses non-normative language, i.e., > = > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." > = > Is this an accurate representation? > = > Now back with the co-chair hat on ... > = > There has been reviews of the draft [1,2,3] by key WG members. Can = > the draft authors please comment on next steps with respect to = > revising the draft. Enrico and I will start the shepherding step in = > parallel to the revision to be submitted. > = > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html > = > Thanks, > = > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, = > Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com > Web: http://ect.bell-labs.com/who/vkg/ | Calendar: = > http://goo.gl/x3Ogq _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > = _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful. From celine.serrutvalette@orange.com Thu Dec 5 01:52:29 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 568F11ADBC7 for ; Thu, 5 Dec 2013 01:52:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPhI4yKke071 for ; Thu, 5 Dec 2013 01:52:26 -0800 (PST) Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 71AA71ADBCB for ; Thu, 5 Dec 2013 01:52:26 -0800 (PST) Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 3CE033B4445; Thu, 5 Dec 2013 10:52:22 +0100 (CET) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 174E438406B; Thu, 5 Dec 2013 10:52:22 +0100 (CET) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Thu, 5 Dec 2013 10:52:21 +0100 From: To: Andrew Allen , Christer Holmberg , "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73GBBnWABZ08rEi0CpmaiqKMA5pB+bsAgAAa3ACAATJ9AIACGRjw Date: Thu, 5 Dec 2013 09:52:20 +0000 Message-ID: <15602_1386237142_52A04CD6_15602_4307_1_F8BE5641EC3C954DA088A8350BDDFA480FB913@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C5670C6@ESESSMB209.ericsson.se> In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.5.82715 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 09:52:29 -0000 Hello, We also agree with this proposal. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: cuss [mailto:cuss-bounces@ietf.org] De la part de Andrew Allen Envoy=E9=A0: mercredi 4 d=E9cembre 2013 03:49 =C0=A0: Christer Holmberg; DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); = cuss@ietf.org Objet=A0: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps I am also OK with Keith's proposal -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Tuesday, December 03, 2013 3:32 AM To: DRAGE, Keith (Keith); Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Hi, I think the text suggested by Keith looks good. Regards, Christer -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith) Sent: 3. joulukuuta 2013 8:56 To: Gurbani, Vijay K (Vijay); cuss@ietf.org Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps In terms of the text added, I have a preference for not using lower case fo= rms of RFC 2119 language if we can avoid it. The reasoning is that it leads= to questions as to whether the upper case form was meant, both in final re= view, publication, and by developers. If we can find therefore some other w= ording that expresses the same intent. I am having trouble thinking of some suitable wording, but my suggestion mi= ght be: "The 'isdn-interwork' value for purpose parameter was used in Internet-Draf= ts that have led to the publication of the present RFC. Although these docu= ments had no other status than "work in progress", this value is implemente= d by some vendors. While not defined by this document, implementations coul= d find it useful for interoperability purposes to support parsing and inter= preting 'isdn-interwork' the same way as 'isdn-uui' when receiving messages= ." I will work through the other comments and respond hopefully later this wee= k. Keith > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > Gurbani > Sent: 02 December 2013 15:16 > To: cuss@ietf.org > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps >=20 > Folks: >=20 > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. >=20 > Below is my personal interpretation of where the matter stands, i.e.,=20 > what I write below is not written as a co-chair but rather to=20 > determine if the WG agree that this is where matters now stand. > Please comment if I deviate from what you all agree. >=20 > - "isdn-network" is tacitly supported, but not overtly so. >=20 > - More specifically, "isdn-network" is not IANA registered, and all > text related to it is not normative. >=20 > - The addition of the Note uses non-normative language, i.e., >=20 > "The 'isdn-interwork' value for purpose parameter was used > in Internet-Drafts that have led to the publication of the > present RFC. Although these documents had no other status than > "work in progress", this value is implemented by some vendors. > Therefore, it is recommended to support parsing and interpreting > 'isdn-interwork' the same way as 'isdn-uui' when receiving > messages." >=20 > Is this an accurate representation? >=20 > Now back with the co-chair hat on ... >=20 > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > the draft authors please comment on next steps with respect to=20 > revising the draft. Enrico and I will start the shepherding step in=20 > parallel to the revision to be submitted. >=20 > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html >=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 _______________________________________________ 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 --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful. _______________________________________________ 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 keith.drage@alcatel-lucent.com Fri Dec 13 09:54:56 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F38F1AE0F4 for ; Fri, 13 Dec 2013 09:54:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3FLFgkHQJI5 for ; Fri, 13 Dec 2013 09:54:53 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9465D1ADF9E for ; Fri, 13 Dec 2013 09:54:53 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBDHshbu021017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Dec 2013 11:54:45 -0600 (CST) Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBDHsh4U000849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Dec 2013 18:54:43 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 13 Dec 2013 18:54:43 +0100 From: "DRAGE, Keith (Keith)" To: Atle Monrad , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Thread-Index: AQHO4KQz6m0bJAR+y0uBhOtWswz/6ZoxmTqAgCD8RzA= Date: Fri, 13 Dec 2013 17:54:43 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F90F4@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <5283CECB.8050804@bell-labs.com> <7D2F7D7ADBA812449F25F4A69922881C209216@ESESSMB203.ericsson.se> In-Reply-To: <7D2F7D7ADBA812449F25F4A69922881C209216@ESESSMB203.ericsson.se> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.39] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 17:54:56 -0000 As below: Keith=20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Atle Monrad > Sent: 22 November 2013 19:04 > To: Gurbani, Vijay K (Vijay); cuss@ietf.org > Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn >=20 > G'day >=20 > I have reviewed the draft again and have a couple of nits. >=20 > 1. > Abstract >=20 > The motivation and use cases for interworking and=20 > transporting ITU-T > DSS1 User-user information element data in SIP are described in the > "Problem Statement and Requirements for Transporting User to User > Call Control Information in SIP" document. As networks move to SIP > it is important that applications requiring this data can=20 > continue to > function in SIP networks as well as the ability to interwork with > this ISDN service for end-to- end transparency. >=20 > Remove space: this ISDN service for end-to-end transparency. >=20 Done - seems to be something xml2rfc does that I was not expecting - hopefu= lly changed the source so it does not happen. > 2. > 3.2. Impacts of the ISDN service on SIP operation >=20 > The ISDN service has the following impacts that need to be=20 > understood > within the SIP environment. >=20 > Call transfer ISDN call transfer cancels all user-to-user > supplementary services. In the ISDN, if user-to-user data is > required after call transfer, then UUS3 has to be renegotiated, > which is not provided by this SIP extension. The impact of this > restriction on the SIP environment is that UUI header fields > cannot be exchanged in transactions clearing down the SIP dialog > after call transfer has occurred. >=20 > Conference ISDN conferencing allows the user to still=20 > exchange user- > to-user data after the conference is created. As far as UUS1 is > concerned, it is not permitted. >=20 > The ISDN three-party supplementary service is similar=20 > in many ways > to conferencing, but is signalled using a different mechanism. > This means that on clearing, the controller using UUS1 implicit > does have the choice of sending data to either or both remote > users. Because SIP conferencing cannot completely emulate the > ISDN three-party supplementary service at the served user, UUS1 > implicit is not possible. >=20 > Diversion When ISDN diversion occurs, any UUS1=20 > user-to-user data is > sent to the forwarded-to-user (assuming that the call meets > requirements for providing the service - this is impacted by the > explicit service only). If the type of diversion is=20 > such that the > call is also delivered to the forwarding user, they will also > receive any UUS1 user-to-user data. >=20 > Would it make sense to add some NLs and/or :s after the three=20 > "ISDN SSs" to split the text and improve readability?? >=20 > e.g. like > Call transfer: > ISDN call transfer cancels all user-to-user > supplementary services. In the ISDN, if user-to-user data is > required after call transfer, then UUS3 has to be renegotiated, > which is not provided by this SIP extension. The impact of this > restriction on the SIP environment is that UUI header fields > cannot be exchanged in transactions clearing down the SIP dialog > after call transfer has occurred. > Or > Call transfer: ISDN call transfer cancels all user-to-user > supplementary services. In the ISDN, if user-to-user data is > required after call transfer, then UUS3 has to be renegotiated, > which is not provided by this SIP extension. The impact of this > restriction on the SIP environment is that UUI header fields > cannot be exchanged in transactions clearing down the SIP dialog > after call transfer has occurred. >=20 I've added the colon. New lines is beyond my xml2rfc capabilities. > ---- > I hope the draft can progress soon >=20 > Cheers > /atle >=20 > ________________________________=20 >=20 >=20 > Atle Monrad > 3GPP CT Chairman >=20 > Group Function Technology - Standardization and Technical=20 > Regulation Ericsson >=20 >=20 >=20 > -----Original Message----- > From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On=20 > Behalf Of Vijay K. Gurbani > Sent: 13. november 2013 20:11 > To: cuss@ietf.org > Subject: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn >=20 > Folks: Enrico and I will like to announce a WGLC for the ISDN=20 > draft [1]. >=20 > The WGLC will run from Wed, Nov 13 2013 to Fri, Nov 29 2013. >=20 > We will appreciate your comments on the draft, posted to the=20 > list. All comments are appreciated, even if it is a simple=20 > one-liner saying that you believe the draft is ready, or=20 > conversely, that it is not ready (and why). >=20 > As you review the draft, as part of your WGLC review, please=20 > identify any issues that may exist in regard to compatibility=20 > with draft-ietf-cuss-uui (the mechanism draft). >=20 > Thank you. >=20 > [1] http://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ >=20 > Vijay K. Gurbani and Enrico Marocco > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > = From keith.drage@alcatel-lucent.com Fri Dec 13 10:06:12 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC0E1AE376 for ; Fri, 13 Dec 2013 10:06:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.899 X-Spam-Level: X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMkH8uehhnmA for ; Fri, 13 Dec 2013 10:06:06 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A676F1AE325 for ; Fri, 13 Dec 2013 10:06:06 -0800 (PST) Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBDI5tcv025006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Dec 2013 12:05:56 -0600 (CST) Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBDI5s5t018319 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Dec 2013 19:05:54 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Fri, 13 Dec 2013 19:05:54 +0100 From: "DRAGE, Keith (Keith)" To: Andrew Allen , "cuss@ietf.org" Thread-Topic: WGLC commentsfor draft-ietf-cuss-sip-uui-isdn Thread-Index: Ac7ms5+uqD1lEgYcTAytxv9IVdFQqgReM1aA Date: Fri, 13 Dec 2013 18:05:53 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F9109@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.39] Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B0F9109FR712WXCHMBA11zeu_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 Subject: Re: [cuss] WGLC commentsfor draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 18:06:12 -0000 --_000_949EF20990823C4C85C18D59AA11AD8B0F9109FR712WXCHMBA11zeu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable See below Keith ________________________________ From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Andrew Allen Sent: 21 November 2013 15:32 To: cuss@ietf.org Subject: [cuss] WGLC commentsfor draft-ietf-cuss-sip-uui-isdn I have reviewed draft-ietf-cuss-sip-uui-isdn Here are some NITS General: inconsistent use of User-to-User (sometimes without hyphens and so= metimes lower case u) Section 3.1 The maximum number of octets of user information that can be transported in 128 octets plus a protocol discriminator. SHOULD BE The maximum number of octets of user information that can be transported is 128 octets plus a protocol discriminator. KED: Done This sentence doesn't make sense to me. I think it needs rephrasing: Only a single user information can be transported in each message. KED: As I don't understand what you don't understand, I do not know how to = revise. It is saying you cannot put two user inforamations in a message, i.= e. SETUP can only have one, CONNECT can only have one, and so on. Tell me w= hat you want. Section 6 What happens to User-to-User header fields relating to different packages is outside the scope of this document. READS BETTER AS What happens to User-to-User header fields relating to other packages is outside the scope of this document. Done Section 8 The UAS MAY include the User-to-User header field in responses to the initial INVITE request, or the BYE requests or responses for the dialog, only where the original INVITE request included a User-to- User header field with the "purpose" header field parameter to "isdn- uui", or where no "purpose" header field parameter was included. SHOULD BE The UAS MAY include the User-to-User header field in responses to the initial INVITE request, or the BYE requests or responses for the dialog, only where the original INVITE request included a User-to- User header field with the "purpose" header field parameter set to "isdn= - uui", or where no "purpose" header field parameter was included. When receiving UUI, when multiple User-to-User header fields are received from the originating user in the same request with the "purpose" header field parameter to "isdn-uui", or with no "purpose" header field parameter, or with some combination of these, the UAC MUST discard all these header fields. SHOULD BE When receiving UUI, when multiple User-to-User header fields are received from the originating user in the same request with the "purpose" header field parameter set to "isdn-uui", or with no "purpose" header field parameter, or with some combination of these, the UAC MUST discard all these header fields. Done. Also discovered another similar instance. Section 9 A receiving SIP entity MUST ignore a received User-to-User header field if the "content" header field parameter is present and the value is some other value that "isdn-uui". SHOULD BE A receiving SIP entity MUST ignore a received User-to-User header field if the "content" header field parameter is present and the value is some other value than "isdn-uui". Done --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful. --_000_949EF20990823C4C85C18D59AA11AD8B0F9109FR712WXCHMBA11zeu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
See below
 
Keith

From: cuss [mailto:cuss-bounces@iet= f.org] On Behalf Of Andrew Allen
Sent: 21 November 2013 15:32
To: cuss@ietf.org
Subject: [cuss] WGLC commentsfor draft-ietf-cuss-sip-uui-isdn

 

I have reviewed draft-ietf-cuss-sip-uui-isdn

 

Here are some NITS

 

General: inconsistent use of User-to-User (sometimes= without hyphens and sometimes lower case u)

 

Section 3.1

 

      The maximum number of = octets of user information that can be

      transported in 128 oct= ets plus a protocol discriminator.

 

SHOULD BE

 

      The maximu=
m number of octets of user information that can be
      transporte=
d is =
128 octets plus a protocol discriminator.

 

KED: Done 

 

 This= sentence doesn’t make sense to me. I think it needs rephrasing:=

 

       =
; Only a single user information can be transported in each message.

 

KED: As I don't understand what you= don't understand, I do not know how to revise. It is saying you canno= t put two user inforamations in a message, i.e. SETUP can only have one, CONNECT can only have one, and so on. Tell me what you = want. 

 

Section 6

 

      What happe=
ns to User-to-User header fields relating to different

      packages i=
s outside the scope of this document.


 


READS BETTER AS


 


      What happe=
ns to User-to-User header fields relating to other


      packages i=
s outside the scope of this document.


 


 


Done


 


Section 8


   The UAS MAY include the User-to-User header field in r=
esponses to the


   initial INVITE request, or the BYE requests or respons=
es for the


   dialog, only where the original INVITE request include=
d a User-to-


   User header field with the "purpose" header =
field parameter to "isdn-


   uui", or where no "purpose" header fiel=
d parameter was included.


 


SHOULD BE


 


   The UAS MAY include the User-to-User header field in r=
esponses to the


   initial INVITE request, or the BYE requests or respons=
es for the


  dialog, only where the original INVITE request included=
 a User-to-


   User header field with the "purpose" header =
field parameter
set to "isdn-


   uui", or where no "purpose" header fiel=
d parameter was included.


 


 


   When receiving UUI, when multiple User-to-User header =
fields are


   received from the originating user in the same request=
 with the


   "purpose" header field parameter to "is=
dn-uui", or with no "purpose"


   header field parameter, or with some combination of th=
ese, the UAC


   MUST discard all these header fields. 



 


SHOULD BE


 


   When receiving UUI, when multiple User-to-User header =
fields are


   received from the originating user in the same request=
 with the


   "purpose" header field parameter
set to "isdn-uui", or with no &=
quot;purpose"


   header field parameter, or with some combination of th=
ese, the UAC


   MUST discard all these header fields. 



 


Done. Also discovered another similar inst=
ance. 


 


 Sect=
ion 9


 


   A receiving


   SIP entity MUST ignore a received User-to-User header =
field if the


   "content" header field parameter is present =
and the value is some


   other value that "isdn-uui".


 


SHOULD BE


 


   A receiving


   SIP entity MUST ignore a received User-to-User header =
field if the


   "content" header field parameter is present =
and the value is some


   other value
than "isdn-uui".


 


Done


 
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient is prohibited. If you have rec= eived this transmission in error, please immediately reply to the sender an= d delete this information from your system. Use, dissemination, distributio= n, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
--_000_949EF20990823C4C85C18D59AA11AD8B0F9109FR712WXCHMBA11zeu_-- From keith.drage@alcatel-lucent.com Fri Dec 13 10:14:24 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFF11AE6D9 for ; Fri, 13 Dec 2013 10:14:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FeHqHEJOh67 for ; Fri, 13 Dec 2013 10:14:22 -0800 (PST) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 320011AE6DB for ; Fri, 13 Dec 2013 10:14:21 -0800 (PST) Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rBDIECZI000780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 13 Dec 2013 12:14:14 -0600 (CST) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBDIECl6022986 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Dec 2013 19:14:12 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 13 Dec 2013 19:14:12 +0100 From: "DRAGE, Keith (Keith)" To: "DRAGE, Keith (Keith)" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps Thread-Index: AQHO73F+vpEt5zUJT0eVzda+GLp/QZpCB8EggBB3YjA= Date: Fri, 13 Dec 2013 18:14:11 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F911F@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <529CA43D.3090900@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F131F@FR712WXCHMBA11.zeu.alcatel-lucent.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.39] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37 Subject: Re: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn; next steps X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 18:14:24 -0000 I've included this in section 8 UAS requirements as a new 5th paragraph Keith=20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of DRAGE,=20 > Keith (Keith) > Sent: 03 December 2013 06:56 > To: Gurbani, Vijay K (Vijay); cuss@ietf.org > Subject: Re: [cuss] WGLC done for=20 > draft-ietf-cuss-sip-uui-isdn; next steps >=20 > In terms of the text added, I have a preference for not using=20 > lower case forms of RFC 2119 language if we can avoid it. The=20 > reasoning is that it leads to questions as to whether the=20 > upper case form was meant, both in final review, publication,=20 > and by developers. If we can find therefore some other=20 > wording that expresses the same intent. >=20 > I am having trouble thinking of some suitable wording, but my=20 > suggestion might be: >=20 > "The 'isdn-interwork' value for purpose parameter was used in=20 > Internet-Drafts that have led to the publication of the=20 > present RFC. Although these documents had no other status=20 > than "work in progress", this value is implemented by some=20 > vendors. While not defined by this document, implementations=20 > could find it useful for interoperability purposes to support=20 > parsing and interpreting 'isdn-interwork' the same way as=20 > 'isdn-uui' when receiving messages." >=20 > I will work through the other comments and respond hopefully=20 > later this week. >=20 > Keith >=20 > > -----Original Message----- > > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Vijay K.=20 > > Gurbani > > Sent: 02 December 2013 15:16 > > To: cuss@ietf.org > > Subject: [cuss] WGLC done for draft-ietf-cuss-sip-uui-isdn;=20 > next steps > >=20 > > Folks: > >=20 > > The WGLC for draft-ietf-cuss-sip-uui-isdn is now over. > >=20 > > Below is my personal interpretation of where the matter=20 > stands, i.e.,=20 > > what I write below is not written as a co-chair but rather to=20 > > determine if the WG agree that this is where matters now stand. =20 > > Please comment if I deviate from what you all agree. > >=20 > > - "isdn-network" is tacitly supported, but not overtly so. > >=20 > > - More specifically, "isdn-network" is not IANA registered, and all > > text related to it is not normative. > >=20 > > - The addition of the Note uses non-normative language, i.e., > >=20 > > "The 'isdn-interwork' value for purpose parameter was used > > in Internet-Drafts that have led to the publication of the > > present RFC. Although these documents had no other status than > > "work in progress", this value is implemented by some vendors. > > Therefore, it is recommended to support parsing and=20 > interpreting > > 'isdn-interwork' the same way as 'isdn-uui' when receiving > > messages." > >=20 > > Is this an accurate representation? > >=20 > > Now back with the co-chair hat on ... > >=20 > > There has been reviews of the draft [1,2,3] by key WG members. Can=20 > > the draft authors please comment on next steps with respect to=20 > > revising the draft. Enrico and I will start the=20 > shepherding step in=20 > > parallel to the revision to be submitted. > >=20 > > [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00531.html > > [2] http://www.ietf.org/mail-archive/web/cuss/current/msg00539.html > > [3] http://www.ietf.org/mail-archive/web/cuss/current/msg00522.html > >=20 > > Thanks, > >=20 > > - vijay > > -- > > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960=20 > Lucent Lane,=20 > > 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:=20 > > http://goo.gl/x3Ogq _______________________________________________ > > cuss mailing list > > cuss@ietf.org > > https://www.ietf.org/mailman/listinfo/cuss > >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > = From keith.drage@alcatel-lucent.com Sun Dec 15 19:25:38 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA29C1AE25A for ; Sun, 15 Dec 2013 19:25:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHhOlyyBPyTN for ; Sun, 15 Dec 2013 19:25:32 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 15EE91AE231 for ; Sun, 15 Dec 2013 19:25:31 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rBG3PTFF026672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 15 Dec 2013 21:25:30 -0600 (CST) 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 rBG3PSkQ024379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Dec 2013 04:25:28 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 16 Dec 2013 04:25:28 +0100 From: "DRAGE, Keith (Keith)" To: "celine.serrutvalette@orange.com" , "Gurbani, Vijay K (Vijay)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Thread-Index: AQHO4KQz6m0bJAR+y0uBhOtWswz/6Zo61B+AgBuD74A= Date: Mon, 16 Dec 2013 03:25:27 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F9917@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <5283CECB.8050804@bell-labs.com> <681_1385654486_529768D6_681_2889_1_b84635f4-ca26-4417-911b-a5721866222a@PEXCVZYH01.corporate.adroot.infra.ftgroup> In-Reply-To: <681_1385654486_529768D6_681_2889_1_b84635f4-ca26-4417-911b-a5721866222a@PEXCVZYH01.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.35 Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 03:25:39 -0000 See below. I will issue the version without the last two changes, but if the discussio= n identifies some other text with which the group agrees, a new version can= always be issued. Regards Keith=20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of=20 > celine.serrutvalette@orange.com > Sent: 28 November 2013 16:01 > To: Gurbani, Vijay K (Vijay); cuss@ietf.org > Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn >=20 > Hello, >=20 > Please find below some comments: >=20 > 1/ About "isdn-interwork" versus "isdn-uui" purpose parameter value:=20 >=20 > The discussions on the "[cuss] "isdn-uui" versus=20 > "isdn-network"" email thread confirmed that there is still=20 > support from other cuss participants for addressing the use=20 > of the "isdn-network" parameter value. So, we don't think the=20 > document can be published without addressing this issue. We=20 > also understand that at least one company would not accept=20 > replacing "RECOMMEND" with "MUST", so we propose to stick to=20 > the initial approach (cf=20 > http://www.ietf.org/mail-archive/web/cuss/current/msg00509.htm > l ) and add the following text in section 11: >=20 > "The 'isdn-interwork' value for purpose parameter was used in=20 > Internet-Drafts that have led to the publication of the=20 > present RFC. Although these documents had no other status=20 > than "work in progress", this value is implemented by some=20 > vendors. Therefore, it is RECOMMENDED to support parsing and=20 > interpreting 'isdn-interwork' the same way as 'isdn-uui' when=20 > receiving." >=20 This one has been dealt with in a separate dialog, and the text agreed as a= result of that dialog incorporated. > 2/ About UAC and UAS procedures: >=20 > After having compared the UAC and UAS procedures in sections=20 > 7 and 8, I noticed that 2 UAC procedures could be replicated=20 > as UAS procedures as well, so I would suggest to add in section 7: > "When receiving UUI, when a User-to-User header field is=20 > received in a response that is not from the originating user=20 > with the "purpose" header field parameter to "isdn-uui", or=20 > with no "purpose" header field parameter, the UAS MUST=20 > discard this header field." > (this procedure seems not present for UAS) >=20 Section 7 is the UAC procedures, and therefore material will never be from = the originating user. This requirement was drafted because UUS1 in ISDN can only be originated fr= om the originating user and therefore this is a unidirectional requirement. Therefore I do not see the need for an equivalent procedure in clause 7. > And to add in section 8: > "When sending UUI for the ISDN package, if the "purpose"=20 > header field is included, the UAS MUST set the User-to-User=20 > "purpose" header field parameter to "isdn-uui"." > (this procedure is present for UAS but not so explicitly written) >=20 Section 8 includes: The UAS MAY include the User-to-User header field in responses to the initial INVITE request, or the BYE requests or responses for the dialog, only where the original INVITE request included a User-to- User header field with the "purpose" header field parameter to "isdn- uui", or where no "purpose" header field parameter was included. When sending UUI for the ISDN package, the UAS SHOULD set the User- to-User "purpose" header field parameter to "isdn-uui". Non- inclusion of the "purpose" header field parameter is permitted, but this is primarily to allow earlier implementations to support this package. The UAS MUST NOT include more than one User-to-User header field for this package in any SIP request or response. Does this not effectively say that. > It could be worthwhile to add them in order to be symmetric=20 > when a procedure is common to both UAC and UAS, otherwise=20 > people could wonder if it means that they are just missing or=20 > if it means that they are not applicable. >=20 >=20 > We would like these 1/ and 2/ comments to be taken into=20 > account before the ISDN draft becomes a RFC. > Thank you in advance. >=20 > Best regards >=20 > Celine Serrut-Valette > Orange Labs >=20 > -----Message d'origine----- > De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De=20 > la part de Vijay K. Gurbani Envoy=E9=A0: mercredi 13 novembre=20 > 2013 20:11 =C0=A0: cuss@ietf.org Objet=A0: [cuss] WGLC for=20 > draft-ietf-cuss-sip-uui-isdn >=20 > Folks: Enrico and I will like to announce a WGLC for the ISDN=20 > draft [1]. >=20 > The WGLC will run from Wed, Nov 13 2013 to Fri, Nov 29 2013. >=20 > We will appreciate your comments on the draft, posted to the=20 > list. All comments are appreciated, even if it is a simple=20 > one-liner saying that you believe the draft is ready, or=20 > conversely, that it is not ready (and why). >=20 > As you review the draft, as part of your WGLC review, please=20 > identify any issues that may exist in regard to compatibility=20 > with draft-ietf-cuss-uui (the mechanism draft). >=20 > Thank you. >=20 > [1] http://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ >=20 > Vijay K. Gurbani and Enrico Marocco > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >=20 > ______________________________________________________________ > ___________________________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des=20 > informations confidentielles ou privilegiees et ne doivent=20 > donc pas etre diffuses, exploites ou copies sans=20 > autorisation. Si vous avez recu ce message par erreur,=20 > veuillez le signaler a l'expediteur et le detruire ainsi que=20 > les pieces jointes. Les messages electroniques etant=20 > susceptibles d'alteration, Orange decline toute=20 > responsabilite si ce message a ete 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=20 > should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the=20 > sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages=20 > that have been modified, changed or falsified. > Thank you. >=20 > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss > = From internet-drafts@ietf.org Sun Dec 15 19:43:15 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5E91AE02B; Sun, 15 Dec 2013 19:43:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5wlzbvygdDE; Sun, 15 Dec 2013 19:43:10 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE651AE039; Sun, 15 Dec 2013 19:43:10 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131216034309.25823.65337.idtracker@ietfa.amsl.com> Date: Sun, 15 Dec 2013 19:43:09 -0800 Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 16 Dec 2013 03:43:16 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Call Control UUI Service for SIP Working = Group of the IETF. Title : Interworking ISDN Call Control User Information with SIP Author(s) : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-06.txt Pages : 19 Date : 2013-12-15 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in the "Problem Statement and Requirements for Transporting User to User Call Control Information in SIP" document. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document defines a usage (a new package) of the User-to-User header field to enable interworking with this ISDN service. This document covers the interworking with both public ISDN and private ISDN capabilities, so the potential interworking with QSIG will also be addressed. The package is identified by a new value "isdn-uui" of the "purpose" header field parameter. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From keith.drage@alcatel-lucent.com Sun Dec 15 19:46:35 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25E21AE25A for ; Sun, 15 Dec 2013 19:46:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7jE0gYqRkfCf for ; Sun, 15 Dec 2013 19:46:30 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5871AE02B for ; Sun, 15 Dec 2013 19:46:29 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rBG3kRja002530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sun, 15 Dec 2013 21:46:28 -0600 (CST) 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 rBG3kQv2028867 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 16 Dec 2013 04:46:26 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 16 Dec 2013 04:46:26 +0100 From: "DRAGE, Keith (Keith)" To: "cuss@ietf.org" Thread-Topic: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt Thread-Index: AQHO+hD6cV7wK0CaLkeZJBlN+FB4iZpWLf3g Date: Mon, 16 Dec 2013 03:46:25 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0F9949@FR712WXCHMBA11.zeu.alcatel-lucent.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.35 Subject: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 03:46:36 -0000 I've made updates in accordance with the changes I've posted to the list ov= er the last few days. You will not I have not at the moment accepted some of the comments, either= because, in one case, I was not sure what the issue is, in a second case b= ecause I considered the comment was incorrect and in the third case because= I considered the text already provided this. The most significant change in the document is the acceptance of the new in= formative paragraph regarding isdninterwork purpose value. Regards Keith -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 16 December 2013 03:43 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Call Control UUI Service for SIP Working = Group of the IETF. Title : Interworking ISDN Call Control User Information with SIP Author(s) : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-06.txt Pages : 19 Date : 2013-12-15 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in the "Problem Statement and Requirements for Transporting User to User Call Control Information in SIP" document. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document defines a usage (a new package) of the User-to-User header field to enable interworking with this ISDN service. This document covers the interworking with both public ISDN and private ISDN capabilities, so the potential interworking with QSIG will also be addressed. The package is identified by a new value "isdn-uui" of the "purpose" header field parameter. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-06 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From R.Jesske@telekom.de Sun Dec 15 22:07:03 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7346E1AE2B3 for ; Sun, 15 Dec 2013 22:07:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.088 X-Spam-Level: X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6f5qOChq9eqM for ; Sun, 15 Dec 2013 22:07:00 -0800 (PST) Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 84C341ADFEE for ; Sun, 15 Dec 2013 22:06:59 -0800 (PST) Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 16 Dec 2013 07:06:57 +0100 Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 16 Dec 2013 07:06:57 +0100 From: To: , Date: Mon, 16 Dec 2013 07:06:55 +0100 Thread-Topic: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt Thread-Index: AQHO+hD6cV7wK0CaLkeZJBlN+FB4iZpWLf3ggAAnWSA= Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DF282AC0F1@HE113667.emea1.cds.t-internal.com> References: <949EF20990823C4C85C18D59AA11AD8B0F9949@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F9949@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 Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 06:07:03 -0000 Hi Keith, Thank you for your draft.=20 I'm happy with all changes you did.=20 >From my side we can proceed with publication. Best Regards Roland -----Urspr=FCngliche Nachricht----- Von: cuss [mailto:cuss-bounces@ietf.org] Im Auftrag von DRAGE, Keith (Keith= ) Gesendet: Montag, 16. Dezember 2013 04:46 An: cuss@ietf.org Betreff: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt I've made updates in accordance with the changes I've posted to the list ov= er the last few days. You will not I have not at the moment accepted some of the comments, either= because, in one case, I was not sure what the issue is, in a second case b= ecause I considered the comment was incorrect and in the third case because= I considered the text already provided this. The most significant change in the document is the acceptance of the new in= formative paragraph regarding isdninterwork purpose value. Regards Keith -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 16 December 2013 03:43 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Call Control UUI Service for SIP Working = Group of the IETF. Title : Interworking ISDN Call Control User Information with SIP Author(s) : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-06.txt Pages : 19 Date : 2013-12-15 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in the "Problem Statement and Requirements for Transporting User to User Call Control Information in SIP" document. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document defines a usage (a new package) of the User-to-User header field to enable interworking with this ISDN service. This document covers the interworking with both public ISDN and private ISDN capabilities, so the potential interworking with QSIG will also be addressed. The package is identified by a new value "isdn-uui" of the "purpose" header field parameter. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-06 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ 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 thomas.belling@nsn.com Mon Dec 16 01:56:59 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869321ADBC7 for ; Mon, 16 Dec 2013 01:56:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qj8QrekaxUcx for ; Mon, 16 Dec 2013 01:56:53 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 6D68C1ADDAC for ; Mon, 16 Dec 2013 01:56:52 -0800 (PST) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rBG9ulEQ010086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 16 Dec 2013 10:56:47 +0100 Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rBG9ullh002286 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Dec 2013 10:56:47 +0100 Received: from DEMUHTC010.nsn-intra.net (10.159.42.41) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 16 Dec 2013 10:56:47 +0100 Received: from DEMUMBX001.nsn-intra.net ([169.254.1.134]) by DEMUHTC010.nsn-intra.net ([10.159.42.41]) with mapi id 14.03.0123.003; Mon, 16 Dec 2013 10:56:47 +0100 From: "Belling, Thomas (NSN - DE/Munich)" To: "keith.drage@alcatel-lucent.com" , "cuss@ietf.org" Thread-Topic: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt Thread-Index: AQHO+hD6cV7wK0CaLkeZJBlN+FB4iZpWLf3ggAAnWSCAAEBpwA== Date: Mon, 16 Dec 2013 09:56:46 +0000 Message-ID: References: <949EF20990823C4C85C18D59AA11AD8B0F9949@FR712WXCHMBA11.zeu.alcatel-lucent.com> <058CE00BD4D6B94FAD033A2439EA1E4B01DF282AC0F1@HE113667.emea1.cds.t-internal.com> In-Reply-To: <058CE00BD4D6B94FAD033A2439EA1E4B01DF282AC0F1@HE113667.emea1.cds.t-internal.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.42.109] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 4020 X-purgate-ID: 151667::1387187808-00001A6F-FB1F7D2C/0-0/0-0 Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 09:56:59 -0000 Thanks, Keith. I also believe that we are finally ready to approve this draft. BR, Thomas ---------------------------------- Dr. Thomas Belling=20 3GPP Standardisation NSN -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of ext R.Jesske@telekom= .de Sent: Monday, December 16, 2013 7:07 AM To: keith.drage@alcatel-lucent.com; cuss@ietf.org Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt Hi Keith, Thank you for your draft.=20 I'm happy with all changes you did.=20 >From my side we can proceed with publication. Best Regards Roland -----Urspr=FCngliche Nachricht----- Von: cuss [mailto:cuss-bounces@ietf.org] Im Auftrag von DRAGE, Keith (Keith= ) Gesendet: Montag, 16. Dezember 2013 04:46 An: cuss@ietf.org Betreff: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt I've made updates in accordance with the changes I've posted to the list ov= er the last few days. You will not I have not at the moment accepted some of the comments, either= because, in one case, I was not sure what the issue is, in a second case b= ecause I considered the comment was incorrect and in the third case because= I considered the text already provided this. The most significant change in the document is the acceptance of the new in= formative paragraph regarding isdninterwork purpose value. Regards Keith -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 16 December 2013 03:43 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-06.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Call Control UUI Service for SIP Working = Group of the IETF. Title : Interworking ISDN Call Control User Information with SIP Author(s) : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-06.txt Pages : 19 Date : 2013-12-15 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in the "Problem Statement and Requirements for Transporting User to User Call Control Information in SIP" document. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document defines a usage (a new package) of the User-to-User header field to enable interworking with this ISDN service. This document covers the interworking with both public ISDN and private ISDN capabilities, so the potential interworking with QSIG will also be addressed. The package is identified by a new value "isdn-uui" of the "purpose" header field parameter. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-06 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ 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 From celine.serrutvalette@orange.com Mon Dec 16 06:57:34 2013 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258061AE32E for ; Mon, 16 Dec 2013 06:57:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42lFY9SPWZAD for ; Mon, 16 Dec 2013 06:57:31 -0800 (PST) Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 1875E1ADFDC for ; Mon, 16 Dec 2013 06:57:30 -0800 (PST) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 6140F2660EF; Mon, 16 Dec 2013 15:57:29 +0100 (CET) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 3E06E27C069; Mon, 16 Dec 2013 15:57:29 +0100 (CET) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Mon, 16 Dec 2013 15:57:29 +0100 From: To: "DRAGE, Keith (Keith)" , "cuss@ietf.org" Thread-Topic: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn Thread-Index: AQHO4KQz6m0bJAR+y0uBhOtWswz/6Zo61B+AgBuD74CAAKM9IA== Date: Mon, 16 Dec 2013 14:57:28 +0000 Message-ID: <11023_1387205849_52AF14D9_11023_2363_1_F8BE5641EC3C954DA088A8350BDDFA480FF883@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <5283CECB.8050804@bell-labs.com> <681_1385654486_529768D6_681_2889_1_b84635f4-ca26-4417-911b-a5721866222a@PEXCVZYH01.corporate.adroot.infra.ftgroup> <949EF20990823C4C85C18D59AA11AD8B0F9917@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F9917@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.3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.16.140017 Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 14:57:34 -0000 Hello, Thank you for the update of the ISDN draft. I have just some comments or questions below on your answers to my previous= comments: 1/ The text about "isdn-interwork" is in section 8 "UAS requirements" but i= t is also applicable to other sections, for instance to section 7 "UAC requ= irements" (when UAC receives UUI in responses), so could it be replicated i= n section 7 "UAC requirements" or only put once in section 11 "Coding requi= rements" in order to be global, as you prefer? Note just an editorial comment: in section 16 about changes, "ISDNinterwork= " purpose value should be replaced by "isdn-interwork". 2/A/ I agree with your comment on "originating user". But I think it would = be better to clarify the expected behavior by UAS [respectively by UAC] on = reception of User-to-User that is not with the "purpose" parameter to "isdn= -uui", or with no "purpose" parameter, in a request [respectively in a resp= onse], as follows:=20=20 "When receiving UUI, when a User-to-User header field is received in a requ= est that is not from the originating user with the "purpose" header field p= arameter to "isdn-uui", or with no "purpose" header field parameter, the UA= C MUST discard this header field." =3D> this sentence of the draft is ok bu= t "UAC" should be replaced by "UAS", isn't it? Because it's the UAS that re= ceives the request containing UUI sent by UAC (same comment for sentences b= eginning by "When receiving UUI, when multiple User-to-User header [...]", = it seems to me that "UAS" and "UAC" are inverted). "When receiving UUI, when a User-to-User header field is received in a resp= onse that is not with the "purpose" header field parameter to "isdn-uui", o= r with no "purpose" header field parameter, the UAC MUST discard this heade= r field." =3D> this sentence could be added in order to specify the UAC beh= avior when it receives unexpected UUI in a response from the UAS. 2/B/ Yes the sentence "When sending UUI for the ISDN package, the UAS SHOUL= D set the User-to-User "purpose" header field parameter to "isdn-uui". Non= -inclusion of the "purpose" [...]" is well present in both sections 7 and 8= .=20 But the sentence "When sending UUI for the ISDN package, if the "purpose" h= eader field is included, the UAC MUST set the User-to-User "purpose" header= field parameter to "isdn-uui"." is only present in section 7 but not in se= ction 8, why? (first sentence aims at recommending to include a purpose par= ameter using a SHOULD whereas second sentence clarifies the required value = using a MUST)=20=20 Thank you for your clarifications. Best regards =20 Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]=20 Envoy=E9=A0: lundi 16 d=E9cembre 2013 04:25 =C0=A0: SERRUT VALETTE Celine IMT/OLN; Gurbani, Vijay K (Vijay); cuss@ietf.= org Objet=A0: RE: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn See below. I will issue the version without the last two changes, but if the discussio= n identifies some other text with which the group agrees, a new version can= always be issued. Regards Keith=20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of=20 > celine.serrutvalette@orange.com > Sent: 28 November 2013 16:01 > To: Gurbani, Vijay K (Vijay); cuss@ietf.org > Subject: Re: [cuss] WGLC for draft-ietf-cuss-sip-uui-isdn >=20 > Hello, >=20 > Please find below some comments: >=20 > 1/ About "isdn-interwork" versus "isdn-uui" purpose parameter value:=20 >=20 > The discussions on the "[cuss] "isdn-uui" versus "isdn-network"" email=20 > thread confirmed that there is still support from other cuss=20 > participants for addressing the use of the "isdn-network" parameter=20 > value. So, we don't think the document can be published without=20 > addressing this issue. We also understand that at least one company=20 > would not accept replacing "RECOMMEND" with "MUST", so we propose to=20 > stick to the initial approach (cf=20 > http://www.ietf.org/mail-archive/web/cuss/current/msg00509.htm > l ) and add the following text in section 11: >=20 > "The '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 no other status than "work in progress",=20 > this value is implemented by some vendors. Therefore, it is=20 > RECOMMENDED to support parsing and interpreting 'isdn-interwork' the=20 > same way as 'isdn-uui' when receiving." >=20 This one has been dealt with in a separate dialog, and the text agreed as a= result of that dialog incorporated. > 2/ About UAC and UAS procedures: >=20 > After having compared the UAC and UAS procedures in sections > 7 and 8, I noticed that 2 UAC procedures could be replicated as UAS=20 > procedures as well, so I would suggest to add in section 7: > "When receiving UUI, when a User-to-User header field is received in a=20 > response that is not from the originating user with the "purpose"=20 > header field parameter to "isdn-uui", or with no "purpose" header=20 > field parameter, the UAS MUST discard this header field." > (this procedure seems not present for UAS) >=20 Section 7 is the UAC procedures, and therefore material will never be from = the originating user. This requirement was drafted because UUS1 in ISDN can only be originated fr= om the originating user and therefore this is a unidirectional requirement. Therefore I do not see the need for an equivalent procedure in clause 7. > And to add in section 8: > "When sending UUI for the ISDN package, if the "purpose"=20 > header field is included, the UAS MUST set the User-to-User "purpose"=20 > header field parameter to "isdn-uui"." > (this procedure is present for UAS but not so explicitly written) >=20 Section 8 includes: The UAS MAY include the User-to-User header field in responses to the initial INVITE request, or the BYE requests or responses for the dialog, only where the original INVITE request included a User-to- User header field with the "purpose" header field parameter to "isdn- uui", or where no "purpose" header field parameter was included. When sending UUI for the ISDN package, the UAS SHOULD set the User- to-User "purpose" header field parameter to "isdn-uui". Non- inclusion of the "purpose" header field parameter is permitted, but this is primarily to allow earlier implementations to support this package. The UAS MUST NOT include more than one User-to-User header field for this package in any SIP request or response. Does this not effectively say that. > It could be worthwhile to add them in order to be symmetric when a=20 > procedure is common to both UAC and UAS, otherwise people could wonder=20 > if it means that they are just missing or if it means that they are=20 > not applicable. >=20 >=20 > We would like these 1/ and 2/ comments to be taken into account before=20 > the ISDN draft becomes a RFC. > Thank you in advance. >=20 > Best 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 Vijay K. Gurbani Envoy=E9=A0: mercredi 13 novembre > 2013 20:11 =C0=A0: cuss@ietf.org Objet=A0: [cuss] WGLC for=20 > draft-ietf-cuss-sip-uui-isdn >=20 > Folks: Enrico and I will like to announce a WGLC for the ISDN draft=20 > [1]. >=20 > The WGLC will run from Wed, Nov 13 2013 to Fri, Nov 29 2013. >=20 > We will appreciate your comments on the draft, posted to the list.=20=20 > All comments are appreciated, even if it is a simple one-liner saying=20 > that you believe the draft is ready, or conversely, that it is not=20 > ready (and why). >=20 > As you review the draft, as part of your WGLC review, please identify=20 > any issues that may exist in regard to compatibility with=20 > draft-ietf-cuss-uui (the mechanism draft). >=20 > Thank you. >=20 > [1] http://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ >=20 > Vijay K. Gurbani and Enrico Marocco > _______________________________________________ > 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 >=20 ___________________________________________________________________________= ______________________________________________ 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.