idnits 2.17.1 draft-nguyen-manet-ecds-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 2, 2013) is 4125 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Nguyen 3 Internet-Draft R. Cole 4 Intended status: Experimental US Army CERDEC 5 Expires: July 6, 2013 January 2, 2013 7 Definition of Managed Objects for the MANET Essential Connected 8 Dominating Set (E-CDS) Process 9 draft-nguyen-manet-ecds-mib-02 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols in the Internet community. 15 In particular, it describes objects for configuring aspects of the 16 Essential Connected Dominating Set (E-CDS) process for Mobile Ad-Hoc 17 Networks (MANETs). The ECDS-MIB also reports state information, 18 performance metrics, and notifications. In addition to 19 configuration, the additional state and performance information is 20 useful to operators troubleshooting multicast forwarding problems. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on July 6, 2013. 39 Copyright Notice 41 Copyright (c) 2013 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The Internet-Standard Management Framework . . . . . . . . . . 3 58 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4.1. ECDS-MIB Management Model . . . . . . . . . . . . . . . . 4 61 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 63 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 64 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 6 65 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6 66 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 6 67 5.5. The Notifications Group . . . . . . . . . . . . . . . . . 7 68 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 69 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 70 6.2. Relationship to the SMF-MIB . . . . . . . . . . . . . . . 7 71 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 7 72 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 73 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 74 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 18 75 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 76 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 77 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 78 13. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 19 79 14. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 19 80 15. Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 81 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 82 16.1. Normative References . . . . . . . . . . . . . . . . . . . 20 83 16.2. Informative References . . . . . . . . . . . . . . . . . . 21 85 1. Introduction 87 This memo defines a portion of the Management Information Base (MIB) 88 for use with network management protocols in the Internet community. 89 In particular, it describes objects for configuring aspects of a 90 process implementing the Essential-Connected Dominating Set (E-CDS) 91 [RFC5614] algorithm for Mobile Ad-Hoc Networks (MANETs). The E-CDS 92 process transforms a 2-hop neighborhood topology information set for 93 routers to dynamically perform relay self-election to form a 94 Connected Dominating Set (CDS). The ECDS-MIB, an extension to the 95 SMF-MIB [draft-ietf-manet-smf-mib-06], reports state information, 96 performance metrics, and notifications. In addition to 97 configuration, this additional state and performance information is 98 useful to operators troubleshooting multicast forwarding problems. 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 [RFC3410]. Managed objects are accessed via a virtual information 105 store, termed the Management Information Base or MIB. MIB objects 106 are generally accessed through the Simple Network Management Protocol 107 (SNMP). Objects in the MIB are defined using the mechanisms defined 108 in the Structure of Management Information (SMI). This memo 109 specifies a MIB module that is compliant to the SMIv2, which is 110 described in STD 58, [RFC2578], STD 58, [RFC2579] and STD 58, 111 [RFC2580]. 113 3. Conventions 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 117 document are to be interpreted as described in [RFC2119]. 119 4. Overview 121 The E-CDS algorithm provides method for implementing selection of 122 Multipoint Relay nodes that define an estimate of the Minimum 123 Connected Dominating Set (MCDS) flooding. The MCDS provides an 124 efficient and complete coverage of the nodes comprising the MANET. 125 The packet forwarding rules do not require knowledge of the previous 126 hop. Routers that run Simplified Multicast Forwarding (SMF) 127 [RFC6621] and have E-CDS enabled can be mixed with routers that run 128 SMF and Classic Flooding (CF) enabled without a problem, even when 129 the CF nodes are not participating in the Neighborhood Discovery 130 Protocol (NHDP) [RFC6130]. Another benefit is that packets 131 opportunistically received from non-symmetric neighbors may be 132 forwarded without compromising flooding efficiency or correctness. 134 Furthermore, multicast sources not participating in NHDP may freely 135 inject their traffic and any neighboring E-CDS relays will properly 136 forward the traffic. The E-CDS based relay set selection algorithm 137 is defined in [RFC5614]. 139 4.1. ECDS-MIB Management Model 141 As mentioned in Overview Section, the ECDS-MIB is an extension to 142 SMF-MIB. The SMF-MIB defines the management interfaces into the SMF 143 process. The SMF process is a framework for efficient broadcast 144 capabilities within a MANET. As part of the management interfaces, 145 the SMF-MIB contains configuration objects required for the common 146 management of all CDS processes. The SMF-MIB contains a capabilities 147 table which lists the set of CDS algorithms supported by the specific 148 router. However, the SMF-MIB does not define objects for 149 configuration which are specific to the particular CDS process in 150 question. Hence, it is required that additional MIB modules be 151 defined for each new CDS process implemented on the router. In this 152 sense, these additional MIB-modules extend the SMF-MIB. 154 ______________ _____________ 155 | | | | 156 | Neighborhood | | Relay Set | 157 | Discovery |------------->| Selection | 158 | | neighbor | Algorithm | 159 |______________| info |_____________| 160 \ / 161 \ / 162 neighbor\ /forwarding 163 info* \ ____________ / status 164 \ | | / 165 `-->| Forwarding |<--' 166 | Process | 167 ~~~~~~~~~~~~~~~~>|____________|~~~~~~~~~~~~~~~~~> 168 incoming packet, forwarded packets 169 interface id*, and 170 previous hop* 172 Figure 1: SMF router Architecture. 174 The various CDS algorithms are referred to as Relay Set Selection 175 Algorithm (RSSA) within the SMF specification. The RSSAs can rely 176 upon topology information gotten from the MANET NHDP, from the 177 specific MANET routing protocol running on the node, or from Layer 2 178 information passed up to the higher layer protocol processes. In the 179 ECDS process, nodes can select themselves as relays using a router 180 identifier and a nodal metric known as "Router Priority" for all one- 181 hop and two-hop neighbors. Changing the Router Priority can result 182 in different realizations of CDSs for a given network topology. 184 4.2. Terms 186 The following definitions apply throughout this document: 188 o Control Objects - Objects which are initialized to default 189 settings or set through the management interface defined by this 190 MIB. 192 o State Objects - objects are automatically generated values which 193 define the current operating state of the E-CDS process in the 194 router. 196 o Performance Objects - objects are automatically generated values 197 which help an administrator or automated tool to assess the 198 performance of the CDS multicast process on the router and the 199 overall multicasting performance within the MANET routing domain. 201 5. Structure of the MIB Module 203 This section presents the structure of the ECDS-MIB module. The 204 objects are arranged into the following groups: 206 o ecdsMIBNotifications - defines notifications that are associated 207 with ECDS-MIB 209 o ecdsMIBObjects - defines objects as part of the structure of ECDS- 210 MIB. These objects are divided as follows: 212 * Configuration Group - this group contains ECDS objects that 213 configure specific options that determine the overall operation 214 of ECDS process. 216 * State Group - this group contains ECDS objects that describe 217 the state of the ECDS process. 219 * Performance Group - this groups contains ECDS objects that help 220 operators to characterize the performance of the ECDS process 221 as configured. 223 o ecdsMIBConformance - defines minimal and full conformance of the 224 implementations of this ECDS-MIB module. 226 5.1. Textual Conventions 228 The textual conventions defined within the ECDS-MIB are as follows: 230 o EcdsStatus - is defined within the ECDS-MIB. This contains the 231 current operational status of the E-CDS process on an interface. 233 5.2. The Configuration Group 235 The E-CDS device is configured with a set of controls. Some of the 236 prominent configuration controls for the SMF E-CDS device follow: 238 o E-CDS Operational Mode (ecdsAdminStatus) - indicates that the 239 router has E-CDS enabled. 241 o Router Identifier (ecdsRouterIDAddrType and ecdsRouterID) - 242 indicates router's unique identifier in E-CDS neighborhood. 244 o Router Priority (ecdsConfiguredRouterPriority) - indicates nodal 245 metric value for all one-hop and two-hop neighbors. 247 o Configuration method that computes Router Priority 248 (ecdsConfiguredRtrPriMethod) - indicates what method the Router 249 Priority is computed, i.e., dynamically configured, management 250 configured, or other. 252 5.3. The State Group 254 The state of an ECDS device can be retrieved from the following 255 objects: 257 o E-CDS Configuration State (ecdsOperationStatus) - a state that 258 indicates whether or not the ECDS process is enabled or disabled 259 on the node. 261 o E-CDS Operational State (ecdsCurrentInEcds) - a state that 262 indicates whether or not the node currently in or out of the Relay 263 Set 265 o E-CDS Current Router Priority Value (ecdsCurrentRtRPriValue) - the 266 Router Priority that is currently assigned to the device. 268 5.4. The Performance Group 270 The E-CDS performance counters consist of per node objects: 272 o Counter of times the given node changed into or out of E-CDS 273 (ecdsInEcdsChange). 275 o Counter of times the Router Priority has been changed 276 (ecdsCurrentRtrPriValueChange). 278 5.5. The Notifications Group 280 The Notifications Sub-tree contains the list of notifications 281 supported within the ECDS-MIB and their intended purpose or utility. 282 These include: 284 o ecdsAdminStatusChange - this notification is sent when 285 ecdsAdminStatus is changed. 287 o ecdsConfiguredMemberChange - this notification is sent when 288 cdsConfiguredMember is changed. 290 o ecdsIfRtrPriChange - this notification is sent when ecdsIfRtrPri 291 value is changed. 293 o ecdsRtrPriMethodChange - this notification is sent when 294 ecdsConfiguredRtrPriMethod is changed. 296 6. Relationship to Other MIB Modules 298 6.1. Relationship to the SNMPv2-MIB 300 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 301 mandatory for all systems, and the objects apply to the entity as a 302 whole. The 'system' group provides identification of the management 303 entity and certain other system-wide data. The ECDS-MIB does not 304 duplicate those objects. 306 6.2. Relationship to the SMF-MIB 308 This ECDS-MIB module is an extension of the SMF-MIB module in the 309 sense previously discussed. To manage SMF router with ECDS-enabled, 310 both SMF-MIB and ECDS-MIB implementations are required. 312 6.3. MIB modules required for IMPORTS 314 The textual conventions imported for use in the SMF-MIB are as 315 follows: 317 o The MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, 318 Unsigned32, Integer32 and mib-2 textual conventions are imported 319 from [RFC2578]. 321 o The TEXTUAL-CONVENTION, RowStatus and TruthValue textual 322 conventions are imported from [RFC2579]. 324 o The MODULE-COMPLIANCE, OBJECT-GROUP and NOTIFICATION-GROUP textual 325 conventions are imported from [RFC2580]. 327 o The InetAddress, InetAddressType and InetAddressPrefixLength 328 textual conventions are imported from [RFC4001]. 330 7. Definitions 332 ECDS-MIB DEFINITIONS ::= BEGIN 334 IMPORTS 336 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 337 Counter32, Integer32, experimental 338 FROM SNMPv2-SMI -- [RFC2578] 340 TEXTUAL-CONVENTION, TruthValue 341 FROM SNMPv2-TC -- [RFC2579] 343 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 344 FROM SNMPv2-CONF -- [RFC2580] 346 InetAddress, InetAddressType 347 FROM INET-ADDRESS-MIB -- [RFC4001] 348 ; 350 manetEcdsMIB MODULE-IDENTITY 351 LAST-UPDATED "201301021000Z" -- 2 January 2013 352 ORGANIZATION "IETF MANET Working Group" 353 CONTACT-INFO 354 "WG E-Mail: manet@ietf.org 356 WG Chairs: jmacker@nrl.navy.mil 357 sratliff@cisco.com 359 Editors: James H. Nguyen 360 US Army CERDEC 361 Space and Terrestrial Communications 362 6010 Frankford Road 363 Aberdeen Proving Ground, MD 21005 364 USA 365 +1 443 395-5628 366 Robert G. Cole 367 US Army CERDEC 368 Space and Terrestrial Communications 369 Aberdeen Proving Ground, MD 21005 370 USA 371 +1 443 395-8744" 373 DESCRIPTION 375 "This MIB module contains managed object definitions for the 376 Manet E-CDS process defined in: [RFC5614] 378 Copyright (C) The IETF Trust (2008). This version of this MIB 379 module is part of RFC xxxx; see the RFC itself for full legal 380 notices." 382 -- revision 383 REVISION "201301021000Z" -- 2 January 2013 384 DESCRIPTION 385 "Initial version of this MIB module, 386 published as draft-nguyen-maney-ecds-mib-02.txt." 387 ::= { experimental 9999 } -- to be assigned by IANA 389 -- 390 -- TEXTUAL Conventions 391 -- 393 EcdsStatus ::= TEXTUAL-CONVENTION 394 STATUS current 395 DESCRIPTION 396 "An indication of the operability of a E-CDS function 397 or feature or example, the status of an node: 399 - 'enabled(1)' indicates that it is performing E-CDS 400 functions 401 - 'disabled(2)' indicates that it is not." 402 SYNTAX INTEGER { 403 enabled (1), 404 disabled (2) 405 } 407 -- 408 -- Top-Level Object Identifier Assignments 409 -- 411 ecdsMIBNotifications OBJECT IDENTIFIER ::= { manetEcdsMIB 0 } 412 ecdsMIBObjects OBJECT IDENTIFIER ::= { manetEcdsMIB 1 } 413 ecdsMIBConformance OBJECT IDENTIFIER ::= { manetEcdsMIB 2 } 415 -- 416 -- ecdsMIBObjects Assignments: 417 -- ecdsConfigurationGroup - 1 418 -- ecdsStateGroup - 2 419 -- ecdsPerformanceGroup - 3 420 -- 422 -- 423 -- ecdsConfigurationGroup 424 -- 425 -- This group contains the E-CDS objects that configure specific 426 -- options that determine the overall performance and operation 427 -- of the multicast forwarding process for the router device 428 -- 430 ecdsConfigurationGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 1 } 432 ecdsAdminStatus OBJECT-TYPE 433 SYNTAX EcdsStatus 434 MAX-ACCESS read-write 435 STATUS current 436 DESCRIPTION 437 "The configured status of the E-CDS process on this 438 device. 440 - Enabled(1) means that E-CDS is configured to run on 441 this device. 442 - Disabled(2) mean that the E-CDS process is 443 configured off. 445 This object is persistent and when written the entity 446 should save the change to non-volatile storage. 448 The default value of ecdsAdminStatus is disabled (2)." 449 DEFVAL { disabled } 450 ::= { ecdsConfigurationGroup 1 } 452 ecdsRouterIDAddrType OBJECT-TYPE 453 SYNTAX InetAddressType 454 MAX-ACCESS read-write 455 STATUS current 456 DESCRIPTION 457 "The address type of the address that is used for 458 'ecdsRouterID' of this router as specified in the 459 'ecdsRouterID' text. 461 Only ipv4(1) and ipv6(2) are supported. 463 ecdsRouterIDAddrType can be set by the management 464 station, the ecdsRouterID must be a routable address 465 assigned to this router. If the management station 466 does not assign this value then the router should 467 choose the highest routable IP address assigned to 468 this router. the default value of ecdsRouterAddrType 469 is ipv4. 471 This object is persistent and when written, the 472 entity should save the change to non-volatitle 473 storage." 474 DEFVAL { ipv4 } 475 ::= { ecdsConfigurationGroup 2 } 477 ecdsRouterID OBJECT-TYPE 478 SYNTAX InetAddress (SIZE(4|16)) 479 MAX-ACCESS read-write 480 STATUS current 481 DESCRIPTION 482 "The IP address used as the E-CDS router ID. This can 483 be set by the management station. If not explicitly 484 set, then the device should select a routable IP 485 address assigned to this router for use as the 486 'ecdsRouterID'. The ecdsRouterID is a logical 487 identification that must be consistent across 488 interoperating E-CDS neighborhoods and it is 489 recommended to be chosen as the numerically largest 490 address contained in a node's 'Neighbor Address List' 491 as defined in NHDP. A ecdsRouterID must be unique 492 within the scope of the operating MANET network 493 regardless of the method used for selecting it. 495 This object is persistent and when written the entity 496 should save the change to non-volatile storage." 497 ::= { ecdsConfigurationGroup 3 } 499 ecdsConfiguredRtrPriMethod OBJECT-TYPE 500 SYNTAX INTEGER { 501 dynamicallyConfigured (1), 502 managementConfigured (2), 503 other (3) 504 } 505 MAX-ACCESS read-write 506 STATUS current 507 DESCRIPTION 508 "This object indicates which method Router Priority 509 value is computed." 510 ::= { ecdsConfigurationGroup 4 } 512 ecdsConfiguredRouterPriority OBJECT-TYPE 513 SYNTAX Integer32 514 MAX-ACCESS read-write 515 STATUS current 516 DESCRIPTION 517 "a nodal metric for all 1-hop and 2-hop neighbors. 518 Relay routers use tuple of router identifier and 519 router priority to compute self-election of MPR." 520 ::= { ecdsConfigurationGroup 5 } 522 ecdsConfiguredMember OBJECT-TYPE 523 SYNTAX INTEGER { 524 potential(1), 525 always(2), 526 never(3) 527 } 528 MAX-ACCESS read-write 529 STATUS current 530 DESCRIPTION 531 "The E-CDS downselects a set of forwarders for 532 multicast forwarding. Sometimes, it is useful to force 533 an agent to be included or excluded from the resulting 534 CDS. This object is a switch to allow for this 535 behavior. 537 - The value potential(1) allows the selected E-CDS 538 to determine if this agent is included or 539 excluded from the E-CDS. 541 - The value always(1) forces the selected E-CDS 542 process 544 - The value never(3) forces not to use E-CDS process 546 - The default setting for this object is 547 'potential(1)'. Other settings could pose 548 operational risks under certain conditions. 550 This object is persistent and when written the entity 551 should save the change to non-volatile storage." 552 DEFVAL { potential } 553 ::= { ecdsConfigurationGroup 6 } 554 -- 555 -- E-CDS State Group 556 -- 558 ecdsStateGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 2 } 560 ecdsOperationStatus OBJECT-TYPE 561 SYNTAX EcdsStatus 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The configured status of the E-CDS process on this 566 device. 568 - enabled(1) means that E-CDS is configured to run on 569 this device. 571 - disabled(2) mean that the E-CDS process is 572 configured off. 574 This object is persistent and when written the entity 575 should save the change to non-volatile storage. 577 The default value of ecdsOperationStatus is 578 disabled (2)." 579 DEFVAL { disabled } 580 ::= { ecdsStateGroup 1 } 582 ecdsCurrentRtrPriValue OBJECT-TYPE 583 SYNTAX Integer32 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "current Router Priority value" 588 ::= { ecdsStateGroup 2 } 590 ecdsCurrentInEcds OBJECT-TYPE 591 SYNTAX TruthValue 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "This object indicates that the current node has E-CDS 596 configured and in E-CDS. true(1) means the router has 597 E-CDS configured or false(2) otherwise." 598 ::= { ecdsStateGroup 3 } 599 -- 600 -- E-CDS Performance Group 601 -- 603 ecdsPerformanceGroup OBJECT IDENTIFIER ::= { ecdsMIBObjects 3 } 605 ecdsInEcdsChange OBJECT-TYPE 606 SYNTAX Counter32 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "This object indicates how many times the current 611 node is configured to be in E-CDS." 612 ::= { ecdsPerformanceGroup 1 } 614 ecdsCurrentRtrPriValueChange OBJECT-TYPE 615 SYNTAX Counter32 616 MAX-ACCESS read-only 617 STATUS current 618 DESCRIPTION 619 "This object indicates how many times the Router 620 Priority of the current node has been changed." 621 ::= { ecdsPerformanceGroup 2 } 623 -- 624 -- E-CDS Notification 625 -- 627 ecdsMIBNotifObjects OBJECT IDENTIFIER ::= { ecdsMIBNotifications 0 } 629 -- 630 -- E-CDS Notification Objects 631 -- 633 ecdsAdminStatusChange NOTIFICATION-TYPE 634 OBJECTS { 635 ecdsRouterID, -- the originator of notification 636 ecdsRouterIDAddrType, -- the originator of notification 637 ecdsAdminStatus -- the new status of E-CDS 638 -- process 639 } 640 STATUS current 641 DESCRIPTION 642 "ecdsAdminStatusChange notification is sent when 643 ecdsAdminStatus is changed." 644 ::= { ecdsMIBNotifObjects 1 } 645 ecdsConfiguredMemberChange NOTIFICATION-TYPE 646 OBJECTS { 647 ecdsRouterID, -- the originator of notification 648 ecdsRouterIDAddrType, -- the originator of notification 649 ecdsConfiguredMember -- the indication of being 650 -- included from E-CDS process 651 } 652 STATUS current 653 DESCRIPTION 654 "ecdsConfiguredMemberChange notification is sent when 655 ecdsConfiguredMember is changed." 656 ::= { ecdsMIBNotifObjects 2 } 658 ecdsRtrPriChange NOTIFICATION-TYPE 659 OBJECTS { 660 ecdsRouterID, -- the originator of 661 -- notification 662 ecdsRouterIDAddrType, -- the originator of 663 -- notification 664 ecdsConfiguredRouterPriority -- the priority value 665 } 666 STATUS current 667 DESCRIPTION 668 "ecdsIfRtrPriChange notification is sent when 669 ecdsIfRtrPri value is changed." 670 ::= { ecdsMIBNotifObjects 3 } 672 ecdsRtrPriMethodChange NOTIFICATION-TYPE 673 OBJECTS { 674 ecdsRouterID, -- the originator of 675 -- notification 676 ecdsRouterIDAddrType, -- the originator of 677 -- notification 678 ecdsConfiguredRtrPriMethod -- the method is used to 679 -- calculate router 680 -- priority 681 } 682 STATUS current 683 DESCRIPTION 684 "ecdsRtrPriMethodChange notification is sent when 685 ecdsConfiguredRtrPriMethod is changed." 686 ::= { ecdsMIBNotifObjects 4 } 688 -- 689 -- Compliance Statements 690 -- 692 ecdsCompliances OBJECT IDENTIFIER ::= { ecdsMIBConformance 1 } 693 ecdsMIBGroups OBJECT IDENTIFIER ::= { ecdsMIBConformance 2 } 695 ecdsBasicCompliance MODULE-COMPLIANCE 696 STATUS current 697 DESCRIPTION 698 "The basic implementation requirements for managed 699 network entities that implement the E-CDS process." 700 MODULE -- this module 701 MANDATORY-GROUPS { 702 ecdsConfigurationComplianceGroup 703 } 704 ::= { ecdsCompliances 1 } 706 ecdsFullCompliance MODULE-COMPLIANCE 707 STATUS current 708 DESCRIPTION 709 "The full implementation requirements for managed 710 network entities that implement the E-CDS process." 711 MODULE -- this module 712 MANDATORY-GROUPS { 713 ecdsConfigurationComplianceGroup, 714 ecdsStateComplianceGroup, 715 ecdsPerformanceComplianceGroup, 716 ecdsNotificationsComplianceGroup 717 } 718 ::= { ecdsCompliances 2 } 720 ecdsConfigurationComplianceGroup OBJECT-GROUP 721 OBJECTS { 722 ecdsAdminStatus, 723 ecdsRouterID, 724 ecdsRouterIDAddrType, 725 ecdsConfiguredRouterPriority, 726 ecdsConfiguredMember, 727 ecdsConfiguredRtrPriMethod 728 } 729 STATUS current 730 DESCRIPTION 731 "Set of configuration objects implemented in this 732 module" 733 ::= { ecdsMIBGroups 1 } 735 ecdsStateComplianceGroup OBJECT-GROUP 736 OBJECTS { 737 ecdsOperationStatus, 738 ecdsCurrentRtrPriValue, 739 ecdsCurrentInEcds 740 } 741 STATUS current 742 DESCRIPTION 743 "set of state objects implemented in this module" 744 ::= { ecdsMIBGroups 2 } 746 ecdsPerformanceComplianceGroup OBJECT-GROUP 747 OBJECTS { 748 ecdsInEcdsChange, 749 ecdsCurrentRtrPriValueChange 750 } 751 STATUS current 752 DESCRIPTION 753 "set of performance objects implemented in this 754 module" 755 ::= { ecdsMIBGroups 3 } 757 ecdsNotificationsComplianceGroup NOTIFICATION-GROUP 758 NOTIFICATIONS { 759 ecdsAdminStatusChange, 760 ecdsConfiguredMemberChange, 761 ecdsRtrPriChange, 762 ecdsRtrPriMethodChange 763 } 764 STATUS current 765 DESCRIPTION 766 "set of notification objects implemented in this 767 module" 768 ::= { ecdsMIBGroups 4 } 770 END 772 8. Security Considerations 774 This section discusses security implications of the choices made in 775 this ECDS-MIB module. 777 There are a number of management objects defined in this MIB module 778 with MAX-ACCESS clause of read-write and/or read-create. Such 779 objects maybe considered sensitive or vulnerable in some network 780 environments. The support of SET operations in a non-secure 781 environment without proper protection can have a negative effect on 782 network operations. These are objects and their sensitivity/ 783 vulnerability: 785 o ecdsAdminStatus - this writable configuration object controls the 786 operational status of the SMF ECDS process. If this setting is 787 configured inconsistently across the MANET multicast domain, then 788 the delivery of multicast data maybe also be inconsistent across 789 the domain. 791 o ecdsRouterIDAddrType and ecdsRouterID - these writable 792 configuration objects define the identifier (ID) of the SMF E-CDS 793 process. These objects should be configured with a routable 794 address defined on the local SMF E-CDS device. The ecdsRouterID 795 is the logical identification that must be consistent across 796 interoperating SMF E-CDS neighborhoods. The ecdsRouterID is 797 recommended to be chosen as the numerically largest address 798 contained in a node's 'Neighbor Address List' as defined in NHDP 799 [RFC6130]. 801 o ecdsConfiguredRtrPriMethod - this writable configuration object 802 indicates how the value of Router Priority is computed. 804 o ecdsConfiguredRouterPriority - this writable configuration object 805 indicates a nodal metric for all 1-hop and 2-hop neighbors. Relay 806 routers use tuple of router identifier and router priority to 807 compute self-election of MPR. 809 o ecdsConfiguredMember - this writable configuration object defines 810 a set of forwarders for multicast forwarding. Sometimes, it is 811 useful to force an agent to be included or excluded from the 812 resulting CDS. This object is a switch to allow for this 813 behavior. Mis-configuration of the object may cause the MANET 814 flooding to break due to logical splits in the topology. 816 9. Applicability Statement 818 This document describes objects for configuring Essential Connected 819 Dominating Set (E-CDS) process parameters on a router. This MIB 820 module, denoted ECDS-MIB module, also reports state, performance 821 information and notifications. Since it is an extension of SMF-MIB 822 module, the same applicability examples can be found in SMF-MIB 823 draft. 825 10. IANA Considerations 827 The MIB module in this document uses the following IANA-assigned 828 OBJECT IDENTIFIER value recorded in the SMI Numbers registry: 830 Descriptor OBJECT IDENTIFIER value 831 ---------- ----------------------- 832 ECDS-MIB { experimental 9999 } 833 IANA EDITOR NOTE: please assign 9999 835 11. Contributors 837 This MIB document uses templates authored by D. Harrington which is 838 based on contributions from the MIB Doctors, especially Juergen 839 Schoenwaelder, Dave Perkins, C.M. Heard, and Randy Presuhn. 841 12. Acknowledgements 843 The authors would like to acknowledge the valuable comments from 844 Ulrich Herberg in the early phases of the development of this MIB- 845 module. Further, the authors would like to acknowledge to work of 846 Brian Little and Ryan Morgan on their software development of the 847 ECDS-MIB. 849 13. Change Log 851 This section tracks the revision history in the development of this 852 ECDS-MIB. It will be removed from the final version of this 853 document. 855 These changes were made from draft-nguyen-manet-ecds-mib-01 to 856 draft-nguyen-manet-ecds-mib-02: 858 1. Added references, applicability statement, security 859 considerations, IANA considerations, acknowledgment. 861 2. Added ecdsRouterIDAddrType object to go along with ecdsRouterID 863 These changes were made from draft-nguyen-manet-ecds-mib-00 to 864 draft-nguyen-manet-ecds-mib-01: 866 1. Initial draft 868 14. Open Issues 870 This section contains the set of open issues related to the 871 development and design of the ECDS-MIB. This section will not be 872 present in the final version of the MIB and will be removed once all 873 the open issues have been resolved. 875 1. Does this MIB module need to include the MDR Level as a state 876 object? 878 2. Within the Security Section, we need to include a discussion of 879 the problems caused by mis-configuring the ecdsRouterID, the 880 ecdsConfigured RtrPriMethod, and the ecdsConfiguredRouterPriority 881 objects. 883 3. Once the SMF-MIB module is published, the references to the RFC 884 must be updated. 886 4. A careful review by the working group. 888 15. Title 890 *************************************************************** 891 * Note to the RFC Editor (to be removed prior to publication) * 892 * * 893 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 894 * of the MIB module point to this draft and are to be * 895 * assigned by the RFC Editor. * 896 * * 897 *************************************************************** 899 16. References 901 16.1. Normative References 903 [RFC2119] Bradner, S., "Key words for use in 904 RFCs to Indicate Requirement Levels", 905 BCP 14, RFC 2119, March 1997. 907 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 908 and J. Schoenwaelder, Ed., "Structure 909 of Management Information Version 2 910 (SMIv2)", STD 58, RFC 2578, 911 April 1999. 913 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 914 and J. Schoenwaelder, Ed., "Textual 915 Conventions for SMIv2", STD 58, 916 RFC 2579, April 1999. 918 [RFC2580] McCloghrie, K., Perkins, D., and J. 919 Schoenwaelder, "Conformance Statements 920 for SMIv2", STD 58, RFC 2580, 921 April 1999. 923 [RFC3418] Presuhn, R., "Management Information 924 Base (MIB) for the Simple Network 925 Management Protocol (SNMP)", STD 62, 926 RFC 3418, December 2002. 928 [RFC4001] Daniele, M., Haberman, B., Routhier, 929 S., and J. Schoenwaelder, "Textual 930 Conventions for Internet Network 931 Addresses", RFC 4001, February 2005. 933 [RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad 934 Hoc Network (MANET) Extension of OSPF 935 Using Connected Dominating Set (CDS) 936 Flooding", RFC 5614, August 2009. 938 [RFC6130] Clausen, T., Dearlove, C., and J. 939 Dean, "Mobile Ad Hoc Network (MANET) 940 Neighborhood Discovery Protocol 941 (NHDP)", RFC 6130, April 2011. 943 [RFC6621] Macker, J., "Simplified Multicast 944 Forwarding", RFC 6621, May 2012. 946 [draft-ietf-manet-smf-mib-06] Cole, R., Macker, J., Adamson, B., and 947 S. Harnedy, "Definition of Managed 948 Objects for the Manet Simplified 949 Multicast Framework Relay Set 950 Process", draft-cole-manet-smf-mib-06 951 (work in progress), February 2009. 953 16.2. Informative References 955 [RFC3410] Case, J., Mundy, R., Partain, D., and 956 B. Stewart, "Introduction and 957 Applicability Statements for Internet- 958 Standard Management Framework", 959 RFC 3410, December 2002. 961 Authors' Addresses 963 James H. Nguyen 964 US Army CERDEC 965 6010 Frankford Road 966 Aberdeen Proving Ground, Maryland 21005 967 USA 969 Phone: +1 443 395 5628 970 EMail: james.h.nguyen4.civ@mail.mil 971 Robert G. Cole 972 US Army CERDEC 973 6010 Frankford Road 974 Aberdeen Proving Ground, Maryland 21005 975 USA 977 Phone: +1 443 395 8744 978 EMail: robert.g.cole@us.army.mil