From vkg@bell-labs.com Mon Jul 2 08:30:36 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6112821F8705 for ; Mon, 2 Jul 2012 08:30:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.599 X-Spam-Level: X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gar0wl2+J4z7 for ; Mon, 2 Jul 2012 08:30:32 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 743B921F86B8 for ; Mon, 2 Jul 2012 08:30:32 -0700 (PDT) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q62FUUCc016281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 2 Jul 2012 10:30:30 -0500 (CDT) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q62FUTWt032171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 2 Jul 2012 10:30:30 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q62FURGZ016620; Mon, 2 Jul 2012 10:30:27 -0500 (CDT) Message-ID: <4FF1BFF6.9070404@bell-labs.com> Date: Mon, 02 Jul 2012 10:36:22 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Alan Johnston , "Drage, Keith (Keith)" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Cc: cuss@ietf.org Subject: [cuss] Revisions of pending drafts X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2012 15:30:36 -0000 Keith, Alan: We need to move the remaining two documents ahead. I am hoping that with the impending deadlines for the Vancouver IETF, we can push these through. Note that we are not meeting face-to-face in Vancouver, but regardless, it'll be good to get done with the work since there does not seem to be any substantive open issues stopping us. The WGLC for draft-ietf-cuss-sip-uui (-06) and draft-ietf-cuss-sip-uui-isdn (-04) expired on May 27, 2012 with reviews submitted on the list. Neither Enrico nor I believe that there are any substantive open issues left. Can you please submit revised versions addressing the WGLC comments. We will like to proceed to sending the documents to IESG as soon as they become available on the list. 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/ From celine.serrutvalette@orange.com Thu Jul 5 07:44:18 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA63321F86EA for ; Thu, 5 Jul 2012 07:44:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTfdzfhINUV0 for ; Thu, 5 Jul 2012 07:44:18 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id A591C21F86E1 for ; Thu, 5 Jul 2012 07:44:17 -0700 (PDT) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 855B922C784; Thu, 5 Jul 2012 16:44:30 +0200 (CEST) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 6B39C27C053; Thu, 5 Jul 2012 16:44:30 +0200 (CEST) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Thu, 5 Jul 2012 16:44:30 +0200 From: To: "keith.drage@alcatel-lucent.com" Thread-Topic: [cuss] Status of cuss documents => purpose parameter value for ISDN Thread-Index: AQHNRLc3g2ez5iy82E2mZ4bOsx7495cRIkxggAmoVnCAACNB8A== Date: Thu, 5 Jul 2012 14:44:23 +0000 Message-ID: <20778_1341499470_4FF5A84E_20778_8501_1_F8BE5641EC3C954DA088A8350BDDFA4801B334@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <4FD0B77D.2010501@bell-labs.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.7.5.120018 Cc: "cuss@ietf.org" Subject: Re: [cuss] Status of cuss documents => purpose parameter value for ISDN X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2012 14:44:18 -0000 Hello, Since you may be currently updating the documents with the remarks received= from WGLC review, I would like to come back again on a topic previously di= scussed (see http://www.ietf.org/mail-archive/web/cuss/current/msg00355.htm= l-comment C10 and http://www.ietf.org/mail-archive/web/cuss/current/msg0041= 8.html): the value of purpose parameter for ISDN. Indeed, some implementations are currently generating purpose=3D"isdn-inter= work" (as indicated in draft-johnston-sipping-cc-uui-08) so this will cause= a backward compatibility issue because currently in the ISDN draft, if pre= sent, purpose parameter value MUST be set to "isdn-uui" and, if received, i= ts value MUST be set to "isdn-uui", otherwise the header would be discarded= (as described in sections 7 and 8 of the ISDN draft) and the interworking = not performed.=20 Since some implementations may already be using purpose=3D"isdn-uui", it ma= y not be acceptable to simply change it back to purpose=3D"isdn-interwork".= Therefore, I propose as a compromise to add the following note along the l= ine of what has been done in draft-ietf-bfcpbis-rfc4583bis-01 (section 6) f= or BFCP topic: Note: 'isdn-interwork' value for purpose parameter was used in Internet-Dra= fts that have led to the publication of the present RFC. Although these doc= uments had not other status than "work in progress", it is implemented by s= ome vendors. Therefore, it is RECOMMENDED to support parsing and interpreti= ng 'isdn-interwork' the same way as 'isdn-uui' when receiving.=20 Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part de V= ijay K. Gurbani Envoy=E9=A0: jeudi 7 juin 2012 16:15 =C0=A0: cuss@ietf.org Objet=A0: [cuss] Status of cuss documents Folks: The WGLC date for the two remaining documents has passed. The WG received a WGLC review on draft-ietf-cuss-sip-uui-06 courtesy of Laura Liess. The review for draft-ietf-cuss-sip-uui-isdn-04 is still pending, and should be out by next week. In the meantime, could the authors of draft-ietf-cuss-sip-uui please start to address the WGLC comments and sent out a revision addressing the comments? To the extent that there are dependencies between these two drafts, I suspect that cuss-sip-uui-isdn depends on cuss-sip-uui. Thus we can start preparation for cuss-sip-uui while we wait for the WGLC review of cuss-sip-uui-isdn. Thanks, Vijay K. Gurbani and Enrico Marocco _______________________________________________ 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, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, 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, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. From R.Jesske@telekom.de Sun Jul 8 22:53:37 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E3C21F84A7 for ; Sun, 8 Jul 2012 22:53:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrMV0P3qtboJ for ; Sun, 8 Jul 2012 22:53:36 -0700 (PDT) Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by ietfa.amsl.com (Postfix) with ESMTP id 089A721F84AF for ; Sun, 8 Jul 2012 22:53:32 -0700 (PDT) Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by tcmail81.telekom.de with ESMTP/TLS/AES128-SHA; 09 Jul 2012 07:53:54 +0200 Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 9 Jul 2012 07:53:52 +0200 From: To: , Date: Mon, 9 Jul 2012 07:53:51 +0200 Thread-Topic: [cuss] Status of cuss documents => purpose parameter value for ISDN Thread-Index: AQHNRLc3g2ez5iy82E2mZ4bOsx7495cRIkxggAmoVnCAACNB8IAFtu2w Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D14752FC04A@HE111648.emea1.cds.t-internal.com> References: <4FD0B77D.2010501@bell-labs.com> <20778_1341499470_4FF5A84E_20778_8501_1_F8BE5641EC3C954DA088A8350BDDFA4801B334@PEXCVZYM13.corporate.adroot.infra.ftgroup> In-Reply-To: <20778_1341499470_4FF5A84E_20778_8501_1_F8BE5641EC3C954DA088A8350BDDFA4801B334@PEXCVZYM13.corporate.adroot.infra.ftgroup> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: cuss@ietf.org Subject: Re: [cuss] Status of cuss documents => purpose parameter value for ISDN X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 05:53:37 -0000 Hi, I can agree on such a note. BR Roland Jesske -----Urspr=FCngliche Nachricht----- Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag von ce= line.serrutvalette@orange.com Gesendet: Donnerstag, 5. Juli 2012 16:44 An: keith.drage@alcatel-lucent.com Cc: cuss@ietf.org Betreff: Re: [cuss] Status of cuss documents =3D> purpose parameter value f= or ISDN Hello, Since you may be currently updating the documents with the remarks received= from WGLC review, I would like to come back again on a topic previously di= scussed (see http://www.ietf.org/mail-archive/web/cuss/current/msg00355.htm= l-comment C10 and http://www.ietf.org/mail-archive/web/cuss/current/msg0041= 8.html): the value of purpose parameter for ISDN. Indeed, some implementations are currently generating purpose=3D"isdn-inter= work" (as indicated in draft-johnston-sipping-cc-uui-08) so this will cause= a backward compatibility issue because currently in the ISDN draft, if pre= sent, purpose parameter value MUST be set to "isdn-uui" and, if received, i= ts value MUST be set to "isdn-uui", otherwise the header would be discarded= (as described in sections 7 and 8 of the ISDN draft) and the interworking = not performed. Since some implementations may already be using purpose=3D"isdn-uui", it ma= y not be acceptable to simply change it back to purpose=3D"isdn-interwork".= Therefore, I propose as a compromise to add the following note along the l= ine of what has been done in draft-ietf-bfcpbis-rfc4583bis-01 (section 6) f= or BFCP topic: Note: 'isdn-interwork' value for purpose parameter was used in Internet-Dra= fts that have led to the publication of the present RFC. Although these doc= uments had not other status than "work in progress", it is implemented by s= ome vendors. Therefore, it is RECOMMENDED to support parsing and interpreti= ng 'isdn-interwork' the same way as 'isdn-uui' when receiving. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De : cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] De la part de Vij= ay K. Gurbani Envoy=E9 : jeudi 7 juin 2012 16:15 =C0 : cuss@ietf.org Objet = : [cuss] Status of cuss documents Folks: The WGLC date for the two remaining documents has passed. The WG received a WGLC review on draft-ietf-cuss-sip-uui-06 courtesy of Lau= ra Liess. The review for draft-ietf-cuss-sip-uui-isdn-04 is still pending, and should= be out by next week. In the meantime, could the authors of draft-ietf-cuss-sip-uui please start = to address the WGLC comments and sent out a revision addressing the comment= s? To the extent that there are dependencies between these two drafts, I suspe= ct that cuss-sip-uui-isdn depends on cuss-sip-uui. Thus we can start prepa= ration for cuss-sip-uui while we wait for the WGLC review of cuss-sip-uui-i= sdn. Thanks, Vijay K. Gurbani and Enrico Marocco _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou = copies sans autorisation. Si vous avez recu ce message par erreur, veuillez= le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le= s messages electroniques etant susceptibles d'alteration, France Telecom - = 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, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you. _______________________________________________ cuss mailing list cuss@ietf.org https://www.ietf.org/mailman/listinfo/cuss From vkg@bell-labs.com Wed Jul 11 15:03:25 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5491811E810F for ; Wed, 11 Jul 2012 15:03:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -107.599 X-Spam-Level: X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dRLJ8g0egzh for ; Wed, 11 Jul 2012 15:03:25 -0700 (PDT) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6080011E813D for ; Wed, 11 Jul 2012 15:03:12 -0700 (PDT) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q6BM3gxi007000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 11 Jul 2012 17:03:43 -0500 (CDT) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q6BM3gOF013831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 11 Jul 2012 17:03:42 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q6BM3gg0012774 for ; Wed, 11 Jul 2012 17:03:42 -0500 (CDT) Message-ID: <4FFDF9A8.7050406@bell-labs.com> Date: Wed, 11 Jul 2012 17:09:44 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.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.37 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Subject: [cuss] NomCom 2012-13 call for volunteers X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2012 22:03:25 -0000 Folks: The NomCom call for volunteers is now open. Please consider volunteering on it if you can. Thanks, ---------- Forwarded message ---------- From: NomCom Chair Date: Fri, Jul 6, 2012 at 2:15 PM Subject: NomCom 2012-13 Call for Volunteers To: IETF Announcement List The IETF nominating committee process for 2012-13 has begun. The IETF nominating committee appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. The 10 nominating committee members are selected randomly from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. The details of the operation of the nomcom can be found in RFC 3777. To be eligible, volunteers for the nomcom need to have attended 3 of the past 5 IETF meetings as of the time this announcement goes out. That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you qualify, and if you will not be seeking appointment to any of the open positions that this nomcom will be filling, please consider volunteering. The list of people whose terms end with the March 2013 IETF meeting, and thus the positions for which the nominating committee is responsible for filling, are as follows: IAOC: -------- Dave Crocker IAB: -------- Alissa Cooper Joel Halpern David Kessens Danny McPherson Jon Peterson Dave Thaler IESG: -------- Russ Housley (General Area) Pete Resnick (Applications Area) Ralph Droms (Internet Area) Ronald Bonica (Operations and Management Area) Robert Sparks (Real-Time Applications and Infrastructure Area) Adrian Farrel (Routing Area) Stephen Farrell (Security Area) Wesley Eddy (Transport Area) The primary activity for this nomcom will begin in August 2012 and should be completed in January 2013. The nomcom will be collecting requirements from the community, as well as talking to candidates and obtaining feedback from community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email before 11:59 pm EDT (UTC - 4 hours) August 5, 2012 as follows: To: mlepinski.ietf@gmail.com Subject: Nomcom 2012-13 Volunteer Please include the following information in the body: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name // typically what goes in the Company field // in the IETF Registration Form [] // // For confirmation if selected Please expect an email response from me within 3 business days stating whether or not you are qualified. If you don't receive a response, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing toward that goal. I will be publishing a more detailed timetable for nomcom activities, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next couple weeks. Thank you, Matthew Lepinski mlepinski.ietf@gmail.com nomcom-chair@ietf.org ---- End of forwarded message ------ - 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/ From alan.b.johnston@gmail.com Fri Jul 13 12:24:37 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298AB21F87A9 for ; Fri, 13 Jul 2012 12:24:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0r6iS6ws7asa for ; Fri, 13 Jul 2012 12:24:35 -0700 (PDT) Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5273521F87A5 for ; Fri, 13 Jul 2012 12:24:35 -0700 (PDT) Received: by yhq56 with SMTP id 56so4477065yhq.31 for ; Fri, 13 Jul 2012 12:25:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8Igcm7hUOsUATYNSOwg0B83BMQGUAc2g7EGx/nSs3fI=; b=Z9k3my7mlvnDzYuLbpUvmwsCuor0BQqu8ahUY56aQnKKbb47QAzduPjMFug9uzzaRJ BruxXC1L4Wa2DsqfmpPB/MlwEbXnlLR3FnSBuxhcwzpqo23Xd0h19Y1UsJYKs6PReLDp QdkO4lS3w8Od8HFxqeBT/m8pJb9j3h2jRGHqJIp7xxM8dSBvxUIXEI7dfDVAVmzSZDNX +hYQlCriU+puH20majGEfKgjI9mR1VSywrrKbnVS66Qs07nLBsy6TNzu0cSlqAJiuZbo oeZkirplHrPnT9ONzpbpSe1fMKaJfnjWg80rci1FYeOSseysEWk4CYC0ZQaVBGljXBCI my4w== MIME-Version: 1.0 Received: by 10.60.9.193 with SMTP id c1mr3241765oeb.47.1342207511856; Fri, 13 Jul 2012 12:25:11 -0700 (PDT) Received: by 10.182.12.10 with HTTP; Fri, 13 Jul 2012 12:25:11 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Jul 2012 14:25:11 -0500 Message-ID: From: Alan Johnston To: Laura Liess Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: cuss@ietf.org Subject: Re: [cuss] WGLC review for draft-ietf-cuss-sip-uui-06 X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 19:24:37 -0000 Laura, Thanks for the detailed review. I have a few comments below. - Alan - On Fri, May 25, 2012 at 5:54 AM, Laura Liess wrote: > Dear Vijay, > > You asked me to provide a WGLC review of the document > draft-ietf-cuss-sip-uui-06. > > I read the document and I think it is in good shape. > > Just a few minor comments: > > Section 3, 5-th paragraph: > Add explicit reference to draft-ietf-cuss-sip-uui-isdn. > Old text: =93Since the basic design of the UUI header field is similar > to the ISDN UUI service, interworking with PSTN protocols will be > straightforward and will be documented in a separate specification, > meeting REQ-6.=94 > New text: =93Since the basic design of the UUI header field is similar > to the ISDN UUI service, interworking with PSTN protocols will be > straightforward and >>is<< documented in a separate specification >>>[I-D.draft-ietf-cuss-sip-uui-isdn]<<, meeting REQ-6.=94 (changed or > added text is between >> and <<). Done. > > Section 4: > - My understanding is that more than one content values can be defi= ned > for a UUI package. If this is the case, the sentence =93Newly defined > UUI packages MUST define a new "content" value.=94 should be something > like =93Newly defined UUI packages MUST define new "content" value >>s > and the default<<.=94 Done. I've also tried to incorporate text explaining that encoding is tied to content rather than package (purpose), as we have discussed on the list. > > Section 4.1, the example at the end of the section: > - The current text: =93redirection response F2 of Figure 3=94. > Is =93Figure 3=94 correct here? > > - The current text: =93The resulting INVITE F5 would contain:=94 = But in > the RFC 6567 Figure 3 (and also in Figure 2), F5 is a 200 OK. Or did > I miss something? Good catch, it is actually Figure 2, and the INVITE is F4. (These all refer to RFC 6567) > > > Section 4.3: > Proxies/B2BUAs at a network border may anonymize SIP URIs in the > History-Info (the DT SBCs do that when the redirecting party requested > privacy) or may drop it (also I don=92t know about real implementations > doing that). This is OK and the issue was already discussed on the ML. > In most scenarios the application in the UA consuming the UUI data > will be probably able to identify the sender at application level. > However, I think it could be useful to have some words about this > issue at the end of Section 4.3, something like: > =93Proxies/B2BUAs at a network border anonymizing a SIP URI in the > History-Info SHOULD leave the corresponding User-to-User parameter, if > present, and the corresponding User-to-User header, unchanged. > Proxies/B2BUAs at a network border dropping a History-Info header > which contains User-to-User parameter, SHOULD not drop the > corresponding User-to-User header. In such cases the UA consuming the > UUI data are not able, at SIP level, to identify the source, but in > most cases it may be able to do it at the application level.=93 > I have included this text: Border elements such as proxies or B2BUAs which anonymize a SIP URI in a History-Info SHOULD leave the corresponding User-to-User parameter, if present, and the corresponding User-to-User header unchanged. Border elements removing a History-Info header containing a User-to-User parameter SHOULD not drop the corresponding User-to-User header. Otherwise, the UA consuming the UUI data may not be able at SIP level to identify the source of the UUI data. > But I am also OK if the authors think adding such a text is not useful. > > Section 10.2 and throughout the document: > Replace [I-D.ietf-cuss-sip-uui-reqs] by [RFC6567]. > > Thank you > Laura > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss From laura.liess.dt@googlemail.com Mon Jul 16 05:30:36 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5034821F87FB for ; Mon, 16 Jul 2012 05:30:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.909 X-Spam-Level: X-Spam-Status: No, score=-2.909 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZczNcZZv1H4v for ; Mon, 16 Jul 2012 05:30:35 -0700 (PDT) Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 414B321F87FC for ; Mon, 16 Jul 2012 05:30:35 -0700 (PDT) Received: by ghbg16 with SMTP id g16so5398191ghb.31 for ; Mon, 16 Jul 2012 05:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Btxo7kEQathi+OTLLbXHINXYdiv0ozg546LqtVvzqZo=; b=pGO912Ly9EeCNsECuVTEzL/P/BTKg++T9ZinggiprPkko3OAtzEtOgfZiBiJ6wUisJ 0bFEe4a1inhRlMBpMRyLmkho7/sZkIrqE1+E3LsqkBtbTsJICVByUR8vij+ubZ96I3oj EjdPK8sI4SVf/+xsT1kQRtN2nrgl/VWuDSj1V74i+7MX5UuC1Pv1kZRdFY5ZJ6Wc7Epp Uxcc5etHUfWH2pAWwNS0Ths/eQfmMl7W0FAdT0o9m4VIKX5CPqB8dzcZ/HgMiUpcGzeK R//KkcmP2t+BX8bt2ADDN4uBj6QoZ2L8ZpMko+2X48UB8fqy4ot2Rir4g6DtsajR50+b m8ZA== MIME-Version: 1.0 Received: by 10.50.179.101 with SMTP id df5mr5128573igc.22.1342441879403; Mon, 16 Jul 2012 05:31:19 -0700 (PDT) Received: by 10.231.200.37 with HTTP; Mon, 16 Jul 2012 05:31:19 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Jul 2012 14:31:19 +0200 Message-ID: From: Laura Liess To: Alan Johnston Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: cuss@ietf.org Subject: Re: [cuss] WGLC review for draft-ietf-cuss-sip-uui-06 X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 12:30:36 -0000 Alan, Thank you. Laura 2012/7/13 Alan Johnston : > Laura, > > Thanks for the detailed review. I have a few comments below. > > - Alan - > > On Fri, May 25, 2012 at 5:54 AM, Laura Liess > wrote: >> Dear Vijay, >> >> You asked me to provide a WGLC review of the document >> draft-ietf-cuss-sip-uui-06. >> >> I read the document and I think it is in good shape. >> >> Just a few minor comments: >> >> Section 3, 5-th paragraph: >> Add explicit reference to draft-ietf-cuss-sip-uui-isdn. >> Old text: =93Since the basic design of the UUI header field is similar >> to the ISDN UUI service, interworking with PSTN protocols will be >> straightforward and will be documented in a separate specification, >> meeting REQ-6.=94 >> New text: =93Since the basic design of the UUI header field is similar >> to the ISDN UUI service, interworking with PSTN protocols will be >> straightforward and >>is<< documented in a separate specification >>>>[I-D.draft-ietf-cuss-sip-uui-isdn]<<, meeting REQ-6.=94 (changed or >> added text is between >> and <<). > > Done. > >> >> Section 4: >> - My understanding is that more than one content values can be def= ined >> for a UUI package. If this is the case, the sentence =93Newly defined >> UUI packages MUST define a new "content" value.=94 should be something >> like =93Newly defined UUI packages MUST define new "content" value >>s >> and the default<<.=94 > > Done. I've also tried to incorporate text explaining that encoding is > tied to content rather than package (purpose), as we have discussed on > the list. > >> >> Section 4.1, the example at the end of the section: >> - The current text: =93redirection response F2 of Figure 3=94. >> Is =93Figure 3=94 correct here? >> >> - The current text: =93The resulting INVITE F5 would contain:=94 = But in >> the RFC 6567 Figure 3 (and also in Figure 2), F5 is a 200 OK. Or did >> I miss something? > > Good catch, it is actually Figure 2, and the INVITE is F4. (These all > refer to RFC 6567) > >> >> >> Section 4.3: >> Proxies/B2BUAs at a network border may anonymize SIP URIs in the >> History-Info (the DT SBCs do that when the redirecting party requested >> privacy) or may drop it (also I don=92t know about real implementations >> doing that). This is OK and the issue was already discussed on the ML. >> In most scenarios the application in the UA consuming the UUI data >> will be probably able to identify the sender at application level. >> However, I think it could be useful to have some words about this >> issue at the end of Section 4.3, something like: >> =93Proxies/B2BUAs at a network border anonymizing a SIP URI in the >> History-Info SHOULD leave the corresponding User-to-User parameter, if >> present, and the corresponding User-to-User header, unchanged. >> Proxies/B2BUAs at a network border dropping a History-Info header >> which contains User-to-User parameter, SHOULD not drop the >> corresponding User-to-User header. In such cases the UA consuming the >> UUI data are not able, at SIP level, to identify the source, but in >> most cases it may be able to do it at the application level.=93 >> > > I have included this text: > > Border elements such as proxies or B2BUAs which anonymize a SIP URI in > a History-Info SHOULD leave the corresponding User-to-User parameter, > if present, and the corresponding User-to-User header unchanged. > Border elements removing a History-Info header containing a > User-to-User parameter SHOULD not drop the corresponding User-to-User > header. Otherwise, the UA consuming the UUI data may not be able at > SIP level to identify the source of the UUI data. > >> But I am also OK if the authors think adding such a text is not useful. >> >> Section 10.2 and throughout the document: >> Replace [I-D.ietf-cuss-sip-uui-reqs] by [RFC6567]. >> >> Thank you >> Laura >> _______________________________________________ >> cuss mailing list >> cuss@ietf.org >> https://www.ietf.org/mailman/listinfo/cuss From internet-drafts@ietf.org Mon Jul 16 13:06:05 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C42F11E8179; Mon, 16 Jul 2012 13:06:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.479 X-Spam-Level: X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5CMa9Y5lGCu; Mon, 16 Jul 2012 13:06:04 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9651511E8088; Mon, 16 Jul 2012 13:06:04 -0700 (PDT) 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.30p3 Message-ID: <20120716200604.27441.45092.idtracker@ietfa.amsl.com> Date: Mon, 16 Jul 2012 13:06:04 -0700 Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-07.txt X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 20:06:05 -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 : A Mechanism for Transporting User to User Call Control I= nformation in SIP Author(s) : Alan Johnston James Rafferty Filename : draft-ietf-cuss-sip-uui-07.txt Pages : 18 Date : 2012-07-16 Abstract: There is a class of applications which benefit from using SIP to exchange User to User Information (UUI) data during session establishment. This information, known as call control UUI data, is a small piece of data inserted by an application initiating the session, and utilized by an application accepting the session. The rules which apply for a specific application are defined by a UUI package. This UUI data is opaque to SIP and its function is unrelated to any basic SIP function. This document defines a new SIP header field, User-to-User, to transport UUI data, along with an extension mechanism. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-07 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From vkg@bell-labs.com Mon Jul 30 10:24:04 2012 Return-Path: X-Original-To: cuss@ietfa.amsl.com Delivered-To: cuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C83C11E8160 for ; Mon, 30 Jul 2012 10:24:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.599 X-Spam-Level: X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3kQu+m13l0l for ; Mon, 30 Jul 2012 10:24:03 -0700 (PDT) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id C32A911E812F for ; Mon, 30 Jul 2012 10:24:03 -0700 (PDT) Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q6UHNxLS023046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 30 Jul 2012 12:23:59 -0500 (CDT) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q6UHNxdV010891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 30 Jul 2012 12:23:59 -0500 Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.41.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q6UHNwsd006426 for ; Mon, 30 Jul 2012 12:23:59 -0500 (CDT) Message-ID: <5016C330.4010909@bell-labs.com> Date: Mon, 30 Jul 2012 12:24:00 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: cuss@ietf.org References: <20120730032233.17770.35790.idtracker@ietfa.amsl.com> In-Reply-To: <20120730032233.17770.35790.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120730032233.17770.35790.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11 Subject: [cuss] Fwd: Need volunteers for the NomCom X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 17:24:04 -0000 Folks: NomCom is still looking for volunteers. Please do consider volunteering. Thanks, -------- Original Message -------- Subject: Need volunteers for the NomCom Date: Sun, 29 Jul 2012 20:22:33 -0700 From: NomCom Chair To: Working Group Chairs We are currently looking for volunteers to serve on the 2012-2013 NomCom. As you know, the success of the NomCom process depends crucially on having a large pool of volunteers from throughout the IETF community. In particular, it is valuable for the pool of volunteers to have strong representation from all of the technical areas within the IETF. I understand that not all IETF participants read the IETF announce list frequently. Therefore, if you would be willing to inform active participants in your working groups about this year's call for NomCom volunteers, I would greatly appreciate it. The NomCom 2012-2013 Call for Volunteers is open until this Sunday, August 5. Details can be found at: https://datatracker.ietf.org/ann/nomcom/49851/ Thank you for your help, - Matt Lepinski mlepinski.ietf@gmail.com nomcom-chair@ietf.org - 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/