From internet-drafts@ietf.org Wed Dec 7 06:59:16 2011 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 26B9A21F8AA9; Wed, 7 Dec 2011 06:59:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.463 X-Spam-Level: X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 z6CAHq41r0zD; Wed, 7 Dec 2011 06:59:15 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C560E21F8A91; Wed, 7 Dec 2011 06:59:15 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.64 Message-ID: <20111207145915.31663.23819.idtracker@ietfa.amsl.com> Date: Wed, 07 Dec 2011 06:59:15 -0800 Cc: cuss@ietf.org Subject: [cuss] I-D Action: draft-ietf-cuss-sip-uui-reqs-08.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: Wed, 07 Dec 2011 14:59:16 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Call Control UUI Service for SIP Work= ing Group of the IETF. Title : Problem Statement and Requirements for Transporting User= to User Call Control Information in SIP Author(s) : Alan Johnston Laura Liess Filename : draft-ietf-cuss-sip-uui-reqs-08.txt Pages : 12 Date : 2011-12-07 This document introduces the transport of call control related User to User Information (UUI) using the Session Initiation Protocol (SIP), and develops several requirements for a new SIP mechanism. Some SIP sessions are established by or related to a non-SIP application. This application may have information that needs to be transported between the SIP User Agents during session establishment. In addition to interworking with the ISDN UUI Service, this extension will also be used for native SIP endpoints requiring application UUI. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-cuss-sip-uui-reqs-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-cuss-sip-uui-reqs-08.txt From xavier.marjou@gmail.com Fri Dec 9 06:50:01 2011 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 5B38621F8551 for ; Fri, 9 Dec 2011 06:50:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.677 X-Spam-Level: X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 S94LMGh5jQKV for ; Fri, 9 Dec 2011 06:50:00 -0800 (PST) Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C643221F8531 for ; Fri, 9 Dec 2011 06:50:00 -0800 (PST) Received: by ghrr18 with SMTP id r18so2823517ghr.31 for ; Fri, 09 Dec 2011 06:50:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=DKGG+JEW15FK/AoB9GZhDorTo5laPG7Z36/YKPWGOR4=; b=ggimjMlycOtmVZx+0Hx438qZGyyhunGVwqsM2PAzO1oPBFv+OYzhhnVXQWIGQf1u09 YHNsOQX2OD9TpXVclWBUtltrmZVIkViT/ClHv+4CgCv5jtgfXKBCxGNGdzY24vJcPGo2 u6vkBobUJrqfZTLuRKx+xCz4DyF3CE1Nyarxc= MIME-Version: 1.0 Received: by 10.236.157.10 with SMTP id n10mr12777385yhk.41.1323442200324; Fri, 09 Dec 2011 06:50:00 -0800 (PST) Sender: xavier.marjou@gmail.com Received: by 10.236.180.230 with HTTP; Fri, 9 Dec 2011 06:50:00 -0800 (PST) Date: Fri, 9 Dec 2011 15:50:00 +0100 X-Google-Sender-Auth: BydleEo7-c7qg7Wvbv5bSkcxBQE Message-ID: From: Xavier Marjou To: cuss@ietf.org Content-Type: multipart/alternative; boundary=20cf30426fc03b286f04b3a9e6b3 Subject: [cuss] "package" vs "purpose" name in draft-ietf-cuss-sip-uui-04 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, 09 Dec 2011 14:50:01 -0000 --20cf30426fc03b286f04b3a9e6b3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, Regarding draft-ietf-cuss-sip-uui-04, one modification I would like is to rename the =93package=94 parameter name into =93purpose=94 which existed un= til draft-ietf-cuss-sip-uui-00. The goal would to allow compatibility with already deployed implementations that are based on the draft-johnston individual draft (draft referenced since a long time in 3GPP documents). There would be no change regarding the semantics: the goal of the defined parameter is to indicate the purpose of the application usage of UUI data and this can be fulfilled by a parameter called =93purpose=94, in order to indicate how and why UUI data is used. Cheers, Xavier --20cf30426fc03b286f04b3a9e6b3 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

