Network Working Group Y. Fu Internet Draft S. Jiang Intended status: Standards Track Huawei Technologies Co., Ltd Expires: August 4, 2012 J.Dong P. Wu Tsinghua University February 1, 2012 Definitions of Managed Objects for 4rd draft-fu-softwire-4rd-mib-00 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 August 4, 2012. 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. Fu, et al. Expires August 4, 2012 [Page 1] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 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 managed objects for 4rd. Table of Contents 1. Introduction ................................................ 3 2. The Internet-Standard Management Framework .................. 3 3. Terminology ................................................. 3 4. Structure of the MIB Module.................................. 3 4.1. The fourRdTunnel Subtree................................ 3 4.2. The fourRdStatisticInfo Subtree ........................ 4 4.3. The fourRdTrap Subtree.................................. 4 4.4. The fourRdConformance Subtree........................... 4 5. MIB modules required for IMPORTS............................. 4 6. Definitions ................................................. 4 7. IANA Considerations ........................................ 13 8. Security Considerations..................................... 13 9. References ................................................. 14 9.1. Normative References................................... 14 9.2. Informative Reference ................................. 14 10. Change Log [RFC Editor please remove] ......................15 Author's Addresses ............................................ 15 Fu, et al. Expires August 4, 2012 [Page 2] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 1. Introduction 4rd [I-D.murakami-softwire-4rd], [I-D.despres-softwire-4rd] is a stateless mechanism for running IPv4 over IPv6-only infrastructure. It provides an automatic tunnelling mechanism for providing IPv4 connectivity service to end users over a service provider's IPv6 network. This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This MIB module may be used for monitoring the devices in the 4rd scenario. 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 [RFC3410]. Managed objects are accessed via a virtual information store, termed the 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 [RFC2578], [RFC2579] and [RFC2580]. 3. Terminology 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 [RFC2119]. 4. Structure of the MIB Module The 4rd MIB provides a way to configure and manage the devices in 4rd scenario through SNMP. 4rd MIB is configurable on a per-interface basis. It depends on several parts of the IF-MIB [RFC2863] and tunnel MIB [RFC4087]. 4.1. The fourRdTunnel Subtree The fourRdTunnel subtree describes managed objects used for managing tunnels in the 4rd scenario. Because the tunnel MIB supports the Fu, et al. Expires August 4, 2012 [Page 3] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 tunnel management function in 4rd, we may reuse it in 4rd MIB. However, a 4rd BR is considered to be a collection of 4rd tunnel endpoints which is distinguished by different mapping rules. It needs to extend the tunnel MIB by some parameters of mapping rule ID to distinguish the different tunnels. 4.2. The fourRdStatisticInfo Subtree The fourRdStatisticInfo subtree provides state and statistical information for 4rd BRs or 4rd tunnel endpoints. 4.3. The fourRdTrap Subtree The fourRdTrap Subtree provides trap information in 4rd instance. 4.4. The fourRdConformance Subtree The Subtree provides conformance information of MIB objects. 5. MIB modules required for IMPORTS This MIB module IMPORTs objects from [RFC4087], [RFC2580], [RFC2578], [RFC2863], [RFC4001], [RFC3411]. 6. Definitions fourRd-MIB DEFFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission, Gauge32, Integer32, Counter64 FROM SNMPv2-SMI RowStatus, StorageType, DisplayString FROM SNMPv2-TC ifIndex, InterfaceIndexOrZero FROM IF-MIB InetAddress, InetAddressIPv6 InetPortNumber, InetAddressPrefixLength FROM INET-ADDRESS-MIB tunnelInetConfigIfIndex FROM tunnelMIB Fu, et al. Expires August 4, 2012 [Page 4] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 fourRdMIB MODULE-IDENTITY LAST-UPDATED "201201310000Z" -- January 31, 2012 ORGANIZATION "IETF Softwire Working Group" CONTACT-INFO "Yu Fu Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District Beijing, P.R. China 100095 EMail: eleven.fuyu@huawei.com Sheng Jiang Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District Beijing, P.R. China 100095 EMail: jiangsheng@huawei.com Jiang Dong Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R. China Email: dongjiang @csnet1.cs.tsinghua.edu.cn Peng Wu Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R. China Email: weapon@csnet1.cs.tsinghua.edu.cn" DESCRIPTION "The MIB module is defined for management of object in the 4rd scenario." ::= { transmission xxx } --xxx to be replaced with correct value fourRdTunnel OBJECT IDENTIFIER :: = { fourRdMIB 1 } fourRdStatisticInfo OBJECT IDENTIFIER :: = { fourRdMIB 2 } fourRdTraps OBJECT IDENTIFIER ::= { fourRdMIB 3 } Fu, et al. Expires August 4, 2012 [Page 5] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 --Conformance fourRdConformance OBJECT IDENTIFIER :: = { fourRdMIB 4 } --fourRdTunnel --fourRdTunnelTable fourRdTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF fourRdTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table containing information on configured tunnels. This table can be used to map CE address to the associated 4rd BR address. It can also be used for row creation." :: = { fourRdTunnel 1 } fourRdTunnelEntry OBJECT-TYPE SYNTAX fourRdTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table contains the information on a particular configured tunnel." INDEX { fourRdTunnelBRAddress, fourRdTunnelMapRuleID} :: = { fourRdTunnelTable 1 } fourRdTunnelEntry :: = SEQUENCE { fourRdTunnelBRAddress InetAddressIPv6, fourRdTunnelMapRuleID Integer32, fourRdTunnelMapRuleIPv6Prefix InetAddressIPv6, fourRdTunnelMapRuleIPv6PrefixLen InetAddressPrefixLength, fourRdTunnelMapRuleIPv4Prefix InetAddress, fourRdTunnelMapRuleIPv4PrefixLen InetAddressPrefixLength, fourRdTunnelMAPRuleExPorts InetPortNumber, fourRdTunnelMAPEALen Integer32, fourRdTunnelCEAddress InetAddressIPv6, fourRdTunnelID Integer32, fourRdTunnelIfIndex tunnelInetConfigIfIndex, fourRdTunnelStatus RowStatus, fourRdTunnelStorageType StorageType } Fu, et al. Expires August 4, 2012 [Page 6] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 fourRdTunnelBRAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the BR. It is one endpoint of the 4rd Tunnel" ::= { fourRdTunnelEntry 1 } fourRdTunnelMapRuleID OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "An identifier used to distinguish the multiple mapping rule which is unique with each CE in the same BR." ::= { fourRdTunnelEntry 2 } fourRdTunnelMapRuleIPv6Prefix OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The IPv6 prefix defined in mapping rule which will be assigned to CE ." ::= { fourRdTunnelEntry 3 } fourRdTunnelMapRuleIPv6PrefixLen OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-create STATUS current DESCRIPTION "The length of the IPv6 prefix defined in the mapping rule. As a parameter for mapping rule, it will be also assigned to CE." ::= { fourRdTunnelEntry 4 } fourRdTunnelMapRuleIPv4Prefix OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION " The IPv4 prefix defined in mapping rule which will be assigned to CE." ::= { fourRdTunnelEntry 5 } Fu, et al. Expires August 4, 2012 [Page 7] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 fourRdTunnelMapRuleIPv4PrefixLen OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS read-create STATUS current DESCRIPTION " The length of the IPv4 prefix defined in the mapping rule. As a parameter for mapping rule, it will be also assigned to CE." ::= { fourRdTunnelEntry 6 } fourRdTunnelMAPRuleExPorts OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The upper bound for range of excluded ports defined in mapping rule which will be assigned to CE." ::= { fourRdTunnelEntry 7 } fourRdTunnelMAPEALen OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The length of the Embedded-Address (EA) defined in mapping rule which will be assigned to CE." ::= { fourRdTunnelEntry 8 } fourRdTunnelCEAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the CE as the another endpoint of 4rd tunnel. It is derived by the parameters defined in the mapping rule assigned to the CE." ::= { fourRdTunnelEntry 9 } fourRdTunnelID OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "An identifier used to distinguish between multiple tunnels in 4rd scenario." ::= { fourRdTunnelEntry 10 } Fu, et al. Expires August 4, 2012 [Page 8] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 fourRdTunnelIfIndex OBJECT-TYPE SYNTAX tunnelInetConfigIfIndex MAX-ACCESS read-only STATUS current DESCRIPTION "If the value of fourRdTunnelStatus for this row is active, then this object contains the value of ifIndex corresponding to the tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned." ::= { fourRdTunnelEntry 11 } fourRdTunnelStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row, by which new entries may be created, or old entries deleted from this table. ::= { fourRdTunnelEntry 12 } fourRdTunnelStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type of this row. If the row is permanent(4), no objects in the row need be writable." ::= { fourRdTunnelEntry 13 } --fourRdStatisticInfo fourRdStatisticTable OBJECT-TYPE SYNTAX SEQUENCE OF fourRdStatisticEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides some statistical information of 4rd." ::= { fourRdStatisticInfo 1 } fourRdStatisticEntry OBJECT-TYPE SYNTAX dsliteStatisticEntry MAX-ACCESS not-accessible STATUS current Fu, et al. Expires August 4, 2012 [Page 9] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 DESCRIPTION "This table provides statistical information of 4rd." INDEX { fourRdStatisticBRAddress } ::= { fourRdStatisticTable 1 } fourRdStatisticEntry ::= SEQUENCE { fourRdStatisticBRAddress InetAddressIPv6, fourRdStatisticDiscard Counter64, fourRdStatisticReceived Counter64, fourRdStatisticTransmitted Counter64, fourRdStatisticConnections Integer32, fourRdStatisticSpecificIP DisplayString, fourRdStatisticStorageType StorageType, fourRdStatisticRowStatus RowStatus } fourRdStatisticBRAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the BR. It is one endpoint of the 4rd Tunnel" ::= { fourRdStatisticEntry 1 } fourRdStatisticDiscard OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-create STATUS current DESCRIPTION " This object indicate the count number of the discarded packet." ::= { fourRdStatisticEntry 2 } fourRdStatisticReceived OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicate the count number of received packet count." ::= { fourRdStatisticEntry 3 } fourRdStatisticTransmitted OBJECT-TYPE SYNTAX Counter64 Fu, et al. Expires August 4, 2012 [Page 10] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicate the count number of transmitted packet count." ::= { fourRdStatisticEntry 4 } fourRdStatisticConnections OBJECT-TYPE SYNTAX Integer32 (60..90) MAX-ACCESS read-write STATUS current DESCRIPTION " This object indicate the threshold of 4rd connections for this BR." ::= { fourRdStatisticEntry 5 } fourRdStatisticSpecificIP OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION " This object indicate the IP address of CE whose port usage reach threshold " ::= { fourRdStatisticEntry 6 } ---fourRd trap fourRdTunnelNumAlarm NOTIFICATION-TYPE STATUS current DESCRIPTION "This trap is triggered when 4rd tunnel reach the threshold." ::= { fourRdTraps 1 } fourRdBRPortUsageOfSpecificIpAlarm NOTIFICATION-TYPE OBJECTS { fourRdStatisticSpecificIP } STATUS current DESCRIPTION "This trap is triggered when the used ports of specific CE address reach the threshold." ::= { dsliteTraps 2 } --Module Conformance statement fourRdCompliances OBJECT IDENTIFIER ::= { fourRdConformance 1 } Fu, et al. Expires August 4, 2012 [Page 11] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 fourRdCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Description." MODULE -- this module MANDATORY-GROUPS { fourRdTunnelGroup, fourRdStatisticInfoGroup } ::= { fourRdCompliances 1 } fourRdGroups OBJECT IDENTIFIER ::= { fourRdConformance 2 } fourRdTunnelGroup OBJECT-GROUP OBJECTS { fourRdTunnelBRAddress, fourRdTunnelMapRuleID, fourRdTunnelMapRuleIPv6Prefix, fourRdTunnelMapRuleIPv6PrefixLen, fourRdTunnelMapRuleIPv4Prefix, fourRdTunnelMapRuleIPv4PrefixLen, fourRdTunnelMAPRuleExPorts, fourRdTunnelMAPEALen, fourRdTunnelCEAddress, fourRdTunnelID, fourRdTunnelIfIndex, fourRdTunnelStatus, dsliteTunnelStorageType } STATUS current DESCRIPTION " The collection of this objects are used to give the information of tunnel in 4rd." ::= { fourRdGroups 1 } fourRdStatisticGroup OBJECT-GROUP OBJECTS { fourRdStatisticBRAddress, fourRdStatisticDiscard, fourRdStatisticReceived, fourRdStatisticTransmitted, fourRdStatisticConnections, fourRdStatisticSpecificIP, fourRdStatisticStorageType, fourRdStatisticRowStatus } STATUS current DESCRIPTION " The collection of this objects are used to give the statistical information of 4rd." ::= { fourRdGroups 2 } fourRdTrapsGroup NOTIFICATION-GROUP NOTIFICATIONS { fourRdTunnelNumAlarm, fourRdBRPortUsageOfSpecificIpAlarm } STATUS current DESCRIPTION Fu, et al. Expires August 4, 2012 [Page 12] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 "The collection of this objects are used to give the trap information of 4rd." ::= { fourRdGroups 3 } END 7. 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 ---------- ----------------------- fourRd-MIB { transmission XXX } 8. Security Considerations The 4rd MIB module can be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. Because this MIB module reuses the IP tunnel MIB, the security considerations for these MIBs are also applicable to the 4rd MIB. 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 principles (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Fu, et al. Expires August 4, 2012 [Page 13] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 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., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", RFC 2580, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholz. "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, December 2002. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. [I-D.mdt-softwire-mapping-address-and-port] Troan, O., "Mapping of Address and Port (MAP)", draft-mdt- softwire-mapping-address-and-port, working in progress. [I-D.mdt-softwire-map-dhcp-option] Mrugalski, T., "DHCPv6 Options for Mapping of Address and Port", draft-mdt-softwire-map-dhcp-option, working in progress. 9.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. Fu, et al. Expires August 4, 2012 [Page 14] Internet-Draft draft-fu-softwire-4rd-mib-00.txt February 2012 10. Change Log [RFC Editor please remove] draft-fu-softwire-4rd-mib-00, original version, 2012-02-01 Author's Addresses Yu Fu Huawei Technologies Co., Ltd Huawei Building, 56 Beiqing Rd., Hai-Dian District, Beijing 100095 P.R. China Email: eleven.fuyu@huawei.com Sheng Jiang Huawei Technologies Co., Ltd Huawei Building, 56 Beiqing Rd., Hai-Dian District, Beijing 100095 P.R. China Email: shengjiang@huawei.com Jiang Dong Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R. China Email: dongjiang@csnet1.cs.tsinghua.edu.cn Peng Wu Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R. China Email: weapon@csnet1.cs.tsinghua.edu.cn Fu, et al. Expires August 4, 2012 [Page 15]