[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
BER and Attribute Syntax
- To: ietf-ldapext <ietf-ldapext@netscape.com>
- Subject: BER and Attribute Syntax
- From: "Steinitz, Dominic J" <Dominic.J.Steinitz@BritishAirways.com>
- Date: 21 Jun 2001 11:41:20 Z
- Alternate-recipient: Allowed
- Content-identifier: 019843B31DD60017
- Content-return: Allowed
- Conversion: Allowed
- Disclose-recipients: Prohibited
- Original-encoded-information-types: IA5-Text
- X400-content-type: P2-1988 ( 22 )
- X400-mts-identifier: [/c=gb/admd=attmail/prmd=ba/; 019843B31DD60017-BAWMTA]
- X400-originator: Dominic.J.Steinitz@BritishAirways.com
- X400-received: by mta BAWMTA in /c=gb/admd=attmail/prmd=ba/; Relayed; 21 Jun 2001 11:41:20 Z
- X400-received: by /c=gb/admd=attmail/prmd=ba/; Relayed; 21 Jun 2001 11:41:20 Z
- X400-recipients: non-disclosure;
I hope this is the right mailing list for asking these sort of questions. If not can someone please direct me to the correct one.
According to BER, the decimal number 1321should be encoded as Universal Primitive 2 1321= [2,2,5,41] but according to the attribute syntax definitions RFC2252 6.16, INTEGER attributes are encoded as a string of the decimal representation. So to encode an ASN.1 INTEGER we should use BER but to encode an INTEGER attribute we should produce an OctetString of the decimal value. Is this correct?
Dominic.
-------------------------------------------------------------------------------------------------
21st century air travel http://www.britishairways.com
-------------------------------------------------------------------------------------------------
21st century air travel http://www.britishairways.com