Hi,=


Regarding draft-ietf-cu= ss-sip-uui-04, one modification I would like is to rename the =93package=94 parameter name into =93purpose= =94 which existed until draft-ietf-cuss-sip-uui-00. The goal would to allow compatibi= lity with already deployed implementations that are based on the draft-johnston individual draft (draft referenced since a long time in 3GPP documents). Th= ere would be no change regarding the semantics: the goal of the defined parameter is to indicate the purpose of = the application usage of UUI data and this can be fulfilled by a parameter call= ed =93purpose=94, in order to indicate how and why UUI data is used.


Cheers,

Xavier

--20cf30426fc03b286f04b3a9e6b3-- From vkg@bell-labs.com Fri Dec 9 06:59:05 2011 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 C56D821F8509 for ; Fri, 9 Dec 2011 06:59:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.48 X-Spam-Level: X-Spam-Status: No, score=-106.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 aXfUyWYke6Yu for ; Fri, 9 Dec 2011 06:59:05 -0800 (PST) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 385E021F84FC for ; Fri, 9 Dec 2011 06:59:05 -0800 (PST) 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 pB9Ex4pt023768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 9 Dec 2011 08:59:04 -0600 (CST) 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 pB9Ex0eE003884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 9 Dec 2011 08:59:04 -0600 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id pB9Ex0fX007792 for ; Fri, 9 Dec 2011 08:59:00 -0600 (CST) Message-ID: <4EE22305.6090003@bell-labs.com> Date: Fri, 09 Dec 2011 09:02:29 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111115 Thunderbird/8.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] Call for volunteers to review draft-ietf-cuss-sip-uui-isdn X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2011 14:59:05 -0000 Folks: We have two documents that need to be processed through the WG process (the requirements document is with IESG). draft-ietf-cuss-sip-uui (the "mechanism" draft) is being expert reviewed (Martin Dolly and Shida Schubert) with an eye towards covering aspects of H-I as well. Shida has sent in his review [1] and Martin will be doing so shortly. Once Martin's review is in, Enrico and I will request a new revision from the authors of draft-ietf-cuss-sip-uui, followed by a larger WGLC. This leaves us to tackle draft-ietf-cuss-sip-uui-isdn draft. No one has volunteered quite yet to expert review it before a larger WGLC. Enrico and I will like to have at least one dedicated review of draft-ietf-cuss-sip-uui-isdn before we go for a WGLC. Please let us know if you are willing to do an expert review. The review itself will be due Jan-10-2012. Thank you, [1] http://www.ietf.org/mail-archive/web/cuss/current/msg00317.html Vijay K. Gurbani and Enrico Marocco From Martin.Huelsemann@telekom.de Tue Dec 13 05:58:40 2011 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 E168521F84DA for ; Tue, 13 Dec 2011 05:58:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.248 X-Spam-Level: X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 Kbl7F-huUbVd for ; Tue, 13 Dec 2011 05:58:40 -0800 (PST) Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id BFF1B21F8500 for ; Tue, 13 Dec 2011 05:58:39 -0800 (PST) Received: from he101250.emea1.cds.t-internal.com ([10.125.92.153]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 13 Dec 2011 14:57:34 +0100 Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.54]) by HE101250.emea1.cds.t-internal.com ([fe80::e439:4046:12e2:e37%15]) with mapi; Tue, 13 Dec 2011 14:57:34 +0100 From: To: , Date: Tue, 13 Dec 2011 14:57:32 +0100 Thread-Topic: [cuss] "package" vs "purpose" name in draft-ietf-cuss-sip-uui-04 Thread-Index: Acy2gfZXLh2YFRFdRFyeuzOb5HWbtQDFlVmA Message-ID: <9762ACF04FA26B4388476841256BDE020115A56F577B@HE111543.emea1.cds.t-internal.com> References: In-Reply-To: Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: multipart/alternative; boundary="_000_9762ACF04FA26B4388476841256BDE020115A56F577BHE111543eme_" MIME-Version: 1.0 Subject: Re: [cuss] "package" vs "purpose" name in draft-ietf-cuss-sip-uui-04 X-BeenThere: cuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Call Control UUI for SIP \(cuss\) working group discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2011 13:58:41 -0000 --_000_9762ACF04FA26B4388476841256BDE020115A56F577BHE111543eme_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, for sure a package is used for a certain purpose. So I agree with Xavier, f= or the solution itself it doesn't matter if the parameter name is 'package'= or 'purpose', however the name 'purpose' would provide a certain degree of= backward compatibility. Regards, Martin ________________________________ Von: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] Im Auftrag von Xa= vier Marjou Gesendet: Freitag, 9. Dezember 2011 15:50 An: cuss@ietf.org Betreff: [cuss] "package" vs "purpose" name in draft-ietf-cuss-sip-uui-04 Hi, Regarding draft-ietf-cuss-sip-uui-04, one modification I would like is to r= ename the "package" parameter name into "purpose" which existed until draft= -ietf-cuss-sip-uui-00. The goal would to allow compatibility with already d= eployed implementations that are based on the draft-johnston individual dra= ft (draft referenced since a long time in 3GPP documents). There would be n= o change regarding the semantics: the goal of the defined parameter is to i= ndicate the purpose of the application usage of UUI data and this can be fu= lfilled by a parameter called "purpose", in order to indicate how and why U= UI data is used. Cheers, Xavier --_000_9762ACF04FA26B4388476841256BDE020115A56F577BHE111543eme_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
 
for sure a package is used for a certain purpose. So = I agree=20 with Xavier, for the solution itself it doesn't matter if the parameter nam= e is=20 'package' or 'purpose', however the name 'purpose' would provide a certain= =20 degree of backward compatibility.
 
Regards, Martin
 
 
 

Von: cuss-bounces@ietf.org=20 [mailto:cuss-bounces@ietf.org] Im Auftrag von Xavier=20 Marjou
Gesendet: Freitag, 9. Dezember 2011 15:50
An:= =20 cuss@ietf.org
Betreff: [cuss] "package" vs "purpose" name in=20 draft-ietf-cuss-sip-uui-04

Regarding draft-ietf-cuss-sip-uui-04, one modification I wou= ld like=20 is to rename the =93package=94 parameter name into =93purpose=94 which ex= isted until=20 draft-ietf-cuss-sip-uui-00. The goal would to allow compatibility with al= ready=20 deployed implementations that are based on the draft-johnston individual = draft=20 (draft referenced since a long time in 3GPP documents). There would be no= =20 change regarding

--_000_9762ACF04FA26B4388476841256BDE020115A56F577BHE111543eme_-- From vkg@bell-labs.com Thu Dec 15 08:11:15 2011 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 F3C3921F8AD2 for ; Thu, 15 Dec 2011 08:11:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.51 X-Spam-Level: X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5 tests=[AWL=0.089, 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 t5rOlYjhYsfJ for ; Thu, 15 Dec 2011 08:11:14 -0800 (PST) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 13AF221F8ABB for ; Thu, 15 Dec 2011 08:11:14 -0800 (PST) Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id pBFGBAps022990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 15 Dec 2011 10:11:10 -0600 (CST) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBFGBAMq013165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 15 Dec 2011 10:11:10 -0600 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id pBFGBAwh018771 for ; Thu, 15 Dec 2011 10:11:10 -0600 (CST) Message-ID: <4EEA1CF4.4050902@bell-labs.com> Date: Thu, 15 Dec 2011 10:14:44 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111115 Thunderbird/8.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.10 Subject: [cuss] Expert review of sip-uui-isdn draft underway 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, 15 Dec 2011 16:11:15 -0000 Folks: Celine Serrutvalette has agreed to perform an expert review of the UUI ISDN draft (thanks, Celine). The expert review is due Jan-10-2012. The token for a second expert review of the SIP mechanism draft is with Martin Dolly. I suspect that once both these expert reviews are in, Enrico and I will ask the editors to modify their respective drafts and proceed to WGLC. Until then, y'all have a nice holiday season. - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/