[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
ABNF of numericoid
- To: ietf-ldapbis@OpenLDAP.org
- Subject: ABNF of numericoid
- From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Date: Sun, 7 Dec 2003 23:26:30 +0100
- In-reply-to: <024e01c35736$a7615450$a518200a@osmium.mtwav.adacel.com.au>
- References: <5.2.0.9.0.20030714102517.01d53a78@127.0.0.1> <024e01c35736$a7615450$a518200a@osmium.mtwav.adacel.com.au>
This thread seems to have been forgotten:
[models] and [bcp64] define numericoid as
numericoid = number *( DOT number )
It should be ( "0" / "1" / "2" ) 1*( DOT number )
with further restrictions on the second component.
In message http://www.OpenLDAP.org/lists/ietf-ldapbis/200307/msg00063.html,
Steven Legg writes:
> X.680 defers to X.660 for the definition of OBJECT IDENTIFIER,
> but notes that an OBJECT IDENTIFIER must have at least two components.
> I don't have a copy of X.660 to check what other requirements
> there are, however it is worth noting that the BER encoding of
> OBJECT IDENTIFIER only supports values where the first component
> is 0, 1 or 2. If the first component is 0 or 1 then the second
> component must be in the range 0 to 39. If the first component
> is 2 then the second component is unlimited.
--
Hallvard