One document matched: draft-ietf-idr-bgp4-mibv2-tc-mib-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY rfc2863 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2863.xml">
<!ENTITY rfc3418 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3418.xml">
<!ENTITY rfc4181 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4181.xml">
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc2578 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2578.xml">
<!ENTITY rfc2579 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2579.xml">
<!ENTITY rfc2580 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2580.xml">
<!ENTITY rfc3410 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3410.xml">
<!ENTITY rfc4271 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4271.xml">
<!ENTITY rfc4273 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4273.xml">
<!ENTITY rfc1657 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1657.xml">
<!ENTITY rfc4456 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4456.xml">
<!ENTITY rfc5065 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5065.xml">
<!ENTITY rfc4760 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4760.xml">
<!ENTITY rfc2545 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2545.xml">
<!ENTITY rfc4001 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4001.xml">
<!ENTITY rfc3107 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3107.xml">
<!ENTITY rfc4022 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4022.xml">
]>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict="no"?>
<?rfc rfcedstyle="yes"?>
<rfc category="std" docName="draft-ietf-idr-bgp4-mibv2-tc-mib-00"
     ipr="trust200811">
  <front>
    <title abbrev="BGP-4 MIB, Version 2">
    Definitions of Textual Conventions for the Management of the Fourth Version of Border Gateway Protocol (BGP-4)
    </title>

    <author fullname="Jeffrey Haas" initials="J" role=""
            surname="Haas">
      <organization>Arbor Networks</organization>

      <address>
        <postal>
          <street></street>

          <city></city>

          <country></country>
        </postal>

        <phone></phone>

        <email>jhaas@arbor.net</email>
      </address>
    </author>

    <date year="2009" />

    <area>Routing Area</area>

    <workgroup>Inter-Domain Routing Working Group</workgroup>

    <keyword>Network Management</keyword>

    <keyword>Management Information base</keyword>

    <keyword>MIB</keyword>

    <keyword>SMIv2</keyword>

    <keyword>BGP</keyword>
    <keyword>BGP4</keyword>
    <keyword>BGP-4</keyword>
    <keyword>Border Gateway Protocol</keyword>

    <abstract>
      <t>This memo defines a portion of the Management Information Base (MIB)
      which defines Textual Conventions for the management of BGP-4.
      The intent is that these textual conventions will be used in
      BGP-related MIB modules that would otherwise define their own
      representations.</t>

    </abstract>
  </front>

  <middle>
    <section title="Introduction">

      <t>This memo defines a portion of the Management Information Base (MIB)
      which defines Textual Conventions for the management of BGP-4.
      The intent is that these textual conventions will be used in
      BGP-related MIB modules that would otherwise define their own
      representations.</t>

      <t>See the BGP-4 specification <xref target="RFC4271"></xref> and
      Multiprotocol Extensions for BGP-4 <xref target="RFC4760"></xref>
      for an introduction to the concepts these textual conventions
      cover.</t>
    </section>

    <section title="The Internet-Standard Management Framework">
      <t> For a detailed overview of the documents that describe the
      current Internet-Standard Management Framework, please refer to
      section 7 of RFC 3410 <xref target="RFC3410"></xref>.</t>

      <t>Managed objects are accessed via a virtual information store,
      termed the Management Information Base or MIB. MIB objects are
      generally accessed through the Simple Network Management Protocol
      (SNMP). Objects in the MIB are defined using the mechanisms
      defined in the Structure of Management Information (SMI). This
      memo specifies a MIB module that is compliant to the SMIv2, which
      is described in STD 58, RFC 2578 <xref target="RFC2578"></xref>,
      STD 58, RFC 2579 <xref target="RFC2579"></xref> and STD 58, RFC
      2580 <xref target="RFC2580"></xref>.</t>
    </section>

    <section title="Conventions">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
      in this document are to be interpreted as described in RFC 2119
      <xref target="RFC2119"></xref>.</t>
    </section>

    <section title="Definitions">
      <figure>
        <artwork>
BGP4V2-TC-MIB DEFINITIONS ::= BEGIN

    IMPORTS
        mib-2, MODULE-IDENTITY FROM SNMPv2-SMI
        TEXTUAL-CONVENTION FROM SNMPv2-TC;

        bgp4V2TC MODULE-IDENTITY
            LAST-UPDATED "200902180000Z"
            ORGANIZATION "IETF IDR Working Group"
            CONTACT-INFO "E-mail:  idr@ietf.org"

            DESCRIPTION
                    "Textual conventions for BGP-4.

                     Copyright (C) The IETF Trust (2009).  This
                     version of this MIB module is part of RFC XXX;
                     see the RFC itself for full legal notices."
-- RFC Editor - replace XXX with RFC number

            REVISION "200902180000Z"
            DESCRIPTION
                   "Initial version."
            ::= { mib-2 XXX }

    --
    -- Textual Conventions
    --

    Bgp4V2IdentifierTC ::= TEXTUAL-CONVENTION
        DISPLAY-HINT "1d."
        STATUS       current
        DESCRIPTION
            "The representation of a BGP Identifier.  BGP Identifiers 
             are presented in the received network byte order.

             The BGP Identifier is displayed as if it is an IP address, 
             even if it would be an illegal one."
        REFERENCE
            "RFC 4273, Section 4.2"
        SYNTAX OCTET STRING(SIZE (4))

    Bgp4V2AddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION
        STATUS       current
        DESCRIPTION
            "The representation of a BGP AFI.  The value of this object
             should be restricted to be between the values of 0 and 65535."
        REFERENCE
            "RFC 4760, Section 3"
        SYNTAX INTEGER {
                ipv4(1),
                ipv6(2)
            }

    Bgp4V2SubsequentAddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION
        STATUS       current
        DESCRIPTION
            "The representation of a BGP SAFI"
        REFERENCE
            "RFC 4760, Section 3.  The value of this object should be
             restricted to be between the values of 0 and 255."
        SYNTAX INTEGER {
                unicast(1),
                multicast(2),
                mpls(4)
            }

END
        </artwork>
      </figure>
    </section>

    <section title="Security Considerations">
      <t>This module does not define any management objects. Instead, it
      defines a set of textual conventions which may be used by other
      modules which use the BGP-4 protocol to define management objects.

      Meaningful security considerations can only be written in the MIB
      modules that define management objects. Therefore, this document
      has no impact on the security of the Internet.</t>
    </section>

    <section title="IANA Considerations">
      <t>IANA is requested to assign this MIB module an OID under mib-2.</t>
    </section>

  </middle>

  <back>

    <references title="Normative References">
      &rfc2119;

      &rfc2578;

      &rfc2579;

      &rfc2580;

      &rfc3410;

      &rfc4271;
      &rfc4760;
    </references>
  </back>
</rfc>