Subject: Re: Differences between ABNF and ASN.1 specifications

From: Tom-PT Taylor <[email-masked]>
Date: Tue, 31 Oct 2000 15:09:03 -0600

John Segers added the terminationIdList construct with an eye to the
possible future, simply because ASN.1 is less flexible than ABNF.

> -----Original Message-----
> From: Troy Cauble [mailto:[email-masked]]
> Sent: Tuesday, October 31, 2000 1:52 PM
> To: [email-masked]
> Subject: Re: Differences between ABNF and ASN.1 specifications
>
>
> Terry L Anderson wrote:
> >
> > I notice two differences between the ABNF and ASN.1
> specifications and I
> > am wondering if these are intentional or errors.
> >
> > 1. In ASN.1
> > AmmRequest {
> >     terminationID    TerminationIDList,
> >     etc.
> > while in ABNF
> > ammRequest contains TerminationID rather than TerminationIDList
> >
> > TerminationID in both cases can contain wildcards and so be
> effectively
> > a list, but the ASN.1 would allow a list of specific ids
> while the ABNF
> > would not.  Is this intentional?
> >
>
> See the second "NOTE" at the beginning of
> section A.2.  Most of the TerminationIDLists
> in the ASN.1 encoding are lists of one.
>
> (Why is that?)
>
> -troy
>