Softwire J. Dong Internet-Draft Y. Cui Intended status: Informational Tsinghua University Expires: September 12, 2011 March 11, 2011 Softwire Mesh Management Information Base(MIB) draft-cui-softwire-mesh-mib-01 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular it defines objects for managing softwire mesh [RFC5565]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 12, 2011. Copyright Notice Copyright (c) 2011 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Dong & Cui Expires September 12, 2011 [Page 1] Internet-Draft swmMIB March 2011 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 6.2. The swmInfo Subtree . . . . . . . . . . . . . . . . . . . 4 6.3. The swmVIfInfo Subtree . . . . . . . . . . . . . . . . . . 4 6.4. The swmNLRINHInfo Subtree . . . . . . . . . . . . . . . . 4 6.5. The swmBGPNeighInfo Subtree . . . . . . . . . . . . . . . 4 6.6. The swmConformance Subtree . . . . . . . . . . . . . . . . 5 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 5 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 5 7.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 11.1. Normative References . . . . . . . . . . . . . . . . . . . 23 11.2. Informative References . . . . . . . . . . . . . . . . . . 23 11.3. URL References . . . . . . . . . . . . . . . . . . . . . . 24 Dong & Cui Expires September 12, 2011 [Page 2] Internet-Draft swmMIB March 2011 1. Introduction Softwire mesh framework RFC 5565 [RFC5565]is a tunneling mechanism which enables connectivity between islands of IPv4, IPv6 or dual- stack networks across single IPv4 or IPv6 backbone networks. In softwire mesh solution, extended multiprotocol-BGP (MP-BGP)is used to set up tunnels and advertise prefixes among address family border routers (AFBRs). This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular it defines objects for managing softwire mesh [RFC5565]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. 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 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Terminology This document uses terminology from softwire problem statement RFC 4925 [RFC4925] and softwire mesh framework RFC5565 [RFC5565]. 4. Conventions 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 [RFC2119]. 5. Overview The softwire mesh MIB provides a way to configure and manage the softwire mesh objects through SNMP. It's a basis for manage and control softwire mesh framework. Dong & Cui Expires September 12, 2011 [Page 3] Internet-Draft swmMIB March 2011 6. Structure of the MIB Module 6.1. Textual Conventions The following textual conventions are defined: swmTunnelType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Represents the TC for tunnel type will be used. According to section 4 of RFC 5512" SYNTAX INTEGER { gre(1), -- GRE encapsulation l2tpv3(2), -- L2TPv3 encapsulation ip-ip(3) -- IP-IP encapsulation } 6.2. The swmInfo Subtree The swmInfo subtree provides basic softwire mesh information about the router. It includes current state of the PE, the time when the PE change its current softwire mesh state. Something else useful will be added. 6.3. The swmVIfInfo Subtree The subtree provides softwire mesh virtual interface information about the router. It includes what kind of tunnel type the PE supports to implement softwire mesh. It also includes information about flow couting which was divided into 4over6 and 6over4. 6.4. The swmNLRINHInfo Subtree The subtree provides softwire mesh NLRI-NH information about the router. It indicates which address will be encapsulated according to the arriving packet's destination address. 6.5. The swmBGPNeighInfo Subtree The subtree provides softwire mesh BGP neighbor information about the router. It includes the address of softwire mesh BGP peer. It also includes what kind of tunnel types that BGP peer can support. This information also be divided into 4over6 BGP neighbors and 6over4 BGP neighbors. Dong & Cui Expires September 12, 2011 [Page 4] Internet-Draft swmMIB March 2011 6.6. The swmConformance Subtree The subtree provides conformance information of MIB objects. 7. Relationship to Other MIB Modules 7.1. Relationship to the SNMPv2-MIB The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being mandatory for all systems, and the objects apply to the entity as a whole. The 'system' group provides identification of the management entity and certain other system-wide data. The swmMIB does not duplicate those objects. 7.2. Relationship to the IF-MIB The Interfaces Group [RFC2863] defines generic managed objects for managing interfaces. This memo contains the extensions to the Interfaces Group for managing softwire mesh that are modeled as virtual interfaces. 7.3. MIB modules required for IMPORTS The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and INET-ADDRESS-MIB [RFC4001]. 8. Definitions SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN IMPORTS TruthValue, TEXTUAL-CONVENTION TimeStamp FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Counter32, Counter64 FROM SNMPv2-SMI InterfaceIndex FROM IF-MIB InetAddressIPv4, InetAddressIPv6, InetAddressPrefixLength FROM INET-ADDRESS-MIB Dong & Cui Expires September 12, 2011 [Page 5] Internet-Draft swmMIB March 2011 swmMIB MODULE-IDENTITY LAST-UPDATED "201103100000Z" -- Mar 10, 2011 ORGANIZATION "Softwire Working Group" CONTACT-INFO " Yong Cui Email: yong@csnet1.cs.tsinghua.edu.cn Jiang Dong Email: dongjiang@csnet1.cs.tsinghua.edu.cn Email comments directly to ther softwire WG Mailing List at softwires@ietf.org " DESCRIPTION "This MIB module contains managed object definitions for the softwire mesh framework." REVISION "201103100000Z" DESCRIPTION "draft-01 version" ::= {transmission xxx} --xxx to be replaced with correct value -- Textual conventions swmTunnelType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Represents the TC for tunnel type will be used.According to section 4 of RFC 5512" SYNTAX INTEGER { gre(1), -- GRE encapsulation l2tpv3(2), -- L2TPv3 encapsulation ip-ip(3) -- IP-IP } -- Top level components of this MIB -- Tables, Scalars swmInfo OBJECT IDENTIFIER ::= { swmMIB 1 } swmVIfInfo OBJECT IDENTIFIER ::= { swmMIB 2 } swmNLRINHInfo OBJECT IDENTIFIER ::= { swmMIB 3 } swmBGPNeighInfo OBJECT IDENTIFIER ::= { swmMIB 4 } Dong & Cui Expires September 12, 2011 [Page 6] Internet-Draft swmMIB March 2011 -- Conformance swmConformance OBJECT IDENTIFIER ::= { swmMIB 5 } -- swmInfo swmState OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Represents whether the mesh function of the router has been started. If the BGP open is sent and softwire mesh capability is negotiated, the mesh function could be considered to be started." ::= { swmInfo 1 } swmLastChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time the swmState change its state." ::= { swmInfo 2 } -- End of swmInfo -- swmVIfInfo -- swmVIfTunnelTable Table swmVIfTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF swmVIFTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and config the softwire mesh virtual interface tunnel information. It shows what kind of tunnels can be used in the router." ::= { swmVIfInfo 1 } swmVIfTunnelEntry OBJECT-TYPE SYNTAX swmVIfTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and config the softwire Dong & Cui Expires September 12, 2011 [Page 7] Internet-Draft swmMIB March 2011 mesh virtual interface tunnel information." INDEX { swmVIfTunnelType } ::= { swmVIfTunnelTable 1 } swmVIfTunnelEntry ::= SEQUENCE { swmVIfTunnelType swmTunnelType, } swmVIfTunnelType OBJECT-TYPE SYNTAX swmTunnelType MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the kind of tunneling type that the server supports." ::= { swmVIfTunnelEntry 1 } -- End of swmVIfTunnelTable Table -- swmVIf4over6Table Table swmVIf4over6Table OBJECT-TYPE SYNTAX SEQUENCE OF swmVIf4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the softwire mesh 4over6 virtual interface information. This table is used to count the 4over6 information." ::= { swmVIfInfo 2 } swmVIf4over6Entry OBJECT-TYPE SYNTAX swmVIf4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the softwire mesh 4over6 virtual interface information." INDEX { swmVIf4over6Index } ::= { swmVIf4over6Table 1 } swmVIf4over6Entry ::= SEQUENCE { swmVIf4over6Index InterfaceIndex, swmVIf4over6InIPv4Packets Counter32, swmVIf4over6OutIPv6Packets Counter32, swmVIf4over6InIPv6Packets Counter32, Dong & Cui Expires September 12, 2011 [Page 8] Internet-Draft swmMIB March 2011 swmVIf4over6OutIPv4Packets Counter32, swmVIf4over6InIPv4Bytes Counter64, swmVIf4over6OutIPv6Bytes Counter64, swmVIf4over6InIPv6Bytes Counter64, swmVIf4over6OutIPv6Bytes Counter64, swmVIf4over6Mtu Unsigned32 } swmVIf4over6Index OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index for the conceptual row indentifying a softwire mesh 4over6 virtual information within this table." ::= { swmVIf4over6Entry 1 } swmVIf4over6InIPv4Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Packets received by the virtual interface. These IPv4 packets will be encapsulated with an IPv6 header according to 4over6 encapsulation table. If these packets need to be fragmented, the number counted here is the packets after fragmentation." ::= { swmVIf4over6Entry 2 } swmVIf4over6OutIPv6Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Packets send by the virtual interface. These IPv6 packets are encapsulated packets from IPv4 packets according to 4over6 encapsulation table." ::= { swmVIf4over6Entry 3 } swmVIf4over6InIPv6Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Packets received by the Dong & Cui Expires September 12, 2011 [Page 9] Internet-Draft swmMIB March 2011 virtual interface. These IPv6 packets will be decapsulated to IPv4 packets." ::= { swmVIf4over6Entry 4 } swmVIf4over6OutIPv4Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Packets send by the virtual interface. These IPv4 packets are decapsulated packets from encapsulated IPv6 packets" ::= { swmVIf4over6Entry 5 } swmVIf4over6InIPv4Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Bytes received by the virtual interface. These IPv4 packets will be encapsulated with an IPv6 header according to 4over6 encapsulation table." ::= { swmVIf4over6Entry 6 } swmVIf4over6OutIPv6Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Bytes send by the virtual interface. These IPv6 packets are encapsulated packets from IPv4 packets according to 4over6 encapsulation table." ::= { swmVIf4over6Entry 7 } swmVIf4over6InIPv6Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Bytes received by the virtual interface. These IPv6 packets will be decapsulated to IPv4 packets." ::= { swmVIf4over6Entry 8 } swmVIf4over6OutIPv4Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only Dong & Cui Expires September 12, 2011 [Page 10] Internet-Draft swmMIB March 2011 STATUS current DESCRIPTION "Represents number of IPv4 Bytes send by the virtual interface. These IPv4 packets are decapsulated packets from encapsulated IPv6 packets" ::= { swmVIf4over6Entry 9 } swmVIf4over6Mtu OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "Represents the 4over6 virtual interface MTU." DEFVAL {1460} ::= { swmVIf4over6Entry 10 } -- End of swmVIf4over6Table Table -- swmVIf6over4Table Table swmVIf6over4Table OBJECT-TYPE SYNTAX SEQUENCE OF swmVIf6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the softwire mesh 6over4 virtual interface information. This table is used to count the 6over4 information." ::= { swmVIfInfo 3 } swmVIf6over4Entry OBJECT-TYPE SYNTAX swmVIf6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the softwire mesh 6over4 virtual interface information." INDEX { swmVIf6over4Index } ::= { swmVIf6over4Table 1 } swmVIf6over4Entry ::= SEQUENCE { swmVIf6over4Index InterfaceIndex, swmVIf6over4InIPv6Packets Counter32, swmVIf6over4OutIPv4Packets Counter32, swmVIf6over4InIPv4Packets Counter32, swmVIf6over4OutIPv6Packets Counter32, swmVIf6over4InIPv6Bytes Counter64, Dong & Cui Expires September 12, 2011 [Page 11] Internet-Draft swmMIB March 2011 swmVIf6over4OutIPv4Bytes Counter64, swmVIf6over4InIPv4Bytes Counter64, swmVIf6over4OutIPv4Bytes Counter64, swmVIf6over4Mtu Unsigned32 } swmVIf6over4Index OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index for the conceptual row indentifying a softwire mesh 6over4 virtual information within this table." ::= { swmVIf6over4Entry 1 } swmVIf6over4InIPv6Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Packets received by the virtual interface. These IPv6 packets will be encapsulated with an IPv4 header according to 6over4 encapsulation table. If these packets need to be fragmented, the number counted here is the IPv6 packets after fragmentation." ::= { swmVIf6over4Entry 2 } swmVIf6over4OutIPv4Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Packets send by the virtual interface. These IPv4 packets are encapsulated packets from IPv6 packets according to 6over4 encapsulation table." ::= { swmVIf6over4Entry 3 } swmVIf6over4InIPv4Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Packets received by the virtual interface. These IPv4 packets will be decapsulated to IPv6 packets according to softwire mesh Dong & Cui Expires September 12, 2011 [Page 12] Internet-Draft swmMIB March 2011 framework." ::= { swmVIf6over4Entry 4 } swmVIf6over4OutIPv6Packets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Packets send by the virtual interface. These IPv6 packets are decapsulated packets from encapsulated IPv4 packets" ::= { swmVIf6over4Entry 5 } swmVIf6over4InIPv6Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv6 Bytes received by the virtual interface. These IPv6 packets will be encapsulated with an IPv4 header according to 6over4 encapsulation table." ::= { swmVIf6over4Entry 6 } swmVIf6over4OutIPv4Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Bytes send by the virtual interface. These IPv4 packets are encapsulated packets from IPv6 packets according to 6over4 encapsulation table." ::= { swmVIf6over4Entry 7 } swmVIf6over4InIPv4Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Represents number of IPv4 Bytes received by the virtual interface. These IPv4 packets will be decapsulated to IPv6 packets." ::= { swmVIf6over4Entry 8 } swmVIf6over4OutIPv6Bytes OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current Dong & Cui Expires September 12, 2011 [Page 13] Internet-Draft swmMIB March 2011 DESCRIPTION "Represents number of IPv6 Bytes send by the virtual interface. These IPv6 packets are decapsulated packets from encapsulated IPv4 packets" ::= { swmVIf6over4Entry 9 } swmVIf6over4Mtu OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "Represents the 6over4 virtual interface MTU." DEFVAL {1460} ::= { swmVIf6over4Entry 10 } -- End of swmVIf6over4Table Table --swmNLRINHInfo -- swmNLRINH4over6Table Table swmNLRINH4over6Table OBJECT-TYPE SYNTAX SEQUENCE OF swmNLRINH4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the softwire mesh 4over6 NLRI-NH information." ::= { swmNLRINHInfo 1 } swmNLRINH4over6Entry OBJECT-TYPE SYNTAX swmNLRINH4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the softwire mesh 4over6 encapsulation information." INDEX { swmNLRINH4over6IPv4Dst, swmNLRINH4over6IPv4Mask } ::= { swmNLRINH4over6Table 1 } swmNLRINH4over6Entry ::= SEQUENCE { swmNLRINH4over6IPv4Dst InetAddressIPv4, swmNLRINH4over6IPv4Mask InetAddressPrefixLength, swmNLRINH4over6IPv6Dst InetAddressIPv6 } Dong & Cui Expires September 12, 2011 [Page 14] Internet-Draft swmMIB March 2011 swmNLRINH4over6IPv4Dst OBJECT-TYPE SYNTAX InetAddressIPv4 MAX-ACCESS read-only STATUS current DESCRIPTION "The destination IPv4 address that decide which destination IPv6 address will be encapsulated." ::= { swmNLRINH4over6Entry 1 } swmNLRINH4over6IPv4Mask OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION "The prefix length of destination IPv4 address." ::= { swmNLRINH4over6Entry 2 } swmNLRINH4over6IPv6Dst OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-only STATUS current DESCRIPTION "The destination IPv6 address that will be encapsulated according to the destination IPv4 address." ::= { swmNLRINH4over6Entry 3 } -- End of swmNLRINH4over6Table -- swmNLRINH6over4Table swmNLRINH6over4Table OBJECT-TYPE SYNTAX SEQUENCE OF swmNLRINH6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the softwire mesh 6over4 encapsulation information." ::= { swmNLRINHInfo 2 } swmNLRINH6over4Entry OBJECT-TYPE SYNTAX swmNLRINH6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the softwire mesh 6over4 encapsulation information." INDEX { swmNLRINH6over4IPv6Dst, swmNLRINH6over4IPv6Mask Dong & Cui Expires September 12, 2011 [Page 15] Internet-Draft swmMIB March 2011 } ::= { swmNLRINH6over4Table 1 } swmNLRINH6over4Entry ::= SEQUENCE { swmNLRINH6over4IPv6Dst InetAddressIPv6, swmNLRINH6over4IPv6Mask InetAddressPrefixLength, swmNLRINH6over4IPv4Dst InetAddressIPv4 } swmNLRINH6over4IPv6Dst OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-only STATUS current DESCRIPTION "The destination IPv6 address that decide which destination IPv4 address will be encapsulated." ::= { swmNLRINH6over4Entry 1 } swmNLRINH6over4IPv6Mask OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION "The prefix length of destination IPv6 address." ::= { swmNLRINH6over4Entry 2 } swmNLRINH6over4IPv4Dst OBJECT-TYPE SYNTAX InetAddressIPv4 MAX-ACCESS read-only STATUS current DESCRIPTION "The destination IPv4 address that will be encapsulated according to the destination IPv6 address." ::= { swmNLRINH6over4Entry 3 } -- End of swmNLRINH6over4Table -- swmBGPNeighInfo -- swmBGPNeigh4over6Table swmBGPNeigh4over6Table OBJECT-TYPE SYNTAX SEQUENCE OF swmBGPNeigh4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the Dong & Cui Expires September 12, 2011 [Page 16] Internet-Draft swmMIB March 2011 softwire mesh 4over6 BGP neighbor information." ::= { swmBGPNeighInfo 1 } swmBGPNeigh4over6Entry OBJECT-TYPE SYNTAX swmBGPNeigh4over6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display the softwire mesh 4over6 BGP neighbor information." INDEX { swmBGPNeigh4over6IPv6Address } ::= { swmBGPNeigh4over6Table 1 } swmBGPNeigh4over6Entry ::= SEQUENCE { swmBGPNeigh4over6IPv6Address InetAddressIPv6 swmBGPNeigh4over6TunnelTable SEQUENCE OF swmBGPNeigh4over6TunnelEntry } swmBGPNeigh4over6IPv6Address OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-only STATUS current DESCRIPTION "The IPv6 address of the router's 4over6 BGP neighbor." ::= { swmBGPNeigh4over6Entry 1 } -- swmBGPNeigh4over6TunnelTable Table swmBGPNeigh4over6TunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF swmBGPNeigh4over6TunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display softwire mesh virtual interface tunnel information of the 4over6 bgp neighbor." ::= { swmBGPNeigh4over6Entry 2 } swmBGPNeigh4over6TunnelEntry OBJECT-TYPE SYNTAX swmBGPNeigh4over6TunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display the softwire mesh virtual interface tunnel information of neighbor." Dong & Cui Expires September 12, 2011 [Page 17] Internet-Draft swmMIB March 2011 INDEX { swmBGPNeigh4over6TunnelType } ::= { swmBGPNeigh4over6TunnelTable 1 } swmBGPNeigh4over6TunnelEntry ::= SEQUENCE { swmBGPNeigh4over6TunnelType swmTunnelType, } swmBGPNeigh4over6TunnelType OBJECT-TYPE SYNTAX swmTunnelType MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the kind of tunneling type that the server's 4over6 BGP neighbor supports." ::= { swmBGPNeigh4over6TunnelEntry 1 } -- End of swmBGPNeigh4over6TunnelTable Table -- End of swmBGPNeigh4over6Table Table -- swmBGPNeigh6over4Table swmBGPNeigh6over4Table OBJECT-TYPE SYNTAX SEQUENCE OF swmBGPNeigh6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the softwire mesh 6over4 BGP neighbor information." ::= { swmBGPNeighInfo 2 } swmBGPNeigh6over4Entry OBJECT-TYPE SYNTAX swmBGPNeigh6over4Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display the softwire mesh 6over4 BGP neighbor information." INDEX { swmBGPNeigh6over4IPv4Address } ::= { swmBGPNeigh6over4Table 1 } swmBGPNeigh6over4Entry ::= SEQUENCE { swmBGPNeigh6over4IPv4Address InetAddressIPv4 swmBGPNeigh6over4TunnelTable SEQUENCE OF swmBGPNeigh6over4TunnelEntry } Dong & Cui Expires September 12, 2011 [Page 18] Internet-Draft swmMIB March 2011 swmBGPNeigh6over4IPv4Address OBJECT-TYPE SYNTAX InetAddressIPv4 MAX-ACCESS read-only STATUS current DESCRIPTION "The IPv4 address of the PE router's 6over4 BGP neighbor." ::= { swmBGPNeigh6over4Entry 1 } -- swmBGPNeigh6over4TunnelTable Table swmBGPNeigh6over4TunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF swmBGPNeigh6over4TunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display softwire mesh virtual interface tunnel information of the 6over4 bgp neighbor." ::= { swmBGPNeigh6over4Entry 2 } swmBGPNeigh6over4TunnelEntry OBJECT-TYPE SYNTAX swmBGPNeigh6over4TunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display the softwire mesh virtual interface tunnel information of 6over4 BGP neighbor." INDEX { swm6over6BGPNeighTunnelType } ::= { swmBGPNeigh6over4TunnelTable 1 } swmBGPNeigh6over4TunnelEntry ::= SEQUENCE { swmBGPNeigh6over4TunnelType swmTunnelType, } swmBGPNeigh6over4TunnelType OBJECT-TYPE SYNTAX swmTunnelType MAX-ACCESS read-only STATUS current DESCRIPTION "Represents the kind of tunneling type that the server's 6over4 BGP neighbor supports." ::= { swmBGPNeigh6over4TunnelEntry 1 } -- End of swmBGPNeigh6over4TunnelTable Table -- End of swmBGPNeigh6over4Table Table Dong & Cui Expires September 12, 2011 [Page 19] Internet-Draft swmMIB March 2011 -- Module Conformance Statement swmGroups OBJECT IDENTIFIER ::= { swmConformance 1 } swmCompliances OBJECT IDENTIFIER ::= { swmConformance 2 } swmCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance to the softwire mesh MIB." MODULE -- this module MANDATORY-GROUPS { swmInfoGroup, swmVIfGroup, swmNLRINHGroup, swmBGPNeighGroup } ::= { swmCompliances 1 } swmInfoGroup OBJECT-GROUP OBJECTS { swmState, swmLastChange } STATUS current DESCRIPTION "The collection of objects which are used to show basic softwire mesh information." ::= { swmGroups 1 } swmVIfGroup OBJECT-GROUP OBJECTS { swmVIfTunnelType swmVIf4over6Index, swmVIf4over6InIPv4Packets, swmVIf4over6OutIPv6Packets, swmVIf4over6InIPv6Packets, swmVIf4over6OutIPv4Packets, swmVIf4over6InIPv4Bytes, swmVIf4over6OutIPv6Bytes, swmVIf4over6InIPv6Bytes, swmVIf4over6OutIPv6Bytes, swmVIf4over6Mtu, swmVIf6over4Index, swmVIf6over4InIPv6Packets, swmVIf6over4OutIPv4Packets, Dong & Cui Expires September 12, 2011 [Page 20] Internet-Draft swmMIB March 2011 swmVIf6over4InIPv4Packets, swmVIf6over4OutIPv6Packets, swmVIf6over4InIPv6Bytes, swmVIf6over4OutIPv4Bytes, swmVIf6over4InIPv4Bytes, swmVIf6over4OutIPv4Bytes, swmVIf6over4Mtu } STATUS current DESCRIPTION "The collection of objects which are used to display and control softwire mesh virtual interface." ::= { swmGroups 2 } swmNLRINHGroup OBJECT-GROUP OBJECTS { swmNLRINH4over6IPv4Dst, swmNLRINH4over6IPv4Mask, swmNLRINH4over6IPv6Dst, swmNLRINH6over4IPv6Dst, swmNLRINH6over4IPv6Mask, swmNLRINH6over4IPv4Dst } STATUS current DESCRIPTION "The collection of objects which are used to display and control softwire mesh encapsulation information." ::= { swmGroups 3 } swmBGPNeighGroup OBJECT-GROUP OBJECTS { swm4over6BGPNeighIPv6Address, swm4over6BGPNeighTunnelType, swmBGPNeigh6over4IPv4Address, swmBGPNeigh6over4TunnelType } STATUS current DESCRIPTION "The collection of objects which are used to display softwire mesh BGP neighbor information." ::= { swmGroups 4 } END Dong & Cui Expires September 12, 2011 [Page 21] Internet-Draft swmMIB March 2011 9. Security Considerations The swmMIB module can be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. There are some management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o Unauthorized changes to the swmVIf4over6Table and swmVIf6over4Table may disrupt the configuration of the 4over6 mtu and 6over4 mtu of the virtual interface. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 10. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- swmMIB { transmission XXX } 11. References Dong & Cui Expires September 12, 2011 [Page 22] Internet-Draft swmMIB March 2011 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, "Softwire Problem Statement", RFC 4925, July 2007. [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute", RFC 5512, April 2009. [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh Framework", RFC 5565, June 2009. 11.2. Informative References [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, October 1997. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. Dong & Cui Expires September 12, 2011 [Page 23] Internet-Draft swmMIB March 2011 11.3. URL References [idguidelines] IETF Internet Drafts editor, "http://www.ietf.org/ietf/1id-guidelines.txt". [idnits] IETF Internet Drafts editor, "http://www.ietf.org/ID-Checklist.html". [xml2rfc] XML2RFC tools and documentation, "http://xml.resource.org". [ops] the IETF OPS Area, "http://www.ops.ietf.org". [ietf] IETF Tools Team, "http://tools.ietf.org". Authors' Addresses Jiang Dong Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 EMail: dongjiang@csnet1.cs.tsinghua.edu.cn Yong Cui Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6260-3059 EMail: yong@csnet1.cs.tsinghua.edu.cn Dong & Cui Expires September 12, 2011 [Page 24]