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

Andrew Allen <aallen@blackberry.com> Thu, 21 November 2013 17:40 UTC

Return-Path: <aallen@blackberry.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 9E7EC1AE091 for <cuss@ietfa.amsl.com>; Thu, 21 Nov 2013 09:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] 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 ySIu9CQP5aQi for <cuss@ietfa.amsl.com>; Thu, 21 Nov 2013 09:40:29 -0800 (PST)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id DF7F41AE061 for <cuss@ietf.org>; Thu, 21 Nov 2013 09:40:28 -0800 (PST)
Received: from xct105ads.rim.net ([10.67.111.46]) by mhs213cnc.rim.net with ESMTP/TLS/AES128-SHA; 21 Nov 2013 12:40:18 -0500
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.03.0158.001; Thu, 21 Nov 2013 11:40:17 -0600
From: Andrew Allen <aallen@blackberry.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "bruno.chatras@orange.com" <bruno.chatras@orange.com>, "cuss@ietf.org" <cuss@ietf.org>
Thread-Topic: [cuss] "isdn-uui" versus "isdn-network"
Thread-Index: AQHO3wT1dpjYGndAPU2F8sy5W0sV45ouyA4AgAEOYICAAI1wAP//nhIA
Date: Thu, 21 Nov 2013 17:40:17 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338E679F8@XMB104ADS.rim.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>
In-Reply-To: <528E4204.8080304@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
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 17:40:31 -0000

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.