From nobody Mon Nov 10 12:58:41 2014 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 95D281ACDF5 for ; Mon, 10 Nov 2014 12:58:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 96kdV5goCXKF for ; Mon, 10 Nov 2014 12:58:34 -0800 (PST) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C4B71ACDC7 for ; Mon, 10 Nov 2014 12:58:33 -0800 (PST) X-AuditID: c1b4fb25-f791c6d00000617b-4a-546126f78c5d Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 3D.2B.24955.7F621645; Mon, 10 Nov 2014 21:58:31 +0100 (CET) Received: from ESESSMB203.ericsson.se ([169.254.3.165]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Mon, 10 Nov 2014 21:58:31 +0100 From: Atle Monrad To: "cuss@ietf.org" Thread-Topic: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 Thread-Index: Ac/9KIKPEA8Ax3YPQZaYIudPpM8Xtw== Date: Mon, 10 Nov 2014 20:58:30 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C168F9F3B@ESESSMB203.ericsson.se> Accept-Language: nb-NO, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.154] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM+Jvje53tcQQg0vvNC2mn/nLaHGj/QWz xdQ+Wwdmjy9PXjJ5LFnyk8lj8sZZLAHMUVw2Kak5mWWpRfp2CVwZy5evYyq4p1+xafY9pgbG uWpdjJwcEgImEoua57NB2GISF+6tB7K5OIQEjjBKXDpynR3CWcIo8eDMAlaQKjYBHYlzP++A 2SICyhJ9qzvYQWxmgQiJv7fPMoHYwgJJEkdPb4CqSZe4+foXO4StJ/Fg8hlmEJtFQFWibf9O oBoODl4BX4lVf4pATEYBWYm5TbwQE8Ulbj2ZzwRxm4DEkj3nmSFsUYmXj/+xQthKEotuf2aC qNeRWLD7ExuErS2xbOFrsHpeAUGJkzOfsExgFJmFZOwsJC2zkLTMQtKygJFlFaNocWpxUm66 kbFealFmcnFxfp5eXmrJJkZgfBzc8lt1B+PlN46HGAU4GJV4eD98jA8RYk0sK67MPcQozcGi JM678Ny8YCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MmSz7U8LPJpyf/5bDc+bqbct8JYr0 Nimaf7py+P9EZm8rjT3Smy9cvjz3UeT1JibeuV6sV29Fd0eeOcvOGLnl0eSpXFeKpW+YW7af s9p9Y8GFV1++W7xcO2Hah46FrLH/fjz4VBgt9lf4iOD71dGi6vJTvjSLn1Tmqb288O3R/WrB s3wLutm+NSmxFGckGmoxFxUnAgCZoU75cAIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/LwlAKRs-uKqk528Lk518Stj8qMA Subject: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 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, 10 Nov 2014 20:58:39 -0000 Folks On June 23rd, I asked some questions to draft-ietf-cuss-sip-uui-isdn-09, an= d one of the questions was: "It is not clear to me if the way this draft us= e the permutations of the term "user to user", i.e. 'user to user', 'User = to User', 'User-to-User' and 'User-to-user' have any logic. If so, I'd be h= appy to understand it..." A few days ago ... version -10 of the draft came out, where the new versio= n of the draft attempted to align the terms as "User to User Information" a= nd "User-to-User header field". After this, it has been some off-list discussions whether this usage of the= se terms is correct or not. My 1st priority is to get the cuss-drafts completed, as 3GPP is still waiti= ng for the drafts to be completed.=20 I do not mind the alignment too much, but as I find consistent use of termi= nology useful, I have compared the draft-ietf-cuss-sip-uui-isdn-10 and draf= t-ietf-cuss-sip-uui-17. Between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17, I f= ind the usage of "User to User Information" and "User-to-User header field"= quite consistent, EXCEPT 3 instances of "user-to-user information" in sec= tion "8.1. Why INFO is Not Used" of draft-ietf-cuss-sip-uui. IMHO the two drafts are aligned at present (with the fixes of "user-to-us= er information" in draft-ietf-cuss-sip-uui-17). If it is a wish to revert a= number of the terms in draft-ietf-cuss-sip-uui-isdn-10, I think the author= s should have a look at draft-ietf-cuss-sip-uui-17 as well for alignment. I have also had a look at RFC6567, which is consistent in the use of the te= rm "User-to-User", thus it is an option to consistently use the terms "User= -to-User Information" AND "User-to-User header field" in both drafts, and b= e in line with the requirements-RFC :-) In addition, both drafts use terms like UUI data, UUI service, UUI content = parameters, UUI application, UUI header field, UUI mechanism, etc .... in a= similar fashion, thus I do not think anything is needed to do in this are= a.=20 At last I have an additional comments that I think you must take onboard in= draft-ietf-cuss-sip-uui-isdn AND in draft-ietf-cuss-sip-uui unless you can= justify the current text. In draft-ietf-cuss-sip-uui, the terms "UUI package" and "package" is used a= bit in a mix. It start off as "UUI package" and move towards "package" pos= sibly due to making the text read a bit easier. I think that the term "UUI = package" is rather easy to do use consistently and should be a quick fix in= all instances where you target mentioning the UUI package and not package = in general. In draft-ietf-cuss-sip-uui-isdn, the terms used are "package", "UUI package= " and "ISDN package". To me it seems that these terms are not used aligned = and correct. While the draft may wish to refer to some instances of "packag= e" (in general) the "UUI package" (generally for any UUI-packages) and e.g.= the "ISDN-UUI package" (specifically), I think you need to review the desc= riptive text and decide on what term to use where. This is also why I think= you should correct the draft-ietf-cuss-sip-uui WRT the term "package" vers= us "UUI package" to have alignment between the two drafts. I hope that these changes can be taken onboard in new revisions of the draf= ts as soon as possible. It is not my intention to send the drafts into anot= her 3-month cycle waiting for new versions. If the current authors have no = time for making a quick update, I propose that new authors (assumed found .= ..) that are willing do the needed corrections by a defined deadline can be= assigned. 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 internet-drafts@ietf= .org Sent: 24. oktober 2014 13:35 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-10.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 w= ith SIP Authors : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-10.txt Pages : 16 Date : 2014-10-24 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User to User information element data in SIP are described in RFC 6567. 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-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-10 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 nobody Mon Nov 10 13:25:06 2014 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 B553F1A1BB5 for ; Mon, 10 Nov 2014 13:25:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.494 X-Spam-Level: X-Spam-Status: No, score=-7.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] 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 NhBVJAZjXB0M for ; Mon, 10 Nov 2014 13:24:54 -0800 (PST) Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81B51A1BB4 for ; Mon, 10 Nov 2014 13:24:53 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id E5B07920ABE2A; Mon, 10 Nov 2014 21:24:48 +0000 (GMT) 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 sAALOq2i012876 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Nov 2014 22:24:52 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.25]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Mon, 10 Nov 2014 22:24:52 +0100 From: "DRAGE, Keith (Keith)" To: Atle Monrad , "cuss@ietf.org" Thread-Topic: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 Thread-Index: Ac/9KIKPEA8Ax3YPQZaYIudPpM8XtwAA+q7A Date: Mon, 10 Nov 2014 21:24:51 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B276D78@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <7D2F7D7ADBA812449F25F4A69922881C168F9F3B@ESESSMB203.ericsson.se> In-Reply-To: <7D2F7D7ADBA812449F25F4A69922881C168F9F3B@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.38] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/100IIYzcIoBtCzPHQLCNqXDT6tY Subject: Re: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 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, 10 Nov 2014 21:25:01 -0000 I thought I was very clear on the ones that are now wrong. In summary - you= cannot make consistent something that is the name of a parameter in a prot= ocol that IETF does not own, or in a service definition that IETF does not = own. As such, you just end up referencing to some concept that does not exi= st. This is the list of changes that need to be reverted: Appears a number of changes deviate from the terminology in other documents= , and should therefore be undone. =20 So the correct terminology is as follows: =20 1) "User-user information element" see ITU-T recommentation Q.931 and IT= U-T Q.957.1 for correct usage, making the following changes incorrect: =20 - Abstract - Section 2 =20 2) "User-to-user signalling supplementary service" see ITU-T Recommendat= ion Q.957.1 for correct usage, making the following changes incorrect: =20 - Section 3 (Title) - Section 3.1 many times - Section 13 (twice) =20 3) Q.763 "User-to-user information" see ITU-T Recommendation Q.763 for c= orrect usage, making following changes incorrect. =20 - Section 2 =20 4) Within the ISDN supplementary service "User-to-user information" or "= user-to-user data". =20 - Section 3.1 many times - Section 6 =20 5) In section 14 please write out name of service in full as in 2) above= . =20 6) Additionally section 14 would probably be better to write (instead of= "User to User package"): =20 "UUI package" which is the terminology in draft-ietf-cuss-sip-uui. =20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Atle Monrad > Sent: 10 November 2014 20:59 > To: cuss@ietf.org > Subject: [cuss] alignment between=20 > draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 >=20 > Folks >=20 > On June 23rd, I asked some questions to=20 > draft-ietf-cuss-sip-uui-isdn-09, and one of the questions=20 > was: "It is not clear to me if the way this draft use the=20 > permutations of the term "user to user", i.e. 'user to=20 > user', 'User to User', 'User-to-User' and 'User-to-user' have=20 > any logic. If so, I'd be happy to understand it..." >=20 > A few days ago ... version -10 of the draft came out, where=20 > the new version of the draft attempted to align the terms as=20 > "User to User Information" and "User-to-User header field". >=20 > After this, it has been some off-list discussions whether=20 > this usage of these terms is correct or not. >=20 > My 1st priority is to get the cuss-drafts completed, as 3GPP=20 > is still waiting for the drafts to be completed.=20 > I do not mind the alignment too much, but as I find=20 > consistent use of terminology useful, I have compared the=20 > draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17. >=20 > Between draft-ietf-cuss-sip-uui-isdn-10 and=20 > draft-ietf-cuss-sip-uui-17, I find the usage of "User to User=20 > Information" and "User-to-User header field" quite=20 > consistent, EXCEPT 3 instances of "user-to-user information"=20 > in section "8.1. Why INFO is Not Used" of draft-ietf-cuss-sip-uui. >=20 > IMHO the two drafts are aligned at present (with the fixes =20 > of "user-to-user information" in draft-ietf-cuss-sip-uui-17).=20 > If it is a wish to revert a number of the terms in=20 > draft-ietf-cuss-sip-uui-isdn-10, I think the authors should=20 > have a look at draft-ietf-cuss-sip-uui-17 as well for alignment. >=20 > I have also had a look at RFC6567, which is consistent in the=20 > use of the term "User-to-User", thus it is an option to=20 > consistently use the terms "User-to-User Information" AND=20 > "User-to-User header field" in both drafts, and be in line=20 > with the requirements-RFC :-) >=20 > In addition, both drafts use terms like UUI data, UUI=20 > service, UUI content parameters, UUI application, UUI header=20 > field, UUI mechanism, etc .... in a similar fashion, thus I=20 > do not think anything is needed to do in this area.=20 >=20 > At last I have an additional comments that I think you must=20 > take onboard in draft-ietf-cuss-sip-uui-isdn AND in=20 > draft-ietf-cuss-sip-uui unless you can justify the current text. >=20 > In draft-ietf-cuss-sip-uui, the terms "UUI package" and=20 > "package" is used a bit in a mix. It start off as "UUI=20 > package" and move towards "package" possibly due to making=20 > the text read a bit easier. I think that the term "UUI=20 > package" is rather easy to do use consistently and should be=20 > a quick fix in all instances where you target mentioning the=20 > UUI package and not package in general. >=20 > In draft-ietf-cuss-sip-uui-isdn, the terms used are=20 > "package", "UUI package" and "ISDN package". To me it seems=20 > that these terms are not used aligned and correct. While the=20 > draft may wish to refer to some instances of "package" (in=20 > general) the "UUI package" (generally for any UUI-packages)=20 > and e.g. the "ISDN-UUI package" (specifically), I think you=20 > need to review the descriptive text and decide on what term=20 > to use where. This is also why I think you should correct the=20 > draft-ietf-cuss-sip-uui WRT the term "package" versus "UUI=20 > package" to have alignment between the two drafts. >=20 > I hope that these changes can be taken onboard in new=20 > revisions of the drafts as soon as possible. It is not my=20 > intention to send the drafts into another 3-month cycle=20 > waiting for new versions. If the current authors have no time=20 > for making a quick update, I propose that new authors=20 > (assumed found ...) that are willing do the needed=20 > corrections by a defined deadline can be assigned. >=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 [mailto:cuss-bounces@ietf.org] On Behalf Of=20 > internet-drafts@ietf.org > Sent: 24. oktober 2014 13:35 > To: i-d-announce@ietf.org > Cc: cuss@ietf.org > Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-10.txt >=20 >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Call Control UUI Service=20 > for SIP Working Group of the IETF. >=20 > Title : Interworking ISDN Call Control User=20 > Information with SIP > Authors : Keith Drage > Alan Johnston > Filename : draft-ietf-cuss-sip-uui-isdn-10.txt > Pages : 16 > Date : 2014-10-24 >=20 > Abstract: > The motivation and use cases for interworking and=20 > transporting ITU-T > DSS1 User to User information element data in SIP are described in > RFC 6567. As networks move to SIP, it is important that=20 > applications > requiring this data can continue to function in SIP=20 > 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. >=20 > This document covers the interworking with both public ISDN and > private ISDN capabilities, so the potential interworking with QSIG > will also be addressed. >=20 > The package is identified by a new value "isdn-uui" of the=20 > "purpose" > header field parameter. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-10 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-10 >=20 >=20 > Please note that it may take a couple of minutes from the=20 > time of submission until the htmlized version and diff are=20 > available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > 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 nobody Mon Nov 10 14:15:52 2014 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 DAC711A870F for ; Mon, 10 Nov 2014 14:15:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 CDBdMUGeJDGc for ; Mon, 10 Nov 2014 14:15:48 -0800 (PST) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7622B1A00FC for ; Mon, 10 Nov 2014 14:15:47 -0800 (PST) X-AuditID: c1b4fb25-f791c6d00000617b-f9-546139119614 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 39.2F.24955.11931645; Mon, 10 Nov 2014 23:15:45 +0100 (CET) Received: from ESESSMB203.ericsson.se ([169.254.3.165]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0174.001; Mon, 10 Nov 2014 23:15:45 +0100 From: Atle Monrad To: "DRAGE, Keith (Keith)" , "cuss@ietf.org" Thread-Topic: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 Thread-Index: Ac/9KIKPEA8Ax3YPQZaYIudPpM8XtwAA+q7AAAFTFaA= Date: Mon, 10 Nov 2014 22:15:44 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C168FA083@ESESSMB203.ericsson.se> References: <7D2F7D7ADBA812449F25F4A69922881C168F9F3B@ESESSMB203.ericsson.se> <949EF20990823C4C85C18D59AA11AD8B276D78@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B276D78@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.149] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvja6gZWKIweVXhhY32l8wWzxtPMvo wOTR+mwvq8eSJT+ZApiiuGxSUnMyy1KL9O0SuDIOf21nL2jzrJg3+zdTA+MFqy5GTg4JAROJ T18Os0PYYhIX7q1n62Lk4hASOMIo8XLWKmaQhJDAEkaJ3z+lQGw2AR2Jcz/vsILYIgJxEq3n e9lAbGGBNIkXfz4xQ8TTJW6+/sUOYVtJzPywBMxmEVCV+HW2hRHE5hXwldj+9h7UsnmMEiv2 tYM1cwpES2z7e4Kli5GDg1FAVmJuEy9ImFlAXOLWk/lMEIcKSCzZc54ZwhaVePn4HyuErSSx 9vB2Foh6HYkFuz+xQdjaEssWvmaG2CsocXLmE5YJjKKzkIydhaRlFpKWWUhaFjCyrGIULU4t TspNNzLWSy3KTC4uzs/Ty0st2cQIjJODW36r7mC8/MbxEKMAB6MSD++Hj/EhQqyJZcWVuYcY pTlYlMR5F56bFywkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBUfjsZZupnhKf16++3rzMVK/a PIfn+pQ9xsuLvc/HmPkuuV5W4VD2fiYfw7E8zmkZhQ8nqe46cIjTsbB4Z+qTK/OCurPZpaaY L037o3RZk/2KTzPr3OqUneE1W2+4mIsfr75gsS6Rz/VvQkct++1zcVNc9P53/xDumjjz7tcZ Pz55f/yW0n5hnhJLcUaioRZzUXEiAIDcmgd0AgAA Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/8bMVGtkmmkdwPw08ITbEPslR2lk Subject: Re: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 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, 10 Nov 2014 22:15:51 -0000 Keith I understand your point, however=20 my point is that if you decide to revert the terminology certain places in= draft-ietf-cuss-sip-uui-isdn you may need to do the same in draft-ietf-cu= ss-sip-uui if you want to have the drafts aligned. The 2nd topic, use of the terms used are "package", "UUI package" and "ISDN= package" is also a topic for consideration between the two drafts. /atle ________________________________=20 Atle Monrad 3GPP CT Chairman Group Function Technology - Standardization and Technical Regulation=20 Ericsson -----Original Message----- From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]=20 Sent: 10. november 2014 11:25 To: Atle Monrad; cuss@ietf.org Subject: RE: [cuss] alignment between draft-ietf-cuss-sip-uui-isdn-10 and d= raft-ietf-cuss-sip-uui-17 I thought I was very clear on the ones that are now wrong. In summary - you= cannot make consistent something that is the name of a parameter in a prot= ocol that IETF does not own, or in a service definition that IETF does not = own. As such, you just end up referencing to some concept that does not exi= st. This is the list of changes that need to be reverted: Appears a number of changes deviate from the terminology in other documents= , and should therefore be undone. =20 So the correct terminology is as follows: =20 1) "User-user information element" see ITU-T recommentation Q.931 and IT= U-T Q.957.1 for correct usage, making the following changes incorrect: =20 - Abstract - Section 2 =20 2) "User-to-user signalling supplementary service" see ITU-T Recommendat= ion Q.957.1 for correct usage, making the following changes incorrect: =20 - Section 3 (Title) - Section 3.1 many times - Section 13 (twice) =20 3) Q.763 "User-to-user information" see ITU-T Recommendation Q.763 for c= orrect usage, making following changes incorrect. =20 - Section 2 =20 4) Within the ISDN supplementary service "User-to-user information" or "= user-to-user data". =20 - Section 3.1 many times - Section 6 =20 5) In section 14 please write out name of service in full as in 2) above= . =20 6) Additionally section 14 would probably be better to write (instead of= "User to User package"): =20 "UUI package" which is the terminology in draft-ietf-cuss-sip-uui. =20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of Atle Monrad > Sent: 10 November 2014 20:59 > To: cuss@ietf.org > Subject: [cuss] alignment between > draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17 >=20 > Folks >=20 > On June 23rd, I asked some questions to=20 > draft-ietf-cuss-sip-uui-isdn-09, and one of the questions > was: "It is not clear to me if the way this draft use the permutations=20 > of the term "user to user", i.e. 'user to user', 'User to User',=20 > 'User-to-User' and 'User-to-user' have any logic. If so, I'd be happy=20 > to understand it..." >=20 > A few days ago ... version -10 of the draft came out, where the new=20 > version of the draft attempted to align the terms as "User to User=20 > Information" and "User-to-User header field". >=20 > After this, it has been some off-list discussions whether this usage=20 > of these terms is correct or not. >=20 > My 1st priority is to get the cuss-drafts completed, as 3GPP is still=20 > waiting for the drafts to be completed. > I do not mind the alignment too much, but as I find consistent use of=20 > terminology useful, I have compared the > draft-ietf-cuss-sip-uui-isdn-10 and draft-ietf-cuss-sip-uui-17. >=20 > Between draft-ietf-cuss-sip-uui-isdn-10 and=20 > draft-ietf-cuss-sip-uui-17, I find the usage of "User to User=20 > Information" and "User-to-User header field" quite consistent, EXCEPT=20 > 3 instances of "user-to-user information" > in section "8.1. Why INFO is Not Used" of draft-ietf-cuss-sip-uui. >=20 > IMHO the two drafts are aligned at present (with the fixes of=20 > "user-to-user information" in draft-ietf-cuss-sip-uui-17). > If it is a wish to revert a number of the terms in=20 > draft-ietf-cuss-sip-uui-isdn-10, I think the authors should have a=20 > look at draft-ietf-cuss-sip-uui-17 as well for alignment. >=20 > I have also had a look at RFC6567, which is consistent in the use of=20 > the term "User-to-User", thus it is an option to consistently use the=20 > terms "User-to-User Information" AND "User-to-User header field" in=20 > both drafts, and be in line with the requirements-RFC :-) >=20 > In addition, both drafts use terms like UUI data, UUI service, UUI=20 > content parameters, UUI application, UUI header field, UUI mechanism,=20 > etc .... in a similar fashion, thus I do not think anything is needed=20 > to do in this area. >=20 > At last I have an additional comments that I think you must take=20 > onboard in draft-ietf-cuss-sip-uui-isdn AND in draft-ietf-cuss-sip-uui=20 > unless you can justify the current text. >=20 > In draft-ietf-cuss-sip-uui, the terms "UUI package" and "package" is=20 > used a bit in a mix. It start off as "UUI package" and move towards=20 > "package" possibly due to making the text read a bit easier. I think=20 > that the term "UUI package" is rather easy to do use consistently and=20 > should be a quick fix in all instances where you target mentioning the=20 > UUI package and not package in general. >=20 > In draft-ietf-cuss-sip-uui-isdn, the terms used are "package", "UUI=20 > package" and "ISDN package". To me it seems that these terms are not=20 > used aligned and correct. While the draft may wish to refer to some=20 > instances of "package" (in > general) the "UUI package" (generally for any UUI-packages) and e.g.=20 > the "ISDN-UUI package" (specifically), I think you need to review the=20 > descriptive text and decide on what term to use where. This is also=20 > why I think you should correct the draft-ietf-cuss-sip-uui WRT the=20 > term "package" versus "UUI package" to have alignment between the two=20 > drafts. >=20 > I hope that these changes can be taken onboard in new revisions of the=20 > drafts as soon as possible. It is not my intention to send the drafts=20 > into another 3-month cycle waiting for new versions. If the current=20 > authors have no time for making a quick update, I propose that new=20 > authors (assumed found ...) that are willing do the needed corrections=20 > by a defined deadline can be assigned. >=20 > Cheers > /atle >=20 > ________________________________ >=20 >=20 > Atle Monrad > 3GPP CT Chairman >=20 > Group Function Technology - Standardization and Technical Regulation=20 > Ericsson >=20 >=20 >=20 > -----Original Message----- > From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of=20 > internet-drafts@ietf.org > Sent: 24. oktober 2014 13:35 > To: i-d-announce@ietf.org > Cc: cuss@ietf.org > Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-10.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. > This draft is a work item of the Call Control UUI Service for SIP=20 > Working Group of the IETF. >=20 > Title : Interworking ISDN Call Control User=20 > Information with SIP > Authors : Keith Drage > Alan Johnston > Filename : draft-ietf-cuss-sip-uui-isdn-10.txt > Pages : 16 > Date : 2014-10-24 >=20 > Abstract: > The motivation and use cases for interworking and transporting=20 > ITU-T > DSS1 User to User information element data in SIP are described in > RFC 6567. As networks move to SIP, it is important that=20 > applications > requiring this data can continue to function in SIP networks as=20 > 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. >=20 > This document covers the interworking with both public ISDN and > private ISDN capabilities, so the potential interworking with QSIG > will also be addressed. >=20 > The package is identified by a new value "isdn-uui" of the=20 > "purpose" > header field parameter. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-cuss-sip-uui-isdn-10 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-10 >=20 >=20 > Please note that it may take a couple of minutes from the time of=20 > submission until the htmlized version and diff are available at=20 > tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > 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 >=20 From nobody Tue Nov 11 15:05:44 2014 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 12BAC1A6F9D; Tue, 11 Nov 2014 15:05:39 -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 YMv8pa_n9Jgv; Tue, 11 Nov 2014 15:05:37 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8471B1A6F67; Tue, 11 Nov 2014 15:05:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.7.2.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141111230537.9240.59684.idtracker@ietfa.amsl.com> Date: Tue, 11 Nov 2014 15:05:37 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/OMgyt7z-XcSNKSvUfwxyL6SLA2U Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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: Tue, 11 Nov 2014 23:05:39 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. 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 Authors : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-11.txt Pages : 16 Date : 2014-11-11 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in RFC 6567. 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 called the ISDN UUI 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-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-cuss-sip-uui-isdn-11 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 nobody Tue Nov 11 15:08:16 2014 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 5B93F1A6F88 for ; Tue, 11 Nov 2014 15:08:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.494 X-Spam-Level: X-Spam-Status: No, score=-7.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] 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 XxuhlPdb3vTw for ; Tue, 11 Nov 2014 15:08:11 -0800 (PST) Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14E521A1B80 for ; Tue, 11 Nov 2014 15:08:11 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 4F81FE02A8B40 for ; Tue, 11 Nov 2014 23:08:05 +0000 (GMT) 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 sABN89M3005916 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 12 Nov 2014 00:08:09 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.25]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Wed, 12 Nov 2014 00:08:09 +0100 From: "DRAGE, Keith (Keith)" To: "cuss@ietf.org" Thread-Topic: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt Thread-Index: AQHP/gQNeOWUg+ySy0aNLFBZEkoYxpxcDEOQ Date: Tue, 11 Nov 2014 23:08:08 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B2782C7@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 Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/5j3qeIDAW64p_2OxbUL6aS2d_qM Subject: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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: Tue, 11 Nov 2014 23:08:13 -0000 This version contains essentially editorial changes from the previous versi= on. Some of those editorials correct names of some protocol elements in DSS= 1 and ISUP, so they are less than editorial in that respect. Regards Keith=20 -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 11 November 2014 23:06 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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 w= ith SIP Authors : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-11.txt Pages : 16 Date : 2014-11-11 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in RFC 6567. 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 called the ISDN UUI 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-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-11 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 nobody Wed Nov 12 12:33:08 2014 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 1729F1A7113 for ; Wed, 12 Nov 2014 12:33:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 FohIQN55etWp for ; Wed, 12 Nov 2014 12:33:05 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0ACF1A8738 for ; Wed, 12 Nov 2014 12:33:04 -0800 (PST) X-AuditID: c1b4fb3a-f79596d000001123-19-5463c3fef9f4 Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 3D.3F.04387.EF3C3645; Wed, 12 Nov 2014 21:33:03 +0100 (CET) Received: from ESESSMB203.ericsson.se ([169.254.3.165]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Wed, 12 Nov 2014 21:33:02 +0100 From: Atle Monrad To: "DRAGE, Keith (Keith)" , "cuss@ietf.org" Thread-Topic: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt Thread-Index: AQHP/gQNeOWUg+ySy0aNLFBZEkoYxpxcDEOQgAFl16A= Date: Wed, 12 Nov 2014 20:33:01 +0000 Message-ID: <7D2F7D7ADBA812449F25F4A69922881C168FC713@ESESSMB203.ericsson.se> References: <949EF20990823C4C85C18D59AA11AD8B2782C7@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B2782C7@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.148] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvje7/w8khBru2slncaH/BbPG08Syj A5NH67O9rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mro2bGMveC5VMXnuctZGxh3iHYxcnJICJhI XH92ihXCFpO4cG89WxcjF4eQwBFGif2NrSwQzhJGiSkv+tlAqtgEdCTO/bwD1iEiECfRer4X LC4s4CFx5vkrJoi4p0T32R7mLkZ2INtK4oMfSJRFQFVi9uyNYNW8Ar4SK6b+YAGxhQSiJDY3 b2IEsTkFoiWavz8CinNwMArISsxt4gUJMwuIS9x6Mp8J4kwBiSV7zjND2KISLx//gzpfSaJx yRNWiHodiQW7P7FB2NoSyxa+ZoZYKyhxcuYTlgmMorOQjJ2FpGUWkpZZSFoWMLKsYhQtTi0u zk03MtJLLcpMLi7Oz9PLSy3ZxAiMkYNbflvtYDz43PEQowAHoxIPr8HZpBAh1sSy4srcQ4zS HCxK4rwLz80LFhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cAYzxumZ5bx3aQt4hCr7TOmQKOE X7dfnPjdqs1usV/h/6Wj1Zsu7Iw2aKs48KlsRa9hYnGCiq+ZD1OWHKdFzkOBWJf4bf2tXye8 XbZ8xRWWFb4TfT7ylR8TrS0+cyn6svnBEJEn/MHrOBzcGB/84OGtnSSq/WvhHsO90vfT3iUp 9QetDDKoqlZiKc5INNRiLipOBABPORAAcgIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/Bsf53Z1N2wSaN8K5B1Jz2bkWet4 Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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: Wed, 12 Nov 2014 20:33:07 -0000 All My comments on alignment of wording (User-User / User-to-User as swell as u= sage of ISDN UUI package versus UUI package) are all clarified and addresse= d. I have no further comments to this draft and hope it can be brought forw= ard at soon as possible.=20 There are a few alignments needed for the -uui draft as well, but they are = identified and will be done. 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 DRAGE, Keith (Keith) Sent: 11. november 2014 13:08 To: cuss@ietf.org Subject: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt This version contains essentially editorial changes from the previous versi= on. Some of those editorials correct names of some protocol elements in DSS= 1 and ISUP, so they are less than editorial in that respect. Regards Keith=20 -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 11 November 2014 23:06 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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 w= ith SIP Authors : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-11.txt Pages : 16 Date : 2014-11-11 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in RFC 6567. 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 called the ISDN UUI 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-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-11 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 nobody Wed Nov 12 17:00:54 2014 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 8AA041A0282; Wed, 12 Nov 2014 17:00:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 qeLvo7VLyw5v; Wed, 12 Nov 2014 17:00:41 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 348CB1A0367; Wed, 12 Nov 2014 17:00:38 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.7.2.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141113010038.9100.83359.idtracker@ietfa.amsl.com> Date: Wed, 12 Nov 2014 17:00:38 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/zPwCzs1NKp0Tkp_QsKGI0RcngbM Cc: cuss mailing list , cuss chair , RFC Editor Subject: [cuss] Protocol Action: 'Interworking ISDN Call Control User Information with SIP' to Proposed Standard (draft-ietf-cuss-sip-uui-isdn-11.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: Thu, 13 Nov 2014 01:00:44 -0000 The IESG has approved the following document: - 'Interworking ISDN Call Control User Information with SIP' (draft-ietf-cuss-sip-uui-isdn-11.txt) as Proposed Standard This document is the product of the Call Control UUI Service for SIP Working Group. The IESG contact persons are Alissa Cooper and Richard Barnes. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-cuss-sip-uui-isdn/ Technical Summary: The move of communications networks to SIP does not ameliorate the need to support use cases for interworking and transporting legacy PSTN-related information in SIP. This document defines a package and associated semantics that allows SIP endpoints to exchange information related to the ISDN UUS1 service. Working Group Summary: A WGLC was held from Nov-13-2013 to Nov-29-2013. As part of the WGLC, reviews were performed by WG members (Andrew Allen, Atle Monrad and Celine Serrut-Valette) and other members affirmed the need to move ahead with the draft. There was one area on which consensus was eventually acheived: draft-ietf-cuss-sip-uui-isdn uses the value of "isdn-uui" for the "purpose" header field parameter. Older versions of the draft used the value "isdn-network". Consequently, there are implementations that use "isdn-network" and doubtlessly, for some valid reasons these implementations are not amenable to change. Text was added to -06 version of the draft that adequately addressed the issue of implicitly supporting "isdn- network" in certain cases. The participants to the discussion are okay with the proposed resolution. Document Quality: The document has been reviewed by multiple WG members and has been affirmed by many more. There are no known issues with document quality. There appear to be existing implementations of the draft, especially since the issue requiring consensus (described above) was specifically so that existing code can continue to work. Personnel: Vijay K. Gurbani is the Document Shepherd. Alissa Cooper is the Responsible Area Director. Who is the Document Shepherd for this document? Who is the Responsible Area Director? If the document requires IANA experts(s), insert 'The IANA Expert(s) for the registries in this document are .' From nobody Thu Nov 20 05:14:56 2014 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 E916B1A040B for ; Thu, 20 Nov 2014 05:14:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 CAlRyClbGnjM for ; Thu, 20 Nov 2014 05:14:51 -0800 (PST) Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 934CD1A0271 for ; Thu, 20 Nov 2014 05:14:51 -0800 (PST) Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 5404F18C1BC; Thu, 20 Nov 2014 14:14:49 +0100 (CET) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 33C1927C072; Thu, 20 Nov 2014 14:14:49 +0100 (CET) Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0210.002; Thu, 20 Nov 2014 14:14:48 +0100 From: To: "DRAGE, Keith (Keith)" , "cuss@ietf.org" Thread-Topic: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt Thread-Index: AQHP/gQNeOWUg+ySy0aNLFBZEkoYxpxcDEOQgA19/nA= Date: Thu, 20 Nov 2014 13:14:48 +0000 Message-ID: <24925_1416489289_546DE949_24925_288_2_F8BE5641EC3C954DA088A8350BDDFA48192E29@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <949EF20990823C4C85C18D59AA11AD8B2782C7@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B2782C7@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.6] 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: 2014.10.23.100020 Archived-At: http://mailarchive.ietf.org/arch/msg/cuss/UdJbyMnEzZMpPmtGgK3t3tShp4k Subject: Re: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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: Thu, 20 Nov 2014 13:14:55 -0000 Hello, Sorry for this late comment (I was absent before), in this new version 11 t= here is an unexpected space in "isdn-interwork" value in section 8 in the f= ollowing sentence:=20 "parsing and interpreting "isdn- interwork" the same way as "isdn-uui" when= receiving messages." This only appears now in version 11 likely because of the change from "purp= ose parameter" to ""purpose" header field parameter" (a little higher in th= e text). I hope this editorial comment could be taken into account before becoming a= n RFC in order to avoid any misunderstanding. Regards, Celine Serrut-Valette Orange Labs -----Message d'origine----- De=A0: cuss [mailto:cuss-bounces@ietf.org] De la part de DRAGE, Keith (Keit= h) Envoy=E9=A0: mercredi 12 novembre 2014 00:08 =C0=A0: cuss@ietf.org Objet=A0: [cuss] FW: I-D Action: draft-ietf-cuss-sip-uui-isdn-11.txt This version contains essentially editorial changes from the previous versi= on. Some of those editorials correct names of some protocol elements in DSS= 1 and ISUP, so they are less than editorial in that respect. Regards Keith=20 -----Original Message----- From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: 11 November 2014 23:06 To: i-d-announce@ietf.org Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-isdn-11.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 w= ith SIP Authors : Keith Drage Alan Johnston Filename : draft-ietf-cuss-sip-uui-isdn-11.txt Pages : 16 Date : 2014-11-11 Abstract: The motivation and use cases for interworking and transporting ITU-T DSS1 User-user information element data in SIP are described in RFC 6567. 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 called the ISDN UUI 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-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cuss-sip-uui-isdn-11 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 ___________________________________________________________________________= ______________________________________________ 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.