| Softwire | L. Cai |
| Internet-Draft | ZTE |
| Intended status: Standards Track | J. Qin |
| Expires: October 13, 2013 | S. Tsuchiya, Ed. |
| Cisco Systems | |
| April 11, 2013 |
Definitions of Managed Objects for 6rd
draft-cai-softwire-6rd-mib-04
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 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 October 13, 2013.
Copyright (c) 2013 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.
This draft describes the Management Information Base (MIB) module for 6rd (IPv6 Rapid Deployment, [RFC5969]), 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 [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].
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].
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.
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 SAMPLE-MIB does not duplicate those objects.
The IP Tunnel MIB [RFC4087] 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 [RFC3371] 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.
This MIB module IMPORTs objects from [RFC4087], [RFC2580], [RFC2578], [RFC2863], [RFC3411].
SIXRD-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE, transmission, Integer32
FROM SNMPv2-SMI
ifIndex
FROM IF-MIB
InetAddressIPv4, InetAddressPrefixLength, InetAddressIPv6
FROM INET-ADDRESS-MIB;
sixRdMIB MODULE-IDENTITY
LAST-UPDATED "201208120000Z" -- August 12, 2012
ORGANIZATION "IETF Softwire Working Group"
CONTACT-INFO
"Lei Cai
ZTE
No. 68 Zijinhua Rd.,
Nanjing, 210012
China
Email: cai.lei3@zte.com.cn
Jacni Qin
Cisco Systems
Shanghai,
China
Email: jacni@jacni.com
Shishio Tsuchiya
Cisco Systems
Midtown Tower, 9-7-1, Akasaka
Minato-Ku, Tokyo 107-6227
Japan
Email: shtsuchi@cisco.com"
DESCRIPTION
"The MIB module defines managed objects for 6rd."
:: = { transmission XX } ---xx to be replaced
sixRdDevice OBJECT-TYPE
SYNTAX Integer32 (0..1)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A value of 1 indicates the device is a 6rd BR,
or 0 indicates the device is a 6rd CE."
::= { sixRdMIB 1 }
sixRdTable OBJECT-TYPE
SYNTAX SEQUENCE OF SixRdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table contains the configuration information
of 6rd on a particular tunnel."
::= { sixRdMIB 2 }
sixRdEntry OBJECT-TYPE
SYNTAX SixRdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing the configuration
information of 6rd on a particular tunnel."
INDEX {ifIndex}
::= { sixRdTable 1 }
SixRdEntry ::= SEQUENCE {
sixRdPrefix InetAddressIPv6,
sixRdPrefixLen InetAddressPrefixLength,
sixRdIpv4MaskLen Integer32
}
sixRdPrefix OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The 6rd prefix of this 6rd domain."
::= { sixRdEntry 1 }
sixRdPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The length of 6rd prefix."
::= { sixRdEntry 2 }
sixRdIpv4MaskLen OBJECT-TYPE
SYNTAX Integer32 (0..32)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of high-order bits that are
identical across all CE IPv4 addresses within
this 6rd domain."
::= { sixRdEntry 3 }
sixRdBrIpv4AddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF SixRdBrIpv4AddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table contains the BR IPv4 Address of given
6rd domain if the value of 6rdDevice is 0 (i.e.,
6rd CE), or should be omitted if the value of
6rdDevice is 1 (i.e., 6rd BR)."
::= { sixRdMIB 3 }
sixRdBrIpv4AddressEntry OBJECT-TYPE
SYNTAX SixRdBrIpv4AddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing the BR IPv4 Address of given
6rd domain."
INDEX {ifIndex,
sixRdBrIpv4Address
}
::= { sixRdBrIpv4AddressTable 1 }
SixRdBrIpv4AddressEntry ::= SEQUENCE {
sixRdBrIpv4Address InetAddressIPv4
}
sixRdBrIpv4Address OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The BR IPv4 Address of this 6rd domain."
::= { sixRdBrIpv4AddressEntry 1 }
END
This document does not introduce any new security concern in addition to what is discussed in Section 6 of [RFC4087].
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:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
sixRdMIB { transmission XXX }
IANAtunnelType ::= TEXTUAL-CONVENTION
SYNTAX INTEGER {
sixRd ("XX") -- 6rd encapsulation
}
| [RFC4181] | Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. |