Subject: ABNF and ASN decrepency......

From: "Atanum" <[email-masked]>
Date: Wed, 4 Jul 2001 16:32:24 +0530

Hi,
the contextRequest is defined to contain contextProperties.. and the contextProperties in turn is defined as below..(with a *)

contextProperties = contextProperty *(COMMA contextProperty)

So does it mean that 

contextProperties  = topologyDescriptor, priority, priority, EmergencyToken, priority, EmergencyToken....etc

So that when we replace contextProperties in the definition of contextRequest.. then it will

contain multiple priority and emergency token...

Regards
Atanu

-**--**--**--**--**--**--**--**--**--**--**--**--**--**-
Ipek Sarac
Oxygen Technologies 
Atatürk Havalimani Serbest Bölge, Plaza Ofis 8K N810-840 34830 
YEŞİLKÖY
İstanbul / TURKEY 
E-mail: [email-masked] 
-**--**--**--**--**--**--**--**--**--**--**--**--**--**-

> 
> Kimden: "Atanum" <[email-masked]>
> Tarih: 2001/07/04 Wed PM 01:32:40 GMT+03:00
> Kime: <[email-masked]>
> CC: "Rosen, Brian" <[email-masked]>,
>         "Madhu Babu Brahmanapally" <[email-masked]>
> 
> Hi Everybody,
> The ABNF spec for megaco defines context property as below
> 
> 
> ;at-most-once
> contextProperty = (topologyDescriptor / priority / EmergencyToken)
> 
> This allows contextRequest to have n numbers of topologyDescriptor,
priority and EmergencyToken in any combination
> according to the ABNF definition...
> 
> On the other hand the ASN spec says that ContextRequest will contain
only one priority and one emergency and a 
> sequence of topologyReq..
> 
> In this case which definition one is supposed to follow.....
> 
> For a stack supporting both the parser.. it becomes difficult in
forming the commands if there is a decrepency in the
> grammer of the two spec....
> 
> Can anyone please clarify...
> 
> Thanking in advance
> 
> Atanu Mondal
> Net Brahma Technologies
> Internext Networking Software
> A Microland Group Venture
> 
> 
>