Re: [cuss] "isdn-uui" versus "isdn-network"
Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 21 November 2013 18:39 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 2BA741AE03D for <cuss@ietfa.amsl.com>;
Thu, 21 Nov 2013 10:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No,
score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 6sczImULTpIB for
<cuss@ietfa.amsl.com>; Thu, 21 Nov 2013 10:39:35 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net
(qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40])
by ietfa.amsl.com (Postfix) with ESMTP id 420181ADFEF for <cuss@ietf.org>;
Thu, 21 Nov 2013 10:39:35 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by
qmta04.westchester.pa.mail.comcast.net with comcast id sDen1m0031ZXKqc54JfUY6;
Thu, 21 Nov 2013 18:39:28 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by
omta21.westchester.pa.mail.comcast.net with comcast id sJfU1m00B3ZTu2S3hJfUfY;
Thu, 21 Nov 2013 18:39:28 +0000
Message-ID: <528E5360.2010004@alum.mit.edu>
Date: Thu, 21 Nov 2013 10:39:28 -0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: cuss@ietf.org
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>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338E679F8@XMB104ADS.rim.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
s=q20121106; t=1385059168; bh=55LC8TewEzkwYMj+IHc1nPQy8WA1rqfYtUEpkygjMl0=;
h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type;
b=KvlvaaxFwnyx7Ao45xr0dF1uzr78G78WsfQKFfMHIl5DCh02c9IX+tlflTMFpR4B+
7JDT+uxo08L/JldB2ipDpFCyMup51ByvNGEG+tMQW8EazFZQbPgcdl9aNCKC1g9eA+
QgYIJKed8ew097YkYUehN99g1D6U4Q4wTjazhVhPcmSWmpHmlfhYh0LnmPA1WBdtmA
9TNmRafxPmlAa+l15rHWsIkDosIuYdG2yh0/w/61MhdPrYr9aiHzspPlxQIZA7jbgV
VF1D5hEWpHF5j85r3WJwggFngMoIQZNdHjaXpJE8ixCkYFUy+4ZLNYURlwHTGvBpKo
ciwHVmL8aQCdA==
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: Thu, 21 Nov 2013 18:39:37 -0000
I don't care enough to take a position either way. Thanks, Paul On 11/21/13 9:40 AM, Andrew Allen wrote: > Vijay > > I don't think we are talking about applying this to the nth degree I think we are simply recognizing that in this case there are deployed systems out there that we ought to attempt to interoperate with if that can relatively easily be achieved.. > > I am not sure it complicates the parser greatly to have two possible tokens (A or B) as the value of a parameter and then in the call processing logic have an if A or B statement. > > Andrew > > -----Original Message----- > From: Vijay K. Gurbani [mailto:vkg@bell-labs.com] > Sent: Thursday, November 21, 2013 12:25 PM > To: Andrew Allen; bruno.chatras@orange.com; cuss@ietf.org > Subject: Re: [cuss] "isdn-uui" versus "isdn-network" > > [As individual, of course.] > > On 11/21/2013 09:31 AM, Andrew Allen wrote: >> >> I have some sympathy for Bruno's position. He is merely asking to >> align with the principle of "Be strict in what you send, but generous >> in what you receive". > > I must say that I disagree. I suspect that Postel's Law was not designed to allow multiple tokens to represent the same semantic. > Plus, implementing Postel's Law to the n-th degree leads to brittle parsers and easy to attack systems. > > There is a school of thought that parsers for large and complex grammars like SIP should be designed using a language-theoretic approach since these grammars produce essentially a complex language. Such complex grammars are PSPACE-complete, making it daunting to come up with a bullet-proof parser if we keep on adding multiple ways to represent similar concepts. > > But regardless, I don't mean to hammer on this. If folks feel that we need to grandfather "isdn-network", that is fine with me. > > Thanks, > > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent > 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com > Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. > > _______________________________________________ > cuss mailing list > cuss@ietf.org > https://www.ietf.org/mailman/listinfo/cuss >
- [cuss] "isdn-uui" versus "isdn-network" Vijay K. Gurbani
- Re: [cuss] "isdn-uui" versus "isdn-network" bruno.chatras
- Re: [cuss] "isdn-uui" versus "isdn-network" Vijay K. Gurbani
- Re: [cuss] "isdn-uui" versus "isdn-network" Andrew Allen
- Re: [cuss] "isdn-uui" versus "isdn-network" Vijay K. Gurbani
- Re: [cuss] "isdn-uui" versus "isdn-network" Andrew Allen
- Re: [cuss] "isdn-uui" versus "isdn-network" Paul Kyzivat
- Re: [cuss] "isdn-uui" versus "isdn-network" Vijay K. Gurbani
- Re: [cuss] "isdn-uui" versus "isdn-network" Christer Holmberg
- Re: [cuss] "isdn-uui" versus "isdn-network" Atle Monrad
- Re: [cuss] "isdn-uui" versus "isdn-network" Vijay K. Gurbani
- Re: [cuss] "isdn-uui" versus "isdn-network" Christer Holmberg
- Re: [cuss] "isdn-uui" versus "isdn-network" bruno.chatras
- Re: [cuss] "isdn-uui" versus "isdn-network" Belling, Thomas (NSN - DE/Munich)
- Re: [cuss] "isdn-uui" versus "isdn-network" DRAGE, Keith (Keith)
- Re: [cuss] "isdn-uui" versus "isdn-network" R.Jesske
- Re: [cuss] "isdn-uui" versus "isdn-network" bruno.chatras
- Re: [cuss] "isdn-uui" versus "isdn-network" Atle Monrad