Subject: RE:

From: "Tom-PT Taylor" <[email-masked]>
Date: Fri, 25 May 2001 09:52:04 -0400

The text of the specification has to be given some consideration in
evaluating the grammar.  Section 7.2.8 describes the circumstances under
which the various parameters are required.  That said, you'll also notice
another difference between the ABNF and ASN.1: the latter imposes an order
on the presentation of parameters.

> -----Original Message-----
> From: Atanu Mondal [mailto:[email-masked]]
> Sent: Tuesday, May 22, 2001 3:21 AM
> To: [email-masked]'
> Cc: [email-masked]'
> Subject: 
> 
> 
> Dear List
> 
> The serviceChangeParm as described in ABNF spec is as below
> serviceChangeParm = (serviceChangeMethod
> /serviceChangeReason/serviceChangeDelay/serviceChangeAddress/s
> erviceChangePr
> ofile/extension/TimeStamp/serviceChangeMgcId/serviceChangeVersion )
>  which makes all the parameters a s optional.
> 
> In ASN syntax the serviceChangeParm is described as below
> 
> serviceChangeParm ::= SEQUENCE
> {
> 	serviceChangeMethod	ServiceChangeMethod,
> 	serviceChangeAddress	ServiceChangeAddress	OPTIONAL,
> 	serviceChangeVersion	INTEGER(0..99)		OPTIONAL,
> 	serviceChangeProfile	ServiceChangeProfile	OPTIONAL,
> 	serviceChangeReason	Value			
> 	serviceChangeDelay	INTEGER(0..4294967295) OPTIONAL,
> 	serviceChangeMgcId	MId 	OPTIONAL,
> 	timeStamp		TimeNotation	OPTIONAL,
> 	nonStandardData	NonStandardData	OPTIONAL,
> }
> 
> Which makes the ServiceChangeMethod as compulsory and the 
> rest optional.
> What is the reason for this decrepency between the two 
> version(ASN and ABNF)
> 
> If anybody can clarify the reason for this decrepency it will be very
> helpful
> Thanking in advance
> 
> Regards
> Atanu
>