OID reference

auxiliaryIO

1.3.6.1.4.1.1206.2.2.1

Description

<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.2.2 (expGlobal)
Node code
1
Node name
auxiliaryIO
Numeric OID
1.3.6.1.4.1.1206.2.2.1
URN notation
urn:oid:1.3.6.1.4.1.1206.2.2.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 2 2 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) nemaExperimental(2) expGlobal(2) auxiliaryIO(1)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/2/2/1
  • /ISO/Identified-Organization/6/1/4/1/1206/2/2/1
  • /ISO/3/6/1/4/1/1206/2/2/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/enterprise/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/enterprises/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/enterprises/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/enterprise/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/enterprise/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/enterprises/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/enterprises/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/ldap-enterprise/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/ldap-enterprise/nema/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/vendor-objects/1206/nemaExperimental/expGlobal/auxiliaryIO
  • /iso/org/dod/internet/private/vendor-objects/nema/nemaExperimental/expGlobal/auxiliaryIO
  • Additional combinations skipped.

Available source records contain 3 distinct definitions; some records may not include a definition.

Show 3 published definitions

auxiliaryIO · unspecified

auxiliaryIO OBJECT IDENTIFIER ::= { expGlobal 1}

auxiliaryIO · unspecified

auxiliaryIO MODULE-IDENTITY
  LAST-UPDATED "202210010000Z"
  ORGANIZATION "NTCIP BSP2 WG"
  CONTACT-INFO
   "name: NTCIP Coordinator
    email: ntcip@nema.org
    postal: National Electrical Manufacturers Association
            1300 North 17th Street, Suite 1752
            Rosslyn, Virginia 22209-3801"
  DESCRIPTION
    "<Definition> This MIB defines the SMIv2 representation of the AuxIO 
     objects that were previously defined in NTCIP 1201 v03. 

     This MIB contains the auxiliary input/output (I/O) objects originally 
     defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the 
     experimental node. When the objects were moved to NTCIP 1201 v02, a 
     slightly revised structure was developed under the global node and the 
     original experimental objects were deprecated. This MIB is provided for 
     backwards compatibility to support access to the experimental objects 
     via an SNMPv3 proxy agent.

     In the context of implementation that supports these objects, there is 
     no difference between what appeared in NTCIP 1203:1997 and what appears 
     here.

     The auxiliary I/O management objects listed herein define a 
     mechanism for the support of unspecified I/O for an NTCIP device.  
     The agency or device specifications should define the intended operation 
     of these ports.
   
     NOTE: These objects are still logically located under the 
     nemaExperimental node and use their originally defined textual names and 
     OIDs. For the purposes of backward compatibility, the object STATUS has 
     been changed to deprecated. For those agents that may support these 
     objects and the new objects under the global node (see Section 2.9), the 
     object definitions shall be treated as aliases in that a write to an 
     object in one group acts as write to the corresponding object in the 
     other group. As aliases, a read of an object in one group also acts as 
     read of the corresponding object in the other group.

     Early NTCIP deployments included the Aux I/O objects defined in NTCIP 
     1203 v01 located under an experimental node.  These objects were moved 
     to a permanent node with the release of NTCIP 1201 v02 and given new 
     names.  This can create confusion and backward compatibility issues.  
     As noted in the object definition, both sets of objects refer to the 
     same functions within the device; hence, both sets of objects cause the
     same device action or provide the same device status.  
     Agency specifications which do NOT require support for the Aux I/O 
     objects under the experimental node should exclude the support 
     for these experimental objects (which have been deprecated) to ensure 
     backward compatibility.  Support of the Aux I/O objects under the 
     permanent node identified in NTCIP 1201 v03 may be optional 
     or mandatory depending on the agency- or project specification.  

     Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O 
     objects. The relationship between mandatory and optional support of
     NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to 
     the Aux I/O objects.


           *** All objects in this MIB have been deprecated. ***

     <Object Identifier> 1.3.6.1.4.1.1206.2.2.1

     Copyright (C) 2010, 2022 by the American Association of State Highway 
     and Transportation Officials (AASHTO), the Institute of Transportation
     Engineers (ITE), and the National Electrical Manufacturers Association
     (NEMA). All intellectual property rights, including, but not limited to,
     the rights of reproduction in whole or in part in any form, translation
     into other languages and display are reserved by the copyright owners 
     under the laws of the United States of America, the Universal Copyright
     Convention, the Berne Convention, and the International and Pan American
     Copyright Conventions. 

                         Joint NEMA, AASHTO, and ITE
                      NTCIP Management Information Base
                            DISTRIBUTION NOTICE
    
     To the extent and in the limited event these materials are distributed 
     by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) 
     module, AASHTO/ITE/NEMA extends the permission for users to make and/or 
     distribute unlimited copies of the unedited MIB module, including copies 
     for commercial distribution, provided that each copy made and/or 
     distributed contains this Notice.

     The MIB module may be distributed with a companion MIB module that 
     contains one or more invocations of the AGENT-CAPABILITIES macro that 
     specifies the capabilities of a specific implementation. By convention, 
     such a companion MIB module might have the same module name followed by 
     '-', followed the enterprise's Internet Assigned Number Authority 
     (IANA)-assigned enterprise number.

     These materials are delivered 'AS IS' without any warranties as to their
     use or performance.
 
     AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR
     RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND 
     THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO 
     NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR 
     ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR 
     SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY 
     CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS 
     OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE 
     MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN 
     ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions 
     do not allow the exclusion or limitation of incidental, consequential or 
     special damages, or the exclusion of implied warranties, so the above 
     limitations may not apply to you.

     Use of these materials does not constitute an endorsement or affiliation 
     by or between AASHTO, ITE, or NEMA and you, your company, or your 
     products and services.

     NTCIP is a trademark of AASHTO/ITE/NEMA."
  REVISION "202210010000Z"
  DESCRIPTION
    "NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously 
     deprecated)."
  REVISION "200610020000Z"
  DESCRIPTION  
    "NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all 
     objects. "
