idnits 2.17.1 draft-ietf-softwire-mesh-mib-01.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 4 instances of too long lines in the document, the longest one being 8 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 (January 3, 2013) is 4103 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 570, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 578, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 581, 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: July 7, 2013 M. Xu 6 Tsinghua University 7 January 3, 2013 9 Softwire Mesh Management Information Base(MIB) 10 draft-ietf-softwire-mesh-mib-01 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 July 7, 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 . . . . . . . . . . . . . . . . . . 13 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 TruthValue, TEXTUAL-CONVENTION 234 TimeStamp 235 FROM SNMPv2-TC 237 OBJECT-GROUP, MODULE-COMPLIANCE 238 FROM SNMPv2-CONF 240 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Counter32, 241 Counter64 242 FROM SNMPv2-SMI 244 IANAtunnelType FROM IANAifType-MIB; 246 InetAddress, InetAddressPrefixLength 247 FROM INET-ADDRESS-MIB 249 swmMIB MODULE-IDENTITY 250 LAST-UPDATED "201301030000Z" -- January 03, 2013 251 ORGANIZATION "Softwire Working Group" 252 CONTACT-INFO " 254 Yong Cui 255 Email: yong@csnet1.cs.tsinghua.edu.cn 257 Jiang Dong 258 Email: dongjiang@csnet1.cs.tsinghua.edu.cn 260 Peng Wu 261 Email: weapon@csnet1.cs.tsinghua.edu.cn 263 Mingwei Xu 264 Email: xmw@cernet.edu.cn 266 Email comments directly to the softwire WG Mailing 267 List at softwires@ietf.org 268 " 270 DESCRIPTION 271 "This MIB module contains managed object definitions for 272 the softwire mesh framework." 274 REVISION "201301030000Z" 275 DESCRIPTION 276 "The MIB module is defined for management of object in 277 the Softwire mesh framework." 279 ::= {transmission xxx} --xxx to be replaced with correct value 281 -- swmSupportedTunnelTable 282 swmSupportedTunnelTable OBJECT-TYPE 283 SYNTAX SEQUENCE OF swmSupportedTunnelEntry 284 MAX-ACCESS not-accessible 285 STATUS current 286 DESCRIPTION 287 "A table of objects that shows what kind of tunnels 288 can be supported by the AFBR." 289 ::= { swmMIB 1 } 291 swmSupportedTunnelEntry OBJECT-TYPE 292 SYNTAX swmSupportedTunnelEntry 293 MAX-ACCESS not-accessible 294 STATUS current 295 DESCRIPTION 296 "A set of objects that shows what kind of tunnels 297 can be supported in the AFBR. If the AFBR supports 298 multiple tunnel types, the swmSupportedTunnelTalbe 299 would have several entries." 300 INDEX { swmSupportedTunnelType } 301 ::= { swmSupportedTunnelTable 1 } 303 swmSupportedTunnelEntry ::= 304 SEQUENCE { 305 swmSupportedTunnelType IANATunnelType 306 } 308 swmSupportedTunnelType OBJECT-TYPE 309 SYNTAX IANATunnelType 310 MAX-ACCESS read-only 311 STATUS current 312 DESCRIPTION 313 "Represents the tunnel type that the AFBR support. " 314 ::= { swmSupportedTunnelTypeEntry 1 } 315 -- end of swmSupportedTunnelTable 317 --swmEncapsTable 318 swmEncapsTable OBJECT-TYPE 319 SYNTAX SEQUENCE OF swmEncapsEntry 320 MAX-ACCESS not-accessible 321 STATUS current 322 DESCRIPTION 323 "A table of objects that display and control the 324 softwire mesh encapsulation information." 325 ::= { swmMIB 2 } 327 swmEncapsEntry OBJECT-TYPE 328 SYNTAX swmEncapsEntry 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "A table of objects that manages the softwire mesh I-IP 333 encapsulation destination based on the E-IP destination prefix." 334 INDEX { ifIndex, 335 swmEncapsEIPDst, 336 swmEncapsEIPMask 337 } 338 ::= { swmEncapsTable 1 } 340 swmEncapsEntry ::= 341 SEQUENCE { 342 swmEncapsEIPDst InetAddress, 343 swmEncapsEIPMask InetAddressPrefixLength, 344 swmEncapsIIPDst InetAddress 345 } 347 swmEncapsEIPDst OBJECT-TYPE 348 SYNTAX InetAddress 349 MAX-ACCESS read-only 350 STATUS current 351 DESCRIPTION 352 "The address of the destination prefix, which is 353 used to for I-IP encapsulation destination lookup 354 based on longest prefix match. The address type is 355 opposite to tunnelIfAddressType in tunnelIfTable." 356 ::= { swmEncapsEntry 1 } 358 swmEncapsEIPMask OBJECT-TYPE 359 SYNTAX InetAddressPrefixLength 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The length of the destination prefix, which .. E-IP address." 364 ::= { swmEncapsEntry 2 } 366 swmEncapsIIPDst OBJECT-TYPE 367 SYNTAX InetAddress 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The I-IP address as the encapsulated destination 372 according to the E-IP address. The address type 373 is the same as tunnelIfAddressType in tunnelIfTable. 374 Since the tunnelIfRemoteInetAddress in tunnelIfTable 375 should be 0.0.0.0 or ::, swmEncapIIPDst is the 376 destination address used in the outer IP header." 377 ::= { swmEncapsEntry 3 } 378 -- End of swmEncapsTable 380 -- swmBGPNeighborTable 381 swmBGPNeighborTable OBJECT-TYPE 382 SYNTAX SEQUENCE OF swmBGPNeighborEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "A table of objects that displays the softwire mesh 387 BGP neighbor information." 388 ::= { swmMIB 3 } 390 swmBGPNeighborEntry OBJECT-TYPE 391 SYNTAX swmBGPNeighborEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "A set of objects that displays the softwire mesh 396 BGP neighbor information." 397 INDEX { 398 ifIndex, 399 swmBGPNeighborInetAddress 400 } 401 ::= { swmBGPNeighborTable 1 } 403 swmBGPNeighborEntry ::= 404 SEQUENCE { 405 swmBGPNeighborInetAddress InetAddress, 406 swmBGPNeighborTunnelType IANATunnelType 407 } 409 swmBGPNeighborInetAddress OBJECT-TYPE 410 SYNTAX InetAddress 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The address of the ABFR's BGP neighbor. The 415 address type is the same as tunnelIfAddressType 416 in tunnelIfTable" 417 ::= { swmBGPNeighborEntry 1 } 419 swmBGPNeighborTunnelType OBJECT-TYPE 420 SYNTAX IANATunnelType 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "Represents the type of tunnel that the 425 AFBR chooses to transmit traffic with another AFBR/BGP neighbor" 426 ::= { swmBGPNeighborEntry 2 } 427 -- End of swmBGPNeighborTable 429 -- conformance information 430 swmMIBConformance 431 OBJECT IDENTIFIER ::= { swmMIB 4 } 432 swmMIBCompliances 433 OBJECT IDENTIFIER ::= { swmMIBConformance 1 } 434 swmMIBGroups 435 OBJECT IDENTIFIER ::= { swmMIBConformance 2 } 437 -- compliance statements 438 swmMIBCompliance MODULE-COMPLIANCE 439 STATUS current 440 DESCRIPTION 441 "Describes the requirements for conformance to the softwire 442 mesh MIB." 444 MODULE -- this module 445 MANDATORY-GROUPS { 446 swmSupportedTunnelGroup, 447 swmEncapsGroup, 448 swmBGPNeighborGroup 449 } 450 ::= { swmMIBCompliances 1 } 452 swmSupportedTunnelGroup OBJECT-GROUP 453 OBJECTS { 454 swmSupportedTunnelType 455 } 456 STATUS current 457 DESCRIPTION 458 "The collection of objects which are used to show 459 what kind of tunnel the AFBR supports." 460 ::= { swmMIBGroups 1 } 462 swmEncapsGroup OBJECT-GROUP 463 OBJECTS { 464 swmEncapsEIPDst, 465 swmEncapsEIPMask, 466 swmEncapsIIPDst 467 } 468 STATUS current 469 DESCRIPTION 470 "The collection of objects which are used to display 471 softwire mesh encapsulation information." 472 ::= { swmMIBGroups 2 } 474 swmBGPNeighborGroup OBJECT-GROUP 475 OBJECTS { 476 swmBGPNeighborInetAddress, 477 swmBGPNeighborTunnelType 478 } 479 STATUS current 480 DESCRIPTION 481 "The collection of objects which are used to display 482 softwire mesh BGP neighbor information." 483 ::= { swmMIBGroups 3 } 485 END 487 8. Security Considerations 489 The swmMIB module can be used for configuration of certain objects, 490 and anything that can be configured can be incorrectly configured, 491 with potentially disastrous results. Because this MIB module reuses 492 the IP tunnel MIB, the security considerations of the IP tunnel MIB 493 is also applicable to the Softwire mesh MIB. 495 SNMP versions prior to SNMPv3 did not include adequate security. 496 Even if the network itself is secure (for example by using IPsec), 497 even then, there is no control as to who on the secure network is 498 allowed to access and GET/SET (read/change/create/delete) the objects 499 in this MIB module. 501 It is RECOMMENDED that implementers consider the security features as 502 provided by the SNMPv3 framework (see [RFC3410], section 8), 503 including full support for the SNMPv3 cryptographic mechanisms (for 504 authentication and privacy). 506 Further, deployment of SNMP versions prior to SNMPv3 is NOT 507 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 508 enable cryptographic security. It is then a customer/operator's 509 responsibility to ensure that the SNMP entity giving access to an 510 instance of this MIB module is properly configured to give access to 511 the objects only to those principals (users) that have legitimate 512 rights to indeed GET or SET (change/create/delete) them. 514 9. IANA Considerations 516 The MIB module in this document uses the following IANA-assigned 517 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 518 the following IANA-assigned tunnelType values recorded in the 519 IANAtunnelType-MIB registry: 521 Descriptor OBJECT IDENTIFIER value 522 ---------- ----------------------- 523 swmMIB { transmission XXX } 525 IANAtunnelType ::= TEXTUAL-CONVENTION 526 SYNTAX INTEGER { 528 softwireMesh ("XX") -- softwire Mesh tunnel 530 } 532 10. Acknowledgements 534 The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi 535 Sun, Sheng Jiang, Yu Fu for their valuable comments. 537 11. References 539 11.1. Normative References 541 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 542 Requirement Levels", BCP 14, RFC 2119, March 1997. 544 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 545 Schoenwaelder, Ed., "Structure of Management 546 Information Version 2 (SMIv2)", STD 58, RFC 2578, 547 April 1999. 549 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 550 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 551 STD 58, RFC 2579, April 1999. 553 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 554 "Conformance Statements for SMIv2", STD 58, RFC 2580, 555 April 1999. 557 [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, 558 "Softwire Problem Statement", RFC 4925, July 2007. 560 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 561 Subsequent Address Family Identifier (SAFI) and the 562 BGP Tunnel Encapsulation Attribute", RFC 5512, 563 April 2009. 565 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire 566 Mesh Framework", RFC 5565, June 2009. 568 11.2. Informative References 570 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC 571 Authors", RFC 2223, October 1997. 573 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 574 "Introduction and Applicability Statements for 575 Internet-Standard Management Framework", RFC 3410, 576 December 2002. 578 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", 579 RFC 2629, June 1999. 581 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of 582 MIB Documents", BCP 111, RFC 4181, September 2005. 584 11.3. URL References 586 [idguidelines] IETF Internet Drafts editor, 587 "http://www.ietf.org/ietf/1id-guidelines.txt". 589 [idnits] IETF Internet Drafts editor, 590 "http://www.ietf.org/ID-Checklist.html". 592 [xml2rfc] XML2RFC tools and documentation, 593 "http://xml.resource.org". 595 [ops] the IETF OPS Area, "http://www.ops.ietf.org". 597 [ietf] IETF Tools Team, "http://tools.ietf.org". 599 Authors' Addresses 601 Yong Cui 602 Tsinghua University 603 Department of Computer Science, Tsinghua University 604 Beijing 100084 605 P.R.China 607 Phone: +86-10-6260-3059 608 EMail: yong@csnet1.cs.tsinghua.edu.cn 609 Jiang Dong 610 Tsinghua University 611 Department of Computer Science, Tsinghua University 612 Beijing 100084 613 P.R.China 615 Phone: +86-10-6278-5822 616 EMail: dongjiang@csnet1.cs.tsinghua.edu.cn 618 Peng Wu 619 Tsinghua University 620 Department of Computer Science, Tsinghua University 621 Beijing 100084 622 P.R.China 624 Phone: +86-10-6278-5822 625 EMail: weapon@csnet1.cs.tsinghua.edu.cn 627 Mingwei Xu 628 Tsinghua University 629 Department of Computer Science, Tsinghua University 630 Beijing 100084 631 P.R.China 633 Phone: +86-10-6278-5822 634 EMail: xmw@cernet.edu.cn