RE: Coding Of Public Signature Algorithm Identifier
"Tom-PT Taylor" <[email protected]> Tue, 14 Jan 2003 14:47:15 -0500
| Newsgroups | gmane.ietf.itrace |
|---|---|
| Message-ID | <[email protected]> |
I took a closer look at X.690 and found that OIDs are coded a bit more compactly than my first guess. The OIDs given in RFC 3279 come out as follows (all numbers in hex): Algorithm Tag Length Value md2WithRSAEncryption: 06 09 2a864886f70d010102 md5WithRSAEncryption 06 09 2a864886f70d010104 sha-1WithRSAEncryption 06 09 2a864886f70d010105 id-dsa-with-sha1 06 07 2a86488e380403 ecdsa-with-SHA1 06 07 2a86488e3d0401 Hence the OIDs range from 9 to 11 octets in total length. I note a discrepancy between what RFC 3279 offers and what list participants have suggested. > -----Original Message----- > From: Taylor, Tom-PT [CAR:5N00:EXCH] > Sent: Tuesday, January 14, 2003 1:22 PM > To: Leech, Marcus [CAR:8M70:EXCH] > Cc: [email protected] > Subject: RE: Coding Of Public Signature Algorithm Identifier > > > I'd estimate something in the order of 20 octets per OID: OID > tag, length, and roughly five integers each with tag, length, > and value. > > > -----Original Message----- > > From: Leech, Marcus [CAR:8M70:EXCH] > > Sent: Tuesday, January 14, 2003 12:56 PM > > To: Taylor, Tom-PT [CAR:5N00:EXCH] > > Cc: [email protected] > > Subject: Re: Coding Of Public Signature Algorithm Identifier > > > > > > "Taylor, Tom-PT [CAR:5N00:EXCH]" wrote: > > > > > > 1) use the OIDs. In that case, how do I specify the > > encoding in our > > > record: use only the value portion of the OID as encoded in > > ASN.1, or > > > use the entire ASN.1 object? > > > > > Much as I dislike OIDs, it might be best here to use the > > entire ASN.1 object. > > It can't be that big, can it? > > > > -- > > > ---------------------------------------------------------------------- > > Marcus Leech Mail: Dept 8M70, > > MS 012, FITZ > > Advisor Phone: (ESN) > > 393-9145 +1 613 763 9145 > > Security Architecture and Planning Fax: (ESN) > > 393-9435 +1 613 763 9435 > > Nortel Networks [email protected] > > -----------------Expressed opinions are my own, not my > > employer's------ > > >