Re: [cuss] ABNF in UUI documents

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 20 February 2013 16:31 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 8142321F88F1 for <cuss@ietfa.amsl.com>; Wed, 20 Feb 2013 08:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.355
X-Spam-Level:
X-Spam-Status: No, score=-0.355 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FYLjYpBnKkHD for <cuss@ietfa.amsl.com>; Wed, 20 Feb 2013 08:31:40 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 670A921F86BA for <cuss@ietf.org>; Wed, 20 Feb 2013 08:31:40 -0800 (PST)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta05.westchester.pa.mail.comcast.net with comcast id 2bHW1l0020SCNGk55gXfNw; Wed, 20 Feb 2013 16:31:39 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta09.westchester.pa.mail.comcast.net with comcast id 2gXf1l01C3ZTu2S3VgXffG; Wed, 20 Feb 2013 16:31:39 +0000
Message-ID: <5124FA6B.30704@alum.mit.edu>
Date: Wed, 20 Feb 2013 11:31:39 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: cuss@ietf.org
References: <EDC0A1AE77C57744B664A310A0B23AE21070160D6A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21070160D6A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
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=1361377899; bh=K4dK3DIWEQB0x3Hlsm62vz1t3ApxMUhMqNIALTnksJo=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=pdxb+8sD0dpUtVgSTI0tPxnV3GNijRhXGB2cdkaeJZopR3+nWbfZix/mh/H8oVuP3 5i/xoKbQjgEly3sWEZ8WBOI8Mr/RwjNNAx9UVWDcvI+nu0pK9L8SKK564U5COJdm80 SJrKyqicJMKkEb4BdtjeZfRsvnC1uH/weaS0ujApfSU7+dqCp+41eyOMaAeu72/RCV 5hohytqNKE1FA8/ukmnGeJTcu9fXc73nnq7HZacC72ie+GCSZ+nCe9Go5m9xoWzj0Q jUZVfVGm1NTqpU0NMC/3arCKYQyIOwC4epxCSOJUef1Yq8Ik70F3aqr1tslz+Kh0oP qcpxfXfJiEiBw==
Subject: Re: [cuss] ABNF in UUI documents
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" <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: Wed, 20 Feb 2013 16:31:41 -0000

Keith,

We are establishing a registry for purpose/package values.
IMO you should use that for "isdn-uui", rather than extending the syntax 
to include it.

	Thanks,
	Paul

On 2/20/13 7:04 AM, DRAGE, Keith (Keith) wrote:
> I make the ABNF more formal in the UUISDN document, and that requires a change to the UUI document.
>
> Currently section 11 of draft-ietf-cuss-sip-uui-isdn-04 defines.
>
> 11.  Coding requirements
>
>     This document defines "isdn-uui" as a new value of the User-to-User
>     "purpose" header field parameter.
>
>     This document defines "isdn-uui" as a new value of the User-to-User
>     "content" header field parameter.  A content value of "isdn-uui"
>     indicates that the contents have a first octet that is a protocol
>     discriminator (see table 4-26 of ITU-T Recommendation Q.931) [Q931]
>     followed by uui-data that can be subject to a length limitation
>     (before encoding or after decoding) that is generally 128 octets.
>
> My question is whether this should define BNF to add this to the BNF of draft-ietf-cuss-sip-uui which is currently.
>
>          UUI         = "User-to-User" HCOLON uui-value *(COMMA uui-value)
>          uui-value   = uui-data *(SEMI uui-param)
>          uui-data    = token / quoted-string
>          uui-param   = pkg-param / cont-param / enc-param / generic-param
>          pkg-param   = "purpose" EQUAL token
>          cont-param  = "content" EQUAL token
>          enc-param   = "encoding" EQUAL ("hex" / token)
>
> If we did this I guess it would look something like:
>
>          pkg-param   = "purpose" EQUAL "isdn-uui" / token
>          cont-param  = "content" EQUAL "isdn-uui" / token
>
> Originally I was thinking we could do something like
>
> 	pkg-param-value /= "isdn-uui"
>
> but that would require an update to draft-ietf-cuss-sip-uui to do:
>
>          pkg-param   = "purpose" EQUAL pkg-param-value
> 	  pkg-param-value = token
>
> Can we make this change to the UUI document, and I'll then follow through with the UUI ISDN document?
>
> regards
>
> Keith
> _______________________________________________
> cuss mailing list
> cuss@ietf.org
> https://www.ietf.org/mailman/listinfo/cuss
>