Re: [ASN.1] BER/DER encoding of a Set

[John Larmouth]

Bancroft Scott wrote:

 Oops!  You have detected a bug in the X.680, as
 AdditionalComponentTypeList is not even defined.

Is this an agreed defect, and is some-one recording it?

-- 
   Prof John Larmouth
   1 Blueberry Road [EMAIL PROTECTED]
   Bowdon   Tel: +44 161 928 1605
   Cheshire WA14 3LSFax: +44 161 928 8069
   England

Re: [ASN.1] BER/DER encoding of a Set

[Olivier DUBUISSON]

John Larmouth wrote:
 
 Bancroft Scott wrote:
 
  Oops!  You have detected a bug in the X.680, as
  AdditionalComponentTypeList is not even defined.
 
 Is this an agreed defect, and is some-one recording it?

Me, as usual, John!
But don't expect me to produce any administrative defect report.
I'm just recording it and will make sure that the Editor has taken it into
account in the 2002 edition.
-- 
Olivier DUBUISSON
france telecom RD
 _ DTL/MSV - 22307 Lannion Cedex - France
( )   tel: +33 2 96 05 38 50 - fax: +33 2 96 05 39 45
/.\/   --
\_/\   Site ASN.1 : http://asn1.elibel.tm.fr/

Re: [ASN.1] BER/DER encoding of a Set

[Bancroft Scott]

On Thu, 21 Jun 2001, Benoit POSTE wrote:

 
 
 Bancroft Scott wrote:
  
 snip
  I don't have X.680 handy at the moment, but if you check the docs you will
  see that SET requires that new extension additions MUST use tags that are
  canonically greater than any other existing tag in the SET, so the above
  is invalid ASN.1.
 
 
That's what I'd really like it to be, for sure. Unfortunately
 here is what I got from 26.3 :
 
 26.3 The ComponentType types in a set type shall all have
 different tags. (See clause 30.) The tag of each new
 ComponentType added to the AdditionalComponentTypeList shall
 be canonically greater (see 6.4) than those of the other
 components in the AdditionalComponentTypeList.
 
I says the other components in the
 AdditionalComponentTypeList, and not any other component of the
 Set type ... :(
 
Do you mean that greater than any other component in the
 SetType is what was meant in the first place? Of course it makes
 decoding and encoding quite a bit easier, but is it correct to
 interpret it that way?
 
On the other hand, it could be my copy of the norm, but I
 thought 1997 was the latest ...

Oops!  You have detected a bug in the X.680, as
AdditionalComponentTypeList is not even defined.

I'm 99% certain I know the answer, but I'll check with the ITU-T | ISO/IEC
ASN.1 Committee and get back to you.

-
Bancroft Scott   Toll Free:1-888-OSS-ASN1
OSS Nokalva  International:1-732-302-0750
[EMAIL PROTECTED] Tech Support :1-732-302-9669 x-1
1-732-302-9669 x-200 Fax  :1-732-302-0023
http://www.oss.com