Re: [Sidrops] I-D Action: draft-ietf-sidrops-6486bis-06.txt

[Ben Maddison <[e-mail]>]

Hi Russ,

On 10/08, Russ Housley wrote:
> Ben:
> 
> Different ASN.1 libraries are better at checking various constraints.
> 
> For example, in pyasn1, these two are equivalent:
> 
>    ver = rfc5280.Version(2)
>    ver = rfc5280.Version('v3')
> 
> However, it does not complain if a value that does not have a name is
> encoded.  That is, it just uses the named values as a more readable
> way to set specific INTEGER values.
> 
Yup. But it was not accidental that I didn't use python for my example!

> <snip/>
> 
> I think all of them are roughly the same to implement, but I tend to
> like the ability to talk about values like "v2" in the text.
> 
I absolutely agree in the case that one implements the necessary data
structures by hand.

However an ASN.1 compiler will usually generate the implementation for
you, and will need to choose how to represent the ASN.1 types in the
language's native types.

My point was that we (module authors) should consider the hints that we
give to compilers in order that they can make good choices.

Cheers,

Ben