idnits 2.17.1 draft-fu-softwire-4rd-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (February 14, 2014) is 3695 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Y. Fu 2 Internet Draft S. Jiang 3 Intended status: Standards Track B.Liu 4 Expires: August 18, 2014 Huawei Technologies Co., Ltd 5 February 14, 2014 7 Definitions of Managed Objects for 4rd 8 draft-fu-softwire-4rd-mib-04 10 Status of this Memo 12 This Internet-Draft is submitted in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF). Note that other groups may also distribute working 17 documents as Internet-Drafts. The list of current Internet-Drafts is 18 at http://datatracker.ietf.org/drafts/current/. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 This Internet-Draft will expire on August 18, 2014. 27 Copyright Notice 29 Copyright (c) 2013 IETF Trust and the persons identified as the 30 document authors. All rights reserved. 32 This document is subject to BCP 78 and the IETF Trust's Legal 33 Provisions Relating to IETF Documents 34 (http://trustee.ietf.org/license-info) in effect on the date of 35 publication of this document. Please review these documents 36 carefully, as they describe your rights and restrictions with respect 37 to this document. Code Components extracted from this document must 38 include Simplified BSD License text as described in Section 4.e of 39 the Trust Legal Provisions and are provided without warranty as 40 described in the Simplified BSD License. 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in the Internet community. 46 In particular, it defines managed objects for 4rd. 48 Table of Contents 50 1. Introduction ................................................. 3 51 2. The Internet-Standard Management Framework ................... 3 52 3. Terminology .................................................. 3 53 4. Structure of the MIB Module .................................. 3 54 4.1. The fourRdRule Subtree .................................. 3 55 4.2. The fourRdConformance Subtree ........................... 4 56 5. MIB modules required for IMPORT .............................. 4 57 6. Definitions .................................................. 4 58 7. IANA Considerations .......................................... 8 59 8. Security Considerations ...................................... 8 60 9. References ................................................... 9 61 9.1. Normative References .................................... 9 62 9.2. Informative References ................................. 10 63 10. Change Log [RFC Editor please remove] ...................... 10 64 Author's Addresses ............................................. 10 66 1. Introduction 68 4rd [I-D. draft-ietf-softwire-4rd] is a stateless mechanism for 69 running IPv4 over IPv6-only infrastructure. It provides both IPv4 and 70 IPv6 connectivity services simultaneously during the IPv4/IPv6 co- 71 existing period. 73 This document defines a portion of the Management Information Base 74 (MIB) for using with network management protocols in the Internet 75 community. This MIB module may be used for monitoring the devices in 76 the 4rd scenario. 78 2. The Internet-Standard Management Framework 80 For a detailed overview of the documents that describe the current 81 Internet-Standard Management Framework, please refer to section 7 of 82 [RFC3410]. 84 Managed objects are accessed via a virtual information store, termed 85 the MIB. MIB objects are generally accessed through the Simple 86 Network Management Protocol (SNMP). 88 Objects in the MIB are defined using the mechanisms defined in the 89 Structure of Management Information (SMI). This memo specifies a MIB 90 module that is compliant to the SMIv2, which is described in 91 [RFC2578], [RFC2579] and [RFC2580]. 93 3. Terminology 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in [RFC2119]. 99 4. Structure of the MIB Module 101 The 4rd MIB provides a way to configure and manage the devices in 4rd 102 scenario through SNMP. 104 4rd MIB is configurable on a per-interface basis. It depends on 105 several parts of the IF-MIB [RFC2863]. 107 4.1. The fourRdRule Subtree 109 The fourRdRule subtree describes managed objects used for managing 110 the multiple mapping rules in the 4rd scenario. 112 4.2. The fourRdConformance Subtree 114 The Subtree provides conformance information of MIB objects. 116 5. MIB modules required for IMPORTS 118 This MIB module IMPORTs objects from [RFC2580], [RFC2578], [RFC2863], 119 [RFC4001], [RFC3411]. 121 6. Definitions 123 FourRd-MIB DEFINITIONS ::= BEGIN 125 IMPORTS 126 MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission, 127 Gauge32, Integer32, Counter64 128 FROM SNMPv2-SMI 130 InetAddress, 131 InetPortNumber, InetAddressPrefixLength 132 FROM INET-ADDRESS-MIB 134 OBJECT-GROUP, MODULE-COMPLIANCE 135 FROM SNMPv2-CONF; 137 fourRdMIB MODULE-IDENTITY 138 LAST-UPDATED "201308120000Z" -- February 14, 2014 139 ORGANIZATION "IETF Softwire Working Group" 140 CONTACT-INFO 141 "Yu Fu 142 Huawei Technologies Co., Ltd 143 Huawei Building, 156 Beiqing Rd., Hai-Dian District 144 Beijing, P.R. China 100095 145 EMail: eleven.fuyu@huawei.com 147 Sheng Jiang 148 Huawei Technologies Co., Ltd 149 Huawei Building, 156 Beiqing Rd., Hai-Dian District 150 Beijing, P.R. China 100095 151 EMail: jiangsheng@huawei.com 152 Bing Liu 153 Huawei Technologies Co., Ltd 154 Huawei Building, 156 Beiqing Rd., Hai-Dian District 155 Beijing, P.R. China 100095 156 EMail: leo.liubing@huawei.com" 158 DESCRIPTION 159 "The MIB module is defined for management of object in the 160 4rd scenario." 161 REVISION "201308120000Z" 162 DESCRIPTION 163 "Initial version. Published as RFC xxxx." 164 --RFC Ed.: RFC-edtitor pls fill in xxxx 165 ::= { transmission xxx } --xxx to be replaced with correct 166 value 168 fourRdMIBObjects OBJECT IDENTIFIER 169 ::= { fourRdMIB 1 } 171 fourRdRule OBJECT IDENTIFIER 172 ::= { fourRdMIBObjects 1 } 174 --Conformance 175 fourRdMIBConformance OBJECT IDENTIFIER 176 ::= { fourRdMIB 2 } 178 fourRdRuleTable OBJECT-TYPE 179 SYNTAX SEQUENCE OF FourRdRuleEntry 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "The (conceptual) table containing rule information of 184 specific mapping rule. It can also be used for row 185 creation." 186 ::= { fourRdRule 1 } 188 fourRdRuleEntry OBJECT-TYPE 189 SYNTAX FourRdRuleEntry 190 MAX-ACCESS not-accessible 191 STATUS current 192 DESCRIPTION 193 "Each entry in this table contains the information on a 194 particular mapping rule." 195 INDEX { fourRdRuleID} 196 ::= { fourRdRuleTable 1 } 198 FourRdRuleEntry ::= 199 SEQUENCE { 200 fourRdRuleID Integer32, 201 fourRdRuleIPv6Prefix InetAddress, 202 fourRdRuleIPv6PrefixLen InetAddressPrefixLength, 203 fourRdRuleIPv4Prefix InetAddress, 204 fourRdRuleIPv4PrefixLen InetAddressPrefixLength, 205 fourRdRuleStartPort InetPortNumber, 206 fourRdRuleEndPort InetPortNumber, 207 fourRdRuleEALen Integer32 208 } 210 fourRdRuleID OBJECT-TYPE 211 SYNTAX Integer32 (1..2147483647) 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "An identifier used to distinguish the multiple mapping 216 rule which is unique with each CE in the same BR." 217 ::= { fourRdRuleEntry 1 } 219 fourRdRuleIPv6Prefix OBJECT-TYPE 220 SYNTAX InetAddress 221 MAX-ACCESS read-write 222 STATUS current 223 DESCRIPTION 224 "The IPv6 prefix defined in mapping rule which will be 225 assigned to CE ." 226 ::= { fourRdRuleEntry 2 } 228 fourRdRuleIPv6PrefixLen OBJECT-TYPE 229 SYNTAX InetAddressPrefixLength 230 MAX-ACCESS read-write 231 STATUS current 232 DESCRIPTION 233 "The length of the IPv6 prefix defined in the mapping rule. 234 As a parameter for mapping rule, it will be also assigned 235 to CE." 236 ::= { fourRdRuleEntry 3 } 238 fourRdRuleIPv4Prefix OBJECT-TYPE 239 SYNTAX InetAddress 240 MAX-ACCESS read-write 241 STATUS current 242 DESCRIPTION 243 " The IPv4 prefix defined in mapping rule which will be 244 assigned to CE." 245 ::= { fourRdRuleEntry 4 } 247 fourRdRuleIPv4PrefixLen OBJECT-TYPE 248 SYNTAX InetAddressPrefixLength 249 MAX-ACCESS read-write 250 STATUS current 251 DESCRIPTION 252 "The length of the IPv4 prefix defined in the mapping 253 rule. As a parameter for mapping rule, it will be also 254 assigned to CE." 255 ::= { fourRdRuleEntry 5 } 257 fourRdRuleStartPort OBJECT-TYPE 258 SYNTAX InetPortNumber 259 MAX-ACCESS read-write 260 STATUS current 261 DESCRIPTION 262 "The start port number of the port range derived 263 from the mapping rule which will be assigned to CE." 264 ::= { fourRdRuleEntry 6 } 266 fourRdRuleEndPort OBJECT-TYPE 267 SYNTAX InetPortNumber 268 MAX-ACCESS read-write 269 STATUS current 270 DESCRIPTION 271 " The end port number of the port range derived 272 from the mapping rule which will be assigned to CE." 273 ::= { fourRdRuleEntry 7 } 275 fourRdRuleEALen OBJECT-TYPE 276 SYNTAX Integer32 277 MAX-ACCESS read-write 278 STATUS current 279 DESCRIPTION 280 "The length of the Embedded-Address (EA) defined in 281 mapping rule which will be assigned to CE." 282 ::= { fourRdRuleEntry 8 } 284 --Module Conformance statement 286 fourRdMIBCompliances OBJECT IDENTIFIER ::= { fourRdMIBConformance 287 1 } 288 fourRdMIBCompliance MODULE-COMPLIANCE 289 STATUS current 290 DESCRIPTION 291 "Describes the minimal requirements for conformance 292 to the fourRd MIB." 293 MODULE -- this module 294 MANDATORY-GROUPS { fourRdRuleGroup } 295 ::= { fourRdMIBCompliances 1 } 297 fourRdGroups OBJECT IDENTIFIER ::= { fourRdNIBConformance 2 } 299 fourRdRuleGroup OBJECT-GROUP 300 OBJECTS { 301 fourRdRuleIPv6Prefix, 302 fourRdRuleIPv6PrefixLen, 303 fourRdRuleIPv4Prefix, 304 fourRdRuleIPv4PrefixLen, 305 fourRdRuleStartPort, 306 fourRdRuleEndPort, 307 fourRdRuleEALen, 308 } 309 STATUS current 310 DESCRIPTION 311 " The collection of this objects are used to give the 312 mapping rule information in 4rd." 313 ::= { fourRdGroups 1 } 315 END 317 7. IANA Considerations 319 The MIB module in this document uses the following IANA-assigned 320 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 322 Descriptor OBJECT IDENTIFIER value 323 ---------- ----------------------- 324 FourRd-MIB { transmission XXX } 326 8. Security Considerations 328 The 4rd MIB module can be used for configuration of certain objects, 329 and anything that can be configured can be incorrectly configured, 330 with potentially disastrous results. Because this MIB module reuses 331 the NAT MIB, the security considerations for these MIBs are also 332 applicable to the 4rd MIB. 334 SNMP versions prior to SNMPv3 did not include adequate security. 335 Even if the network itself is secure (for example by using IPSec), 336 even then, there is no control as to who on the secure network is 337 allowed to access and GET/SET (read/change/create/delete) the objects 338 in this MIB module. 340 It is RECOMMENDED that implementers consider the security features as 341 provided by the SNMPv3 framework (see [RFC3410], section 8), 342 including full support for the SNMPv3 cryptographic mechanisms (for 343 authentication and privacy). 345 Further, deployment of SNMP versions prior to SNMPv3 is NOT 346 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 347 enable cryptographic security. It is then a customer/operator 348 responsibility to ensure that the SNMP entity giving access to an 349 instance of this MIB module is properly configured to give access to 350 the objects only to those principles (users) that have legitimate 351 rights to indeed GET or SET (change/create/delete) them. 353 9. References 355 9.1. Normative References 357 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 358 Requirement Levels", BCP 14, RFC 2119, March 1997. 360 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 361 "Structure of Management Information Version 2 (SMIv2)", 362 RFC 2578, April 1999. 364 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual 365 Conventions for SMIv2", RFC 2579, April 1999. 367 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 368 "Conformance Statements for SMIv2", RFC 2580, April 1999. 370 [RFC2863] McCloghrie, K. and F. Kastenholz. "The Interfaces Group 371 MIB", RFC 2863, June 2000. 373 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 374 Architecture for Describing Simple Network Management 375 Protocol (SNMP) Management Frameworks", RFC 3411, December 376 2002. 378 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 379 Schoenwaelder, "Textual Conventions for Internet Network 380 Addresses", RFC 4001, February 2005. 382 [I-D. ietf-softwire-4rd] 383 R. Despres, et al., "IPv4 Residual Deployment via IPv6-a 384 unified Stateless Solution (4rd)", draft-ietf-softwire-4rd, 385 working in progress. 387 9.2. Informative References 389 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 390 "Introduction and Applicability Statements for Internet- 391 Standard Management Framework", RFC 3410, December 2002. 393 10. Change Log [RFC Editor please remove] 395 draft-fu-softwire-4rd-mib-00, original version, 2012-02-01 396 draft-fu-softwire-4rd-mib-01, 01 version, 2012-07-16 397 draft-fu-softwire-4rd-mib-02, 02 version, 2013-01-17 398 draft-fu-softwire-4rd-mib-03, 03 version, 2013-08-12 400 Author's Addresses 402 Yu Fu 403 Huawei Technologies Co., Ltd 404 Huawei Building, 156 Beiqing Rd., 405 Hai-Dian District, Beijing 100095 406 P.R. China 408 Email: eleven.fuyu@huawei.com 410 Sheng Jiang 411 Huawei Technologies Co., Ltd 412 Huawei Building, 156 Beiqing Rd., 413 Hai-Dian District, Beijing 100095 414 P.R. China 416 Email: jiangsheng@huawei.com 418 Bing Liu 419 Huawei Technologies Co., Ltd 420 Huawei Building, 156 Beiqing Rd., 421 Hai-Dian District, Beijing 100095 422 P.R. China 424 Email: leo.liubing@huawei.com