Hi,

If somebody could help me understand this, it will be of great help to me.

This is using PER unaligned coding..

1. The extension additions after the "..., " should they be treated as
an open type component?

PE::Sequence{
ec1     EC1,
ec2     EC2,
...,

ext1 EXT1 OPTIONAL,

}


EXT1::=Sequence {
er      ER      OPTIONAL,
...
}

ER{

int1 integer (0..63)
int2 Integer(0..262413)

}
For example inorder to encode the following extension addition for the
PE sequence, after encoding ec1 and ec2, the binaries would like the
following:: for ext1 - extension addtion sequence encoding. 

EXT1_EXT        0       - Not Included

ER_Optional     1       - Included

int1     Length 0x00 = represents 1byte
int1    0x01

int2    Length 0x02 = represents 3bytes
int2    0x010000

2. If we don't consider it as an open type then, we encode this PE as
the components before "...," am I correct?

Thanks,
Nirupama.


_______________________________________________
ASN1 mailing list
[email protected]
http://lists.asn1.org/mailman/listinfo/asn1

Reply via email to