The experimental subtree is used to identify object types used only on an experimental basis. Changing OBJECT IDENTIFIERs once assigned is challenging due to an installed base. Thus, this node should only be used for experiments, such as research efforts that are strictly limited to be short-term projects to investigate and test ideas. More permanent node assignments should be obtained prior to any longer-term or larger- scale deployment to prevent complications if, and when, the solution becomes more widely adopted.
OID reference
nemaExperimental
1.3.6.1.4.1.1206.2
Description
The experimental subtree is used to identify object types used only on an experimental basis. Changing OBJECT IDENTIFIERs once assigned is challenging due to an installed base. Thus, this node should only be used for experiments, such as research efforts that are strictly limited to be short-term projects to investiga…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206 (1206, nema)
- Node code
- 2
- Node name
- nemaExperimental
- Numeric OID
- 1.3.6.1.4.1.1206.2
- URN notation
- urn:oid:1.3.6.1.4.1.1206.2
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 2}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2)}
- {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2)}
- OID-IRI notation
- /1/3/6/1/4/1/1206/2
- /ISO/Identified-Organization/6/1/4/1/1206/2
- /ISO/3/6/1/4/1/1206/2
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/nemaExperimental
- /iso/identified-organization/dod/internet/private/enterprise/nema/nemaExperimental
- /iso/identified-organization/dod/internet/private/enterprises/1206/nemaExperimental
- /iso/identified-organization/dod/internet/private/enterprises/nema/nemaExperimental
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/nemaExperimental
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/nemaExperimental
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/nemaExperimental
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/nemaExperimental
- /iso/org/dod/internet/private/enterprise/1206/nemaExperimental
- /iso/org/dod/internet/private/enterprise/nema/nemaExperimental
- /iso/org/dod/internet/private/enterprises/1206/nemaExperimental
- /iso/org/dod/internet/private/enterprises/nema/nemaExperimental
- /iso/org/dod/internet/private/ldap-enterprise/1206/nemaExperimental
- /iso/org/dod/internet/private/ldap-enterprise/nema/nemaExperimental
- /iso/org/dod/internet/private/vendor-objects/1206/nemaExperimental
- /iso/org/dod/internet/private/vendor-objects/nema/nemaExperimental
- Additional combinations skipped.
Published definitions
Available source records contain 2 distinct definitions; some records may not include a definition.
Show 2 published definitions
nemaExperimental · unspecified
nemaExperimental OBJECT IDENTIFIER ::= { nema 2 }nemaExperimental · current
nemaExperimental OBJECT-IDENTITY
STATUS current
DESCRIPTION "The experimental subtree is used to identify object types used
only on an experimental basis. Changing OBJECT IDENTIFIERs once assigned
is challenging due to an installed base. Thus, this node should only be
used for experiments, such as research efforts that are strictly limited
to be short-term projects to investigate and test ideas. More permanent
node assignments should be obtained prior to any longer-term or larger-
scale deployment to prevent complications if, and when, the solution
becomes more widely adopted."
::= { nema 2 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Definitions without a descriptionNTCIP published standard MIB annexes (reviewed modules)
nemaExperimental · unspecifiedNTCIP published standard MIB annexes (reviewed modules)
Status in source: unspecified.
Names: nemaExperimental
Technical details
{
"smi_kind": "OBJECT IDENTIFIER",
"definition": [
"nemaExperimental",
"OBJECT",
"IDENTIFIER",
"::=",
"{",
"nema",
"2",
"}"
]
}- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 8004 v02, Structure and Identification of Management Information (SMI) Published June 2010 — original PDF
· Official record
Module: NTCIP8004v02
See published definition above
Module imports
{'RFC1155-SMI': ['enterprise'], 'RFC1213-MIB': ['DisplayString']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: The normative Annex A.2 comments the DEFINITIONS header while printing explicit OBJECT IDENTIFIER assignments below it. Activate only that parser header in a same-length derived copy; no OID expression or numeric arc is changed. Literal source definitions and the complete PDF remain available.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: RFC1155-SMI, missing or unreadable imports of protocols. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP8004v0217r.pdf — NTCIP8004v02 (MIB transcription)Related source files and packages:
- NTCIP 8004 v02, Structure and Identification of Management Information (SMI) Published June 2010 — original PDF
- RFC 1155 — original SMI enterprise namespace
- NTCIP8004-NEMA.mib — ITE namespace dependency
Show more related files and packages
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1101:1996, Simple Transportation Management Framework Published December 2001 (Rescinded) — original PDF
· Official record
Module: NEMA_SMI
Same published definition (formatting differs; exact original is in the source file)
Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of enterprises. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1101Rescinded-2006.pdf — NEMA_SMI (MIB transcription) - NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 8004 v01, Structure and Identification of Management Information (SMI) Published May 2008 (superceded by NTCIP 8004 v02) — original PDF
· Official record
Module: NTCIP8004-v01-2008
Module imports
{'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['DisplayString']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: The normative namespace annex prints a module label with a space. Use an equal-length internal parsing label only; all explicit OBJECT IDENTIFIER assignments, numbers and the literal original PDF remain unchanged. This internal label is not an OID registration.
· Download NTCIP8004v0138r.pdf — NTCIP8004-v01-2008 (MIB transcription)
Records for description 1ITE public NTCIP working repository MIBs
nemaExperimental · currentITE public NTCIP working repository MIBs
Status in source: current.
Names: nemaExperimental
Technical details
{
"smi_kind": "OBJECT-IDENTITY",
"definition": [
"nemaExperimental",
"OBJECT-IDENTITY",
"STATUS",
"current",
"DESCRIPTION",
"\"The experimental subtree is used to identify object types used only on an experimental basis. Changing OBJECT IDENTIFIERs once assigned is challenging due to an installed base. Thus, this node should only be used for experiments, such as research efforts that are strictly limited to be short-term projects to investigate and test ideas. More permanent node assignments should be obtained prior to any longer-term or larger- scale deployment to prevent complications if, and when, the solution becomes more widely adopted.\"",
"::=",
"{",
"nema",
"2",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"The experimental subtree is used to identify object types used only on an experimental basis. Changing OBJECT IDENTIFIERs once assigned is challenging due to an installed base. Thus, this node should only be used for experiments, such as research efforts that are strictly limited to be short-term projects to investigate and test ideas. More permanent node assignments should be obtained prior to any longer-term or larger- scale deployment to prevent complications if, and when, the solution becomes more widely adopted."
],
null
]
}- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-8004 — docs/mibs/NTCIP8004-NEMA.mib
Module: NTCIP8004-NEMA
See published definition above
Module imports
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'enterprises']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-8004 — docs/mibs/NTCIP8004-NEMA.mib
Registration
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)
Direct children (2)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.2.1 | exp-global | 1 | 11 | |
| 1.3.6.1.4.1.1206.2.2 | expGlobal | 1 | 15 |
Siblings (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.1 | nemaMgmt | 0 | 0 | |
| 1.3.6.1.4.1.1206.3 | nemaPrivate | 0 | 0 | |
| 1.3.6.1.4.1.1206.4 | transportation | 5 | 4282 |