idnits 2.17.1 draft-ietf-softwire-mesh-mib-03.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 5 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 (March 11, 2013) is 4063 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 227, but not defined == Missing Reference: 'RFC4087' is mentioned on line 194, but not defined == Missing Reference: 'RFC4001' is mentioned on line 228, but not defined == Unused Reference: 'RFC2223' is defined on line 633, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 641, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 644, 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: September 12, 2013 M. Xu 6 Tsinghua University 7 March 11, 2013 9 Softwire Mesh Management Information Base (MIB) 10 draft-ietf-softwire-mesh-mib-03 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 September 12, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 6 79 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 80 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 81 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 82 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 83 11.1. Normative References . . . . . . . . . . . . . . . . . . . 13 84 11.2. Informative References . . . . . . . . . . . . . . . . . . 14 85 11.3. URL References . . . . . . . . . . . . . . . . . . . . . . 14 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 The tunnelIfAddressType in tunnelIfTable represents the type of 216 address in the corresponding tunnelIfLocalInetAddress and 217 tunnelIfRemoteInetAddress objects. The tunnelIfAddressType is 218 identical to swmEncapsIIPDstType in softwire mesh, which can support 219 either IPv4-over-IPv6 or IPv6-over-IPv4. When swmEncapsEIPDstType is 220 IPv6 and swmEncapsIIPDstType is IPv4, the mesh is IPv6-over-IPv4; 221 When swmEncapsEIPDstType is IPv4 and swmEncapsIIPDstType is IPv6, the 222 encapsulation would be IPv4-over-IPv6. 224 6.3. MIB modules required for IMPORTS 226 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 227 SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and INET-ADDRESS-MIB 228 [RFC4001]. 230 7. Definitions 231 SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN 233 IMPORTS 234 MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI 236 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF 238 InetAddress, InetAddressType, InetAddressPrefixLength 239 FROM INET-ADDRESS-MIB 241 ifIndex FROM IF-MIB 243 IANAtunnelType FROM IANAifType-MIB; 245 swmMIB MODULE-IDENTITY 246 LAST-UPDATED "201303100000Z" -- March 10, 2013 247 ORGANIZATION "Softwire Working Group" 248 CONTACT-INFO " 250 Yong Cui 251 Email: yong@csnet1.cs.tsinghua.edu.cn 253 Jiang Dong 254 Email: dongjiang@csnet1.cs.tsinghua.edu.cn 256 Peng Wu 257 Email: weapon@csnet1.cs.tsinghua.edu.cn 259 Mingwei Xu 260 Email: xmw@cernet.edu.cn 262 Email comments directly to the softwire WG Mailing 263 List at softwires@ietf.org 264 " 266 DESCRIPTION 267 "This MIB module contains managed object definitions for 268 the softwire mesh framework." 270 REVISION "201303100000Z" 271 DESCRIPTION 272 "The MIB module is defined for management of object in 273 the Softwire mesh framework." 274 ::= { transmission 999 } --999 to be replaced with correct value 276 swmMIBObjects OBJECT IDENTIFIER ::= { swmMIB 1 } 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 by the AFBR." 286 ::= { swmMIBObjects 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 multiple tunnel types, the swmSupportedTunnelTalbe 296 would have several entries." 297 INDEX { swmSupportedTunnelType } 298 ::= { swmSupportedTunnelTable 1 } 300 SwmSupportedTunnelEntry ::= SEQUENCE { 301 swmSupportedTunnelType IANAtunnelType 302 } 304 swmSupportedTunnelType OBJECT-TYPE 305 SYNTAX IANAtunnelType 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "Represents the tunnel type that the AFBR support. " 310 ::= { swmSupportedTunnelEntry 1 } 311 -- end of swmSupportedTunnelTable 313 --swmEncapsTable 314 swmEncapsTable OBJECT-TYPE 315 SYNTAX SEQUENCE OF SwmEncapsEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "A table of objects that display and control the 320 softwire mesh encapsulation information." 321 ::= { swmMIBObjects 2 } 323 swmEncapsEntry OBJECT-TYPE 324 SYNTAX SwmEncapsEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "A table of objects that manages the softwire mesh I-IP 329 encapsulation destination based on the E-IP destination prefix." 330 INDEX { ifIndex, 331 swmEncapsEIPDstType, 332 swmEncapsEIPDst, 333 swmEncapsEIPMask 334 } 335 ::= { swmEncapsTable 1 } 337 SwmEncapsEntry ::= SEQUENCE { 338 swmEncapsEIPDstType InetAddressType, 339 swmEncapsEIPDst InetAddress, 340 swmEncapsEIPMask InetAddressPrefixLength, 341 swmEncapsIIPDstType InetAddressType, 342 swmEncapsIIPDst InetAddress 343 } 345 swmEncapsEIPDstType OBJECT-TYPE 346 SYNTAX InetAddressType 347 MAX-ACCESS not-accessible 348 STATUS current 349 DESCRIPTION 350 "This object specifies the address type used for 351 swmEncapsEIPDst." 352 ::= { swmEncapsEntry 1 } 354 swmEncapsEIPDst OBJECT-TYPE 355 SYNTAX InetAddress 356 MAX-ACCESS not-accessible 357 STATUS current 358 DESCRIPTION 359 "The address of the destination prefix, which is 360 used for I-IP encapsulation destination lookup 361 based on longest prefix match. The address type is 362 opposite to tunnelIfAddressType in tunnelIfTable." 363 ::= { swmEncapsEntry 2 } 365 swmEncapsEIPMask OBJECT-TYPE 366 SYNTAX InetAddressPrefixLength 367 MAX-ACCESS not-accessible 368 STATUS current 369 DESCRIPTION 370 "The prefix length of E-IP address." 371 ::= { swmEncapsEntry 3 } 373 swmEncapsIIPDstType OBJECT-TYPE 374 SYNTAX InetAddressType 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "This object specifies the address type used for 379 swmEncapsIIPDst." 380 ::= { swmEncapsEntry 4 } 382 swmEncapsIIPDst OBJECT-TYPE 383 SYNTAX InetAddress 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The I-IP address as the encapsulated destination 388 according to the E-IP address. The address type 389 is the same as tunnelIfAddressType in tunnelIfTable. 390 Since the tunnelIfRemoteInetAddress in tunnelIfTable 391 should be 0.0.0.0 or ::, swmEncapIIPDst is the 392 destination address used in the outer IP header." 393 ::= { swmEncapsEntry 5 } 394 -- End of swmEncapsTable 396 -- swmBGPNeighborTable 397 swmBGPNeighborTable OBJECT-TYPE 398 SYNTAX SEQUENCE OF SwmBGPNeighborEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "A table of objects that displays the softwire mesh 403 BGP neighbor information." 404 ::= { swmMIBObjects 3 } 406 swmBGPNeighborEntry OBJECT-TYPE 407 SYNTAX SwmBGPNeighborEntry 408 MAX-ACCESS not-accessible 409 STATUS current 410 DESCRIPTION 411 "A set of objects that displays the softwire mesh 412 BGP neighbor information." 413 INDEX { 414 ifIndex, 415 swmBGPNeighborInetAddressType, 416 swmBGPNeighborInetAddress 417 } 418 ::= { swmBGPNeighborTable 1 } 420 SwmBGPNeighborEntry ::= SEQUENCE { 421 swmBGPNeighborInetAddressType InetAddressType, 422 swmBGPNeighborInetAddress InetAddress, 423 swmBGPNeighborTunnelType IANAtunnelType 424 } 426 swmBGPNeighborInetAddressType OBJECT-TYPE 427 SYNTAX InetAddressType 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "This object specifies the address type used for 432 swmBGPNeighborInetAddress." 433 ::= { swmBGPNeighborEntry 1 } 435 swmBGPNeighborInetAddress OBJECT-TYPE 436 SYNTAX InetAddress 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "The address of the ABFR's BGP neighbor. The 441 address type is the same as tunnelIfAddressType 442 in tunnelIfTable" 443 ::= { swmBGPNeighborEntry 2 } 445 swmBGPNeighborTunnelType OBJECT-TYPE 446 SYNTAX IANAtunnelType 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "Represents the type of tunnel that the 451 AFBR chooses to transmit traffic with another AFBR/BGP neighbor" 452 ::= { swmBGPNeighborEntry 3 } 453 -- End of swmBGPNeighborTable 455 -- conformance information 456 swmMIBConformance 457 OBJECT IDENTIFIER ::= { swmMIB 2 } 458 swmMIBCompliances 459 OBJECT IDENTIFIER ::= { swmMIBConformance 1 } 460 swmMIBGroups 461 OBJECT IDENTIFIER ::= { swmMIBConformance 2 } 463 -- compliance statements 464 swmMIBCompliance MODULE-COMPLIANCE 465 STATUS current 466 DESCRIPTION 467 "Describes the requirements for conformance to the softwire 468 mesh MIB. 470 The following index objects cannot be added as OBJECT 471 clauses but nevertheless have the compliance 472 requirements: 473 " 474 -- OBJECT swmEncapsEIPDstType 475 -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } 476 -- DESCRIPTION 477 -- "An implementation is required to support 478 -- global IPv4 and/or IPv6 addresses, depending 479 -- on its support for IPv4 and IPv6." 481 -- OBJECT swmEncapsEIPDst 482 -- SYNTAX InetAddress (SIZE(4|16)) 483 -- DESCRIPTION 484 -- "An implementation is required to support 485 -- global IPv4 and/or IPv6 addresses, depending 486 -- on its support for IPv4 and IPv6." 488 -- OBJECT swmEncapsEIPMask 489 -- SYNTAX InetAddressPrefixLength (ipv4(1),ipv4z(3),ipv6(2),ipv6z(2)) 490 -- DESCRIPTION 491 -- "An implementation is required to support 492 -- global IPv4 and/or IPv6 addresses, depending 493 -- on its support for IPv4 and IPv6." 495 -- OBJECT swmBGPNeighborInetAddressType 496 -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } 497 -- DESCRIPTION 498 -- "An implementation is required to support 499 -- global IPv4 and/or IPv6 addresses, depending 500 -- on its support for IPv4 and IPv6." 502 -- OBJECT swmBGPNeighborInetAddress 503 -- SYNTAX InetAddress (SIZE(4|16)) 504 -- DESCRIPTION 505 -- "An implementation is required to support 506 -- global IPv4 and/or IPv6 addresses, depending 507 -- on its support for IPv4 and IPv6." 509 MODULE -- this module 510 MANDATORY-GROUPS { 511 swmSupportedTunnelGroup, 512 swmEncapsGroup, 513 swmBGPNeighborGroup 514 } 515 ::= { swmMIBCompliances 1 } 517 swmSupportedTunnelGroup OBJECT-GROUP 518 OBJECTS { 519 swmSupportedTunnelType 520 } 521 STATUS current 522 DESCRIPTION 523 "The collection of objects which are used to show 524 what kind of tunnel the AFBR supports." 525 ::= { swmMIBGroups 1 } 527 swmEncapsGroup OBJECT-GROUP 528 OBJECTS { 529 swmEncapsIIPDstType, 530 swmEncapsIIPDst 531 } 532 STATUS current 533 DESCRIPTION 534 "The collection of objects which are used to display 535 softwire mesh encapsulation information." 536 ::= { swmMIBGroups 2 } 538 swmBGPNeighborGroup OBJECT-GROUP 539 OBJECTS { 540 swmBGPNeighborTunnelType 541 } 542 STATUS current 543 DESCRIPTION 544 "The collection of objects which are used to display 545 softwire mesh BGP neighbor information." 546 ::= { swmMIBGroups 3 } 548 END 550 8. Security Considerations 552 The swmMIB module can be used for configuration of certain objects, 553 and anything that can be configured can be incorrectly configured, 554 with potentially disastrous results. Because this MIB module reuses 555 the IP tunnel MIB, the security considerations of the IP tunnel MIB 556 is also applicable to the Softwire mesh MIB. 558 SNMP versions prior to SNMPv3 did not include adequate security. 559 Even if the network itself is secure (for example by using IPsec), 560 even then, there is no control as to who on the secure network is 561 allowed to access and GET/SET (read/change/create/delete) the objects 562 in this MIB module. 564 It is RECOMMENDED that implementers consider the security features as 565 provided by the SNMPv3 framework (see [RFC3410], section 8), 566 including full support for the SNMPv3 cryptographic mechanisms (for 567 authentication and privacy). 569 Further, deployment of SNMP versions prior to SNMPv3 is NOT 570 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 571 enable cryptographic security. It is then a customer/operator's 572 responsibility to ensure that the SNMP entity giving access to an 573 instance of this MIB module is properly configured to give access to 574 the objects only to those principals (users) that have legitimate 575 rights to indeed GET or SET (change/create/delete) them. 577 9. IANA Considerations 579 The MIB module in this document uses the following IANA-assigned 580 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 581 the following IANA-assigned tunnelType values recorded in the 582 IANAtunnelType-MIB registry: 584 Descriptor OBJECT IDENTIFIER value 585 ---------- ----------------------- 586 swmMIB { transmission XXX } 588 IANAtunnelType ::= TEXTUAL-CONVENTION 589 SYNTAX INTEGER { 591 softwireMesh ("XX") -- softwire Mesh tunnel 593 } 595 10. Acknowledgements 597 The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi 598 Sun, Sheng Jiang, Yu Fu for their valuable comments. 600 11. References 602 11.1. Normative References 604 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 605 Requirement Levels", BCP 14, RFC 2119, March 1997. 607 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 608 Schoenwaelder, Ed., "Structure of Management 609 Information Version 2 (SMIv2)", STD 58, RFC 2578, 610 April 1999. 612 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 613 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 614 STD 58, RFC 2579, April 1999. 616 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 617 "Conformance Statements for SMIv2", STD 58, RFC 2580, 618 April 1999. 620 [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, 621 "Softwire Problem Statement", RFC 4925, July 2007. 623 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 624 Subsequent Address Family Identifier (SAFI) and the 625 BGP Tunnel Encapsulation Attribute", RFC 5512, 626 April 2009. 628 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire 629 Mesh Framework", RFC 5565, June 2009. 631 11.2. Informative References 633 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC 634 Authors", RFC 2223, October 1997. 636 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 637 "Introduction and Applicability Statements for 638 Internet-Standard Management Framework", RFC 3410, 639 December 2002. 641 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", 642 RFC 2629, June 1999. 644 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of 645 MIB Documents", BCP 111, RFC 4181, September 2005. 647 11.3. URL References 649 [idguidelines] IETF Internet Drafts editor, 650 "http://www.ietf.org/ietf/1id-guidelines.txt". 652 [idnits] IETF Internet Drafts editor, 653 "http://www.ietf.org/ID-Checklist.html". 655 [xml2rfc] XML2RFC tools and documentation, 656 "http://xml.resource.org". 658 [ops] the IETF OPS Area, "http://www.ops.ietf.org". 660 [ietf] IETF Tools Team, "http://tools.ietf.org". 662 Authors' Addresses 664 Yong Cui 665 Tsinghua University 666 Department of Computer Science, Tsinghua University 667 Beijing 100084 668 P.R.China 670 Phone: +86-10-6260-3059 671 EMail: yong@csnet1.cs.tsinghua.edu.cn 673 Jiang Dong 674 Tsinghua University 675 Department of Computer Science, Tsinghua University 676 Beijing 100084 677 P.R.China 679 Phone: +86-10-6278-5822 680 EMail: dongjiang@csnet1.cs.tsinghua.edu.cn 682 Peng Wu 683 Tsinghua University 684 Department of Computer Science, Tsinghua University 685 Beijing 100084 686 P.R.China 688 Phone: +86-10-6278-5822 689 EMail: weapon@csnet1.cs.tsinghua.edu.cn 691 Mingwei Xu 692 Tsinghua University 693 Department of Computer Science, Tsinghua University 694 Beijing 100084 695 P.R.China 697 Phone: +86-10-6278-5822 698 EMail: xmw@cernet.edu.cn