idnits 2.17.1 draft-fu-softwire-dslite-mib-00.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 (May 4, 2011) is 4740 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) ** Obsolete normative reference: RFC 4008 (Obsoleted by RFC 7658) == Outdated reference: A later version (-11) exists of draft-ietf-softwire-dual-stack-lite-08 Summary: 1 error (**), 0 flaws (~~), 3 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 Sh. Jiang 3 Intended status: Standards Track Huawei Technologies Co., Ltd 4 Expires: November 4, 2011 Y. Cui 5 J.Dong 6 Tsinghua University 7 May 4, 2011 9 DS-Lite Management Information Base (MIB) 10 draft-fu-softwire-dslite-mib-00 12 Status of this Memo 14 This Internet-Draft is submitted in full conformance with the 15 provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF). Note that other groups may also distribute working 19 documents as Internet-Drafts. The list of current Internet-Drafts is 20 at http://datatracker.ietf.org/drafts/current/. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 This Internet-Draft will expire on October 27, 2011. 29 Copyright Notice 31 Copyright (c) 2011 IETF Trust and the persons identified as the 32 document authors. All rights reserved. 34 This document is subject to BCP 78 and the IETF Trust's Legal 35 Provisions Relating to IETF Documents 36 (http://trustee.ietf.org/license-info) in effect on the date of 37 publication of this document. Please review these documents 38 carefully, as they describe your rights and restrictions with respect 39 to this document. Code Components extracted from this document must 40 include Simplified BSD License text as described in Section 4.e of 41 the Trust Legal Provisions and are provided without warranty as 42 described in the Simplified BSD License. 44 Abstract 46 This memo defines a portion of the Management Information Base (MIB) 47 for use with network management protocols in the Internet community. 48 In particular, it defines managed objects for DS-Lite. 50 Table of Contents 52 1. Introduction ..................................................3 53 2. The Internet-Standard Management Framework ....................3 54 3. Terminology ...................................................3 55 4. Difference from the IP tunnel MIB and NAT MIB .................3 56 5. Structure of the MIB Module....................................4 57 5.1. The DSliteMIBTunnel Subtree...............................4 58 5.2. The DSliteMIBNAT Subtree..................................4 59 5.3. The DSliteMIBRelationInfo Subtree ........................4 60 5.4. The DSliteMIBConformance Subtree .........................5 61 6. MIB modules required for IMPORTS...............................5 62 7. Definitions ...................................................5 63 8. IANA Considerations ..........................................12 64 9. Security Considerations.......................................12 65 10. References ..................................................13 66 10.1. Normative References....................................13 67 10.2. Informative References..................................14 68 11. Change Log [RFC Editor please remove] .......................14 69 Author's Addresses ..............................................14 71 1. Introduction 73 Dual-Stack Lite [I-D.ietf-softwire-dual-stack-lite] is a solution to 74 offer both IPv4 and IPv6 connectivity to customers crossing IPv6 only 75 infrastructure. One of its key components is an IPv4-over-IPv6 76 tunnel, which is used to provide IPv4 connection across service 77 provider IPv6 network. Another key component is a carrier-grade 78 IPv4-IPv4 NAT to share service provider IPv4 addresses among 79 customers. 81 This document defines a portion of the Management Information Base 82 (MIB) for use with network management protocols in the Internet 83 community. This MIB module may be used for configuration and 84 monitoring the devices in the Dual-Stack Lite scenario. 86 2. The Internet-Standard Management Framework 88 For a detailed overview of the documents that describe the current 89 Internet-Standard Management Framework, please refer to section 7 of 90 [RFC3410]. 92 Managed objects are accessed via a virtual information store, termed 93 the MIB. MIB objects are generally accessed through the Simple 94 Network Management Protocol (SNMP). 96 Objects in the MIB are defined using the mechanisms defined in the 97 Structure of Management Information (SMI). This memo specifies a MIB 98 module that is compliant to the SMIv2, which is described in 99 [RFC2578], [RFC2579] and [RFC2580]. 101 3. Terminology 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 4. Difference from the IP tunnel MIB and NAT MIB 109 The key technologies for DS-Lite are IP in IP (IPv4-in-IPv6) tunnel 110 and NAT (IPv4 to IPv4 translation). 112 The NAT-MIB [RFC4008] is designed to carry translation from any 113 address family to any address family, therefore supports IPv4 to IPv4 114 translation. 116 The tunnel MIB [RFC4087] is designed for managing tunnels of any type 117 over IPv4 and IPv6 networks, therefore supports IP in IP tunnels. 119 However, NAT MIB and tunnel MIB together are not sufficient to 120 support DS-Lite. This document describes the specific MIB 121 requirements for DS-Lite, as below. 123 In DS-Lite scenario, the tunnel type is IP in IP, more 124 precisely, is IPv4 in IPv6. Therefore, it is unnecessary to 125 describe tunnel type in DS-Lite MIB. 127 In DS-Lite scenario, the translation type is IPv4 private 128 address to IPv4 public address. Therefore, it is unnecessary to 129 describe the type of address in the corresponding 130 tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects 131 in DS-Lite MIB. 133 In DS-lite scenario, the AFTR is not only the tunnel end 134 concentrator, but also a 4-4 translator. Within the AFTR, 135 tunnel information and translation information MUST be mapped 136 each other. Two independent MIB is not able to reflect this 137 mapping relationship. Therefore, a combined MIB is necessary. 139 5. Structure of the MIB Module 141 The DS-Lite MIB provides a way to configure and manage the devices in 142 DS-Lite scenario through SNMP. 144 DS-Lite MIB is configurable on a per-interface basis. It depends on 145 several parts of the IF-MIB [RFC2863], tunnel MIB [RFC4087], and NAT 146 MIB [RFC4008]. 148 5.1. The DSliteMIBTunnel Subtree 150 The DSliteMIBTunnel subtree describes managed objects used for 151 managing tunnels in the DS-Lite scenario. Because the tunnel MIB 152 supports the tunnel management function in DS-Lite, we may reuse it 153 in DS-Lite MIB. 155 5.2. The DSliteMIBNAT Subtree 157 The DSliteMIBNAT Subtree describes managed objects used for 158 configuration as well as monitoring of AFTR which is capable of NAT 159 function. Because the NAT MIB supports the NAT management function in 160 DS-Lite, we MAY reuse it in DS-Lite MIB. 162 5.3. The DSliteMIBRelationInfo Subtree 164 The DSliteMIBRelationInfo Subtree provides the information of mapping 165 relationship between the tunnel MIB and NAT MIB. It is vital 166 information for DS-Lite implementer. It also includes information 167 about traffic statistics. 169 5.4. The DSliteMIBConformance Subtree 171 The Subtree provides conformance information of MIB objects. 173 6. MIB modules required for IMPORTS 175 This MIB module IMPORTs objects from [RFC4087], [RFC4008], [RFC2580], 176 [RFC2578], [RFC2863], [RFC4001],[RFC3411]. 178 Notes: The IF-MIB defines the MTU for the interface which includes 179 the virtual interface of the tunnel, so DS-Lite MIB does not need to 180 define the MTU for tunnel. 182 7. Definitions 184 DSLite-MIB DEFFINITIONS ::= BEGIN 186 IMPORTS 187 MODULE-IDENTITY, OBJECT-TYPE, mib-2, transmission, 188 Gauge32 189 FROM SNMPv2-SMI 191 ifIndex 192 FROM IF-MIB 194 InetAddress, InetPortNumber 195 FROM INET-ADDRESS-MIB 197 tunnelMIB 198 FROM tunnelMIB 200 natMIB 201 FROM natMIB 203 DSliteMIB MODULE-IDENTITY 204 LAST-UPDATED "201104260000Z" -- April 26, 2011 205 ORGANIZATION "IETF Softwire Working Group" 206 CONTACT-INFO 207 "Yu Fu 208 Huawei Technologies Co., Ltd 209 Huawei Building, No.3 Xinxi Rd, Hai-Dian District 210 Beijing, P.R. China 100085 211 EMail: fy@huawei.com 212 Sheng Jiang 213 Huawei Technologies Co., Ltd 214 Huawei Building, No.3 Xinxi Rd, Hai-Dian District 215 Beijing, P.R. China 100085 216 EMail: jiangsheng@huawei.com 218 Yong Cui 219 Tsinghua University 220 Department of Computer Science, Tsinghua University 221 Beijing 100084 222 P.R. China 223 Email: yong@csnet1.cs.tsinghua.edu.cn 225 Jiang Dong 226 Tsinghua University 227 Department of Computer Science, Tsinghua University 228 Beijing 100084 229 P.R. China 230 Email: dongjiang@csnet1.cs.tsinghua.edu.cn" 232 DESCRIPTION 233 "The MIB module is defined for management of object in the 234 DS-Lite scenario. " 235 ::= { transmission xxx } --xxx to be replaced with correct 236 value 238 DSLiteMIBRelationInfo OBJECT IDENTIFIER 239 :: = { DSLiteMIB 1 } 241 --Conformance 242 DSLiteMIBConformance OBJECT IDENTIFIER 243 :: = { DSLiteMIB 2 } 245 --DSLiteMIBRelationInfo 246 --DSLiteMIBBindRelationTable Table 247 --DSLiteMIBPortBindRelationTable Table 249 DSLiteMIBBindRelationTable OBJECT-TYPE 250 SYNTAX SEQUENCE OF DSLiteMIBBindRelationEntry 251 MAX-ACCESS not-accessible 252 STATUS current 253 DESCRIPTION 254 "The (conceptual) table containing mapping information 255 between tunnel information and currently active NAT BINDs 256 This table can be used to map the tunnel initiator to 257 natAddrBindEntry." 258 :: = { DSLiteMIBRelationInfo 1 } 260 DSLiteMIBBindRelationEntry OBJECT-TYPE 261 SYNTAX DSLiteMIBBindRelationEntry 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "Each entry in this table holds the relationship between 266 tunnel information and nat bind information. These entries 267 are lost upon agent restart." 268 INDEX { ifIndex, 269 natAddrBindLocalAddr, 270 tunnelIfLocalAddress } 271 :: = { DSLiteMIBBindRelationTable 1 } 273 DSLiteMIBBindRelationEntry :: = 274 SEQUENCE { 275 NatAddrBindEntry NatAddrBindEntry, 276 tunnelIfLocalAddress IpAddress, 277 DSLiteMIBBindNumberOfTunnel Gauge32, 278 DSLiteMIBBindInIPv6Packets Counter32, 279 DSLiteMIBBindOutIPv6Packets Counter32, 280 DSLiteMIBBindOutIPv4Packets Counter32, 281 DSLiteMIBBindInIPv6Bytes Counter64, 282 DSLiteMIBBindOutIPv4Bytes Counter64, 283 DSLiteMIBBindOutIPv6Bytes Counter64 284 } 286 DSLiteMIBBindNumberOfTunnel OBJECT-TYPE 287 SYNTAX Gauge32 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "This object maintains a count of the number of tunnels 292 that currently exist with the same endpoint, AFTR." 293 ::= { DSLiteMIBBindRelationEntry 3 } 295 DSLiteMIBBindInIPv6Packets OBJECT-TYPE 296 SYNTAX Counter32 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "This object represents number of IPv6 Packets received by 301 the AFTR. These IPv6 packets includes native IPv6 packets 302 and IPv6 packets encapsulated from IPv4 packets send by the 303 tunnel initiator." 304 ::= { DSLiteMIBBindRelationEntry 4 } 306 DSLiteMIBBindOutIPv6Packets OBJECT-TYPE 307 SYNTAX Counter32 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "This object represents number of IPv6 Packets forwarded by 312 the AFTR. These IPv6 packets are native IPv6 packets 313 received in AFTR." 314 ::= { DSLiteMIBBindRelationEntry 5 } 316 DSLiteMIBBindOutIPv4Packets OBJECT-TYPE 317 SYNTAX Counter32 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "This object represents number of IPv4 Packets sent by 322 the AFTR. These IPv4 packets are decapsulated packets from 323 encapsulated IPv6 packets." 324 ::= { DSLiteMIBBindRelationEntry 6 } 326 DSLiteMIBBindInIPv6Bytes OBJECT-TYPE 327 SYNTAX Counter64 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "This object represents number of IPv6 Bytes forwarded by 332 the AFTR." 333 ::= { DSLiteMIBBindRelationEntry 7 } 335 DSLiteMIBBindOutIPv6Bytes OBJECT-TYPE 336 SYNTAX Counter64 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 "This object represents number of IPv6 Bytes received by 341 AFTR." 342 ::= { DSLiteMIBBindRelationEntry 8 } 344 DSLiteMIBBindOutIPv4Bytes OBJECT-TYPE 345 SYNTAX Counter64 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "This object represents number of IPv4 Bytes sent by 350 AFTR." 351 ::= { DSLiteMIBBindRelationEntry 9 } 353 DSLiteMIBPortBindRelationTable OBJECT-TYPE 354 SYNTAX SEQUENCE OF DSLiteMIBPortBindRelationEntry 355 MAX-ACCESS not-accessible 356 STATUS current 357 DESCRIPTION 358 "The (conceptual) table containing mapping information 359 between tunnel information and currently active NAPT BINDs 360 This table can be used to map the tunnel initiator to 361 natAddrPortBindEntry. " 362 :: = { DSLiteMIBRelationInfo 2 } 364 DSLiteMIBPortBindRelationEntry OBJECT-TYPE 365 SYNTAX DSLiteMIBPortBindRelationEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "Each entry in this table holds the relationship between 370 tunnel information and nat bind information. These entries 371 are lost upon agent restart." 372 INDEX { ifIndex, 373 natAddrPortBindLocalAddr, 374 natAddrPortBindLocalPort, 375 tunnelIfLocalAddress } 376 :: = { DSLiteMIBPortBindRelationTable 1 } 378 DSLiteMIBPortBindRelationEntry :: = 379 SEQUENCE { 380 natAddrPortBindEntry natAddrPortBindEntry, 381 tunnelIfLocalAddress IpAddress, 382 DSLiteMIBPortBindNumberOfTunnel Gauge32, 383 DSLiteMIBPortBindInIPv6Packets Counter32, 384 DSLiteMIBPortBindOutIPv6Packets Counter32, 385 DSLiteMIBPortBindOutIPv4Packets Counter32, 386 DSLiteMIBPortBindInIPv6Bytes Counter64, 387 DSLiteMIBPortBindOutIPv4Bytes Counter64, 388 DSLiteMIBPortBindOutIPv6Bytes Counter64 389 } 391 DSLiteMIBPortBindNumberOfTunnel OBJECT-TYPE 392 SYNTAX Gauge32 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "This object maintains a count of the number of tunnels 397 that currently exist with the same endpoint, AFTR." 398 ::= { DSLiteMIBPortBindRelationEntry 3 } 400 DSLiteMIBPortBindInIPv6Packets OBJECT-TYPE 401 SYNTAX Counter32 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "This object represents number of IPv6 Packets received by 406 the virtual interface of AFTR. These IPv6 packets includes 407 native IPv6 packets and IPv6 packets encapsulated from IPv4 408 packets send by the tunnel initiator." 409 ::= { DSLiteMIBPortBindRelationEntry 4 } 411 DSLiteMIBPortBindOutIPv6Packets OBJECT-TYPE 412 SYNTAX Counter32 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "This object represents number of IPv6 Packets forwarded by 417 the AFTR. These IPv6 packets are native IPv6 packets 418 received in AFTR." 419 ::= { DSLiteMIBPortBindRelationEntry 5 } 421 DSLiteMIBPortBindOutIPv4Packets OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "This object represents number of IPv4 Packets sent by 427 the AFTR. These IPv4 packets are decapsulated packets from 428 encapsulated IPv6 packets." 429 ::= { DSLiteMIBPortBindRelationEntry 6 } 431 DSLiteMIBPortBindInIPv6Bytes OBJECT-TYPE 432 SYNTAX Counter64 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "This object represents number of IPv6 Bytes forwarded by 437 the AFTR." 438 ::= { DSLiteMIBPortBindRelationEntry 7 } 440 DSLiteMIBPortBindOutIPv6Bytes OBJECT-TYPE 441 SYNTAX Counter64 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "This object represents number of IPv6 Bytes received by 446 the virtual interface of AFTR." 447 ::= { DSLiteMIBPortBindRelationEntry 8 } 449 DSLiteMIBPortBindOutIPv4Bytes OBJECT-TYPE 450 SYNTAX Counter64 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "This object represents number of IPv4 Bytes sent by 455 the AFTR." 456 ::= { DSLiteMIBPortBindRelationEntry 9 } 458 --Module Conformance statement 460 DSLiteMIBGroups OBJECT IDENTIFIER 461 :: = { DSLiteMIBConformance 1 } 463 DSLiteMIBCompliances OBJECT IDENTIFIER 464 :: = { DSLiteMIBConformance 2 } 466 DSLiteMIBCompliance MODULE-COMPLIANCE 467 STATUS current 468 DESCRIPTION 469 "Description of the requirements for conformance to the 470 DS-Lite MIB the AFTR." 472 MODULE - this module 473 MANDATORY - GROUPS { DSLiteMIBRelationInfoGroup } 474 :: = { DSLiteMIBCompliances 1 } 476 DSLiteMIBRelationInfoGroup OBJECT-GROUP 477 OBJECTS { 478 NatAddrBindEntry NatAddrBindEntry, 479 tunnelIfLocalAddress IpAddress, 480 DSLiteMIBBindNumberOfTunnel Gauge32, 481 DSLiteMIBBindInIPv6Packets Counter32, 482 DSLiteMIBBindOutIPv6Packets Counter32, 483 DSLiteMIBBindOutIPv4Packets Counter32, 484 DSLiteMIBBindInIPv6Bytes Counter64, 485 DSLiteMIBBindOutIPv4Bytes Counter64, 486 DSLiteMIBBindOutIPv6Bytes Counter64, 487 natAddrPortBindEntry natAddrPortBindEntry, 488 DSLiteMIBPortBindNumberOfTunnel Gauge32, 489 DSLiteMIBPortBindInIPv6Packets Counter32, 490 DSLiteMIBPortBindOutIPv6Packets Counter32, 491 DSLiteMIBPortBindOutIPv4Packets Counter32, 492 DSLiteMIBPortBindInIPv6Bytes Counter64, 493 DSLiteMIBPortBindOutIPv4Bytes Counter64, 494 DSLiteMIBPortBindOutIPv6Bytes Counter64 495 } 496 STATUS current 497 DESCRIPTION 498 "The collection of objects which are used to represent 499 the mapping information between tunnel information and 500 currently active NAT BINDs of the AFTR." 501 :: = { DSLiteMIBGroup 1 } 503 END 505 8. IANA Considerations 507 The MIB module in this document uses the following IANA-assigned 508 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 510 Descriptor OBJECT IDENTIFIER value 511 ---------- ----------------------- 512 DSLite-MIB { transmission XXX } 514 9. Security Considerations 516 The DS-Lite MIB module can be used for configuration of certain 517 objects, and anything that can be configured can be incorrectly 518 configured, with potentially disastrous results. Because this MIB 519 module reuse the IP tunnel MIB and nat MIB, the security 520 considerations for these MIBs are also applicable to the DS-Lite 521 MIB. 523 Unauthorized read access to tunnelIfLocalAddress, or any object in 524 the DSLiteMIBBindRelationTable or DSLiteMIBPortBindRelationTable 525 would reveal information about the mapping information. 527 SNMP versions prior to SNMPv3 did not include adequate security. 528 Even if the network itself is secure (for example by using IPSec), 529 even then, there is no control as to who on the secure network is 530 allowed to access and GET/SET (read/change/create/delete) the objects 531 in this MIB module. 533 It is RECOMMENDED that implementers consider the security features as 534 provided by the SNMPv3 framework (see [RFC3410], section 8), 535 including full support for the SNMPv3 cryptographic mechanisms (for 536 authentication and privacy). 538 Further, deployment of SNMP versions prior to SNMPv3 is NOT 539 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 540 enable cryptographic security. It is then a customer/operator 541 responsibility to ensure that the SNMP entity giving access to an 542 instance of this MIB module is properly configured to give access to 543 the objects only to those principals (users) that have legitimate 544 rights to indeed GET or SET (change/create/delete) them. 546 10. References 548 10.1. Normative References 550 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 551 Requirement Levels", BCP 14, RFC 2119, March 1997. 553 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 554 "Structure of Management Information Version 2 (SMIv2)", 555 RFC 2578, April 1999. 557 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual 558 Conventions for SMIv2", RFC 2579, April 1999. 560 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 561 "Conformance Statements for SMIv2", RFC 2580, April 1999. 563 [RFC2863] McCloghrie, K. and F. Kastenholz. "The Interfaces Group 564 MIB", RFC 2863, June 2000. 566 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 567 Architecture for Describing Simple Network Management 568 Protocol (SNMP) Management Frameworks", RFC 3411, December 569 2002. 571 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 572 Schoenwaelder, "Textual Conventions for Internet Network 573 Addresses", RFC 4001, February 2005. 575 [RFC4008] Rohit, R., Srisuresh, P., Raghunarayan,R., Pai, N., and 576 Wang, C., "Definitions of Managed Objects for Network 577 Address Translators (NAT)", RFC 4008, March 2005. 579 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. 581 10.2. Informative References 583 [I-D.ietf-softwire-dual-stack-lite] 584 Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 585 Stack Lite Broadband Deployments Following IPv4 586 Exhaustion", draft-ietf-softwire-dual-stack-lite-08 587 (work in progress), August 2010. 589 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 590 "Introduction and Applicability Statements for Internet- 591 Standard Management Framework", RFC 3410, December 2002. 593 11. Change Log [RFC Editor please remove] 595 draft-fu-softwire-dslite-mib-00, original version, 2011-05-04 597 Author's Addresses 599 Yu Fu 600 Huawei Technologies Co., Ltd 601 Huawei Building, No.3 Xinxi Rd., 602 Shang-Di Information Industry Base, Hai-Dian District, Beijing 100085 603 P.R. China 604 Email: fy@huawei.com 606 Sheng Jiang 607 Huawei Technologies Co., Ltd 608 Huawei Building, No.3 Xinxi Rd., 609 Shang-Di Information Industry Base, Hai-Dian District, Beijing 100085 610 P.R. China 611 Email: shengjiang@huawei.com 613 Yong Cui 614 Tsinghua University 615 Department of Computer Science, Tsinghua University 616 Beijing 100084 617 P.R. China 618 Email: yong@csnet1.cs.tsinghua.edu.cn 620 Jiang Dong 621 Tsinghua University 622 Department of Computer Science, Tsinghua University 623 Beijing 100084 624 P.R. China 625 Email: dongjiang@csnet1.cs.tsinghua.edu.cn