idnits 2.17.1 draft-cole-manet-dymo-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1215. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1226. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1233. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1239. 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 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 14, 2008) is 5886 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: 'TODO' is mentioned on line 1037, but not defined == Missing Reference: 'TODOs' is mentioned on line 1164, but not defined == Outdated reference: A later version (-26) exists of draft-ietf-manet-dymo-12 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole, Ed. 3 Internet-Draft Johns Hopkins University 4 Intended status: Standards Track I. Chakeres 5 Expires: September 15, 2008 Motorola 6 March 14, 2008 8 Definition of Managed Objects for the DYMO Manet Routing Protocol 9 draft-cole-manet-dymo-mib-00 11 Status of This Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on September 15, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2008). 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 44 In particular, it describes objects for configuring aspects of the 45 DYMO routing process. The DYMO MIB also reports state information, 46 performance metrics, and notifications. In addition to 47 configuration, this additional state and performance information is 48 useful to management stations troubleshooting routing problems. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. The Internet-Standard Management Framework . . . . . . . . . . 3 54 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4.1. DYMO Management Model . . . . . . . . . . . . . . . . . . 4 57 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 59 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 60 5.2. The General Information Group . . . . . . . . . . . . . . 4 61 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 5 62 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 5 63 5.4.1. Peers Table . . . . . . . . . . . . . . . . . . . . . 5 64 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 6 65 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 7 66 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 67 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 68 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 69 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 7 70 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 71 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21 72 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 73 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 24 74 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 75 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 76 12.1. Normative References . . . . . . . . . . . . . . . . . . . 24 77 12.2. Informative References . . . . . . . . . . . . . . . . . . 24 78 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25 79 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 25 81 1. Introduction 83 This memo defines a portion of the Management Information Base (MIB) 84 for use with network management protocols in the Internet community. 85 In particular, it describes objects for configuring aspects of a 86 Dynamic MANET On-demand (DYMO) routing [I-D.ietf-manet-dymo] process. 87 The DYMO MIB also reports state information, performance metrics, and 88 notifications. In addition to configuration, this additional state 89 and performance information is useful to management stations 90 troubleshooting routing problems. 92 2. The Internet-Standard Management Framework 94 For a detailed overview of the documents that describe the current 95 Internet-Standard Management Framework, please refer to section 7 of 96 RFC 3410 [RFC3410]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. MIB objects are generally 100 accessed through the Simple Network Management Protocol (SNMP). 101 Objects in the MIB are defined using the mechanisms defined in the 102 Structure of Management Information (SMI). This memo specifies a MIB 103 module that is compliant to the SMIv2, which is described in STD 58, 104 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 105 [RFC2580]. 107 3. Conventions 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 111 document are to be interpreted as described in RFC 2119 [RFC2119]. 113 4. Overview 115 The Dynamic MANET On-demand (DYMO) routing protocol 116 [I-D.ietf-manet-dymo] is intended for use by mobile nodes in 117 wireless, multihop networks. DYMO determines unicast routes among 118 DYMO routers within the network in an on-demand fashion, offering 119 improved convergence in dynamic topologies. 121 A DYMO routers' MIB contains DYMO process configuration parameters 122 (e.g. interfaces), state information (e.g. sequence number), 123 performance metrics (e.g. number of control messages), and 124 notifications. 126 4.1. DYMO Management Model 128 This section describes the management model for the DYMO routing 129 protocol. 131 4.2. Terms 133 The following definitions apply throughout this document: 135 o Configuration Objects - switches, tables, objects which are 136 initialized to default settings or set through the management 137 interface defined by this MIB. 139 o Tunable Configuration Objects - objects whose values affect timing 140 or attempt bounds on the DYMO protocol. 142 o State Objects - automatically generated values which define the 143 current operating state of the DYMO protocol process in the 144 router. 146 o Performance Objects - automatically generated values which help an 147 administrator or automated tool to assess the performance of the 148 DYMO protocol process on the router and the overall routing 149 performance within the DYMO routing domain. 151 5. Structure of the MIB Module 153 This section presents the structure of the DYMO MIB module. The 154 objects are arranged into the following groups: 156 o General Information Group - ... 158 o Configuration Group - ... 160 o State Group - ... 162 o Performance Group - ... 164 o Notification Group - ... 166 5.1. Textual Conventions 168 This section is TBD. 170 5.2. The General Information Group 172 This section provides general information about the capabilities of 173 the routing device. ... 175 5.3. The Configuration Group 177 The DYMO device is configured with a set of controls. The list of 178 configuration controls for the DYMO device follow. 180 Protocol Configuration Parameters and Tables: 182 o DymoInterfaces - If DYMO_INTERFACES is set to other than all, then 183 the DYMO router must be told which interfaces to run the DYMO 184 protocol over. This would be a table containing the interfaces 185 and associated information. 187 o LocalHosts - If RESPONSIBLE_ADDRESSES is set to other than self 188 address, then the DYMO router must be configured with the set of 189 local host addresses for which it is to generate RREP messages. 191 Protocol Tuning Configuration Parameters: 193 o MSG_HOPLIMIT 195 o RREQ_RETRIES 197 Timer Configuration: 199 o ROUTE_TIMEOUT 201 o ROUTE_AGE_MIN_TIMEOUT 203 o ROUTE_AGE_MAX_TIMEOUT 205 o ROUTE_USED_TIMEOUT 207 o ROUTE_DELETE_TIMEOUT 209 5.4. The State Group 211 The State Subtree reports current state information. State 212 information from the DYMO-MIB is contained in the 'Peers' Table. 214 5.4.1. Peers Table 216 The DYMO peers table consists of the following entries: 218 o Network Address (IP address and prefix) 220 o Sequence Number 221 o Next-hop? 223 o Next-hop interface? 225 o Distance? 227 5.5. The Performance Group 229 The Performance subtree reports statistics that relate to DYMO 230 protocol activity. The DYMO performance statistics consists of the 231 following objects and tables: 233 o OwnSequenceNumber 235 o RREQ initiated 237 o RREQ sent 239 o RREQ received 241 o RREP initiated 243 o RREP sent 245 o RREP received 247 o RRER initiated 249 o RRER sent 251 o RRER received 253 o Per interface statistics table with the following entries: 255 * RREQ initiated 257 * RREQ sent 259 * RREQ received 261 * RREP initiated 263 * RREP sent 265 * RREP received 267 * RRER initiated 268 * RRER sent 270 * RRER received 272 5.6. The Notifications Group 274 The Notifications Subtree contains the list of notifications 275 supported within the DYMO-MIB and their intended purpose or utility. 276 This group is currently empty. 278 6. Relationship to Other MIB Modules 280 [TODO]: The text of this section specifies the relationship of the 281 MIB modules contained in this document to other standards, 282 particularly to standards containing other MIB modules. Definitions 283 imported from other MIB modules and other MIB modules that SHOULD be 284 implemented in conjunction with the MIB module contained within this 285 document are identified in this section. 287 6.1. Relationship to the SNMPv2-MIB 289 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 290 mandatory for all systems, and the objects apply to the entity as a 291 whole. The 'system' group provides identification of the management 292 entity and certain other system-wide data. The DYMO-MIB does not 293 duplicate those objects. 295 6.2. Relationship to the IF-MIB 297 [TODO] This section is included as an example; If the MIB module is 298 not an adjunct of the Interface MIB, then this section should be 299 removed. 301 6.3. MIB modules required for IMPORTS 303 [TODO]: Citations are not permitted within a MIB module, but any 304 module mentioned in an IMPORTS clause or document mentioned in a 305 REFERENCE clause is a Normative reference, and must be cited 306 someplace within the narrative sections. If there are imported items 307 in the MIB module, such as Textual Conventions, that are not already 308 cited, they can be cited in text here. Since relationships to other 309 MIB modules should be described in the narrative text, this section 310 is typically used to cite modules from which Textual Conventions are 311 imported. 313 The following DYMO-MIB module IMPORTS objects from SNMPv2-SMI 314 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 315 [RFC2863] 317 7. Definitions 319 DYMO-MIB DEFINITIONS ::= BEGIN 321 -- This MIB is currently in a very initial stage. 322 -- Not all proposed objects have been identified yet 323 -- in the current draft. The MIB have not been 324 -- formally checked by any MIB checkers yet. 326 IMPORTS 327 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 328 Gauge32, Integer32, Unsigned32 329 FROM SNMPv2-SMI --[RFC2578] 330 TEXTUAL-CONVENTION, StorageType, TimeStamp, 331 TruthValue, RowStatus 332 FROM SNMPv2-TC --[RFC2579] 333 MODULE-COMPLIANCE, OBJECT-GROUP 334 FROM SNMPv2-CONF --[STD58] 335 InetAddressType, InetAddress 336 FROM INET-ADDRESS-MIB --[RFC3291] 337 InterfaceIndexOrZero 338 FROM IF-MIB --[RFC2863] 340 dymoMIB MODULE-IDENTITY 341 LAST-UPDATED "200803101500Z" -- March 10, 2008 342 ORGANIZATION "IETF MANET working group" 343 CONTACT-INFO 344 "WG E-Mail: manet@ietf.org 346 WG Chairs: ian.chakeres@gmail.com 347 jmacker@nrl.navy.mil 349 Editors: Robert G. Cole 350 Johns Hopkins University 351 Applied Physics Lab and 352 Department of Computer Science 353 11000 Johns Hopkins Road 354 Room 02-257 355 Laurel, MD 22014 356 USA 357 +1 443 778-6951 358 robert.cole@jhuapl.edu 360 Ian D Chakeres 361 Motorola 362 Bagmane Tech Park 363 66/1, Plot 5, CV Raman Nagar 364 Bangalore, Karnataka 560093 365 India 366 ian.chakeres@gmail.com" 368 DESCRIPTION 369 "This DYMO MIB module is applicable to devices 370 implementing ... 372 Copyright (C) The IETF Trust (2008). This version 373 of this MIB module is part of RFC xxxx; see the RFC 374 itself for full legal notices." 376 -- revision 377 REVISION "200802151500Z" -- February 15, 2008 378 DESCRIPTION 379 "The original draft of this MIB module. Published 380 as draft-cole-dymo-mib-00.txt" 381 REVISION "20080310100Z" -- March 10, 2008 382 DESCRIPTION 383 "The second draft of this MIB module. Simplified 384 MIB significantly; reducing configuration option 385 per the current DYMO protocol draft. Removed 386 overlap with MIB-II." 388 -- RFC-Editor assigns XXXX 389 ::= { manet XX } -- to be assigned by IANA 391 -- 392 -- Object Identifier Assignments 393 -- 394 dymoMIBObjects OBJECT IDENTIFIER ::= { dymoMIB 1 } 395 dymoMIBNotifications OBJECT IDENTIFIER ::= { dymoMIB 2 } 396 dymoMIBConformance OBJECT IDENTIFIER ::= { dymoMIB 3 } 398 -- 399 -- Textual Conventions 400 -- 402 -- 403 -- dymoConfigurationGroup 404 -- 406 -- Contains the DYMO objects which configure specific options 407 -- which determine the overall performance and operation of the 408 -- routing protocol. 410 dymoConfigurationGroup OBJECT IDENTIFIER ::= { dymo 2 } 412 --Configuration Tables 413 --DymoInterfaces 414 --LocalHosts 416 --Protocol Tuning Configuration Parameter Objects: 417 --MSG_HOPLIMIT 418 --RREQ_RETRIES 420 --Timer Configuration Objects 421 --ROUTE_TIMEOUT 422 --ROUTE_AGE_MIN_TIMEOUT 423 --ROUTE_AGE_MAX_TIMEOUT 424 --ROUTE_USED_TIMEOUT 425 --ROUTE_DELETE_TIMEOUT 427 --Configuration Tables: 429 --DymoInterfaces Table 431 dymoIfTable OBJECT-TYPE 432 SYNTAX SEQUENCE OF DymoIfEntry 433 MAX-ACCESS not-accessible 434 STATUS current 435 DESCRIPTION 436 "The DYMO Interface Table describes the interfaces 437 from the viewpoint of DYMO. This should augment the 438 IfGroup and IpGroup from MIB-II." 439 REFERENCE 440 "" 441 ::= { dymoConfigurationGroup 1 } 443 dymoIfEntry OBJECT-TYPE 444 SYNTAX DymoIfEntry 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "The DYMO interface entry describes one interface 449 from the viewpoint of DYMO. 451 Information in this table is persistent and when this object 452 is written the entity SHOULD save the change to non-volatile 453 storage." 454 INDEX { dymoIfIpAddress } 455 ::= { dymoIfTable 1 } 457 DymoIfEntry ::= 458 SEQUENCE { 459 dymoIfIpAddress 460 InetAddress, 461 dymoIfState 462 INTEGER, 463 dymoIfStatus 464 RowStatus 465 } 467 dymoIfIpAddress OBJECT-TYPE 468 SYNTAX InetAddress 469 MAX-ACCESS read-only -- read-only since originally an 470 -- SMIv1 index 471 STATUS current 472 DESCRIPTION 473 "The IP address of this DYMO interface." 474 ::= { dymoIfEntry 1 } 476 dymoIfState OBJECT-TYPE 477 SYNTAX INTEGER { 478 down (1), 479 loopback (2), 480 waiting (3) 481 } 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "The DYMO Interface State." 486 DEFVAL { down } 487 ::= { dymoIfEntry 2 } 489 dymoIfStatus OBJECT-TYPE 490 SYNTAX RowStatus 491 MAX-ACCESS read-create 492 STATUS current 493 DESCRIPTION 494 "This object permits management of the table by 495 facilitating actions such as row creation, 496 construction, and destruction. 498 The value of this object has no effect on 499 whether other objects in this conceptual row can be 500 modified." 501 ::= { dymoIfEntry 3 } 503 --LocalHosts Table 505 -- (insert LocalHosts Table here.) 507 dymoLocalHostsTable OBJECT-TYPE 508 SYNTAX SEQUENCE OF DymoLocalHostsEntry 509 MAX-ACCESS not-accessible 510 STATUS obsolete 511 DESCRIPTION 512 "The Dymo Local Hosts Table identifies 513 the addresses for which responsibility 514 lies within the local DYMO device. 515 It contains a set of IP address ranges 516 specified by an IP address/IP network mask pair. 517 For example, class B address range of X.X.X.X 518 with a network mask of 255.255.0.0 includes all IP 519 addresses from X.X.0.0 to X.X.255.255." 520 REFERENCE 521 "" 522 ::= { dymoConfigurationGroup 2 } 524 dymoLocalHostsEntry OBJECT-TYPE 525 SYNTAX dymoLocalHostsEntry 526 MAX-ACCESS not-accessible 527 STATUS current 528 DESCRIPTION 529 "A single local host address range. 531 Information in this table is persistent and when this object 532 is written the entity SHOULD save the change to non-volatile 533 storage." 534 REFERENCE 535 "" 536 INDEX { dymoLocalHostNet } 537 ::= { dymoLocalHostsTable 1 } 539 DymoLocalHostsEntry ::= 540 SEQUENCE { 541 dymoLocalHostNet InetAddress, 542 dymoLocalHostMask InetAddress, 543 dymoLocalHostStatus RowStatus 544 } 546 dymoLocalHostNet OBJECT-TYPE 547 SYNTAX InetAddress 548 MAX-ACCESS read-create 549 STATUS current 550 DESCRIPTION 551 "The IP address of the net or subnet indicated 552 by the range." 554 REFERENCE 555 "" 556 ::= { dymoLocalHostsEntry 1 } 558 dymoLocalHostMask OBJECT-TYPE 559 SYNTAX InetAddress 560 MAX-ACCESS read-create 561 STATUS current 562 DESCRIPTION 563 "The subnet mask that pertains to the net or 564 subnet." 565 REFERENCE 566 "" 567 ::= { dymoLocalHostsEntry 2 } 569 dymoLocalHostStatus OBJECT-TYPE 570 SYNTAX RowStatus 571 MAX-ACCESS read-create 572 STATUS current 573 DESCRIPTION 574 "This object permits management of the table by 575 facilitating actions such as row creation, 576 construction, and destruction. 578 The value of this object has no effect on 579 whether other objects in this conceptual row can be 580 modified." 581 ::= { dymoLocalHostEntry 3 } 583 --Protocol Tuning Configuration Parameter Objects: 584 -- (insert Protocol Config Parameter Ojects here.) 586 dymoMsgHopLimit OBJECT-TYPE 587 SYNTAX Integer32 (1..1024) 588 UNITS "" 589 MAX-ACCESS read-write 590 STATUS current 591 DESCRIPTION 592 "The DYMO MSG_HOPLIMIT parameter value." 593 REFERENCE 594 "" 595 DEFVAL { 10 } 596 ::= { dymoConfigurationGroup 3 } 598 dymoRreqRetries OBJECT-TYPE 599 SYNTAX Integer32 (1..1024) 600 UNITS "" 601 MAX-ACCESS read-write 602 STATUS current 603 DESCRIPTION 604 "The DYMO RREQ_TRIES parameter value." 605 REFERENCE 606 "" 607 DEFVAL { 3 } 608 ::= { dymoConfigurationGroup 4 } 610 --Timer Configuration Objects 611 -- (insert Timer Configuration Objects here.) 613 dymoRouteTimeout OBJECT-TYPE 614 SYNTAX Integer32 (1..1024) 615 UNITS "seconds" 616 MAX-ACCESS read-write 617 STATUS current 618 DESCRIPTION 619 "The DYMO ROUTE_TIMEOUT parameter value." 620 REFERENCE 621 "" 622 DEFVAL { 5 } 623 ::= { dymoConfigurationGroup 5 } 625 dymoRouteAgeMinimumTimeout OBJECT-TYPE 626 SYNTAX Integer32 (1..1024) 627 UNITS "seconds" 628 MAX-ACCESS read-write 629 STATUS current 630 DESCRIPTION 631 "The DYMO ROUTE_AGE_MIN_TIMEOUT 632 parameter value. The default 633 value for this object should 634 be equal to the 635 dymoNetworkTraversalTime." 636 REFERENCE 637 "" 638 DEFVAL { 1 } 639 ::= { dymoConfigurationGroup 6 } 641 dymoRouteAgeMaximumTimeout OBJECT-TYPE 642 SYNTAX Integer32 (1..1024) 643 UNITS "seconds" 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "The DYMO ROUTE_AGE_MAX_TIMEOUT 648 parameter value." 649 REFERENCE 650 "" 651 DEFVAL { 60 } 652 ::= { dymoConfigurationGroup 7 } 654 dymoRouteUsedTimeout OBJECT-TYPE 655 SYNTAX Integer32 (1..1024) 656 UNITS "seconds" 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "The DYMO ROUTE_USED_TIMEOUT parameter 661 value. The default value for this object 662 should be the 663 dymoRouteTimeout value." 664 REFERENCE 665 "" 666 DEFVAL { 5 } 667 ::= { dymoConfigurationGroup 8 } 669 dymoRouteDeleteTimeout OBJECT-TYPE 670 SYNTAX Integer32 (1..1800) 671 UNITS "seconds" 672 MAX-ACCESS read-write 673 STATUS current 674 DESCRIPTION 675 "The DYMO ROUTE_DELETE_TIMEOUT 676 parameter value. The default 677 setting for this object should 678 be set to 2*dymoRouteTimeout." 679 REFERENCE 680 "" 681 DEFVAL { 10 } 682 ::= { dymoConfigurationGroup 9 } 684 -- 685 -- dymoStateGroup 686 -- 688 -- Contains information describing the current state of the DYMO 689 -- process. 691 dymoStateGroup OBJECT IDENTIFIER ::= { dymo 3 } 692 --General State Information, i.e., 694 --Peers Table 695 --table entries with the following mandatory objects, i.e., 696 --Peers.Address 697 --Peers.SeqNum 698 --Peers.NextHopAddress 699 --Peers.NextHopInterface 700 --Peers.Distance 702 --Peers Table 704 dymoPeersTable OBJECT-TYPE 705 SYNTAX SEQUENCE OF DymoPeersEntry 706 MAX-ACCESS not-accessible 707 STATUS current 708 DESCRIPTION 709 "The DYMO Peers 710 Table describes the current Peers that this 711 devices has overhead within the past xxx seconds." 712 REFERENCE 713 "" 714 ::= { dymoStateGroup 1 } 716 dymoPeersEntry OBJECT-TYPE 717 SYNTAX DymoPeerEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "The DYMO Peers entry describes 722 a peer that this devices has 723 recently overheard." 724 INDEX { dymoPeerIpAddress } -- not sure best 725 -- indexing 726 ::= { dymoPeersTable 1 } 728 DymoPeerEntry ::= 729 SEQUENCE { 730 dymoPeerIpAddress 731 InetAddress, 732 dymoPeerSeqNo 733 INTEGER, 734 dymoPeerNextHopIpAddress 735 InetAddress, 736 dymoPeerNextHopInterface 737 InetAddress, 738 dymoPeerDist 739 INTEGER 740 } 742 dymoPeerIpAddress OBJECT-TYPE 743 SYNTAX InetAddress 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The IP address of the peer." 748 ::= { dymoPeerEntry 1 } 750 dymoPeerSeqNo OBJECT-TYPE 751 SYNTAX INTEGER 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The ..." 756 ::= { dymoPeerEntry 2 } 758 dymoPeerNextHopIPAddress OBJECT-TYPE 759 SYNTAX InetAddress 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The IP address of ..." 764 ::= { dymoPeerEntry 3 } 766 dymoPeerNextHopInterface OBJECT-TYPE 767 SYNTAX InetAddress 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "The IP address of ..." 772 ::= { dymoPeerEntry 4 } 774 dymoPeerDist OBJECT-TYPE 775 SYNTAX INTEGER 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The ..." 780 ::= { dymoPeerEntry 5 } 782 -- 783 -- dymoPerformanceGroup 784 -- 785 -- Contains objects which help to characterize the performance of 786 -- the DYMO process, typically counters. 788 dymoPerformanceGroup OBJECT IDENTIFIER ::= { dymo 4 } 790 --Aggregate Objects 791 --OwnSequenceNumber 792 --RREQ initiated 793 --RREQ sent 794 --RREQ received 795 --RREP initiated 796 --RREP sent 797 --RREP received 798 --RRER initiated 799 --RRER sent 800 --RRER received 802 --Per Interface Table 803 --RREQ initiated 804 --RREQ sent 805 --RREQ received 806 --RREP initiated 807 --RREP sent 808 --RREP received 809 --RRER initiated 810 --RRER sent 811 --RRER received 813 dymoRreqInitiated OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "A counter of the number of 819 RREQ messages that this DYMO 820 device has initiated." 821 ::= { dymoPerformanceGroup 1 } 823 dymoRreqSent OBJECT-TYPE 824 SYNTAX Counter32 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "A counter of the number of 829 RREQ messages that this DYMO 830 device has sent." 831 ::= { dymoPerformanceGroup 2 } 833 dymoRreqReceived OBJECT-TYPE 834 SYNTAX Counter32 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "A counter of the number of 839 RREQ messages that this DYMO 840 device has received." 841 ::= { dymoPerformanceGroup 3 } 843 dymoRrepInitiated OBJECT-TYPE 844 SYNTAX Counter32 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "A counter of the number of 849 RREP messages that this DYMO 850 device has initiated." 851 ::= { dymoPerformanceGroup 4 } 853 dymoRrepSent OBJECT-TYPE 854 SYNTAX Counter32 855 MAX-ACCESS read-only 856 STATUS current 857 DESCRIPTION 858 "A counter of the number of 859 RREP messages that this DYMO 860 device has sent." 861 ::= { dymoPerformanceGroup 5 } 863 dymoRrepReceived OBJECT-TYPE 864 SYNTAX Counter32 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "A counter of the number of 869 RREP messages that this DYMO 870 device has received." 871 ::= { dymoPerformanceGroup 6 } 873 dymoRrerInitiated OBJECT-TYPE 874 SYNTAX Counter32 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "A counter of the number of 879 RRER messages that this DYMO 880 device has initiated." 882 ::= { dymoPerformanceGroup 7 } 884 dymoRrerSent OBJECT-TYPE 885 SYNTAX Counter32 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "A counter of the number of 890 RRER messages that this DYMO 891 device has sent." 892 ::= { dymoPerformanceGroup 8 } 894 dymoRrerReceived OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "A counter of the number of 900 RRER messages that this DYMO 901 device has received." 902 ::= { dymoPerformanceGroup 9 } 904 --Per Interface Table 905 -- include per interface table here (tbd) 907 -- 908 -- Notifications 909 -- 911 --What are the valuable notification information for the 912 --DYMO-MIB? (tbd) 914 -- 915 -- Conformance information 916 -- 918 -- To be determined. 920 dymoCompliances OBJECT IDENTIFIER ::= { dymoConformance 1 } 921 dymoGroups OBJECT IDENTIFIER ::= { dymoConformance 2 } 923 -- Compliance Statements 924 dymoGeneralCompliance MODULE-COMPLIANCE 925 STATUS current 926 DESCRIPTION 927 "A general compliance which allows ...." 928 MODULE -- this module 930 MANDATORY-GROUPS { dymoGeneralGroup } 932 ::= { dymoCompliances 1 } 934 -- 935 -- DYMO Group Compliance 936 -- 938 -- 939 -- Groups 940 -- 942 END 944 8. Security Considerations 946 [TODO] Each specification that defines one or more MIB modules MUST 947 contain a section that discusses security considerations relevant to 948 those modules. This section MUST be patterned after the latest 949 approved template (available at 950 http://www.ops.ietf.org/mib-security.html). Remember that the 951 objective is not to blindly copy text from the template, but rather 952 to think and evaluate the risks/vulnerabilities and then state/ 953 document the result of this evaluation. 955 [TODO] if you have any read-write and/or read-create objects, please 956 include the following boilerplate paragraph. 958 There are a number of management objects defined in this MIB module 959 with a MAX-ACCESS clause of read-write and/or read-create. Such 960 objects may be considered sensitive or vulnerable in some network 961 environments. The support for SET operations in a non-secure 962 environment without proper protection can have a negative effect on 963 network operations. These are the tables and objects and their 964 sensitivity/vulnerability: 966 o [TODO] writeable MIB objects that could be especially disruptive 967 if abused MUST be explicitly listed by name and the associated 968 security risks MUST be spelled out; RFC 2669 has a very good 969 example. 971 o [TODO] list the writable tables and objects and state why they are 972 sensitive. 974 [TODO] else if there are no read-write objects in your MIB module, 975 use the following boilerplate paragraph. 977 There are no management objects defined in this MIB module that have 978 a MAX-ACCESS clause of read-write and/or read-create. So, if this 979 MIB module is implemented correctly, then there is no risk that an 980 intruder can alter or create any management objects of this MIB 981 module via direct SNMP SET operations. 983 [TODO] if you have any sensitive readable objects, please include the 984 following boilerplate paragraph. 986 Some of the readable objects in this MIB module (i.e., objects with a 987 MAX-ACCESS other than not-accessible) may be considered sensitive or 988 vulnerable in some network environments. It is thus important to 989 control even GET and/or NOTIFY access to these objects and possibly 990 to even encrypt the values of these objects when sending them over 991 the network via SNMP. These are the tables and objects and their 992 sensitivity/vulnerability: 994 o [TODO] you must explicitly list by name any readable objects that 995 are sensitive or vulnerable and the associated security risks MUST 996 be spelled out (for instance, if they might reveal customer 997 information or violate personal privacy laws such as those of the 998 European Union if exposed to unathorized parties) 1000 o [TODO] list the tables and objects and state why they are 1001 sensitive. 1003 [TODO] discuss what security the protocol used to carry the 1004 information should have. The following three boilerplate paragraphs 1005 should not be changed without very good reason. Changes will almost 1006 certainly require justification during IESG review. 1008 SNMP versions prior to SNMPv3 did not include adequate security. 1009 Even if the network itself is secure (for example by using IPSec), 1010 even then, there is no control as to who on the secure network is 1011 allowed to access and GET/SET (read/change/create/delete) the objects 1012 in this MIB module. 1014 It is RECOMMENDED that implementers consider the security features as 1015 provided by the SNMPv3 framework (see [RFC3410], section 8), 1016 including full support for the SNMPv3 cryptographic mechanisms (for 1017 authentication and privacy). 1019 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1020 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1021 enable cryptographic security. It is then a customer/operator 1022 responsibility to ensure that the SNMP entity giving access to an 1023 instance of this MIB module is properly configured to give access to 1024 the objects only to those principals (users) that have legitimate 1025 rights to indeed GET or SET (change/create/delete) them. 1027 9. IANA Considerations 1029 [TODO] In order to comply with IESG policy as set forth in 1030 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 1031 submitted to the IESG for publication MUST contain an IANA 1032 Considerations section. The requirements for this section vary 1033 depending what actions are required of the IANA. see RFC4181 section 1034 3.5 for more information on writing an IANA clause for a MIB module 1035 document. 1037 [TODO] select an option and provide the necessary details. 1039 Option #1: 1041 The MIB module in this document uses the following IANA-assigned 1042 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1044 Descriptor OBJECT IDENTIFIER value 1045 ---------- ----------------------- 1047 sampleMIB { mib-2 XXX } 1049 Option #2: 1051 Editor's Note (to be removed prior to publication): the IANA is 1052 requested to assign a value for "XXX" under the 'mib-2' subtree and 1053 to record the assignment in the SMI Numbers registry. When the 1054 assignment has been made, the RFC Editor is asked to replace "XXX" 1055 (here and in the MIB module) with the assigned value and to remove 1056 this note. 1058 Note well: prior to official assignment by the IANA, a draft document 1059 MUST use placeholders (such as "XXX" above) rather than actual 1060 numbers. See RFC4181 Section 4.5 for an example of how this is done 1061 in a draft MIB module. 1063 Option #3: 1065 This memo includes no request to IANA. 1067 10. Contributors 1069 This MIB document uses the template authored by D. Harrington which 1070 is based on contributions from the MIb Doctors, especially Juergen 1071 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1073 11. Acknowledgements 1075 12. References 1077 12.1. Normative References 1079 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1080 Interfaces Group MIB", RFC 2863, June 2000. 1082 [RFC3418] Presuhn, R., "Management Information Base 1083 (MIB) for the Simple Network Management 1084 Protocol (SNMP)", STD 62, RFC 3418, 1085 December 2002. 1087 [RFC2119] Bradner, S., "Key words for use in RFCs to 1088 Indicate Requirement Levels", BCP 14, 1089 RFC 2119, March 1997. 1091 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1092 Schoenwaelder, Ed., "Structure of Management 1093 Information Version 2 (SMIv2)", STD 58, 1094 RFC 2578, April 1999. 1096 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1097 Schoenwaelder, Ed., "Textual Conventions for 1098 SMIv2", STD 58, RFC 2579, April 1999. 1100 [RFC2580] McCloghrie, K., Perkins, D., and J. 1101 Schoenwaelder, "Conformance Statements for 1102 SMIv2", STD 58, RFC 2580, April 1999. 1104 [I-D.ietf-manet-dymo] Chakeres, I. and C. Perkins, "Dynamic MANET 1105 On-demand (DYMO) Routing", 1106 draft-ietf-manet-dymo-12 (work in progress), 1107 February 2008. 1109 12.2. Informative References 1111 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1112 Stewart, "Introduction and Applicability 1113 Statements for Internet-Standard Management 1114 Framework", RFC 3410, December 2002. 1116 Appendix A. Change Log 1118 The following changes have been made from draft-cole-dymo-mib-00 . 1120 Not applicable to draft 00 1122 1. 1124 Appendix B. Open Issues 1126 This section contains the set of open issues related to the 1127 development and design of the DYMO-MIB. This section will not be 1128 present in the final version of the MIB and will be removed once all 1129 the open issues have been resolved. 1131 1. Agree on set of configuration options to be supported, e.g., 1132 Gateway config, local hosts, responsible addresses, etc. 1134 2. Will DYMO require an MANET_ID (Instance ID) for running multiple 1135 DYMO processes over the same interfaces? 1137 3. Is support for addresses-less interfaces required? 1139 4. Incorporate MIB-II IfGroup interworking with DymoIfTable. 1141 5. Incorporate MIB-II IpGroup interworking with DymoIfTable. 1143 6. Incorporate MIB-II IpForwardingGroup interworking with 1144 DymoRIBTable. 1146 7. What performance objects are of interest and utility? 1148 8. What notifications are of interest and utility? 1150 9. Work on the Security Section. This MIB does have settable 1151 objects, but not sensitive objects (true?). 1153 10. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 1155 11. Identify all objects requiring non-volatile storage in their 1156 DESCRIPTION clauses. 1158 12. Incorporate parameter relationship conditions into their 1159 DESCRIPTION clauses. 1161 13. Work up a better management model in the textual description of 1162 the DYMO-MIB. Perhaps include management usecases. 1164 14. Cleanup all the [TODOs] from the MIB template. 1166 *************************************************************** 1167 * Note to the RFC Editor (to be removed prior to publication) * 1168 * * 1169 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 1170 * of the MIB module point to this draft and are to be * 1171 * assigned by the RFC Editor. * 1172 * * 1173 * 2) The reference to RFCXXX2 throughout this document point * 1174 * to the current draft-cole-dymo-xx.txt. This * 1175 * need to be replaced with the XXX RFC number. * 1176 * * 1177 *************************************************************** 1179 Authors' Addresses 1181 Robert G. Cole (editor) 1182 Johns Hopkins University 1183 11100 Johns Hopkins Road, Room 257 1184 Laurel, Maryland 21073 1185 USA 1187 Phone: +1 443 778 6951 1188 EMail: robert.cole@jhuapl.edu 1189 URI: http://www.cs.jhu.edu/~rgcole/ 1191 Ian D Chakeres 1192 Motorola 1193 Bagmane Tech Park 1194 66/1, Plot 5, CV Raman Nagar 1195 Bangalore, Karnataka 560093 1196 India 1198 EMail: ian.chakeres@gmail.com 1199 URI: http://www.ianchak.com/ 1201 Full Copyright Statement 1203 Copyright (C) The IETF Trust (2008). 1205 This document is subject to the rights, licenses and restrictions 1206 contained in BCP 78, and except as set forth therein, the authors 1207 retain all their rights. 1209 This document and the information contained herein are provided on an 1210 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1211 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1212 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1213 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1214 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1215 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1217 Intellectual Property 1219 The IETF takes no position regarding the validity or scope of any 1220 Intellectual Property Rights or other rights that might be claimed to 1221 pertain to the implementation or use of the technology described in 1222 this document or the extent to which any license under such rights 1223 might or might not be available; nor does it represent that it has 1224 made any independent effort to identify any such rights. Information 1225 on the procedures with respect to rights in RFC documents can be 1226 found in BCP 78 and BCP 79. 1228 Copies of IPR disclosures made to the IETF Secretariat and any 1229 assurances of licenses to be made available, or the result of an 1230 attempt made to obtain a general license or permission for the use of 1231 such proprietary rights by implementers or users of this 1232 specification can be obtained from the IETF on-line IPR repository at 1233 http://www.ietf.org/ipr. 1235 The IETF invites any interested party to bring to its attention any 1236 copyrights, patents or patent applications, or other proprietary 1237 rights that may cover technology that may be required to implement 1238 this standard. Please address the information to the IETF at 1239 ietf-ipr@ietf.org. 1241 Acknowledgement 1243 Funding for the RFC Editor function is provided by the IETF 1244 Administrative Support Activity (IASA).