Re: [cuss] ABNF in UUI documents

These issues are orthogonal.

Placing a value in an IANA registry does not define it, all it does is make some attempt at stopping someone else from using it for a different purpose.

The normative definition is the base RFC. 

All I am doing is ensuring that the ABNF defines the values, rather than the text. If you extract the ABNF from both documents and combine them, then you can very strings against it.

What I am proposing is exactly what has been done for some, but not all, attribute values in SDP.

Keith

> -----Original Message-----
> From: cuss-bounces@ietf.org [mailto:cuss-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: 20 February 2013 16:32
> To: cuss@ietf.org
> Subject: Re: [cuss] ABNF in UUI documents
> 
> 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
> >
> 
> _______________________________________________
> cuss mailing list
> cuss@ietf.org
> https://www.ietf.org/mailman/listinfo/cuss