-
the Type is bound to the object identifier value....meaning u have to
decode the object identifier first and then
look in the specification for the corresponding value of type....
in case of PER encoding...this will be a open type..meaning u will have a
length field followed by the complete encoding.....
"LSM"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.my> cc:
Subject:
07/03/01 06:10
AM
Please respond
to asn1
Hi,
I have a trouble to understand TYPE-IDENTIFIER. How should I encode and
decode
this (from T38):
IFPPacket::=SEQUENCE
{
type-of-msg Type-of-msg,
data-field Data-field OPTIONAL
}
{
primary-ifp-packet TYPE-IDENTIFIER.&Type (IFPPacket)
}
>From the network monitor program, I always see 1 octect, which has the same
value as number of octet of IFPPacket. From X.681:
TYPE-IDENTIFIER ::= CLASS
{
&id OBJECT IDENTIFIER UNIQUE,
&Type
}
WITH SYNTAX {&Type IDENTIFIED BY &id}
But I cannot understand where the above octet comming from.
Thanks a lot.
(See attached file: att1.htm)
(See attached file: att1.htm)
|
Hi,
I have a trouble to understand TYPE-IDENTIFIER. How should I encode and decode this (from T38): IFPPacket::=SEQUENCE
{ type-of-msg Type-of-msg, data-field Data-field OPTIONAL } { primary-ifp-packet TYPE-IDENTIFIER.&Type (IFPPacket) } From the network monitor program, I always see 1 octect, which has the same value as number of octet of IFPPacket. From X.681: TYPE-IDENTIFIER ::= CLASS { &id OBJECT IDENTIFIER UNIQUE, &Type } WITH SYNTAX {&Type IDENTIFIED BY &id} But I cannot understand where the above octet comming from. Thanks a lot.
|
