idnits 2.17.1 draft-ietf-softwire-mesh-mib-02.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 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([RFC5565]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 24, 2013) is 4078 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) == Missing Reference: 'RFC2863' is mentioned on line 226, but not defined == Missing Reference: 'RFC4087' is mentioned on line 194, but not defined == Missing Reference: 'RFC4001' is mentioned on line 227, but not defined == Unused Reference: 'RFC2223' is defined on line 563, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 571, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 574, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 4925 ** Obsolete normative reference: RFC 5512 (Obsoleted by RFC 9012) -- Obsolete informational reference (is this intentional?): RFC 2223 (Obsoleted by RFC 7322) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 4 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Softwire Y. Cui 3 Internet-Draft J. Dong 4 Intended status: Standards Track P. Wu 5 Expires: August 28, 2013 M. Xu 6 Tsinghua University 7 February 24, 2013 9 Softwire Mesh Management Information Base (MIB) 10 draft-ietf-softwire-mesh-mib-02 12 Abstract 14 This memo defines a portion of the Management Information Base (MIB) 15 for use with network management protocols in the Internet community. 16 In particular it defines objects for managing softwire mesh 17 [RFC5565]. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 28, 2013. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 This document may contain material from IETF Documents or IETF 52 Contributions published or made publicly available before November 53 10, 2008. The person(s) controlling the copyright in some of this 54 material may not have granted the IETF Trust the right to allow 55 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 2. The Internet-Standard Management Framework . . . . . . . . . . 3 67 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 70 5.1. The swmSupportedTunnlTable Subtree . . . . . . . . . . . . 3 71 5.2. The swmEncapsTable Subtree . . . . . . . . . . . . . . . . 4 72 5.3. The swmBGPNeighborTable Subtree . . . . . . . . . . . . . 4 73 5.4. The swmMIBConformance Subtree . . . . . . . . . . . . . . 4 74 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4 75 6.1. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 4 76 6.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . 5 77 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 78 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 79 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 80 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 81 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 82 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 83 11.1. Normative References . . . . . . . . . . . . . . . . . . . 12 84 11.2. Informative References . . . . . . . . . . . . . . . . . . 12 85 11.3. URL References . . . . . . . . . . . . . . . . . . . . . . 13 87 1. Introduction 89 Softwire mesh framework RFC 5565 [RFC5565] is a tunneling mechanism 90 which enables connectivity between islands of IPv4 networks across 91 single IPv6 backbone and vice versa. In softwire mesh, extended 92 multiprotocol-BGP (MP-BGP)is used to set up tunnels and advertise 93 prefixes among address family border routers (AFBRs). 95 This memo defines a portion of the Management Information Base (MIB) 96 for use with network management protocols in the Internet community. 97 In particular it defines objects for managing softwire mesh 98 [RFC5565]. 100 2. The Internet-Standard Management Framework 102 For a detailed overview of the documents that describe the current 103 Internet-Standard Management Framework, please refer to section 7 of 104 RFC 3410 [RFC3410]. 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. MIB objects are generally 108 accessed through the Simple Network Management Protocol (SNMP). They 109 are defined using the mechanisms stated in the Structure of 110 Management Information (SMI). This memo specifies a MIB module that 111 is compliant to the SMIv2, which is described in STD 58, RFC 2578 112 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 114 3. Terminology 116 This document uses terminology from softwire problem statement RFC 117 4925 [RFC4925] and softwire mesh framework RFC5565 [RFC5565]. 119 4. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 5. Structure of the MIB Module 127 The softwire mesh MIB provides a method to configure and manage the 128 softwire mesh objects through SNMP. 130 5.1. The swmSupportedTunnlTable Subtree 132 Since AFBR need to negotiate with BGP peer what kind of tunnel they 133 will use, it should firstly announce the types of tunnels it 134 supports. The swmSupportedTunnlTable subtree provides the 135 information. According to section 4 of RFC 5512[RFC5512], current 136 softwire mesh tunnel types include IP-IP, GRE and L2TPv3. 138 5.2. The swmEncapsTable Subtree 140 The swmEncapsTable subtree provides softwire mesh NLRI-NH information 141 about the AFBR. It keeps the mapping between E-IP prefix and I-IP 142 address of next hop. The mappings determine which I-IP destination 143 address will be used to encapsulate the received packet's according 144 to its E-IP destination address. The definitions of E-IP and I-IP 145 are explained in section 4.1 of RFC 5565[RFC5565]. 147 5.3. The swmBGPNeighborTable Subtree 149 The subtree provides softwire mesh BGP neighbor information of an 150 AFBR. It includes the address of the softwire mesh BGP peer, and the 151 kind of tunnel that the AFBR would use to communicate with this BGP 152 peer. 154 5.4. The swmMIBConformance Subtree 156 The subtree provides conformance information of MIB objects. 158 6. Relationship to Other MIB Modules 160 6.1. Relationship to the IF-MIB 162 The Interfaces MIB [RFC2863] defines generic managed objects for 163 managing interfaces. Each logical interface (physical or virtual) 164 has an ifEntry. Tunnels are handled by creating logical interfaces 165 (ifEntry). Being a tunnel, softwire mesh has an entry in the 166 Interface MIB, as well as an entry in IP Tunnel MIB. Those 167 corresponding entries are indexed by ifIndex. 169 The ifOperStatus in the ifTable would be used to represents whether 170 the mesh function of the AFBR has been triggered. If the software 171 mesh capability is negotiated during the BGP OPEN phase, the mesh 172 function is considered to be started, and the ifOperStatus is "up". 173 Otherwise the ifOperStatus is "down". 175 In the case of IPv4-over-IPv6 softwire mesh tunnel, the ifInUcastPkts 176 counts the number of IPv6 packets which are sent to the virtual 177 interface for decapsulation into IPv4. The ifOutUcastPkts counts the 178 number of IPv6 packets which are generated by encapsulating IPv4 179 packets sent to the virtual interface. Particularly, if these IPv4 180 packets need fragmentation, ifOutUcastPkts counts the number of 181 packets after fragmentation. 183 In the case of IPv6-over-IPv4 softwire mesh tunnel, the ifInUcastPkts 184 counts the number of IPv4 packets, which are sent to the virtual 185 interface for decapsulation into IPv6. The ifOutUcastPkts counts the 186 number of IPv4 packets, which are generated by encapsulating IPv6 187 packets sent to the virtual interface. Particularly, if these IPv6 188 packets need to be fragmented, tifOutUcastPkts counts the number of 189 packets after fragmentation. Similar definition apply to other 190 counting objects in ifTable. 192 6.2. Relationship to the IP Tunnel MIB 194 The IP Tunnel MIB [RFC4087] contains objects applicable to all IP 195 tunnels, including softwire mesh. On the other hand, Softwire Mesh 196 MIB extends the IP tunnel MIB to further describe encapsulation- 197 specific information. 199 Running a point to multi-point tunnel, it is necessary for a softwire 200 mesh AFBR to maintain an encapsulation table, used to perform correct 201 "forwarding" among AFBRs. This forwarding on an AFBR is performed by 202 using the E-IP destination address to look up the I-IP encapsulation 203 destination address in the encapsulation table. An AFBR also needs 204 to know the BGP peer information of the other AFBRs, so that it can 205 negotiate the NLRI-NH information and the tunnel parameters with 206 them. 208 Softwire mesh requires the implmentation of the IP Tunnel MIB. The 209 tunnelIfEncapsMethod in the tunnelIfEntry should be set to 210 softwireMesh("xx"), and corresponding entry in the softwire mesh MIB 211 module will exist for this tunnelIfEntry. The 212 tunnelIfRemoteInetAddress must be set to 0.0.0.0 for IPv4 or :: for 213 IPv6 because it is a point to multi-point tunnel. 215 Since tunnelIfAddressType in tunnelIfTable represents the type of 216 address in the corresponding tunnelIfLocalInetAddress and 217 tunnelIfRemoteInetAddress objects, we can use this semantic to 218 specify the type of the softwire mesh, which is either IPv4-over-IPv6 219 or IPv6-over-IPv4. When tunnelIfAddressType is IPv4, the mesh is 220 IPv6-over-IPv4; When tunnelIfAddressType is IPv6, the encapsulation 221 would be IPv4-over-IPv6. 223 6.3. MIB modules required for IMPORTS 225 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 226 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and 227 INET-ADDRESS-MIB [RFC4001]. 229 7. Definitions 230 SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN 232 IMPORTS 233 MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI 235 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF 237 InetAddress, InetAddressPrefixLength FROM INET-ADDRESS-MIB 239 ifIndex FROM IF-MIB 241 IANAtunnelType FROM IANAifType-MIB; 243 swmMIB MODULE-IDENTITY 244 LAST-UPDATED "201302180000Z" -- February 18, 2013 245 ORGANIZATION "Softwire Working Group" 246 CONTACT-INFO " 248 Yong Cui 249 Email: yong@csnet1.cs.tsinghua.edu.cn 251 Jiang Dong 252 Email: dongjiang@csnet1.cs.tsinghua.edu.cn 254 Peng Wu 255 Email: weapon@csnet1.cs.tsinghua.edu.cn 257 Mingwei Xu 258 Email: xmw@cernet.edu.cn 260 Email comments directly to the softwire WG Mailing 261 List at softwires@ietf.org 262 " 264 DESCRIPTION 265 "This MIB module contains managed object definitions for 266 the softwire mesh framework." 268 REVISION "201302180000Z" 269 DESCRIPTION 270 "The MIB module is defined for management of object in 271 the Softwire mesh framework." 272 ::= { transmission 999 } --999 to be replaced with correct value 274 swmMIBObjects OBJECT IDENTIFIER ::= { swmMIB 1 } 276 -- swmSupportedTunnelTable 277 swmSupportedTunnelTable OBJECT-TYPE 278 SYNTAX SEQUENCE OF SwmSupportedTunnelEntry 279 MAX-ACCESS not-accessible 280 STATUS current 281 DESCRIPTION 282 "A table of objects that shows what kind of tunnels 283 can be supported by the AFBR." 284 ::= { swmMIBObjects 1 } 286 swmSupportedTunnelEntry OBJECT-TYPE 287 SYNTAX SwmSupportedTunnelEntry 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "A set of objects that shows what kind of tunnels 292 can be supported in the AFBR. If the AFBR supports 293 multiple tunnel types, the swmSupportedTunnelTalbe 294 would have several entries." 295 INDEX { swmSupportedTunnelType } 296 ::= { swmSupportedTunnelTable 1 } 298 SwmSupportedTunnelEntry ::= SEQUENCE { 299 swmSupportedTunnelType IANAtunnelType 300 } 302 swmSupportedTunnelType OBJECT-TYPE 303 SYNTAX IANAtunnelType 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "Represents the tunnel type that the AFBR support. " 308 ::= { swmSupportedTunnelEntry 1 } 309 -- end of swmSupportedTunnelTable 311 --swmEncapsTable 312 swmEncapsTable OBJECT-TYPE 313 SYNTAX SEQUENCE OF SwmEncapsEntry 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "A table of objects that display and control the 318 softwire mesh encapsulation information." 319 ::= { swmMIBObjects 2 } 321 swmEncapsEntry OBJECT-TYPE 322 SYNTAX SwmEncapsEntry 323 MAX-ACCESS not-accessible 324 STATUS current 325 DESCRIPTION 326 "A table of objects that manages the softwire mesh I-IP 327 encapsulation destination based on the E-IP destination prefix." 328 INDEX { ifIndex, 329 swmEncapsEIPDst, 330 swmEncapsEIPMask 331 } 332 ::= { swmEncapsTable 1 } 334 SwmEncapsEntry ::= SEQUENCE { 335 swmEncapsEIPDst InetAddress, 336 swmEncapsEIPMask InetAddressPrefixLength, 337 swmEncapsIIPDst InetAddress 338 } 340 swmEncapsEIPDst OBJECT-TYPE 341 SYNTAX InetAddress 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The address of the destination prefix, which is 346 used for I-IP encapsulation destination lookup 347 based on longest prefix match. The address type is 348 opposite to tunnelIfAddressType in tunnelIfTable." 349 ::= { swmEncapsEntry 1 } 351 swmEncapsEIPMask OBJECT-TYPE 352 SYNTAX InetAddressPrefixLength 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The prefix length of E-IP address." 357 ::= { swmEncapsEntry 2 } 359 swmEncapsIIPDst OBJECT-TYPE 360 SYNTAX InetAddress 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The I-IP address as the encapsulated destination 365 according to the E-IP address. The address type 366 is the same as tunnelIfAddressType in tunnelIfTable. 367 Since the tunnelIfRemoteInetAddress in tunnelIfTable 368 should be 0.0.0.0 or ::, swmEncapIIPDst is the 369 destination address used in the outer IP header." 370 ::= { swmEncapsEntry 3 } 371 -- End of swmEncapsTable 373 -- swmBGPNeighborTable 374 swmBGPNeighborTable OBJECT-TYPE 375 SYNTAX SEQUENCE OF SwmBGPNeighborEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "A table of objects that displays the softwire mesh 380 BGP neighbor information." 381 ::= { swmMIBObjects 3 } 383 swmBGPNeighborEntry OBJECT-TYPE 384 SYNTAX SwmBGPNeighborEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "A set of objects that displays the softwire mesh 389 BGP neighbor information." 390 INDEX { 391 ifIndex, 392 swmBGPNeighborInetAddress 393 } 394 ::= { swmBGPNeighborTable 1 } 396 SwmBGPNeighborEntry ::= SEQUENCE { 397 swmBGPNeighborInetAddress InetAddress, 398 swmBGPNeighborTunnelType IANAtunnelType 399 } 401 swmBGPNeighborInetAddress OBJECT-TYPE 402 SYNTAX InetAddress 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "The address of the ABFR's BGP neighbor. The 407 address type is the same as tunnelIfAddressType 408 in tunnelIfTable" 409 ::= { swmBGPNeighborEntry 1 } 411 swmBGPNeighborTunnelType OBJECT-TYPE 412 SYNTAX IANAtunnelType 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "Represents the type of tunnel that the 417 AFBR chooses to transmit traffic with another AFBR/BGP neighbor" 418 ::= { swmBGPNeighborEntry 2 } 419 -- End of swmBGPNeighborTable 421 -- conformance information 422 swmMIBConformance 423 OBJECT IDENTIFIER ::= { swmMIB 2 } 424 swmMIBCompliances 425 OBJECT IDENTIFIER ::= { swmMIBConformance 1 } 426 swmMIBGroups 427 OBJECT IDENTIFIER ::= { swmMIBConformance 2 } 429 -- compliance statements 430 swmMIBCompliance MODULE-COMPLIANCE 431 STATUS current 432 DESCRIPTION 433 "Describes the requirements for conformance to the softwire 434 mesh MIB." 436 MODULE -- this module 437 MANDATORY-GROUPS { 438 swmSupportedTunnelGroup, 439 swmEncapsGroup, 440 swmBGPNeighborGroup 441 } 442 ::= { swmMIBCompliances 1 } 444 swmSupportedTunnelGroup OBJECT-GROUP 445 OBJECTS { 446 swmSupportedTunnelType 447 } 448 STATUS current 449 DESCRIPTION 450 "The collection of objects which are used to show 451 what kind of tunnel the AFBR supports." 452 ::= { swmMIBGroups 1 } 454 swmEncapsGroup OBJECT-GROUP 455 OBJECTS { 456 swmEncapsEIPDst, 457 swmEncapsEIPMask, 458 swmEncapsIIPDst 459 } 460 STATUS current 461 DESCRIPTION 462 "The collection of objects which are used to display 463 softwire mesh encapsulation information." 464 ::= { swmMIBGroups 2 } 466 swmBGPNeighborGroup OBJECT-GROUP 467 OBJECTS { 468 swmBGPNeighborInetAddress, 469 swmBGPNeighborTunnelType 471 } 472 STATUS current 473 DESCRIPTION 474 "The collection of objects which are used to display 475 softwire mesh BGP neighbor information." 476 ::= { swmMIBGroups 3 } 478 END 480 8. Security Considerations 482 The swmMIB module can be used for configuration of certain objects, 483 and anything that can be configured can be incorrectly configured, 484 with potentially disastrous results. Because this MIB module reuses 485 the IP tunnel MIB, the security considerations of the IP tunnel MIB 486 is also applicable to the Softwire mesh MIB. 488 SNMP versions prior to SNMPv3 did not include adequate security. 489 Even if the network itself is secure (for example by using IPsec), 490 even then, there is no control as to who on the secure network is 491 allowed to access and GET/SET (read/change/create/delete) the objects 492 in this MIB module. 494 It is RECOMMENDED that implementers consider the security features as 495 provided by the SNMPv3 framework (see [RFC3410], section 8), 496 including full support for the SNMPv3 cryptographic mechanisms (for 497 authentication and privacy). 499 Further, deployment of SNMP versions prior to SNMPv3 is NOT 500 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 501 enable cryptographic security. It is then a customer/operator's 502 responsibility to ensure that the SNMP entity giving access to an 503 instance of this MIB module is properly configured to give access to 504 the objects only to those principals (users) that have legitimate 505 rights to indeed GET or SET (change/create/delete) them. 507 9. IANA Considerations 509 The MIB module in this document uses the following IANA-assigned 510 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 511 the following IANA-assigned tunnelType values recorded in the 512 IANAtunnelType-MIB registry: 514 Descriptor OBJECT IDENTIFIER value 515 ---------- ----------------------- 516 swmMIB { transmission XXX } 518 IANAtunnelType ::= TEXTUAL-CONVENTION 519 SYNTAX INTEGER { 521 softwireMesh ("XX") -- softwire Mesh tunnel 523 } 525 10. Acknowledgements 527 The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi 528 Sun, Sheng Jiang, Yu Fu for their valuable comments. 530 11. References 532 11.1. Normative References 534 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 535 Requirement Levels", BCP 14, RFC 2119, March 1997. 537 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 538 Schoenwaelder, Ed., "Structure of Management 539 Information Version 2 (SMIv2)", STD 58, RFC 2578, 540 April 1999. 542 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 543 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 544 STD 58, RFC 2579, April 1999. 546 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 547 "Conformance Statements for SMIv2", STD 58, RFC 2580, 548 April 1999. 550 [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, 551 "Softwire Problem Statement", RFC 4925, July 2007. 553 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 554 Subsequent Address Family Identifier (SAFI) and the 555 BGP Tunnel Encapsulation Attribute", RFC 5512, 556 April 2009. 558 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire 559 Mesh Framework", RFC 5565, June 2009. 561 11.2. Informative References 563 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC 564 Authors", RFC 2223, October 1997. 566 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 567 "Introduction and Applicability Statements for 568 Internet-Standard Management Framework", RFC 3410, 569 December 2002. 571 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", 572 RFC 2629, June 1999. 574 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of 575 MIB Documents", BCP 111, RFC 4181, September 2005. 577 11.3. URL References 579 [idguidelines] IETF Internet Drafts editor, 580 "http://www.ietf.org/ietf/1id-guidelines.txt". 582 [idnits] IETF Internet Drafts editor, 583 "http://www.ietf.org/ID-Checklist.html". 585 [xml2rfc] XML2RFC tools and documentation, 586 "http://xml.resource.org". 588 [ops] the IETF OPS Area, "http://www.ops.ietf.org". 590 [ietf] IETF Tools Team, "http://tools.ietf.org". 592 Authors' Addresses 594 Yong Cui 595 Tsinghua University 596 Department of Computer Science, Tsinghua University 597 Beijing 100084 598 P.R.China 600 Phone: +86-10-6260-3059 601 EMail: yong@csnet1.cs.tsinghua.edu.cn 603 Jiang Dong 604 Tsinghua University 605 Department of Computer Science, Tsinghua University 606 Beijing 100084 607 P.R.China 609 Phone: +86-10-6278-5822 610 EMail: dongjiang@csnet1.cs.tsinghua.edu.cn 611 Peng Wu 612 Tsinghua University 613 Department of Computer Science, Tsinghua University 614 Beijing 100084 615 P.R.China 617 Phone: +86-10-6278-5822 618 EMail: weapon@csnet1.cs.tsinghua.edu.cn 620 Mingwei Xu 621 Tsinghua University 622 Department of Computer Science, Tsinghua University 623 Beijing 100084 624 P.R.China 626 Phone: +86-10-6278-5822 627 EMail: xmw@cernet.edu.cn