::= { expGlobal 1}

auxiliaryIO · unspecified

auxiliaryIO MODULE-IDENTITY
LAST-UPDATED "20230701145436Z"
ORGANIZATION "NTCIP BSP2 WG"
CONTACT-INFO
  "name: NTCIP Coordinator
   email: ntcip@nema.org
   postal: National Electrical Manufacturers Association
            1300 North 17th Street, Suite 1752
            Rosslyn, Virginia 22209-3801"
DESCRIPTION
  "<Definition> This MIB defines the SMIv2 representation of the AuxIO
  objects that were previously defined in NTCIP 1201 v03.
  This MIB contains the auxiliary input/output (I/O) objects originally
  defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental
  node. When the objects were moved to NTCIP 1201 v02, a slightly revised
  structure was developed under the global node and the original experimental
  objects were deprecated. This MIB is provided for backwards compatibility
  to support access to the experimental objects via an SNMPv3 proxy agent.
  In the context of implementation that supports these objects, there is no
  difference between what appeared in NTCIP 1203:1997 and what appears here.
  The auxiliary I/O management objects listed herein define a mechanism for
  the support of unspecified I/O for an NTCIP device. The agency or device
  specifications should define the intended operation of these ports.
  NOTE: These objects are still logically located under the nemaExperimental
  node and use their originally defined textual names and OIDs. For the
  purposes of backward compatibility, the object STATUS has been changed to
  deprecated. For those agents that may support these objects and the new
  objects under the global node (see Section 2.9), the object definitions
  shall be treated as aliases in that a write to an object in one group acts
  as write to the corresponding object in the other group. As aliases, a read
  of an object in one group also acts as read of the corresponding object in
  the other group.



                                                                                                         

                 
       

  Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203
  v01 located under an experimental node. These objects were moved to a
  permanent node with the release of NTCIP 1201 v02 and given new names. This
  can create confusion and backward compatibility issues. As noted in the
  object definition, both sets of objects refer to the same functions within
  the device; hence, both sets of objects cause the same device action or
  provide the same device status. Agency specifications which do NOT require
  support for the Aux I/O objects under the experimental node should exclude
  the support for these experimental objects (which have been deprecated) to
  ensure backward compatibility. Support of the Aux I/O objects under the
  permanent node identified in NTCIP 1201 v03 may be optional or mandatory
  depending on the agency- or project specification.
  Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects.
  The relationship between mandatory and optional support of NTCIP 1201 v01
  (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects.
  *** All objects in this MIB have been deprecated. ***
  <Object Identifier> 1.3.6.1.4.1.1206.2.2.1"
REVISION "20230701145436Z"
DESCRIPTION
  "NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously
  deprecated)."
