OID Repository https://oid-base.com Display OID:

iso(1) identified-organization(3) dod(6) internet(1)
directory(1) -- 24 child OIDs -- reserved(0) nisSchema(1) nameForm(2) auxObject(3) vendorName(4) vendorVersion(5) pcimSchema(6) lcup(7) cancelOp(8) pcelsSchema(9) uddi(10) vPIM(11) assertion(12) readEntry(13) increment(14) x509(15) uuid(16) lburp(17) ldap(18) turnValue(19) entryDN(20) txn(21) dontUseCopy(22) xmpp(23)

OID description

OID: {iso(1) identified-organization(3) dod(6) internet(1) directory(1)} (ASN.1 notation) 1.3.6.1.1 (dot notation) /ISO/Identified-Organization/6/1/1 (OID-IRI notation)

Description: Structure of Management Information (SMI) network management directory

Information: Defined in IETF RFC 1155. See also IETF RFC 2578 and IETF RFC 4520. Child OIDs are listed as Lightweight Directory Access Protocol (LDAP) Parameters. This OID is used for the ISODE/PSINet White Pages pilot, and as a root of some further assignments like the Network Information Service (NIS) schema OID of IETF RFC 2307. For registration procedures, see IETF RFC 3383, section 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 the Internet Assigned Numbers Authority (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" (IETF RFC 1155). -----

Short URL for this page: Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer). All rights reserved © 2007-2024

Webmaster

1 Feb 2022