Definitions of Managed Objects for 6rd ZTE
No. 68 Zijinhua Rd., Nanjing 210012 China +86 25 5287 2205 cai.lei3@zte.com.cn
Cisco Systems
Shanghai China +86 1891 836 3666 jacni@jacni.com
Cisco Systems
Midtown Tower, 9-7-1, Akasaka Minato-Ku Tokyo 107-6227 Japan +81 3 6434 6543 shtsuchi@cisco.com
Softwire MIB This document defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it defines objects for managing 6rd devices.
This draft describes the Management Information Base (MIB) module for 6rd (IPv6 Rapid Deployment, ), which specifies an automatic tunneling mechanism to deploy IPv6 to sites via a operator's IPv4 network.
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 . 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 , STD 58, RFC 2579 and STD 58, RFC 2580 .
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 .
The MIB Module specified herein provides one way to manage the 6rd devices through SNMP.
This table contains the configuration information for 6rd.
This table contains the BR IPv4 Address for configurations on given 6rd CE device.
This table contains counter of packets drop by 6rd receiving rule.
The 'system' group in the SNMPv2-MIB 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 SAMPLE-MIB does not duplicate those objects.
The IP Tunnel MIB contains objects common to all IP tunnels, including 6rd. Additionally, tunnel encapsulation specific MIB (like what is defined in this document) extend the IP tunnel MIB to further describe encapsulation specific information, for example (in case of 6rd): 6rd prefix, 6rd Prefix Length, IPv4Mask Length and BR IPv4 Address. The implementation of the IP Tunnel MIB is required for 6rd. The tunnelIfEncapsMethod in the tunnelIfEntry should be set to sixRd("xx"), and an entry in the 6rd MIB module will exist for every tunnelIfEntry with this tunnelIfEncapsMethod. The tunnelIfRemoteAddress must be set to 0.0.0.0. [Ed.Note:]This is similar to the situation of L2TP MIB case, since the IANA is requested to assign a value for sixRdMIB under the "transmission" subtree. Also, a new IANAtunnelType (rather than IANAifType) value is needed and should be recorded in the IANAifType-MIB registry, refer to Section 8.
Each logical interface (physical or virtual) has an ifEntry in the Interfaces MIB. Tunnels are handled by creating a logical interface (ifEntry) for each tunnel.
IP MIB provides traffic statics counter and status for 6rd virtual interface.
This MIB module IMPORTs objects from , , , , .
This document does not introduce any new security concern in addition to what is discussed in Section 6 of .
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and the following IANA-assigned tunnelType values recorded in the IANAifType-MIB registry: