IETF Logo Mail Archive

Re: [cuss] "isdn-uui" versus "isdn-network"

"Belling, Thomas (NSN - DE/Munich)" <thomas.belling@nsn.com> Mon, 25 November 2013 11:34 UTC

Return-Path: <thomas.belling@nsn.com>
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 CD5101AD8E3 for <cuss@ietfa.amsl.com>; Mon, 25 Nov 2013 03:34:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 b5xyclE4oO2a for <cuss@ietfa.amsl.com>; Mon, 25 Nov 2013 03:34:42 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 987771ACCFC for <cuss@ietf.org>; Mon, 25 Nov 2013 03:34:41 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rAPBYccE009233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 25 Nov 2013 12:34:38 +0100
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rAPBYbaS000320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Nov 2013 12:34:37 +0100
Received: from DEMUHTC010.nsn-intra.net (10.159.42.41) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 25 Nov 2013 12:34:37 +0100
Received: from DEMUMBX001.nsn-intra.net ([169.254.1.156]) by DEMUHTC010.nsn-intra.net ([10.159.42.41]) with mapi id 14.03.0123.003; Mon, 25 Nov 2013 12:34:37 +0100
From: "Belling, Thomas (NSN - DE/Munich)" <thomas.belling@nsn.com>
To: "ext Vijay K. Gurbani" <vkg@bell-labs.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] "isdn-uui" versus "isdn-network"
Thread-Index: AQHO3wT0/rnx1aTdzE2fpUK6uaPrRZouX5ewgAFvMwCAAB+7AIAABCiAgAAWioCAAYtzgIAABZoAgARJUDA=
Date: Mon, 25 Nov 2013 11:34:35 +0000
Message-ID: <BDBE1A97E84675488F72A48C23811F3515DB08D1@DEMUMBX001.nsn-intra.net>
References: <5281161C.1060404@bell-labs.com> <17974_1384966290_528CE892_17974_4141_1_88CAD1D4E8773F42858B58CAA28272A0112D245F@PEXCVZYM12.corporate.adroot.infra.ftgroup> <BBF5DDFE515C3946BC18D733B20DAD2338E677A4@XMB104ADS.rim.net> <528E4204.8080304@bell-labs.com> <BBF5DDFE515C3946BC18D733B20DAD2338E679F8@XMB104ADS.rim.net> <528E5869.7080905@bell-labs.com> <7D2F7D7ADBA812449F25F4A69922881C209134@ESESSMB203.ericsson.se> <528FA8D6.8050301@bell-labs.com>
In-Reply-To: <528FA8D6.8050301@bell-labs.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2034
X-purgate-ID: 151667::1385379278-00006154-EAB8784B/0-0/0-0
Subject: Re: [cuss] "isdn-uui" versus "isdn-network"
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" <cuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cuss>, <mailto:cuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cuss/>
List-Post: <mailto:cuss@ietf.org>
List-Help: <mailto:cuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cuss>, <mailto:cuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2013 11:34:45 -0000

For me, it is also quite important to finalize the work.

I have a certain sympathy for considering backward compatibility, as I understand that the concerns relate to real deployments and seem of interest to make things work in reality. I thus support related wording in the draft.

I understand the point that drafts should be regarded as experimental and subject to change. However, this is only fine if features demanded in the market are finalized within a reasonable time. If work goes on for about five years (as in the current case), backward compatibility will become a real concern no matter if purists like it. The main takeaway could be to aim to finalize work in a reasonable amount of time.

BR, Thomas


----------------------------------
Dr. Thomas Belling 
3GPP Standardisation
NSN



-----Original Message-----
From: cuss [mailto:cuss-bounces@ietf.org] On Behalf Of ext Vijay K. Gurbani
Sent: Friday, November 22, 2013 7:56 PM
To: cuss@ietf.org
Subject: Re: [cuss] "isdn-uui" versus "isdn-network"

On 11/22/2013 12:36 PM, Atle Monrad wrote:
> Hi
>
> I guess each of the "shall we allow multiple representations" needs to 
> be handled on a case-by-case basis, but generally speaking I 
> understand that the chairs and ADs aren't too enthusiastic with too 
> many ...
>
> What 3GPP really wants for Christmas is the draft to be completed.
> Somebody must take a decision on this soon.

... which means that by Nov 29, 2013 it'd be nice to hear from others who have an opinion.

Many thanks to those who have already expressed one.

Cheers,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq _______________________________________________
cuss mailing list
cuss@ietf.org
https://www.ietf.org/mailman/listinfo/cuss

v2.23.0 | Report a Bug | By Email