idnits 2.17.1 draft-ietf-softwire-mesh-mib-05.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 8 instances of too long lines in the document, the longest one being 10 characters in excess of 72. 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 12, 2014) is 3695 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: 'RFC4001' is mentioned on line 232, but not defined == Unused Reference: 'RFC2223' is defined on line 645, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 655, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 660, 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: 3 errors (**), 0 flaws (~~), 7 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 13, 2014 M. Xu 6 Tsinghua University 7 A. Yla-Jaaski 8 Aalto University 9 March 12, 2014 11 Softwire Mesh Management Information Base (MIB) 12 draft-ietf-softwire-mesh-mib-05 14 Abstract 16 This memo defines a portion of the Management Information Base (MIB) 17 for use with network management protocols in the Internet community. 18 In particular it defines objects for managing softwire mesh. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on September 13, 2014. 37 Copyright Notice 39 Copyright (c) 2014 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 This document may contain material from IETF Documents or IETF 53 Contributions published or made publicly available before November 54 10, 2008. The person(s) controlling the copyright in some of this 55 material may not have granted the IETF Trust the right to allow 56 modifications of such material outside the IETF Standards Process. 57 Without obtaining an adequate license from the person(s) controlling 58 the copyright in such materials, this document may not be modified 59 outside the IETF Standards Process, and derivative works of it may 60 not be created outside the IETF Standards Process, except to format 61 it for publication as an RFC or to translate it into languages other 62 than English. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. The Internet-Standard Management Framework . . . . . . . . . 3 68 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 71 5.1. The swmSupportedTunnelTable Subtree . . . . . . . . . . . 3 72 5.2. The swmEncapsTable Subtree . . . . . . . . . . . . . . . 3 73 5.3. The swmBGPNeighborTable Subtree . . . . . . . . . . . . . 4 74 5.4. The swmConformance Subtree . . . . . . . . . . . . . . . 4 75 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4 76 6.1. Relationship to the IF-MIB . . . . . . . . . . . . . . . 4 77 6.2. Relationship to the IP Tunnel MIB . . . . . . . . . . . . 5 78 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . 5 79 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 80 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 81 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 82 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 83 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 84 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 85 11.2. Informative References . . . . . . . . . . . . . . . . . 14 87 1. Introduction 89 The Softwire mesh framework RFC 5565 [RFC5565] is a tunneling 90 mechanism that enables the connectivity between islands of IPv4 91 networks across a single IPv6 backbone and vice versa. In softwire 92 mesh, extended multiprotocol-BGP (MP-BGP)is used to set up tunnels 93 and advertise 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. 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 the softwire problem statement 118 RFC 4925 [RFC4925] and the softwire mesh framework RFC 5565 119 [RFC5565]. 121 4. Conventions 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 125 document are to be interpreted as described in RFC 2119 [RFC2119]. 127 5. Structure of the MIB Module 129 The softwire mesh MIB provides a method to configure and manage the 130 softwire mesh objects through SNMP. 132 5.1. The swmSupportedTunnelTable Subtree 134 The AFBR may need to announce the types of tunnels it supports, in 135 order to negotiate with a BGP peer what kind of tunnel they will use. 136 The swmSupportedTunnelTable subtree provides the information. 137 According to section 4 of RFC 5512 [RFC5512], current softwire mesh 138 tunnel types include IP-IP, GRE and L2TPv3. 140 5.2. The swmEncapsTable Subtree 142 The swmEncapsTable subtree provides softwire mesh NLRI-NH information 143 about the AFBR. It keeps the mapping between the External-IP (E-IP) 144 prefix and the Internal-IP (I-IP) address of the next hop. The 145 mappings determine which I-IP destination address will be used to 146 encapsulate the received packet according to its E-IP destination 147 address. The definitions of E-IP and I-IP are explained in section 148 4.1 of RFC 5565[RFC5565]. 150 5.3. The swmBGPNeighborTable Subtree 152 The subtree provides the softwire mesh BGP neighbor information of an 153 AFBR. It includes the address of the softwire mesh BGP peer, and the 154 kind of tunnel that the AFBR would use to communicate with this BGP 155 peer. 157 5.4. The swmConformance Subtree 159 The subtree provides the conformance information of MIB objects. 161 6. Relationship to Other MIB Modules 163 6.1. Relationship to the IF-MIB 165 The Interfaces MIB [RFC2863] defines generic managed objects for 166 managing interfaces. Each logical interface (physical or virtual) 167 has an ifEntry. Tunnels are handled by creating logical interfaces 168 (ifEntry). Being a tunnel, softwire mesh has an entry in the 169 Interface MIB, as well as an entry in IP Tunnel MIB. Those 170 corresponding entries are indexed by ifIndex. 172 The ifOperStatus in the ifTable represents whether the mesh function 173 of the AFBR has been triggered. If the software mesh capability is 174 negotiated during the BGP OPEN phase, the mesh function is considered 175 to be started, and the ifOperStatus is "up". Otherwise the 176 ifOperStatus is "down". 178 In the case of an IPv4-over-IPv6 softwire mesh tunnel, ifInUcastPkts 179 counts the number of IPv6 packets which are sent to the virtual 180 interface for decapsulation into IPv4. The ifOutUcastPkts counts the 181 number of IPv6 packets which are generated by encapsulating IPv4 182 packets sent to the virtual interface. Particularly, if these IPv4 183 packets need fragmentation, ifOutUcastPkts counts the number of 184 packets after fragmentation. 186 In the case of an IPv6-over-IPv4 softwire mesh tunnel, ifInUcastPkts 187 counts the number of IPv4 packets, which are sent to the virtual 188 interface for decapsulation into IPv6. The ifOutUcastPkts counts the 189 number of IPv4 packets, which are generated by encapsulating IPv6 190 packets sent to the virtual interface. Particularly, if these IPv6 191 packets need to be fragmented, tifOutUcastPkts counts the number of 192 packets after fragmentation. Similar definitions apply to other 193 counter objects in the ifTable. 195 6.2. Relationship to the IP Tunnel MIB 197 The IP Tunnel MIB [RFC4087] contains objects applicable to all IP 198 tunnels, including softwire mesh. Meanwhile, the Softwire Mesh MIB 199 extends the IP Tunnel MIB to further describe encapsulation-specific 200 information. 202 Running a point to multi-point tunnel, it is necessary for a softwire 203 mesh AFBR to maintain an encapsulation table, used to perform correct 204 "forwarding" among AFBRs. This forwarding function on an AFBR is 205 performed by using the E-IP destination address to look up in the 206 encapsulation table for the I-IP encapsulation destination address. 207 An AFBR also needs to know the BGP peer information of the other 208 AFBRs, so that it can negotiate the NLRI-NH information and the 209 tunnel parameters with them. 211 The Softwire mesh MIB requires the implementation of the IP Tunnel 212 MIB. The tunnelIfEncapsMethod in the tunnelIfEntry MUST be set to 213 softwireMesh("xx"), and a corresponding entry in the softwire mesh 214 MIB module will be presented for the tunnelIfEntry. The 215 tunnelIfRemoteInetAddress MUST be set to 0.0.0.0 for IPv4 or :: for 216 IPv6 because it is a point to multi-point tunnel. 218 The tunnelIfAddressType in the tunnelIfTable represents the type of 219 address in the corresponding tunnelIfLocalInetAddress and 220 tunnelIfRemoteInetAddress objects. The tunnelIfAddressType is 221 identical to swmEncapsIIPDstType in softwire mesh, which can support 222 either IPv4-over-IPv6 or IPv6-over-IPv4. When the 223 swmEncapsEIPDstType is IPv6 and the swmEncapsIIPDstType is IPv4, the 224 tunnel type is IPv6-over-IPv4; When the swmEncapsEIPDstType is IPv4 225 and the swmEncapsIIPDstType is IPv6, the encapsulation mode would be 226 IPv4-over-IPv6. 228 6.3. MIB modules required for IMPORTS 230 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 231 SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and INET-ADDRESS-MIB 232 [RFC4001]. 234 7. Definitions 236 SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN 238 IMPORTS 239 MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI 241 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF 242 InetAddress, InetAddressType, InetAddressPrefixLength FROM INET-ADDRESS-MIB 244 ifIndex FROM IF-MIB 246 IANAtunnelType FROM IANAifType-MIB; 248 swmMIB MODULE-IDENTITY 249 LAST-UPDATED "201309030000Z" -- September 3, 2013 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 Antti Yla-Jaaski 266 Email: antti.yla-jaaski@aalto.fi 268 Email comments directly to the softwire WG Mailing 269 List at softwires@ietf.org 270 " 272 DESCRIPTION 273 "This MIB module contains managed object definitions for 274 the softwire mesh framework." 276 REVISION "201309030000Z" 277 DESCRIPTION 278 "The MIB module is defined for management of object in 279 the Softwire mesh framework." 280 ::= { transmission 999 } --999 to be replaced with correct value 282 swmObjects OBJECT IDENTIFIER ::= { swmMIB 1 } 284 -- swmSupportedTunnelTable 285 swmSupportedTunnelTable OBJECT-TYPE 286 SYNTAX SEQUENCE OF SwmSupportedTunnelEntry 287 MAX-ACCESS not-accessible 288 STATUS current 289 DESCRIPTION 290 "A table of objects that shows what kind of tunnels 291 can be supported by the AFBR." 292 ::= { swmObjects 1 } 294 swmSupportedTunnelEntry OBJECT-TYPE 295 SYNTAX SwmSupportedTunnelEntry 296 MAX-ACCESS not-accessible 297 STATUS current 298 DESCRIPTION 299 "A set of objects that show what kind of tunnels 300 can be supported in the AFBR. If the AFBR supports 301 multiple tunnel types, the swmSupportedTunnelTable 302 would have several entries." 303 INDEX { swmSupportedTunnelType } 304 ::= { swmSupportedTunnelTable 1 } 306 SwmSupportedTunnelEntry ::= SEQUENCE { 307 swmSupportedTunnelType IANAtunnelType 308 } 310 swmSupportedTunnelType OBJECT-TYPE 311 SYNTAX IANAtunnelType 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "Represents the tunnel type that the AFBR support. " 316 ::= { swmSupportedTunnelEntry 1 } 317 -- end of swmSupportedTunnelTable 319 --swmEncapsTable 320 swmEncapsTable OBJECT-TYPE 321 SYNTAX SEQUENCE OF SwmEncapsEntry 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "A table of objects that display and control the 326 softwire mesh encapsulation information." 327 ::= { swmObjects 2 } 329 swmEncapsEntry OBJECT-TYPE 330 SYNTAX SwmEncapsEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "A table of objects that manage the softwire mesh I-IP 335 encapsulation destination based on the E-IP destination prefix." 336 INDEX { ifIndex, 337 swmEncapsEIPDstType, 338 swmEncapsEIPDst, 339 swmEncapsEIPPrefixLength 340 } 341 ::= { swmEncapsTable 1 } 343 SwmEncapsEntry ::= SEQUENCE { 344 swmEncapsEIPDstType InetAddressType, 345 swmEncapsEIPDst InetAddress, 346 swmEncapsEIPPrefixLength InetAddressPrefixLength, 347 swmEncapsIIPDstType InetAddressType, 348 swmEncapsIIPDst InetAddress 349 } 351 swmEncapsEIPDstType OBJECT-TYPE 352 SYNTAX InetAddressType 353 MAX-ACCESS not-accessible 354 STATUS current 355 DESCRIPTION 356 "This object specifies the address type used for 357 swmEncapsEIPDst. It is different from the tunnelIfAddressType 358 in the tunnelIfTable." 359 ::= { swmEncapsEntry 1 } 361 swmEncapsEIPDst OBJECT-TYPE 362 SYNTAX InetAddress 363 MAX-ACCESS not-accessible 364 STATUS current 365 DESCRIPTION 366 "The E-IP destination prefix, which is 367 used for I-IP encapsulation destination looking up." 368 ::= { swmEncapsEntry 2 } 370 swmEncapsEIPPrefixLength OBJECT-TYPE 371 SYNTAX InetAddressPrefixLength 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "The prefix length of the E-IP destination prefix." 376 ::= { swmEncapsEntry 3 } 378 swmEncapsIIPDstType OBJECT-TYPE 379 SYNTAX InetAddressType 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "This object specifies the address type used for 384 swmEncapsIIPDst. It is the same as the tunnelIfAddressType 385 in the tunnelIfTable." 387 ::= { swmEncapsEntry 4 } 389 swmEncapsIIPDst OBJECT-TYPE 390 SYNTAX InetAddress 391 MAX-ACCESS read-only 392 STATUS current 393 DESCRIPTION 394 "The I-IP destination address, which is used as the encapsulation 395 destination for the corresponding E-IP prefix. Since the 396 tunnelIfRemoteInetAddress in the tunnelIfTable should be 0.0.0.0 or ::, 397 swmEncapIIPDst should be the destination address used in the outer 398 IP header." 399 ::= { swmEncapsEntry 5 } 400 -- End of swmEncapsTable 402 -- swmBGPNeighborTable 403 swmBGPNeighborTable OBJECT-TYPE 404 SYNTAX SEQUENCE OF SwmBGPNeighborEntry 405 MAX-ACCESS not-accessible 406 STATUS current 407 DESCRIPTION 408 "A table of objects that display the softwire mesh 409 BGP neighbor information." 410 ::= { swmObjects 3 } 412 swmBGPNeighborEntry OBJECT-TYPE 413 SYNTAX SwmBGPNeighborEntry 414 MAX-ACCESS not-accessible 415 STATUS current 416 DESCRIPTION 417 "A set of objects that display the softwire mesh 418 BGP neighbor information." 419 INDEX { 420 ifIndex, 421 swmBGPNeighborInetAddressType, 422 swmBGPNeighborInetAddress 423 } 424 ::= { swmBGPNeighborTable 1 } 426 SwmBGPNeighborEntry ::= SEQUENCE { 427 swmBGPNeighborInetAddressType InetAddressType, 428 swmBGPNeighborInetAddress InetAddress, 429 swmBGPNeighborTunnelType IANAtunnelType 430 } 432 swmBGPNeighborInetAddressType OBJECT-TYPE 433 SYNTAX InetAddressType 434 MAX-ACCESS not-accessible 435 STATUS current 436 DESCRIPTION 437 "This object specifies the address type used for 438 swmBGPNeighborInetAddress." 439 ::= { swmBGPNeighborEntry 1 } 441 swmBGPNeighborInetAddress OBJECT-TYPE 442 SYNTAX InetAddress 443 MAX-ACCESS not-accessible 444 STATUS current 445 DESCRIPTION 446 "The address of the ABFR's BGP neighbor. The 447 address type is the same as the tunnelIfAddressType 448 in the tunnelIfTable." 449 ::= { swmBGPNeighborEntry 2 } 451 swmBGPNeighborTunnelType OBJECT-TYPE 452 SYNTAX IANAtunnelType 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "Represents the type of tunnel that the 457 AFBR chooses to transmit traffic with another AFBR/BGP neighbor." 458 ::= { swmBGPNeighborEntry 3 } 459 -- End of swmBGPNeighborTable 461 -- conformance information 462 swmConformance 463 OBJECT IDENTIFIER ::= { swmMIB 2 } 464 swmCompliances 465 OBJECT IDENTIFIER ::= { swmConformance 1 } 466 swmGroups 467 OBJECT IDENTIFIER ::= { swmConformance 2 } 469 -- compliance statements 470 swmCompliances MODULE-COMPLIANCE 471 STATUS current 472 DESCRIPTION 473 "Describes the requirements for conformance to the softwire 474 mesh MIB. 476 The following index objects cannot be added as OBJECT 477 clauses but nevertheless have compliance requirements: 478 " 479 -- OBJECT swmEncapsEIPDstType 480 -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } 481 -- DESCRIPTION 482 -- "An implementation is required to support 483 -- global IPv4 and/or IPv6 addresses, depending 484 -- on its support for IPv4 and IPv6." 486 -- OBJECT swmEncapsEIPDst 487 -- SYNTAX InetAddress (SIZE(4|16)) 488 -- DESCRIPTION 489 -- "An implementation is required to support 490 -- global IPv4 and/or IPv6 addresses, depending 491 -- on its support for IPv4 and IPv6." 493 -- OBJECT swmEncapsEIPPrefixLength 494 -- SYNTAX InetAddressPrefixLength (ipv4(1),ipv4z(3),ipv6(2),ipv6z(2)) 495 -- DESCRIPTION 496 -- "An implementation is required to support 497 -- global IPv4 and/or IPv6 addresses, depending 498 -- on its support for IPv4 and IPv6." 500 -- OBJECT swmBGPNeighborInetAddressType 501 -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } 502 -- DESCRIPTION 503 -- "An implementation is required to support 504 -- global IPv4 and/or IPv6 addresses, depending 505 -- on its support for IPv4 and IPv6." 507 -- OBJECT swmBGPNeighborInetAddress 508 -- SYNTAX InetAddress (SIZE(4|16)) 509 -- DESCRIPTION 510 -- "An implementation is required to support 511 -- global IPv4 and/or IPv6 addresses, depending 512 -- on its support for IPv4 and IPv6." 514 MODULE -- this module 515 MANDATORY-GROUPS { 516 swmSupportedTunnelGroup, 517 swmEncapsGroup, 518 swmBGPNeighborGroup 519 } 520 ::= { swmCompliances 1 } 522 swmSupportedTunnelGroup OBJECT-GROUP 523 OBJECTS { 524 swmSupportedTunnelType 525 } 526 STATUS current 527 DESCRIPTION 528 "The collection of objects which are used to show 529 what kind of tunnel the AFBR supports." 530 ::= { swmGroups 1 } 532 swmEncapsGroup OBJECT-GROUP 533 OBJECTS { 534 swmEncapsEIPDst, 535 swmEncapsEIPPrefixLength, 536 swmEncapsIIPDst 537 } 538 STATUS current 539 DESCRIPTION 540 "The collection of objects which are used to display 541 softwire mesh encapsulation information." 542 ::= { swmGroups 2 } 544 swmBGPNeighborGroup OBJECT-GROUP 545 OBJECTS { 546 swmBGPNeighborInetAddress, 547 swmBGPNeighborTunnelType 548 } 549 STATUS current 550 DESCRIPTION 551 "The collection of objects which are used to display 552 softwire mesh BGP neighbor information." 553 ::= { swmGroups 3 } 555 END 557 8. Security Considerations 559 The swmMIB module can be used for configuration of certain objects, 560 and anything that can be configured can be incorrectly configured, 561 with potentially disastrous results. Because this MIB module reuses 562 the IP tunnel MIB, the security considerations of the IP tunnel MIB 563 is also applicable to the Softwire mesh MIB. 565 SNMP versions prior to SNMPv3 did not include adequate security. 566 Even if the network itself is secure (for example by using IPsec), 567 even then, there is no control as to who on the secure network is 568 allowed to access and GET/SET (read/change/create/delete) the objects 569 in this MIB module. 571 It is RECOMMENDED that implementers consider the security features as 572 provided by the SNMPv3 framework (see [RFC3410], section 8), 573 including full support for the SNMPv3 cryptographic mechanisms (for 574 authentication and privacy). 576 Further, deployment of SNMP versions prior to SNMPv3 is NOT 577 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 578 enable cryptographic security. It is then a customer/operator's 579 responsibility to ensure that the SNMP entity giving access to an 580 instance of this MIB module is properly configured to give access to 581 the objects only to those principals (users) that have legitimate 582 rights to indeed GET or SET (change/create/delete) them. 584 9. IANA Considerations 586 The MIB module in this document uses the following IANA-assigned 587 OBJECT IDENTIFIER values recorded in the SMI Numbers registry, and 588 the following IANA-assigned tunnelType values recorded in the 589 IANAtunnelType-MIB registry: 591 Descriptor OBJECT IDENTIFIER value 592 ---------- ----------------------- 593 swmMIB { transmission XXX } 595 IANAtunnelType ::= TEXTUAL-CONVENTION 596 SYNTAX INTEGER { 598 softwireMesh ("XX") -- softwire Mesh tunnel 600 } 602 Editor's Note (to be removed prior to publication): the IANA is 603 requested to assign a value for "XXX" under the 'mib-2' subtree and 604 to record the assignment in the SMI Numbers registry. When the 605 assignment has been made, the RFC Editor is asked to replace "XXX" 606 (here and in the MIB module) with the assigned value and to remove 607 this note. 609 10. Acknowledgements 611 The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi 612 Sun, Sheng Jiang, Yu Fu for their valuable comments. 614 11. References 616 11.1. Normative References 618 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 619 Requirement Levels", BCP 14, RFC 2119, March 1997. 621 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 622 Schoenwaelder, Ed., "Structure of Management Information 623 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 625 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 626 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 627 58, RFC 2579, April 1999. 629 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 630 "Conformance Statements for SMIv2", STD 58, RFC 2580, 631 April 1999. 633 [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, "Softwire 634 Problem Statement", RFC 4925, July 2007. 636 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 637 Subsequent Address Family Identifier (SAFI) and the BGP 638 Tunnel Encapsulation Attribute", RFC 5512, April 2009. 640 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh 641 Framework", RFC 5565, June 2009. 643 11.2. Informative References 645 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 646 RFC 2223, October 1997. 648 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 649 MIB", RFC 2863, June 2000. 651 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 652 "Introduction and Applicability Statements for Internet- 653 Standard Management Framework", RFC 3410, December 2002. 655 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 656 June 1999. 658 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005. 660 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB 661 Documents", BCP 111, RFC 4181, September 2005. 663 Authors' Addresses 665 Yong Cui 666 Tsinghua University 667 Department of Computer Science, Tsinghua University 668 Beijing 100084 669 P.R.China 671 Phone: +86-10-6260-3059 672 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 700 Antti Yla-Jaaski 701 Aalto University 702 Konemiehentie 2 703 Espoo 02150 704 Finland 706 Phone: +358-40-5954222 707 EMail: antti.yla-jaaski@aalto.fi