Reference record for OID 1.3.6.1.1

parent

1.3.6.1 (internet)

node code

1

node name

directory

dot oid

1.3.6.1.1

type

OBJECT IDENTIFIER

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) directory(1)}

{iso(1) org(3) dod(6) internet(1) directory(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) directory(1)}

iri oid

/iso/identified-organization/dod/internet/directory

/iso/org/dod/internet/directory

/iso/iso-identified-organization/dod/internet/directory

iri by oid_info

/ISO/Identified-Organization/6/1/1

Description by oid_info

Structure of Management Information (SMI) Network Management Directory
View at oid-info.com

Information by circitor

directory    OBJECT IDENTIFIER ::= { internet 1 }

Information by cisco_v1

directory       OBJECT IDENTIFIER ::= { internet 1 }

Information by oid_info

Child OIDs are listed at Lightweight Directory Access Protocol (LDAP) Parameters.

See IETF RFC 2578 and RFC 4520.

This OID is used for the ISODE/PSINet White Pages pilot, and as a root of some further assignments like the NIS Schema OID of IETF RFC 2307.

For registration procedures, see IETF RFC 3383, 3.1:
-----
Numerous LDAP schema and protocol elements are identified by Object Identifiers. Specifications which assign OIDs to elements SHOULD state who delegated the OIDs for its use.
For IETF developed elements, specifications SHOULD use OIDs under "Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID arc will be assigned upon Expert Review with Specification Required.
Only one OID per specification will be assigned. The specification MAY then assign any number of OIDs within this arc without further coordination with IANA.
For elements developed by others, any properly delegated OID can be used, including those under "Internet Private Enterprise Numbers" (1.3.6.1.4.1.x) assigned by IANA.
To avoid interoperability problems between early implementations of "works in progress" and implementations of the published specification (e.g., the RFC), experimental OIDs SHOULD be used in "works in progress" and early implementations. OIDs under the Internet Experimental OID arc (1.3.6.1.3.x) may be used for this purpose.
Experimental OIDs are not to used in published specifications (e.g., RFCs).
Practices for IANA assignment of Internet Enterprise and Experimental OIDs are detailed in STD 16 [RFC1155].
-----

Information by mibdepot

directory     OBJECT IDENTIFIER ::= { internet 1 }

Information by cisco

directory      OBJECT IDENTIFIER ::= { internet 1 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6)

US DoD

Children (23)

Brothers (7)