idnits 2.17.1 draft-ietf-softwire-mesh-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 : ---------------------------------------------------------------------------- ** There are 3 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 (July 2, 2012) is 4313 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 225, but not defined == Missing Reference: 'RFC4087' is mentioned on line 193, but not defined == Missing Reference: 'RFC4001' is mentioned on line 226, but not defined == Unused Reference: 'RFC2223' is defined on line 568, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 576, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 579, 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: January 3, 2013 M. Xu 6 Tsinghua University 7 July 2, 2012 9 Softwire Mesh Management Information Base(MIB) 10 draft-ietf-softwire-mesh-mib-00 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 January 3, 2013. 36 Copyright Notice 38 Copyright (c) 2012 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, IPv6 or dual- 91 stack networks across single IPv4 or IPv6 backbone networks. In 92 softwire mesh solution, extended multiprotocol-BGP (MP-BGP)is used to 93 set up tunnels and advertise prefixes among address family border 94 routers (AFBRs). 96 This memo defines a portion of the Management Information Base (MIB) 97 for use with network management protocols in the Internet community. 98 In particular it defines objects for managing softwire mesh 99 [RFC5565]. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC 3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). They 110 are defined using the mechanisms stated in the Structure of 111 Management Information (SMI). This memo specifies a MIB module that 112 is compliant to the SMIv2, which is described in STD 58, RFC 2578 113 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 115 3. Terminology 117 This document uses terminology from softwire problem statement RFC 118 4925 [RFC4925] and softwire mesh framework RFC5565 [RFC5565]. 120 4. Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 5. Structure of the MIB Module 128 The softwire mesh MIB provides a method to configure and manage the 129 softwire mesh objects through SNMP. 131 5.1. The swmSupportedTunnlTable Subtree 133 Since AFBR need to negotiate with BGP peer what kind of tunnel they 134 will use, it should firstly announce the types of tunnels it 135 supports. The swmSupportedTunnlTable subtree provides the 136 information. According to section 4 of RFC 5512[RFC5512], current 137 softwire mesh tunnel types include IP-IP, GRE and L2TPv3. 139 5.2. The swmEncapsTable Subtree 141 The swmEncapsTable subtree provides softwire mesh NLRI-NH information 142 about the AFBR. It indicates which I-IP destination address will be 143 encapsulated according to the arriving packet's E-IP destination 144 address. The definitions of E-IP and I-IP are explained in section 145 4.1 of RFC 5565[RFC5565]. 147 5.3. The swmBGPNeighborTable Subtree 149 The subtree provides softwire mesh BGP neighbor information about the 150 AFBR. It includes the address of 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 a logical interface 165 (ifEntry) for each tunnel. Softwire mesh tunnel also acts as a 166 virtual interface, which has corresponding entries in IP Tunnel MIB 167 and Interface MIB. Those corresponding entries are indexed by 168 ifIndex. 170 The ifOperStatus in ifTable would be used to represent whether the 171 mesh function of the AFBR has been started. During the BGP OPEN 172 phase, if the softwire mesh capability is negotiated, the mesh 173 function could be considered to be started, and ifOperStatus is "up". 174 Otherwise the ifOperStatus is "down". 176 If it is IPv4-over-IPv6 softwire mesh tunnel, the ifInUcastPkts will 177 represent the number of IPv6 packets which can be decapsulated to 178 IPv4 in the virtual interface. The ifOutUcastPkts contains the 179 number of IPv6 packets which have been encapsulated with IPv4 packets 180 in it. Particularly, if these IPv4 packets need to be fragmented, 181 the number counted here is the packets after fragmentation. 183 If it is IPv6-over-IPv4 softwire mesh tunnel, the ifInUcastPkts 184 stands for the number of IPv4 packets which would be decapsulated to 185 IPv6 in the virtual interface. The ifOutUcastPkts represents the 186 number of IPv4 packets which have been encapsulated from IPv6. 187 Particularly, if these IPv6 packets need to be fragmented, the number 188 counted here is the packets after fragmentation. Similar definition 189 apply to other counting objects in ifTalbe. 191 6.2. Relationship to the IP Tunnel MIB 193 The IP Tunnel MIB [RFC4087] contains objects common to all IP 194 tunnels, including softwire mesh. Additionally, tunnel encapsulation 195 specific MIB (as is defined in this document) extends the IP tunnel 196 MIB to further described encapsulation specific information. 198 Since softwire mesh is a point to multi-point tunnel, we need to 199 specify an encapsulation table to support E-IP routing among AFBRs. 200 With the encapsulation information, the correct forwarding of E-IP 201 packets will be performed among AFBRs by using I-IP encapsulation. 202 Each AFBR also needs to know information about remote BGP peers 203 (AFBRs), so that these AFBRs can negotiate E-IP information and the 204 tunnel types they support. 206 The implementation of the IP Tunnel MIB is required for softwire 207 mesh. The tunnelIfEncapsMethod in the tunnelIfEntry should be set to 208 softwireMesh("xx"), and corresponding entry in the softwire mesh MIB 209 module will exist for every tunnelIfEntry with this 210 tunnelIfEncapsMethod. The tunnelIfRemoteInetAddress must be set to 211 0.0.0.0 for IPv4 or :: for IPv6 because it is a point to multi-point 212 tunnel. 214 Since tunnelIfAddressType in tunnelIfTable represents the type of 215 address in the corresponding tunnelIfLocalInetAddress and 216 tunnelIfRemoteInetAddress objects, we can also use the 217 tunnelIfAddressType to specify the softwire mesh tunnel is IPv4-over- 218 IPv6 or IPv6-over-IPv4. When tunnelIfAddressType is IPv4, the 219 encapsulation would be IPv6- over-IPv4; When tunnelIfAddressType is 220 IPv6, the encapsulation would be IPv4-over-IPv6. 222 6.3. MIB modules required for IMPORTS 224 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 225 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and 226 INET-ADDRESS-MIB [RFC4001]. 228 7. Definitions 230 SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN 231 IMPORTS 232 TruthValue, TEXTUAL-CONVENTION 233 TimeStamp 234 FROM SNMPv2-TC 236 OBJECT-GROUP, MODULE-COMPLIANCE 237 FROM SNMPv2-CONF 239 MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Counter32, 240 Counter64 241 FROM SNMPv2-SMI 243 IANAtunnelType FROM IANAifType-MIB; 245 InetAddress, InetAddressPrefixLength 246 FROM INET-ADDRESS-MIB 248 swmMIB MODULE-IDENTITY 249 LAST-UPDATED "201207020000Z" -- July 02, 2012 250 ORGANIZATION "Softwire Working Group" 251 CONTACT-INFO " 253 Yong Cui 254 Email: yong@csnet1.cs.tsinghua.edu.cn 256 Jiang Dong 257 Email: dongjiang@csnet1.cs.tsinghua.edu.cn 259 Peng Wu 260 Email: weapon@csnet1.cs.tsinghua.edu.cn 262 Mingwei Xu 263 Email: xmw@cernet.edu.cn 265 Email comments directly to the softwire WG Mailing 266 List at softwires@ietf.org 267 " 269 DESCRIPTION 270 "This MIB module contains managed object definitions for 271 the softwire mesh framework." 273 REVISION "201207020000Z" 274 DESCRIPTION 275 "The MIB module is defined for management of object in 276 the Softwire mesh framework." 277 ::= {transmission xxx} --xxx to be replaced with correct value 278 -- swmSupportedTunnelTable 279 swmSupportedTunnelTable OBJECT-TYPE 280 SYNTAX SEQUENCE OF swmSupportedTunnelEntry 281 MAX-ACCESS not-accessible 282 STATUS current 283 DESCRIPTION 284 "A table of objects that shows what kind of tunnels 285 can be supported in the AFBR." 286 ::= { swmMIB 1 } 288 swmSupportedTunnelEntry OBJECT-TYPE 289 SYNTAX swmSupportedTunnelEntry 290 MAX-ACCESS not-accessible 291 STATUS current 292 DESCRIPTION 293 "A set of objects that shows what kind of tunnels 294 can be supported in the AFBR. If the AFBR supports 295 several kinds of tunnel type, the 296 swmSupportedTunnelTalbe would has several entries." 297 INDEX { swmSupportedTunnelType } 298 ::= { swmSupportedTunnelTable 1 } 300 swmSupportedTunnelEntry ::= 301 SEQUENCE { 302 swmSupportedTunnelType IANATunnelType 303 } 305 swmSupportedTunnelType OBJECT-TYPE 306 SYNTAX IANATunnelType 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "Represents the kind of tunneling type that the AFBR 311 support. " 312 ::= { swmSupportedTunnelTypeEntry 1 } 313 -- end of swmSupportedTunnelTable 315 --swmEncapsTable 316 swmEncapsTable OBJECT-TYPE 317 SYNTAX SEQUENCE OF swmEncapsEntry 318 MAX-ACCESS not-accessible 319 STATUS current 320 DESCRIPTION 321 "A table of objects that display and control the 322 softwire mesh encapsulation information." 323 ::= { swmMIB 2 } 325 swmEncapsEntry OBJECT-TYPE 326 SYNTAX swmEncapsEntry 327 MAX-ACCESS not-accessible 328 STATUS current 329 DESCRIPTION 330 "A set of objects that display and control the 331 softwire mesh encapsulation information." 332 INDEX { ifIndex, 333 swmEncapsEIPDst, 334 swmEncapsEIPMask 335 } 336 ::= { swmEncapsTable 1 } 338 swmEncapsEntry ::= 339 SEQUENCE { 340 swmEncapsEIPDst InetAddress, 341 swmEncapsEIPMask InetAddressPrefixLength, 342 swmEncapsIIPDst InetAddress 343 } 345 swmEncapsEIPDst OBJECT-TYPE 346 SYNTAX InetAddress 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "The destination E-IP address that decide which 351 I-IP address will be encapsulated. The address Type 352 is opposite to tunnelIfAddressType in tunnelIfTable." 353 ::= { swmEncapsEntry 1 } 355 swmEncapsEIPMask OBJECT-TYPE 356 SYNTAX InetAddressPrefixLength 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The prefix length of E-IP address." 361 ::= { swmEncapsEntry 2 } 363 swmEncapsIIPDst OBJECT-TYPE 364 SYNTAX InetAddress 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The I-IP address that will be encapsulated 369 according to the E-IP address.The address Type 370 is the same as tunnelIfAddressType in tunnelIfTable. 371 Since the tunnelIfRemoteInetAddress in tunnelIfTable 372 should be 0.0.0.0 or ::, swmEncapIIPDst is the 373 destination address used in the outer IP header." 375 ::= { swmEncapsEntry 3 } 376 -- End of swmEncapsTable 378 -- swmBGPNeighborTable 379 swmBGPNeighborTable OBJECT-TYPE 380 SYNTAX SEQUENCE OF swmBGPNeighborEntry 381 MAX-ACCESS not-accessible 382 STATUS current 383 DESCRIPTION 384 "A table of objects that display the softwire mesh 385 BGP neighbor information." 386 ::= { swmMIB 3 } 388 swmBGPNeighborEntry OBJECT-TYPE 389 SYNTAX swmBGPNeighborEntry 390 MAX-ACCESS not-accessible 391 STATUS current 392 DESCRIPTION 393 "A set of objects that display the softwire mesh 394 BGP neighbor information." 395 INDEX { 396 ifIndex, 397 swmBGPNeighborInetAddress 398 } 399 ::= { swmBGPNeighborTable 1 } 401 swmBGPNeighborEntry ::= 402 SEQUENCE { 403 swmBGPNeighborInetAddress InetAddress, 404 swmBGPNeighborTunnelType IANATunnelType 405 } 407 swmBGPNeighborInetAddress OBJECT-TYPE 408 SYNTAX InetAddress 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The address of the ABFR's BGP neighbor. The 413 address type is the same as tunnelIfAddressType 414 in tunnelIfTable" 415 ::= { swmBGPNeighborEntry 1 } 417 swmBGPNeighborTunnelType OBJECT-TYPE 418 SYNTAX IANATunnelType 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 "Represents the kind of tunneling type that the 423 AFBR used to comunication with the BGP neighbor" 424 ::= { swmBGPNeighborEntry 2 } 425 -- End of swmBGPNeighborTable 427 -- conformance information 428 swmMIBConformance 429 OBJECT IDENTIFIER ::= { swmMIB 4 } 430 swmMIBCompliances 431 OBJECT IDENTIFIER ::= { swmMIBConformance 1 } 432 swmMIBGroups 433 OBJECT IDENTIFIER ::= { swmMIBConformance 2 } 435 -- compliance statements 436 swmMIBCompliance MODULE-COMPLIANCE 437 STATUS current 438 DESCRIPTION 439 "Describes the requirements for conformance to the softwire 440 mesh MIB." 442 MODULE -- this module 443 MANDATORY-GROUPS { 444 swmSupportedTunnelGroup, 445 swmEncapsGroup, 446 swmBGPNeighborGroup 447 } 448 ::= { swmMIBCompliances 1 } 450 swmSupportedTunnelGroup OBJECT-GROUP 451 OBJECTS { 452 swmSupportedTunnelType 453 } 454 STATUS current 455 DESCRIPTION 456 "The collection of objects which are used to show 457 what kind of tunnel the AFBR supports." 458 ::= { swmMIBGroups 1 } 460 swmEncapsGroup OBJECT-GROUP 461 OBJECTS { 462 swmEncapsEIPDst, 463 swmEncapsEIPMask, 464 swmEncapsIIPDst 465 } 466 STATUS current 467 DESCRIPTION 468 "The collection of objects which are used to display 469 softwire mesh encapsulation information." 470 ::= { swmMIBGroups 2 } 472 swmBGPNeighborGroup OBJECT-GROUP 473 OBJECTS { 474 swmBGPNeighborInetAddress, 475 swmBGPNeighborTunnelType 476 } 477 STATUS current 478 DESCRIPTION 479 "The collection of objects which are used to display 480 softwire mesh BGP neighbor information." 481 ::= { swmMIBGroups 3 } 483 END 485 8. Security Considerations 487 The swmMIB module can be used for configuration of certain objects, 488 and anything that can be configured can be incorrectly configured, 489 with potentially disastrous results. Because this MIB module reuses 490 the IP tunnel MIB, the security considerations of the IP tunnel MIB 491 is also applicable to the Softwire mesh MIB. 493 SNMP versions prior to SNMPv3 did not include adequate security. 494 Even if the network itself is secure (for example by using IPsec), 495 even then, there is no control as to who on the secure network is 496 allowed to access and GET/SET (read/change/create/delete) the objects 497 in this MIB module. 499 It is RECOMMENDED that implementers consider the security features as 500 provided by the SNMPv3 framework (see [RFC3410], section 8), 501 including full support for the SNMPv3 cryptographic mechanisms (for 502 authentication and privacy). 504 Further, deployment of SNMP versions prior to SNMPv3 is NOT 505 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 506 enable cryptographic security. It is then a customer/operator's 507 responsibility to ensure that the SNMP entity giving access to an 508 instance of this MIB module is properly configured to give access to 509 the objects only to those principals (users) that have legitimate 510 rights to indeed GET or SET (change/create/delete) them. 512 9. IANA Considerations 514 The MIB module in this document uses the following IANA-assigned 515 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 516 the following IANA-assigned tunnelType values recorded in the 517 IANAtunnelType-MIB registry: 519 Descriptor OBJECT IDENTIFIER value 520 ---------- ----------------------- 521 swmMIB { transmission XXX } 523 IANAtunnelType ::= TEXTUAL-CONVENTION 524 SYNTAX INTEGER { 526 softwireMesh ("XX") -- softwire Mesh tunnel 528 } 530 10. Acknowledgements 532 The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi 533 Sun, Sheng Jiang, Yu Fu for their valuable comments. 535 11. References 537 11.1. Normative References 539 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 540 Requirement Levels", BCP 14, RFC 2119, March 1997. 542 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 543 Schoenwaelder, Ed., "Structure of Management 544 Information Version 2 (SMIv2)", STD 58, RFC 2578, 545 April 1999. 547 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 548 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 549 STD 58, RFC 2579, April 1999. 551 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 552 "Conformance Statements for SMIv2", STD 58, RFC 2580, 553 April 1999. 555 [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, 556 "Softwire Problem Statement", RFC 4925, July 2007. 558 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 559 Subsequent Address Family Identifier (SAFI) and the 560 BGP Tunnel Encapsulation Attribute", RFC 5512, 561 April 2009. 563 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire 564 Mesh Framework", RFC 5565, June 2009. 566 11.2. Informative References 568 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC 569 Authors", RFC 2223, October 1997. 571 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 572 "Introduction and Applicability Statements for 573 Internet-Standard Management Framework", RFC 3410, 574 December 2002. 576 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", 577 RFC 2629, June 1999. 579 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of 580 MIB Documents", BCP 111, RFC 4181, September 2005. 582 11.3. URL References 584 [idguidelines] IETF Internet Drafts editor, 585 "http://www.ietf.org/ietf/1id-guidelines.txt". 587 [idnits] IETF Internet Drafts editor, 588 "http://www.ietf.org/ID-Checklist.html". 590 [xml2rfc] XML2RFC tools and documentation, 591 "http://xml.resource.org". 593 [ops] the IETF OPS Area, "http://www.ops.ietf.org". 595 [ietf] IETF Tools Team, "http://tools.ietf.org". 597 Authors' Addresses 599 Yong Cui 600 Tsinghua University 601 Department of Computer Science, Tsinghua University 602 Beijing 100084 603 P.R.China 605 Phone: +86-10-6260-3059 606 EMail: yong@csnet1.cs.tsinghua.edu.cn 607 Jiang Dong 608 Tsinghua University 609 Department of Computer Science, Tsinghua University 610 Beijing 100084 611 P.R.China 613 Phone: +86-10-6278-5822 614 EMail: dongjiang@csnet1.cs.tsinghua.edu.cn 616 Peng Wu 617 Tsinghua University 618 Department of Computer Science, Tsinghua University 619 Beijing 100084 620 P.R.China 622 Phone: +86-10-6278-5822 623 EMail: weapon@csnet1.cs.tsinghua.edu.cn 625 Mingwei Xu 626 Tsinghua University 627 Department of Computer Science, Tsinghua University 628 Beijing 100084 629 P.R.China 631 Phone: +86-10-6278-5822 632 EMail: xmw@cernet.edu.cn