Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!RHINO.NCSL.NIST.GOV!tebbutt
From: tebbutt@RHINO.NCSL.NIST.GOV (John Tebbutt)
Newsgroups: comp.protocols.iso
Subject: Re:  An ASN.1 question
Message-ID: <8906061553.AA00672@rhino.ncsl.nist.gov>
Date: 6 Jun 89 15:53:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: National Institute of Standards and Technology (NIST)
Lines: 22

Karl,

I believe that your encoding is legal. In ISO 8825, section 18.2 states that the
encoding of a non-implicit tagged type shall be constructed. The contents octets
should hold the proper encoding of the type from which the tagged type was 
derived (in your example, Integer).

Section 6.3.2 b states that you may use the definite or indefinite length
encoding at your option, if the encoding is constructed.

Since the tagged type in your example was not IMPLICIT, the encoding must be
constructed. And since the encoding must be constructed, you have the option
whether to use the definite or indefinite length encoding FOR THE TAGGED TYPE.
The encoding of the Integer within the contents octets of the tagged type must
be primitive, of course, and so the related length field needs to be of the
definite variety.

Good Luck !

						John Tebbutt
						National Institute of Standards
							and Technology