| … | |
… | |
| 729 | dot, e.g. C<1.3.6.1.213>. |
729 | dot, e.g. C<1.3.6.1.213>. |
| 730 | |
730 | |
| 731 | =item C<BER_TYPE_RELOID> |
731 | =item C<BER_TYPE_RELOID> |
| 732 | |
732 | |
| 733 | Same as C<BER_TYPE_OID> but uses relative object identifier |
733 | Same as C<BER_TYPE_OID> but uses relative object identifier |
| 734 | encoding: ASN.1 has this hack of encoding the first two OID components |
734 | encoding: ASN.1 uses some hack encoding of the first two OID components |
| 735 | into a single integer in a weird attempt to save an insignificant amount |
735 | into a single integer in a weird attempt to save an insignificant amount |
| 736 | of space in an otherwise wasteful encoding, and relative OIDs are |
736 | of space in an otherwise wasteful encoding, and relative OIDs are |
| 737 | basically OIDs without this hack. The practical difference is that the |
737 | basically OIDs without this hack. The practical difference is that the |
| 738 | second component of an OID can only have the values 1..40, while relative |
738 | second component of an OID can only have the values 1..40, while relative |
| 739 | OIDs do not have this restriction. |
739 | OIDs do not have this restriction. |
