Reference record for OID 1.3.6.1.2.1.171

parent

1.3.6.1.2.1 (mib-2, mib)

node code

171

node name

midcomMIB

dot oid

1.3.6.1.2.1.171

type

MODULE-IDENTITY

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) midcomMIB(171)}

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) midcomMIB(171)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) midcomMIB(171)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) midcomMIB(171)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) midcomMIB(171)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) midcomMIB(171)}

iri oid

/iso/identified-organization/dod/internet/mgmt/mib-2/midcomMIB

/iso/identified-organization/dod/internet/mgmt/mib/midcomMIB

/iso/org/dod/internet/mgmt/mib-2/midcomMIB

/iso/org/dod/internet/mgmt/mib/midcomMIB

/iso/iso-identified-organization/dod/internet/mgmt/mib-2/midcomMIB

/iso/iso-identified-organization/dod/internet/mgmt/mib/midcomMIB

iri by oid_info

/ISO/Identified-Organization/6/1/2/1/171

Description by oid_info

midcomMIB MODULE-IDENTITY
LAST-UPDATED "200708091011Z" -- August 09, 2007
ORGANIZATION "IETF Middlebox Communication Working Group"
CONTACT-INFO
"WG charter: https://datatracker.ietf.org/wg/midcom/charter/
Mailing Lists: General Discussion: [email protected]
To Subscribe: [email protected]
In Body: subscribe your_email_address
Co-editor:
Juergen Quittek
NEC Europe Ltd.
Kurfuersten-Anlage 36
69115 Heidelberg
Germany
Tel: +49 6221 4342-115
Email: [email protected]
Co-editor:
Martin Stiemerling
NEC Europe Ltd.
Kurfuersten-Anlage 36
69115 Heidelberg
Germany
Tel: +49 6221 4342-113
Email: [email protected]
Co-editor:
Pyda Srisuresh
Kazeon Systems, Inc.
1161 San Antonio Rd.
Mountain View, CA 94043
U.S.A.
Tel: +1 408 836-4773
Email: [email protected]"
DESCRIPTION
"This MIB module defines a set of basic objects for configuring middleboxes, such as firewalls and network address translators, in order to enable communication across these devices.
Managed objects defined in this MIB module are structured in three kinds of objects:
- transaction objects required according to the MIDCOM protocol requirements defined in RFC 3304 and according to the MIDCOM protocol semantics defined in RFC 3989,
- configuration objects that can be used for retrieving or setting parameters of the implementation of transaction objects,
- optional monitoring objects that provide information about used resource and statistics
The transaction objects are organized in two subtrees:
- objects modeling MIDCOM policy rules in the midcomRuleTable
- objects modeling MIDCOM policy rule groups in the midcomGroupTable
Note that typically, configuration objects are not intended to be written by MIDCOM clients. In general, write access to these objects needs to be restricted more strictly than write access to objects in the transaction subtrees.
Copyright (C) The Internet Society (2008). This version of this MIB module is part of RFC 5190; see the RFC itself for full legal notices."
REVISION "200708091011Z" -- August 09, 2007
DESCRIPTION "Initial version, published as RFC 5190."
View at oid-info.com

Description by mibdepot

This MIB module defines a set of basic objects for
configuring middleboxes, such as firewalls and network
address translators, in order to enable communication
across these devices.

Managed objects defined in this MIB module are structured
in three kinds of objects:
- transaction objects required according to the MIDCOM
protocol requirements defined in RFC 3304 and according
to the MIDCOM protocol semantics defined in RFC 3989,
- configuration objects that can be used for retrieving or
setting parameters of the implementation of transaction
objects,
- optional monitoring objects that provide information
about used resource and statistics

The transaction objects are organized in two subtrees:
- objects modeling MIDCOM policy rules in the
midcomRuleTable
- objects modeling MIDCOM policy rule groups in the
midcomGroupTable

Note that typically, configuration objects are not intended
to be written by MIDCOM clients. In general, write access
to these objects needs to be restricted more strictly than
write access to objects in the transaction subtrees.

Copyright (C) The Internet Society (2008). This version
of this MIB module is part of RFC 5190; see the RFC
itself for full legal notices.

Parsed from file rfc5190-Middlebox-Communication-MIDCOM.mib.txt
Company: None
Module: MIDCOM-MIB

Description by circitor

This MIB module defines a set of basic objects for
configuring middleboxes, such as firewalls and network



address translators, in order to enable communication
across these devices.

Managed objects defined in this MIB module are structured
in three kinds of objects:
- transaction objects required according to the MIDCOM
protocol requirements defined in RFC 3304 and according
to the MIDCOM protocol semantics defined in RFC 3989,
- configuration objects that can be used for retrieving or
setting parameters of the implementation of transaction
objects,
- optional monitoring objects that provide information
about used resource and statistics

The transaction objects are organized in two subtrees:
- objects modeling MIDCOM policy rules in the
midcomRuleTable
- objects modeling MIDCOM policy rule groups in the
midcomGroupTable

Note that typically, configuration objects are not intended
to be written by MIDCOM clients. In general, write access
to these objects needs to be restricted more strictly than
write access to objects in the transaction subtrees.

