OID reference

mplsTeP2mpStdMIB

1.3.6.1.4.1.29601.2.59

Description

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these do…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.29601.2 (2)
Node code
59
Node name
mplsTeP2mpStdMIB
Numeric OID
1.3.6.1.4.1.29601.2.59
URN notation
urn:oid:1.3.6.1.4.1.29601.2.59
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 29601 2 59}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 29601 2 mplsTeP2mpStdMIB(59)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 29601 2 mplsTeP2mpStdMIB(59)}
OID-IRI notation
  • /1/3/6/1/4/1/29601/2/59
  • /ISO/Identified-Organization/6/1/4/1/29601/2/59
  • /ISO/3/6/1/4/1/29601/2/59
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/identified-organization/dod/internet/private/enterprises/29601/2/mplsTeP2mpStdMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/29601/2/mplsTeP2mpStdMIB
  • /iso/org/dod/internet/private/enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/org/dod/internet/private/enterprises/29601/2/mplsTeP2mpStdMIB
  • /iso/org/dod/internet/private/ldap-enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/org/dod/internet/private/vendor-objects/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-identified-organization/dod/internet/private/enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-identified-organization/dod/internet/private/enterprises/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-organization/dod/internet/private/enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-organization/dod/internet/private/enterprises/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/29601/2/mplsTeP2mpStdMIB
  • /iso/iso-organization/dod/internet/private/vendor-objects/29601/2/mplsTeP2mpStdMIB

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

Show 2 published definitions

mplsTeP2mpStdMIB · unspecified

mplsTeP2mpStdMIB MODULE-IDENTITY
      LAST-UPDATED "200904170000Z"  -- April 17, 2009
      ORGANIZATION
         "Multiprotocol Label Switching (MPLS) Working Group"
      CONTACT-INFO
           "        Adrian Farrel
                    Old Dog Consulting
            Email:  adrian@olddog.co.uk

                    Seisho Yasukawa
                    NTT Corporation
            Email:  s.yasukawa@hco.ntt.co.jp

                    Thomas D. Nadeau
                    British Telecom
            Email:  tom.nadeau@bt.com

                   Comments about this document should be emailed
                   directly to the MPLS working group mailing list at
                   mpls@lists.ietf.org"

      DESCRIPTION
           "Copyright (c) 2009 IETF Trust and the persons identified as
            the document authors. All rights reserved.

            This document is subject to BCP 78 and the IETF Trust's
            Legal Provisions Relating to IETF Documents in effect on the
            date of publication of this document
            (http://trustee.ietf.org/license-info). Please review these
            documents carefully, as they describe your rights and
            restrictions with respect to this document.

            The initial version of this MIB module was published in
            RFC XXXX. For full legal notices see the RFC itself or see:
            http://www.ietf.org/copyrights/ianamib.html
-- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note.

            This MIB module contains managed object definitions
            for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
            defined in:
            1. Signaling Requirements for Point-to-Multipoint
               Traffic-Engineered MPLS Label Switched Paths (LSPs),
               S. Yasukawa, RFC 4461, April 2006.
            2. Extensions to Resource Reservation Protocol - Traffic
               Engineering (RSVP-TE) for Point-to-Multipoint TE Label
               Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D.,
               and Yasukawa, S., RFC 4875, May 2007."

      -- Revision history.

      REVISION
         "200904170000Z"  -- April 17, 2009
      DESCRIPTION
           "Initial version issued as part of RFC XXXX."
-- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note.

::= {enterprises aricent-communication-holding-ltd(29601) iss(2) 59}

mplsTeP2mpStdMIB · unspecified

mplsTeP2mpStdMIB MODULE-IDENTITY
      LAST-UPDATED "201209050000Z" 
      ORGANIZATION "ARICENT COMMUNICATIONS SOFTWARE"
      CONTACT-INFO "support@aricent.com"

      DESCRIPTION
            "This document is subject to BCP 78 and the IETF Trust's
            Legal Provisions Relating to IETF Documents in effect on the
            date of publication of this document
            (http://trustee.ietf.org/license-info). Please review these
            documents carefully, as they describe your rights and
            restrictions with respect to this document.

            The initial version of this MIB module was published in
            RFC XXXX. For full legal notices see the RFC itself or see:
            http://www.ietf.org/copyrights/ianamib.html
-- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note.

            This MIB module contains managed object definitions
            for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
            defined in:
            1. Signaling Requirements for Point-to-Multipoint
               Traffic-Engineered MPLS Label Switched Paths (LSPs),
               S. Yasukawa, RFC 4461, April 2006.
            2. Extensions to Resource Reservation Protocol - Traffic
               Engineering (RSVP-TE) for Point-to-Multipoint TE Label
               Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D.,
               and Yasukawa, S., RFC 4875, May 2007."

      -- Revision history.

      REVISION
         "201209050000Z"
      DESCRIPTION
           "Initial version issued as part of RFC XXXX."
-- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note.

::= {enterprises aricent-communication-holding-ltd(29601) iss(2) 59}

Meaning

Descriptions

2 unique

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

Description 1

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

mplsTeP2mpStdMIB · unspecifiedBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: unspecified.

Names: mplsTeP2mpStdMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "mplsTeP2mpStdMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303930343137303030305a22"
    ],
    "ORGANIZATION",
    "\"Multiprotocol Label Switching (MPLS) Working Group\"",
    "CONTACT-INFO",
    "\" Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk Seisho Yasukawa NTT Corporation Email: s.yasukawa@hco.ntt.co.jp Thomas D. Nadeau British Telecom Email: tom.nadeau@bt.com Comments about this document should be emailed directly to the MPLS working group mailing list at mpls@lists.ietf.org\"",
    "DESCRIPTION",
    "\"Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.\"",
    "REVISION",
    [
      "literal",
      "223230303930343137303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version issued as part of RFC XXXX.\"",
    "::=",
    "{",
    "enterprises",
    "aricent-communication-holding-ltd",
    "(",
    "29601",
    ")",
    "iss",
    "(",
    "2",
    ")",
    "59",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200904170000Z"
    ],
    [
      "ORGANIZATION",
      "Multiprotocol Label Switching (MPLS) Working Group"
    ],
    [
      "CONTACT-INFO",
      "Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk Seisho Yasukawa NTT Corporation Email: s.yasukawa@hco.ntt.co.jp Thomas D. Nadeau British Telecom Email: tom.nadeau@bt.com Comments about this document should be emailed directly to the MPLS working group mailing list at mpls@lists.ietf.org"
    ],
    [
      "DESCRIPTION",
      "Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007."
    ],
    [
      "Revisions",
      [
        [
          "200904170000Z",
          [
            "DESCRIPTION",
            "Initial version issued as part of RFC XXXX."
          ]
        ]
      ]
    ]
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

mplsTeP2mpStdMIB · unspecifiedMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: unspecified.

Names: mplsTeP2mpStdMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "mplsTeP2mpStdMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313230393035303030305a22"
    ],
    "ORGANIZATION",
    "\"ARICENT COMMUNICATIONS SOFTWARE\"",
    "CONTACT-INFO",
    "\"support@aricent.com\"",
    "DESCRIPTION",
    "\"This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.\"",
    "REVISION",
    [
      "literal",
      "223230313230393035303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version issued as part of RFC XXXX.\"",
    "::=",
    "{",
    "enterprises",
    "aricent-communication-holding-ltd",
    "(",
    "29601",
    ")",
    "iss",
    "(",
    "2",
    ")",
    "59",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201209050000Z"
    ],
    [
      "ORGANIZATION",
      "ARICENT COMMUNICATIONS SOFTWARE"
    ],
    [
      "CONTACT-INFO",
      "support@aricent.com"
    ],
    [
      "DESCRIPTION",
      "This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. The initial version of this MIB module was published in RFC XXXX. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXXX with the RFC number for this -- document and remove this note. This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007."
    ],
    [
      "Revisions",
      [
        [
          "201209050000Z",
          [
            "DESCRIPTION",
            "Initial version issued as part of RFC XXXX."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.29601)

Arpna Gupta

Direct children (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.59.0 mplsTeP2mpNotifications22
1.3.6.1.4.1.29601.2.59.1 mplsTeP2mpScalars33
1.3.6.1.4.1.29601.2.59.2 mplsTeP2mpObjects544
1.3.6.1.4.1.29601.2.59.3 mplsTeP2mpConformance00

Siblings (83)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.29601.2.60 bfdTCStdMib00
1.3.6.1.4.1.29601.2.61 fsMsdpMIB293
1.3.6.1.4.1.29601.2.62 fsmgmdMIB198
1.3.6.1.4.1.29601.2.63 fsFips18
1.3.6.1.4.1.29601.2.64 fsSec14
1.3.6.1.4.1.29601.2.66 fsrbridgeMIB167
1.3.6.1.4.1.29601.2.67 fstlm234
1.3.6.1.4.1.29601.2.68 fsWebTstMIB118
1.3.6.1.4.1.29601.2.70 fsusrMgmt225
1.3.6.1.4.1.29601.2.71 fsmef8231
1.3.6.1.4.1.29601.2.72 fsL2VpnMIB5119
1.3.6.1.4.1.29601.2.75 fsMIStdTcpIpvx335
1.3.6.1.4.1.29601.2.76 fsMITcp671
1.3.6.1.4.1.29601.2.77 fsMIBgp47549
1.3.6.1.4.1.29601.2.79 fsSynceMIB230
1.3.6.1.4.1.29601.2.85 fsvrrpv3131
1.3.6.1.4.1.29601.2.86 fsVplsBgpMIB223
1.3.6.1.4.1.29601.2.88 fsEsat, fsY15649169
1.3.6.1.4.1.29601.2.89 fsvxlan1112
1.3.6.1.4.1.29601.2.90 fsWssUser557
1.3.6.1.4.1.29601.2.92 futureMIDhcpRelay242
1.3.6.1.4.1.29601.2.93 fsHb212
1.3.6.1.4.1.29601.2.94 fsIcchMIB428
1.3.6.1.4.1.29601.2.99 fsDns641
1.3.6.1.4.1.29601.2.100 fs11AC357
1.3.6.1.4.1.29601.2.101 fsLldpMed575
1.3.6.1.4.1.29601.2.102 fsMIFsbMIB596
1.3.6.1.4.1.29601.2.103 fsIssu223
1.3.6.1.4.1.29601.2.105 fs2544679
1.3.6.1.4.1.29601.2.107 fs6374MIB9165
1.3.6.1.4.1.29601.2.108 futureL2tpMIB180
1.3.6.1.4.1.29601.2.122 fsIpv6Snp254
1.3.6.1.4.1.29601.2.123 futureLbdMIB217