hi, We actually are concerned about representing the L portion of the TLV where L > 255.As mentioned in my query,this L cannot be accomodated in a single octet. So,we would like to know how to represent this using BER recommandations without using any standard ASN.1 Compilers.
thanks and regards kb devaraj --- Prajnananda Tripathy <[EMAIL PROTECTED]> wrote: > > Hi Dev > If i undertand correctly , is it the same tag > which is used for BER.Do u > want to derive at the tag number which is more than > two octet? > > Prajnananda > -----Original Message----- > From: deva raj [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 16, 2001 01:14 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [ASN.1] BER Decoding Clarifications > > > Hi all, > > In a custom protocol implementation , I am planning > to > use BER. In this case, the first octet represent the > > application tag (definable using a single octet) . > But if the length of the content exceeds 255 octets > , > then how many octets beginning from the second > positin > must be accounted for determining the length of the > content. > > To put in short, how many octets will represent the > value portion of TLV if the length exceeds 255 > octets > which obviously cannot be accomodated in single > octet > representing length > > I am trying to encode and decode by using our own > logic without using any standard ASN.1 Compilers. > > Thanks in advance > > > Devaraj > > > __________________________________________________ > Do You Yahoo!? > Make a great connection at Yahoo! Personals. > http://personals.yahoo.com __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
