W3C home > Mailing lists > Public > ietf-discuss@w3.org > April 2001

Re: Two new drafts: Multipart/Interleaved and Application /BatchBeep

From: Keith Moore <moore@cs.utk.edu>
Date: Tue, 24 Apr 2001 16:06:44 -0400
Message-Id: <200104242006.QAA18235@astro.cs.utk.edu>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
cc: discuss@apps.ietf.org
> And, of course, none of this has to do with ASN.1 but rather to do
> with BER, PER, DER, etc., i.e., with particular ASN.1 Encoding
> Rules.

actually, I think it has more to do with the way you use ASN.1
(i.e. the actual ASN.1 specification for your protocol)
than any of the ways of encoding ASN.1

in other words, if you decide that your protocol will implicitly
determine field tags by position then you use ASN.1 SEQUENCE
but if you decide that field tags should be explicit then you'll
use some sort of OPTIONAL structure that contains the tag and
the value [*]  and if you decide that your protocol will expose
(say) the entire structure of an email address in the ASN.1 layer
then it will naturally take up more space than if you just encode
the entire email address as a single IA5STRING.

[*] if memory serves... but I have done my best to forget how ASN.1
works.  so if you claim I've made errors I'll only congratulate
myself on how much I've forgotten.


let's stamp out gratuitous use of *both* ASN.1 and XML in our lifetime!
Received on Tuesday, 24 April 2001 16:07:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:08:11 UTC