Softwire L. Cai Internet-Draft ZTE Updates: RFC4087 (if approved) J. Qin Intended status: Standards Track S. Tsuchiya Expires: February 13, 2013 Cisco Systems August 12, 2012 Definitions of Managed Objects for 6rd draft-cai-softwire-6rd-mib-03 Abstract 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. 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 February 13, 2013. Copyright Notice Copyright (c) 2012 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. Cai, et al. Expires February 13, 2013 [Page 1] Internet-Draft 6rd MIB August 2012 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3 4.1. sixRdTable . . . . . . . . . . . . . . . . . . . . . . . . 3 4.2. sixRdBrIpv4AddressTable . . . . . . . . . . . . . . . . . . 3 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . . 4 5.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 4 5.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . . 4 5.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 4 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Cai, et al. Expires February 13, 2013 [Page 2] Internet-Draft 6rd MIB August 2012 1. Introduction 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. 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. 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]. 4. Structure of the MIB Module The MIB Module specified herein provides one way to manage the 6rd devices through SNMP. 4.1. sixRdTable This table contains the configuration information for 6rd. 4.2. sixRdBrIpv4AddressTable This table contains the BR IPv4 Address for configurations on given 6rd CE device. Cai, et al. Expires February 13, 2013 [Page 3] Internet-Draft 6rd MIB August 2012 5. Relationship to Other MIB Modules 5.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 SAMPLE-MIB does not duplicate those objects. 5.2. Relationship to the IP Tunnel MIB 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. 5.3. MIB modules required for IMPORTS This MIB module IMPORTs objects from [RFC4087], [RFC2580], [RFC2578], [RFC2863], [RFC3411]. 6. Definitions SIXRD-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, transmission, Integer32 FROM SNMPv2-SMI ifIndex FROM IF-MIB Cai, et al. Expires February 13, 2013 [Page 4] Internet-Draft 6rd MIB August 2012 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." Cai, et al. Expires February 13, 2013 [Page 5] Internet-Draft 6rd MIB August 2012 ::= { 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 Cai, et al. Expires February 13, 2013 [Page 6] Internet-Draft 6rd MIB August 2012 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 7. Security Considerations This document does not introduce any new security concern in addition to what is discussed in Section 6 of [RFC4087]. 8. IANA Considerations 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: Cai, et al. Expires February 13, 2013 [Page 7] Internet-Draft 6rd MIB August 2012 Descriptor OBJECT IDENTIFIER value ---------- ----------------------- sixRdMIB { transmission XXX } IANAtunnelType ::= TEXTUAL-CONVENTION SYNTAX INTEGER { sixRd ("XX") -- 6rd encapsulation } 9. References 9.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. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3371] Caves, E., Calhoun, P., and R. Wheeler, "Layer Two Tunneling Protocol "L2TP" Management Information Base", RFC 3371, August 2002. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. Cai, et al. Expires February 13, 2013 [Page 8] Internet-Draft 6rd MIB August 2012 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification", RFC 5969, August 2010. 9.2. Informative References [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. Authors' Addresses Lei Cai ZTE No. 68 Zijinhua Rd., Nanjing, 210012 China Phone: +86 25 5287 2205 Email: cai.lei3@zte.com.cn Jacni Qin Cisco Systems Shanghai, China Phone: +86 1891 836 3666 Email: jacni@jacni.com Shishio Tsuchiya Cisco Systems Midtown Tower, 9-7-1, Akasaka Minato-Ku, Tokyo 107-6227 Japan Phone: +81 3 6434 6543 Email: shtsuchi@cisco.com Cai, et al. Expires February 13, 2013 [Page 9]