Copyright (C) The Internet Society (2008). This version
of this MIB module is part of RFC 5190; see the RFC
itself for full legal notices.

Parsed from file MIDCOM-MIB.mib
Module: MIDCOM-MIB

Information by oid_info

Automatically extracted from IETF RFC 5190.

Information by mibdepot

midcomMIB MODULE-IDENTITY
       LAST-UPDATED "200708091011Z"  
       ORGANIZATION "IETF Middlebox Communication Working Group"
       CONTACT-INFO
          "WG charter:
             http://www.ietf.org/html.charters/midcom-charter.html

           Mailing Lists:
             General Discussion: [email protected]
             To Subscribe: [email protected]
             In Body: subscribe your_email_address

           Co-editor:
             Juergen Quittek
             NEC Europe Ltd.
             Kurfuersten-Anlage 36
             69115 Heidelberg
             Germany
             Tel: +49 6221 4342-115
             Email: [email protected]

           Co-editor:
             Martin Stiemerling
             NEC Europe Ltd.
             Kurfuersten-Anlage 36
             69115 Heidelberg
             Germany
             Tel: +49 6221 4342-113
             Email: [email protected]

           Co-editor:
             Pyda Srisuresh
             Kazeon Systems, Inc.
             1161 San Antonio Rd.
             Mountain View, CA 94043
             U.S.A.
             Tel: +1 408 836-4773
             Email: [email protected]"

       DESCRIPTION
           "This MIB module defines a set of basic objects for
            configuring middleboxes, such as firewalls and network
            address translators, in order to enable communication
            across these devices.

            Managed objects defined in this MIB module are structured
            in three kinds of objects:
              - transaction objects required according to the MIDCOM
                protocol requirements defined in RFC 3304 and according
                to the MIDCOM protocol semantics defined in RFC 3989,
              - configuration objects that can be used for retrieving or
                setting parameters of the implementation of transaction
                objects,
              - optional monitoring objects that provide information
                about used resource and statistics

            The transaction objects are organized in two subtrees:
              - objects modeling MIDCOM policy rules in the
                midcomRuleTable
              - objects modeling MIDCOM policy rule groups in the
                midcomGroupTable

            Note that typically, configuration objects are not intended
            to be written by MIDCOM clients.  In general, write access
            to these objects needs to be restricted more strictly than
            write access to objects in the transaction subtrees.

            Copyright (C) The Internet Society (2008).  This version
            of this MIB module is part of RFC 5190;  see the RFC
            itself for full legal notices."

       REVISION    "200708091011Z"  
       DESCRIPTION "Initial version, published as RFC 5190."
       ::= { mib-2 171 }

Information by circitor

midcomMIB MODULE-IDENTITY
    LAST-UPDATED "200708091011Z"  
    ORGANIZATION "IETF Middlebox Communication Working Group"
    CONTACT-INFO
       "WG charter:
          http://www.ietf.org/html.charters/midcom-charter.html

        Mailing Lists:
          General Discussion: [email protected]
          To Subscribe: [email protected]
          In Body: subscribe your_email_address

        Co-editor:
          Juergen Quittek
          NEC Europe Ltd.
          Kurfuersten-Anlage 36
          69115 Heidelberg
          Germany
          Tel: +49 6221 4342-115
          Email: [email protected]

        Co-editor:
          Martin Stiemerling
          NEC Europe Ltd.
          Kurfuersten-Anlage 36
          69115 Heidelberg
          Germany
          Tel: +49 6221 4342-113
          Email: [email protected]

        Co-editor:
          Pyda Srisuresh
          Kazeon Systems, Inc.
          1161 San Antonio Rd.
          Mountain View, CA 94043
          U.S.A.
          Tel: +1 408 836-4773
          Email: [email protected]"

    DESCRIPTION
        "This MIB module defines a set of basic objects for
         configuring middleboxes, such as firewalls and network



         address translators, in order to enable communication
         across these devices.

         Managed objects defined in this MIB module are structured
         in three kinds of objects:
           - transaction objects required according to the MIDCOM
             protocol requirements defined in RFC 3304 and according
             to the MIDCOM protocol semantics defined in RFC 3989,
           - configuration objects that can be used for retrieving or
             setting parameters of the implementation of transaction
             objects,
           - optional monitoring objects that provide information
             about used resource and statistics

         The transaction objects are organized in two subtrees:
           - objects modeling MIDCOM policy rules in the
             midcomRuleTable
           - objects modeling MIDCOM policy rule groups in the
             midcomGroupTable

         Note that typically, configuration objects are not intended
         to be written by MIDCOM clients.  In general, write access
         to these objects needs to be restricted more strictly than
         write access to objects in the transaction subtrees.

         Copyright (C) The Internet Society (2008).  This version
         of this MIB module is part of RFC 5190;  see the RFC
         itself for full legal notices."

    REVISION    "200708091011Z"  
    DESCRIPTION "Initial version, published as RFC 5190."
    ::= { mib-2 171 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6.1.2)

Internet Assigned Numbers Authority

Children (3)

Brothers (248)

To many brothers! Only 100 nearest brothers are shown.