REVISION "200610020000Z"
DESCRIPTION
  "NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all
  objects."
::= { expGlobal 1 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA.

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

3 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Definitions without a descriptionNTCIP published standard MIB annexes (reviewed modules)1 record · 1 source
auxiliaryIO · unspecifiedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unspecified.

Names: auxiliaryIO

Technical details
{
  "smi_kind": "OBJECT IDENTIFIER",
  "definition": [
    "auxiliaryIO",
    "OBJECT",
    "IDENTIFIER",
    "::=",
    "{",
    "expGlobal",
    "1",
    "}"
  ]
}
Records for description 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

auxiliaryIO · unspecifiedITE public NTCIP working repository MIBs1 source

Status in source: unspecified.

Names: auxiliaryIO

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "auxiliaryIO",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230323231303031303030305a22"
    ],
    "ORGANIZATION",
    "\"NTCIP BSP2 WG\"",
    "CONTACT-INFO",
    "\"name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801\"",
    "DESCRIPTION",
    "\"<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA.\"",
    "REVISION",
    [
      "literal",
      "223230323231303031303030305a22"
    ],
    "DESCRIPTION",
    "\"NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously deprecated).\"",
    "REVISION",
    [
      "literal",
      "223230303631303032303030305a22"
    ],
    "DESCRIPTION",
    "\"NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all objects. \"",
    "::=",
    "{",
    "expGlobal",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "202210010000Z"
    ],
    [
      "ORGANIZATION",
      "NTCIP BSP2 WG"
    ],
    [
      "CONTACT-INFO",
      "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801"
    ],
    [
      "DESCRIPTION",
      "<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA."
    ],
    [
      "Revisions",
      [
        [
          "202210010000Z",
          [
            "DESCRIPTION",
            "NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously deprecated)."
          ]
        ],
        [
          "200610020000Z",
          [
            "DESCRIPTION",
            "NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all objects."
          ]
        ]
      ]
    ]
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

auxiliaryIO · unspecifiedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unspecified.

Names: auxiliaryIO

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "auxiliaryIO",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "2232303233303730313134353433365a22"
    ],
    "ORGANIZATION",
    "\"NTCIP BSP2 WG\"",
    "CONTACT-INFO",
    "\"name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801\"",
    "DESCRIPTION",
    "\"<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1\"",
    "REVISION",
    [
      "literal",
      "2232303233303730313134353433365a22"
    ],
    "DESCRIPTION",
    "\"NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously deprecated).\"",
    "REVISION",
    [
      "literal",
      "223230303631303032303030305a22"
    ],
    "DESCRIPTION",
    "\"NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all objects.\"",
    "::=",
    "{",
    "expGlobal",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "20230701145436Z"
    ],
    [
      "ORGANIZATION",
      "NTCIP BSP2 WG"
    ],
    [
      "CONTACT-INFO",
      "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801"
    ],
    [
      "DESCRIPTION",
      "<Definition> This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** <Object Identifier> 1.3.6.1.4.1.1206.2.2.1"
    ],
    [
      "Revisions",
      [
        [
          "20230701145436Z",
          [
            "DESCRIPTION",
            "NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously deprecated)."
          ]
        ],
        [
          "200610020000Z",
          [
            "DESCRIPTION",
            "NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all objects."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.2.2.1.1 maxAuxIODigital00
1.3.6.1.4.1.1206.2.2.1.2 maxAuxIOAnalog00
1.3.6.1.4.1.1206.2.2.1.3 auxIOTable17
1.3.6.1.4.1.1206.2.2.1.127 auxIOConformance23