Network Working Group Y. Fu Internet Draft S. Jiang Intended status: Standards Track B.Liu Expires: January 18, 2013 Huawei Technologies Co., Ltd July 16, 2012 Definitions of Managed Objects for 4rd draft-fu-softwire-4rd-mib-01 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 January 18, 2013. 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. 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. Fu, et al. Expires January 18, 2013 [Page 1] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 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 fourRdInterfaceInfo ................................. 3 4.2. The fourRdNat Subtree ................................... 4 4.3. The fourRdStatisticInfo Subtree ......................... 4 4.4. The fourRdTrap Subtree .................................. 4 4.5. 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 References ................................. 15 10. Change Log [RFC Editor please remove] ...................... 15 Author's Addresses ............................................. 15 Fu, et al. Expires January 18, 2013 [Page 2] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 1. Introduction 4rd [I-D. draft-ietf-softwire-4rd] is a stateless mechanism for running IPv4 over IPv6-only infrastructure. It provides both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 co- existing period. 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 NAT MIB [RFC4008]. 4.1. The fourRdInterfaceInfo The fourRdInterfaceInfo is defined in the MIB module to configure interface specific for 4rd services enabled for the interface. Fu, et al. Expires January 18, 2013 [Page 3] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 4.2. The fourRdNat Subtree The fourRdNat subtree describes managed objects used for managing the packet translation on BR in the 4rd scenario. Because the NAT MIB supports the packet translation management function in 4rd, we may reuse it in 4rd MIB. However, a 4rd BR will be configured more than one CE mapping rules and a BR mapping rule. It needs to extend the NAT MIB by some parameters for different mapping rules. 4.3. The fourRdStatisticInfo Subtree The fourRdStatisticInfo subtree provides state and statistical information for 4rd BRs. 4.4. The fourRdTrap Subtree The fourRdTrap Subtree provides trap information in 4rd scenario. 4.5. The fourRdConformance Subtree The Subtree provides conformance information of MIB objects. 5. MIB modules required for IMPORTS This MIB module IMPORTs objects from [RFC4008], [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 Fu, et al. Expires January 18, 2013 [Page 4] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 NatAddrMapId, natAddrMapName, natAddrMapEntryType, natAddrMapLocalPortFrom, natAddrMapLocalPortTo, natAddrMapGlobalPortFrom, natAddrMapGlobalPortTo FROM natMIB fourRdMIB MODULE-IDENTITY LAST-UPDATED "201207160000Z" -- July 16, 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 Bing Liu Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District Beijing, P.R. China 100095 EMail: leo.liubing@huawei.com" DESCRIPTION "The MIB module is defined for management of object in the 4rd scenario." ::= { transmission xxx } --xxx to be replaced with correct value fourRdInterfaceInfo OBJECT IDENTIFIER :: = { fourRdMIB 1 } fourRdNat OBJECT IDENTIFIER :: = { fourRdMIB 2 } fourRdStatisticInfo OBJECT IDENTIFIER :: = { fourRdMIB 3 } fourRdTraps OBJECT IDENTIFIER ::= { fourRdMIB 4 } Fu, et al. Expires January 18, 2013 [Page 5] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 --Conformance fourRdConformance OBJECT IDENTIFIER :: = { fourRdMIB 5 } fourRdInterfaceTable OBJECT-TYPE SYNTAX SEQUENCE OF fourRdInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies the attributes for interfaces on the BR supporting 4rd function." ::= { fourRdInterfaceInfo 1 } fourRdInterfaceEntry OBJECT-TYPE SYNTAX fourRdInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " An entry containing additional information applicable to a particular NAT interface." INDEX { ifIndex } ::= { fourRdInterfaceTable 1 } fourRdInterfaceEntry ::= SEQUENCE { fourRdInterfaceRealm INTEGER, fourRdInterfaceIPAddress InetAddressIPv6 } --fourRdNat --fourRdNatTable fourRdNatTable OBJECT-TYPE SYNTAX SEQUENCE OF fourRdNatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table containing information on configured for NAT. It can also be used for row creation." :: = { fourRdNat 1 } fourRdNatEntry OBJECT-TYPE SYNTAX fourRdNatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table contains the information on a particular configured NAT." Fu, et al. Expires January 18, 2013 [Page 6] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 INDEX { fourRdNATBRAddress, fourRdNATMapRuleID} :: = { fourRdNatTable 1 } fourRdTunnelEntry :: = SEQUENCE { fourRdNATBRAddress InetAddressIPv6, fourRdNATMapRuleID Integer32, fourRdNATMapRuleIPv6Prefix InetAddressIPv6, fourRdNATMapRuleIPv6PrefixLen InetAddressPrefixLength, fourRdNATMapRuleIPv4Prefix InetAddress, fourRdNATMapRuleIPv4PrefixLen InetAddressPrefixLength, fourRdNATMapEALen Integer32, fourRdNATInAddress InetAddressIPv6, fourRdNATOutAddress InetAddress, fourRdNATIfIndex ifIndex, fourRdNATAddrMapEntryType natAddrMapEntryType, fourRdNATStatus RowStatus, fourRdNATStorageType StorageType } fourRdNATBRAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the BR. It is a NAT translator." ::= { fourRdNATEntry 1 } fourRdNATMapRuleID 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." ::= { fourRdNATEntry 2 } fourRdNATMapRuleIPv6Prefix OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The IPv6 prefix defined in mapping rule which will be assigned to CE ." ::= { fourRdNATEntry 3 } Fu, et al. Expires January 18, 2013 [Page 7] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 fourRdNATMapRuleIPv6PrefixLen 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." ::= { fourRdNATEntry 4 } fourRdNATMapRuleIPv4Prefix OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION " The IPv4 prefix defined in mapping rule which will be assigned to CE." ::= { fourRdNATEntry 5 } fourRdNATMapRuleIPv4PrefixLen 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." ::= { fourRdNATEntry 6 } fourRdNATMAPEALen 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." ::= { fourRdNATEntry 7 } fourRdNATCEAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the CE. It is derived by the parameters defined in the mapping rule assigned to the CE." ::= { fourRdNATEntry 8 } Fu, et al. Expires January 18, 2013 [Page 8] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 fourRdNATInAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The IPv6 Address translated from in the NAT." ::= { fourRdNATEntry 9 } fourRdNATOutAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION " The IP Address translated to in the NAT." ::= { fourRdNATEntry 10 } fourRdNATAddrMapEntryType OBJECT-TYPE SYNTAX natAddrMapEntryType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of this object in 4rd scenario is the static map." ::= { fourRdNATEntry 11 } fourRdNATStatus 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. ::= { fourRdNATEntry 12 } fourRdNATStorageType 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." ::= { fourRdNATEntry 13 } --fourRdStatisticInfo Fu, et al. Expires January 18, 2013 [Page 9] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 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 DESCRIPTION "This table provides statistical information of 4rd." INDEX { fourRdStatisticBRAddress } ::= { fourRdStatisticTable 1 } fourRdStatisticEntry ::= SEQUENCE { fourRdStatisticBRAddress InetAddressIPv6, fourRdStatisticDiscard Counter64, fourRdStatisticInTranslates Counter64, fourRdStatisticOutTranslates Counter64, fourRdStatisticSpecificIP DisplayString, fourRdStatisticStorageType StorageType, fourRdStatisticRowStatus RowStatus } fourRdStatisticBRAddress OBJECT-TYPE SYNTAX InetAddressIPv6 MAX-ACCESS read-create STATUS current DESCRIPTION "The address of the BR." ::= { 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 } Fu, et al. Expires January 18, 2013 [Page 10] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 fourRdStatisticInTranslates OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicate the count Number of packets received on this BR that were translated." ::= { fourRdStatisticEntry 3 } fourRdStatisticOutTranslates OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicate the count number of translated packets that were sent out from this BR." ::= { fourRdStatisticEntry 4 } 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 5 } fourRdStatisticStorageType 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." ::= { fourRdStatisticEntry 6 } fourRdStatisticRowStatus 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. ::= { fourRdStatisticEntry 7 } Fu, et al. Expires January 18, 2013 [Page 11] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 ---fourRd trap fourRdBRPortUsageOfSpecificIpAlarm NOTIFICATION-TYPE OBJECTS { fourRdStatisticSpecificIP } STATUS current DESCRIPTION "This trap is triggered when the used ports of specific CE address reach the threshold." ::= { fourRdTraps 1 } --Module Conformance statement fourRdCompliances OBJECT IDENTIFIER ::= { fourRdConformance 1 } fourRdCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Description." MODULE -- this module MANDATORY-GROUPS { fourRdNATGroup, fourRdStatisticInfoGroup } ::= { fourRdCompliances 1 } fourRdGroups OBJECT IDENTIFIER ::= { fourRdConformance 2 } fourRdNATGroup OBJECT-GROUP OBJECTS { fourRdNATBRAddress, fourRdNATMapRuleID, fourRdNATMapRuleIPv6Prefix, fourRdNATMapRuleIPv6PrefixLen, fourRdNATMapRuleIPv4Prefix, fourRdNATMapRuleIPv4PrefixLen, fourRdNATMapEALen, fourRdNATInAddress, fourRdNATOutAddress, fourRdNATIfIndex, fourRdNATAddrMapEntryType, fourRdNATStatus, fourRdNATlStorageType } STATUS current DESCRIPTION " The collection of this objects are used to give the information of NAT in 4rd." ::= { fourRdGroups 1 } fourRdStatisticGroup OBJECT-GROUP OBJECTS { fourRdStatisticBRAddress, fourRdStatisticDiscard, fourRdStatisticInTranslates, fourRdStatisticOutTranslates, Fu, et al. Expires January 18, 2013 [Page 12] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 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 { fourRdBRPortUsageOfSpecificIpAlarm } STATUS current DESCRIPTION "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 NAT 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). Fu, et al. Expires January 18, 2013 [Page 13] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 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. 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. [RFC4008] Rohit, R., Srisuresh, P., Raghunarayan, R., Pai, N., and C. Wang, "Definitions of Managed Objects for Network Address Translators (NAT)", RFC 4008, March 2005. [I-D. ietf-softwire-4rd] R. Despres, et al., "IPv4 Residual Deployment via IPv6-a unified Stateless Solution (4rd)", draft-ietf-softwire-4rd, working in progress. Fu, et al. Expires January 18, 2013 [Page 14] Internet-Draft draft-fu-softwire-4rd-mib-01.txt July 2012 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. 10. Change Log [RFC Editor please remove] draft-fu-softwire-4rd-mib-00, original version, 2012-02-01 draft-fu-softwire-4rd-mib-01, 01 version, 2012-07-16 Author's Addresses Yu Fu Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District, Beijing 100095 P.R. China Email: eleven.fuyu@huawei.com Sheng Jiang Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District, Beijing 100095 P.R. China Email: jiangsheng@huawei.com Bing Liu Huawei Technologies Co., Ltd Huawei Building, 156 Beiqing Rd., Hai-Dian District, Beijing 100095 P.R. China Email: leo.liubing@huawei.com Fu, et al. Expires January 18, 2013 [Page 15]