idnits 2.17.1 draft-cai-softwire-6rd-mib-05.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 : ---------------------------------------------------------------------------- ** There are 5 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 16, 2013) is 3998 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) == Unused Reference: 'RFC4181' is defined on line 403, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Softwire L. Cai 3 Internet-Draft ZTE 4 Intended status: Standards Track J. Qin 5 Expires: November 17, 2013 S. Tsuchiya, Ed. 6 Cisco Systems 7 May 16, 2013 9 Definitions of Managed Objects for 6rd 10 draft-cai-softwire-6rd-mib-05 12 Abstract 14 This document defines a portion of the Management Information Base 15 (MIB) for use with network management protocols. In particular, it 16 defines objects for managing 6rd devices. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 17, 2013. 35 Copyright Notice 37 Copyright (c) 2013 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. The Internet-Standard Management Framework . . . . . . . . . 2 54 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 4. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 56 4.1. sixRdTable . . . . . . . . . . . . . . . . . . . . . . . 3 57 4.2. sixRdBrIpv4AddressTable . . . . . . . . . . . . . . . . . 3 58 4.3. sixRdSecurityCeck . . . . . . . . . . . . . . . . . . . . 3 59 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 3 60 5.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . 3 61 5.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . 3 62 5.3. Relationship to the Interfaces MIB . . . . . . . . . . . 4 63 5.4. Relationship to the IP MIB . . . . . . . . . . . . . . . 4 64 5.5. MIB modules required for IMPORTS . . . . . . . . . . . . 4 65 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 67 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 69 9.1. Normative References . . . . . . . . . . . . . . . . . . 8 70 9.2. Informative References . . . . . . . . . . . . . . . . . 9 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 73 1. Introduction 75 This draft describes the Management Information Base (MIB) module for 76 6rd (IPv6 Rapid Deployment, [RFC5969]), which specifies an automatic 77 tunneling mechanism to deploy IPv6 to sites via a operator's IPv4 78 network. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 3. Conventions 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119 [RFC2119]. 100 4. Structure of the MIB Module 102 The MIB Module specified herein provides one way to manage the 6rd 103 devices through SNMP. 105 4.1. sixRdTable 107 This table contains the configuration information for 6rd. 109 4.2. sixRdBrIpv4AddressTable 111 This table contains the BR IPv4 Address for configurations on given 112 6rd CE device. 114 4.3. sixRdSecurityCeck 116 This table contains counter of packets drop by 6rd receiving rule. 118 5. Relationship to Other MIB Modules 120 5.1. Relationship to the SNMPv2-MIB 122 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 123 mandatory for all systems, and the objects apply to the entity as a 124 whole. The 'system' group provides identification of the management 125 entity and certain other system-wide data. The SAMPLE-MIB does not 126 duplicate those objects. 128 5.2. Relationship to the IP Tunnel MIB 130 The IP Tunnel MIB [RFC4087] contains objects common to all IP 131 tunnels, including 6rd. Additionally, tunnel encapsulation specific 132 MIB (like what is defined in this document) extend the IP tunnel MIB 133 to further describe encapsulation specific information, for example 134 (in case of 6rd): 6rd prefix, 6rd Prefix Length, IPv4Mask Length and 135 BR IPv4 Address. 137 The implementation of the IP Tunnel MIB is required for 6rd. The 138 tunnelIfEncapsMethod in the tunnelIfEntry should be set to 139 sixRd("xx"), and an entry in the 6rd MIB module will exist for every 140 tunnelIfEntry with this tunnelIfEncapsMethod. The 141 tunnelIfRemoteAddress must be set to 0.0.0.0. 143 [Ed.Note:]This is similar to the situation of L2TP MIB [RFC3371] 144 case, since the IANA is requested to assign a value for sixRdMIB 145 under the "transmission" subtree. Also, a new IANAtunnelType (rather 146 than IANAifType) value is needed and should be recorded in the 147 IANAifType-MIB registry, refer to Section 8. 149 5.3. Relationship to the Interfaces MIB 151 Each logical interface (physical or virtual) has an ifEntry in the 152 Interfaces MIB[RFC2863]. Tunnels are handled by creating a logical 153 interface (ifEntry) for each tunnel. 155 5.4. Relationship to the IP MIB 157 IP MIB[RFC4293] provides traffic statics counter and status for 6rd 158 virtual interface. 160 5.5. MIB modules required for IMPORTS 162 This MIB module IMPORTs objects from [RFC4087], [RFC2580], [RFC2578], 163 [RFC2863], [RFC3411]. 165 6. Definitions 167 SIXRD-MIB DEFINITIONS ::= BEGIN 169 IMPORTS 170 OBJECT-TYPE, transmission, Integer32 171 FROM SNMPv2-SMI 173 ifIndex 174 FROM IF-MIB 176 InetAddressIPv4, InetAddressPrefixLength, InetAddressIPv6 177 FROM INET-ADDRESS-MIB; 179 sixRdMIB MODULE-IDENTITY 180 LAST-UPDATED "201208120000Z" -- August 12, 2012 181 ORGANIZATION "IETF Softwire Working Group" 182 CONTACT-INFO 183 "Lei Cai 184 ZTE 185 No. 68 Zijinhua Rd., 186 Nanjing, 210012 187 China 188 Email: cai.lei3@zte.com.cn 190 Jacni Qin 191 Cisco Systems 192 Shanghai, 193 China 194 Email: jacni@jacni.com 196 Shishio Tsuchiya 197 Cisco Systems 198 Midtown Tower, 9-7-1, Akasaka 199 Minato-Ku, Tokyo 107-6227 200 Japan 201 Email: shtsuchi@cisco.com" 203 DESCRIPTION 204 "The MIB module defines managed objects for 6rd." 206 :: = { transmission XX } ---xx to be replaced 208 sixRdDevice OBJECT-TYPE 209 SYNTAX Integer32 (0..1) 210 MAX-ACCESS read-write 211 STATUS current 212 DESCRIPTION 213 "A value of 1 indicates the device is a 6rd BR, 214 or 0 indicates the device is a 6rd CE." 215 ::= { sixRdMIB 1 } 217 sixRdTable OBJECT-TYPE 218 SYNTAX SEQUENCE OF SixRdEntry 219 MAX-ACCESS not-accessible 220 STATUS current 221 DESCRIPTION 222 "The table contains the configuration information 223 of 6rd on a particular tunnel." 224 ::= { sixRdMIB 2 } 226 sixRdEntry OBJECT-TYPE 227 SYNTAX SixRdEntry 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION 231 "An entry containing the configuration 232 information of 6rd on a particular tunnel." 233 INDEX {ifIndex} 234 ::= { sixRdTable 1 } 236 SixRdEntry ::= SEQUENCE { 237 sixRdPrefix InetAddressIPv6, 238 sixRdPrefixLen InetAddressPrefixLength, 239 sixRdIpv4MaskLen Integer32 240 } 242 sixRdPrefix OBJECT-TYPE 243 SYNTAX InetAddressIPv6 244 MAX-ACCESS read-write 245 STATUS current 246 DESCRIPTION 247 "The 6rd prefix of this 6rd domain." 248 ::= { sixRdEntry 1 } 250 sixRdPrefixLen OBJECT-TYPE 251 SYNTAX InetAddressPrefixLength 252 MAX-ACCESS read-write 253 STATUS current 254 DESCRIPTION 255 "The length of 6rd prefix." 256 ::= { sixRdEntry 2 } 258 sixRdIpv4MaskLen OBJECT-TYPE 259 SYNTAX Integer32 (0..32) 260 MAX-ACCESS read-write 261 STATUS current 262 DESCRIPTION 263 "The number of high-order bits that are 264 identical across all CE IPv4 addresses within 265 this 6rd domain." 266 ::= { sixRdEntry 3 } 268 sixRdBrIpv4AddressTable OBJECT-TYPE 269 SYNTAX SEQUENCE OF SixRdBrIpv4AddressEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "The table contains the BR IPv4 Address of given 274 6rd domain if the value of 6rdDevice is 0 (i.e., 275 6rd CE), or should be omitted if the value of 276 6rdDevice is 1 (i.e., 6rd BR)." 277 ::= { sixRdMIB 3 } 279 sixRdBrIpv4AddressEntry OBJECT-TYPE 280 SYNTAX SixRdBrIpv4AddressEntry 281 MAX-ACCESS not-accessible 282 STATUS current 283 DESCRIPTION 284 "An entry containing the BR IPv4 Address of given 285 6rd domain." 286 INDEX {ifIndex, 287 sixRdBrIpv4Address 288 } 289 ::= { sixRdBrIpv4AddressTable 1 } 291 SixRdBrIpv4AddressEntry ::= SEQUENCE { 292 sixRdBrIpv4Address InetAddressIPv4 293 } 295 sixRdBrIpv4Address OBJECT-TYPE 296 SYNTAX InetAddressIPv4 297 MAX-ACCESS read-write 298 STATUS current 299 DESCRIPTION 300 "The BR IPv4 Address of this 6rd domain." 301 ::= { sixRdBrIpv4AddressEntry 1 } 303 sixRdSecurityCeck OBJECT-TYPE 304 SYNTAX SEQUENCE OF sixRdSecurityCeckInvalidPackets 305 MAX-ACCESS not-accessible 306 STATUS current 307 DESCRIPTION 308 "This table contains counter of packets drop by 6rd 309 receiving rule." 310 ::= { sixRdMIB 4 } 312 sixRdSecurityCeckInvalidPackets OBJECT-TYPE 313 SYNTAX Counter64 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "6rd BR/CE MUST validate the embedded IPv4 source 318 address of the encapsulated IPv6 packet with the IPv4 319 source address it is encapsulated by according to the 320 configured parameters of the 6rd domain. If the two 321 source addresses do not match, the packet MUST be dropped 322 and a counter incremented. This counter indicates the total 323 number of octets dropped packets by the receiving rules." 324 INDEX {ifIndex} 325 ::= { sixRdSecurityCeckInvalidPackets 1 } 327 END 329 7. Security Considerations 331 This document does not introduce any new security concern in addition 332 to what is discussed in Section 6 of [RFC4087]. 334 8. IANA Considerations 336 The MIB module in this document uses the following IANA-assigned 337 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 338 the following IANA-assigned tunnelType values recorded in the 339 IANAifType-MIB registry: 341 Descriptor OBJECT IDENTIFIER value 342 ---------- ----------------------- 344 sixRdMIB { transmission XXX } 346 IANAtunnelType ::= TEXTUAL-CONVENTION 347 SYNTAX INTEGER { 349 sixRd ("XX") -- 6rd encapsulation 351 } 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., Ed., Perkins, D., Ed., and J. 361 Schoenwaelder, Ed., "Structure of Management Information 362 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 364 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 365 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 366 58, RFC 2579, April 1999. 368 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 369 "Conformance Statements for SMIv2", STD 58, RFC 2580, 370 April 1999. 372 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 373 MIB", RFC 2863, June 2000. 375 [RFC3371] Caves, E., Calhoun, P., and R. Wheeler, "Layer Two 376 Tunneling Protocol "L2TP" Management Information Base", 377 RFC 3371, August 2002. 379 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 380 "Introduction and Applicability Statements for Internet- 381 Standard Management Framework", RFC 3410, December 2002. 383 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 384 Architecture for Describing Simple Network Management 385 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 386 December 2002. 388 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 389 Simple Network Management Protocol (SNMP)", STD 62, RFC 390 3418, December 2002. 392 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. 394 [RFC4293] Routhier, S., "Management Information Base for the 395 Internet Protocol (IP)", RFC 4293, April 2006. 397 [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 398 Infrastructures (6rd) -- Protocol Specification", RFC 399 5969, August 2010. 401 9.2. Informative References 403 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB 404 Documents", BCP 111, RFC 4181, September 2005. 406 Authors' Addresses 408 Lei Cai 409 ZTE 410 No. 68 Zijinhua Rd., 411 Nanjing 210012 412 China 414 Phone: +86 25 5287 2205 415 Email: cai.lei3@zte.com.cn 417 Jacni Qin 418 Cisco Systems 419 Shanghai 420 China 422 Phone: +86 1891 836 3666 423 Email: jacni@jacni.com 424 Shishio Tsuchiya (editor) 425 Cisco Systems 426 Midtown Tower, 9-7-1, Akasaka 427 Minato-Ku, Tokyo 107-6227 428 Japan 430 Phone: +81 3 6434 6543 431 Email: shtsuchi@cisco.com