idnits 2.17.1 draft-ietf-manet-smf-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 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 date (April 24, 2009) is 5473 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 1836, but not defined == Missing Reference: 'RFC3411' is mentioned on line 383, but not defined == Missing Reference: 'RFC4001' is mentioned on line 387, but not defined == Missing Reference: 'TODOs' is mentioned on line 1962, but not defined == Outdated reference: A later version (-14) exists of draft-ietf-manet-smf-08 ** Downref: Normative reference to an Experimental draft: draft-ietf-manet-smf (ref. 'I-D.ietf-manet-smf') Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force R. Cole 3 Internet-Draft Johns Hopkins University 4 Intended status: Standards Track J. Macker 5 Expires: October 26, 2009 B. Adamson 6 Naval Research Laboratory 7 S. Harnedy 8 Booz Allen Hamilton 9 April 24, 2009 11 Definition of Managed Objects for the Manet Simplified Multicast 12 Framework Relay Set Process 13 draft-ietf-manet-smf-mib-00 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on October 26, 2009. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents in effect on the date of 45 publication of this document (http://trustee.ietf.org/license-info). 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. 49 Abstract 51 This memo defines a portion of the Management Information Base (MIB) 52 for use with network management protocols in the Internet community. 53 In particular, it describes objects for configuring aspects of the 54 Simplified Multicast Forwarding (SMF) process. The SMF MIB also 55 reports state information, performance metrics, and notifications. 56 In addition to configuration, this additional state and performance 57 information is useful to management stations troubleshooting 58 multicast forwarding problems. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. The Internet-Standard Management Framework . . . . . . . . . . 3 64 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 4.1. SMF Management Model . . . . . . . . . . . . . . . . . . . 4 67 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 69 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 70 5.2. The Capabilities Group . . . . . . . . . . . . . . . . . . 6 71 5.3. The Configuration Group . . . . . . . . . . . . . . . . . 7 72 5.4. The State Group . . . . . . . . . . . . . . . . . . . . . 7 73 5.5. The Performance Group . . . . . . . . . . . . . . . . . . 7 74 5.6. The Notifications Group . . . . . . . . . . . . . . . . . 8 75 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 76 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 77 6.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 78 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 79 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 80 8. Security Considerations . . . . . . . . . . . . . . . . . . . 38 81 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 82 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 41 83 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41 84 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 85 12.1. Normative References . . . . . . . . . . . . . . . . . . . 41 86 12.2. Informative References . . . . . . . . . . . . . . . . . . 41 87 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 42 88 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 42 89 Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 91 1. Introduction 93 This memo defines a portion of the Management Information Base (MIB) 94 for use with network management protocols in the Internet community. 95 In particular, it describes objects for configuring aspects of a 96 process implementing Simplified Multicast Forwarding (SMF) 97 [I-D.ietf-manet-smf]. SMF provides multicast duplicate packet 98 detection (DPD) and supports algorithms for constructing an estimate 99 of a mobile ad hoc network (MANET) Minimum Connected Dominating Set 100 (MCDS) for efficient multicast forwarding. The SMF MIB also reports 101 state information, performance metrics, and notifications. In 102 addition to configuration, this additional state and performance 103 information is useful to management stations troubleshooting 104 multicast forwarding problems. 106 2. The Internet-Standard Management Framework 108 For a detailed overview of the documents that describe the current 109 Internet-Standard Management Framework, please refer to section 7 of 110 RFC 3410 [RFC3410]. 112 Managed objects are accessed via a virtual information store, termed 113 the Management Information Base or MIB. MIB objects are generally 114 accessed through the Simple Network Management Protocol (SNMP). 115 Objects in the MIB are defined using the mechanisms defined in the 116 Structure of Management Information (SMI). This memo specifies a MIB 117 module that is compliant to the SMIv2, which is described in STD 58, 118 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 119 [RFC2580]. 121 3. 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 4. Overview 129 SMF provides methods for implementing DPD-based multicast forwarding 130 with the optional use of CDS-based relay sets. The MCDS is the 131 smallest set of MANET nodes (comprising a connected cluster) which 132 cover all the nodes in the cluster with their transmissions. As the 133 density of the MANET nodes increase, the fraction of nodes required 134 in an MCDS decreases. Using the MCDS as a multicast forwarding set 135 then becomes an efficient multicast mechanism for MANETs. 137 Various algorithms for the construction of estimates of the MCDS 138 exist. The Simplified Multicast Framework [I-D.ietf-manet-smf] 139 describes some of these. It further defines various operational 140 modes for a node which is participating in the collective creation of 141 the MCDS estimates. These modes depend upon the set of related MANET 142 routing and discovery protocols and mechanisms in operation in the 143 specific MANET node. 145 A SMF routers' MIB contains SMF process configuration parameters 146 (e.g. specific CDS algorithm), state information (e.g., current 147 membership in the CDS), performance counters (e.g., packet counters), 148 and notifications. 150 4.1. SMF Management Model 152 This section describes the management model for the SMF node process. 154 Figure 1 (reproduced from Figure 4 of [I-D.ietf-manet-smf]) shows the 155 relationship between the SMF Relay Set selection algorithm and the 156 related algorithms, processes and protocols running in the MANET 157 nodes. The Relay Set Selection Algorithm (RSSA) can rely upon 158 topology information gotten from the MANET Neighborhood Discovery 159 Protocol (NHDP), from the specific MANET routing protocol running on 160 the node, or from Layer 2 information passed up to the higher layer 161 protocol processes. 163 Possible L2 Trigger/Information 164 | 165 | 166 ______________ ______|_____ __________________ 167 | MANET | | | | | 168 | Neighborhood | | Relay Set | | Other Heuristics | 169 | Discovery |------------| Selection |-------| (Preference,etc) | 170 | Protocol | neighbor | Algorithm | | | 171 |______________| info |____________| |__________________| 172 \ / 173 \ / 174 neighbor\ / Dynamic Relay 175 info* \ ____________ / Set Status 176 \ | SMF | / (State, {neighbor info}) 177 `---| Relay Set |---' 178 | State | 179 ---|____________| 180 / 181 / 182 ______________ 183 | Coexistent | 184 | MANET | 185 | Unicast | 186 | Process | 187 |______________| 189 Figure 1: SMF Relay Set Control Options 191 4.2. Terms 193 The following definitions apply throughout this document: 195 o Configuration Objects - switches, tables, objects which are 196 initialized to default settings or set through the management 197 interface defined by this MIB. 199 o Tunable Configuration Objects - objects whose values affect timing 200 or attempt bounds on the SMF RS process. 202 o State Objects - automatically generated values which define the 203 current operating state of the SMF RS process in the router. 205 o Performance Objects - automatically generated values which help an 206 administrator or automated tool to assess the performance of the 207 CDS multicast process on the router and the overall multicasting 208 performance within the MANET routing domain. 210 5. Structure of the MIB Module 212 This section presents the structure of the SMF MIB module. The 213 objects are arranged into the following groups: 215 o smfMIBNotifications - defines the notifications associated with 216 the SMF MIB. 218 o smfMIBObjects - defines the objects forming the basis for the SMF 219 MIB. These objects are divided up by function into the following 220 groups: 222 o 224 * Capabilities Group - This group contains the SMF objects that 225 the device uses to advertise its local capabilities with 226 respect to, e.g., the supported RSSAs. 228 * Configuration Group - This group contains the SMF objects that 229 configure specific options that determine the overall operation 230 of the SMF RSSA and the resulting multicast performance. 232 * State Group - Contains information describing the current state 233 of the SMF RSSA process such as the Neighbor Table. 235 * Performance Group - Contains objects which help to characterize 236 the performance of the SMF RSSA process, typically statistics 237 counters. 239 o smfMIBConformance - defines minimal and full conformance of 240 implementations to this SMF MIB. 242 5.1. Textual Conventions 244 The textual conventions used in the SMF MIB are as follows. The 245 RowStatus textual convention is imported from RFC 2579 [RFC2579]. 247 5.2. The Capabilities Group 249 The SMF device supports a set of capabilities. The list of 250 capabilities which the device can advertise are: 252 o Operational Mode - topology information from NHDP, CDS-aware 253 unicast routing or Cross-layer from Layer 2 255 o SMF RSSA - the specific RSSA operational on the device 257 5.3. The Configuration Group 259 The SMF device is configured with a set of controls. The list of 260 configuration controls for the SMF device follow. 262 o Operational Mode - topology information from NHDP, CDS-aware 263 unicast routing or Cross-layer from Layer 2 265 o SMF RSSA - the specific RSSA operational on the device 267 o Duplicate Packet detection for IPv4 - Identification-based or 268 Hash-based DPD 270 o Duplicate Packet detection for IPv6 - Identification-based or 271 Hash-based DPD 273 o NHDP RSSA Message TLV - if NHDP mode is selected, then is the RSSA 274 Message TLV included in the NHDP exchanges. (Question: Is this 275 and the following two TLVs optional and are they included as a 276 group or independently of one another?) 278 o NHDP RSSA Address Block TLV - if NHDP mode is selected, then is 279 the RSSA Address Block TLV included in the NHDP exchanges. 281 o Router Priority TLV - if NHDP mode is selected, then is the Router 282 Priority TLV included in the NHDP exchanges. 284 5.4. The State Group 286 The State Subtree reports current state information. 288 o Node RSS State - is the node currently in or out of the Relay Set. 290 o Neighbors Table - a table containing current neighbors and their 291 operational RSSA. 293 5.5. The Performance Group 295 The Performance subtree reports primarily counters that relate to SMF 296 RSSA performance. The SMF performance counters consists of per node 297 and per interface objects: (Note: Need to have a discussion of the 298 important and measurable events related to SMF RSSA multicast 299 performance.) (Note: Do we need to break these out by type, i.e., v4 300 versus v6?) 302 o Total multicast packets received - 303 o Total multicast packets forwarded - 305 o Total duplicate multicast packets detected - 307 o Per interface statistics table with the following entries: 309 o 311 * Multicast packets received 313 * Multicast packets forwarded 315 * Duplicate multicast packets detected 317 5.6. The Notifications Group 319 The Notifications Subtree contains the list of notifications 320 supported within the SMF-MIB and their intended purpose or utility. 321 This group is currently empty. 323 6. Relationship to Other MIB Modules 325 [TODO]: The text of this section specifies the relationship of the 326 MIB modules contained in this document to other standards, 327 particularly to standards containing other MIB modules. Definitions 328 imported from other MIB modules and other MIB modules that SHOULD be 329 implemented in conjunction with the MIB module contained within this 330 document are identified in this section. 332 6.1. Relationship to the SNMPv2-MIB 334 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 335 mandatory for all systems, and the objects apply to the entity as a 336 whole. The 'system' group provides identification of the management 337 entity and certain other system-wide data. The SMF-MIB does not 338 duplicate those objects. 340 6.2. Relationship to the IF-MIB 342 [TODO] This section is included as an example; If the MIB module is 343 not an adjunct of the Interface MIB, then this section should be 344 removed. 346 6.3. MIB modules required for IMPORTS 348 [TODO]: Citations are not permitted within a MIB module, but any 349 module mentioned in an IMPORTS clause or document mentioned in a 350 REFERENCE clause is a Normative reference, and must be cited 351 someplace within the narrative sections. If there are imported items 352 in the MIB module, such as Textual Conventions, that are not already 353 cited, they can be cited in text here. Since relationships to other 354 MIB modules should be described in the narrative text, this section 355 is typically used to cite modules from which Textual Conventions are 356 imported. 358 The following SMF-MIB module IMPORTS objects from SNMPv2-SMI 359 [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB 360 [RFC2863] 362 7. Definitions 364 MANET-SMF-MIB DEFINITIONS ::= BEGIN 366 IMPORTS 368 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 369 Counter32, Unsigned32, Integer32, mib-2 370 FROM SNMPv2-SMI -- [RFC2578] 372 TEXTUAL-CONVENTION, RowStatus, TruthValue 373 FROM SNMPv2-TC -- [RFC2579] 375 MODULE-COMPLIANCE, OBJECT-GROUP, 376 NOTIFICATION-GROUP 377 FROM SNMPv2-CONF -- [RFC2580] 379 InterfaceIndexOrZero 380 FROM IF-MIB -- [RFC2863] 382 SnmpAdminString 383 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 385 InetAddress, InetAddressType, 386 InetAddressPrefixLength 387 FROM INET-ADDRESS-MIB -- [RFC4001] 388 ; 390 manetSmfMIB MODULE-IDENTITY 391 LAST-UPDATED "200904211300Z" -- April 21, 2009 392 ORGANIZATION "IETF MANET Working Group" 393 CONTACT-INFO 394 "WG E-Mail: manet@ietf.org 396 WG Chairs: ian.chakeres@gmail.com 397 jmacker@nrl.navy.mil 399 Editors: Robert G. Cole 400 Johns Hopkins University 401 Applied Physics Lab and 402 Department of Computer Science 403 11000 Johns Hopkins Road 404 Room 02-257 405 Laurel, MD 22014 406 USA 407 +1 443 778-6951 408 robert.cole@jhuapl.edu 410 Joseph Macker 411 Naval Research Laboratory 412 Washington, D.C. 20375 413 USA 414 macker@itd.nrl.navy.mil 416 Brian Adamson 417 Naval Research Laboratory 418 Washington, D.C. 20375 419 USA 420 adamson@itd.nrl.navy.mil 422 Sean Harnedy 423 Booz Allen Hamilton 424 333 City Boulevard West 425 Orange, CA 92868 426 USA 427 +1 714 938-3898 428 harnedy_sean@bah.com" 430 DESCRIPTION 431 "This MIB module contains managed object definitions for 432 the Manet SMF RSSA process defined in: Macker, J.(ed.), 433 Simplified Multicast Forwarding draft-ietf-manet-smf-08, 434 November 03, 2008. 436 Copyright (C) The IETF Trust (2008). This version 437 of this MIB module is part of RFC xxxx; see the RFC 438 itself for full legal notices." 440 -- Revision History 441 REVISION "200904211300Z" -- April 21, 2009 442 DESCRIPTION 443 "Updated draft of this MIB module published as 444 draft-ietf-manet-smf-mib-00.txt. A few changes 445 were made in the development of this draft. 446 Specifically, the following changes were made: 447 - Removed the smfGatewayFilterTable from this 448 draft. It is a useful construct, e.g., 449 an IPTABLES-MIB, but might best be handled 450 as a seperate MIB and worked within a 451 security focused working group. 452 - Removed the smfReportsGroup. This capability 453 is being replaced with a new and more general 454 method for offline reporting. This is being 455 worked as a new MIB module refered to as the 456 REPORT-MIB. 457 - Rev'd as a new MANET WG document. 458 " 459 REVISION "200902271300Z" -- February 27, 2009 460 DESCRIPTION 461 "Updated draft of this MIB module published as 462 draft-cole-manet-smf-mib-02.txt. Fairly extensive 463 revisions and additions to this MIB were made 464 in this version. Specifically, the following 465 changes were made in development of this version: 466 - added a Capabilities Group within the Objects 467 Group to allow the device to report supported 468 capabilities, e.g., RSSAs supported. 469 - added administrative status objects for device 470 and interfaces 471 - added multicast address forwarding tables, both 472 for configured (within Configuration Group) and 473 discovered (within the State Group). 474 - added additional Performance counters related 475 to DPD functions. 476 - Split up the performance counters into IPv4 477 and IPv6, for both global and per interface 478 statistics. 479 - Split out the reports capability into a seperate 480 Reports Group under the Objects Group. 481 " 482 REVISION "200811031300Z" -- November 03, 2008 483 DESCRIPTION 484 "Updated draft of this MIB module published as 485 draft-cole-manet-smf-mib-01.txt. Added gateway filter 486 table and reports capabilities following rmon." 487 REVISION "200807071200Z" -- July 07, 2008 488 DESCRIPTION 489 "Initial draft of this MIB module published as 490 draft-cole-manet-smf-mib-00.txt." 491 -- RFC-Editor assigns XXXX 492 ::= { mib-2 998 } -- to be assigned by IANA 494 -- 495 -- TEXTUAL CONVENTIONs 496 -- 498 Status ::= TEXTUAL-CONVENTION 499 STATUS current 500 DESCRIPTION 501 "An indication of the operability of a DYMO 502 function or feature. For example, the status 503 of an interface: 'enabled' indicates that 504 it is willing to communicate with other DYMO routers, 505 and 'disabled' indicates that it is not." 506 SYNTAX INTEGER { 507 enabled (1), 508 disabled (2) 509 } 511 SmfOpModeID ::= TEXTUAL-CONVENTION 512 DISPLAY-HINT "d" 513 STATUS current 514 DESCRIPTION 515 "An index that identifies through reference to a specific 516 SMF operations mode ... 517 " 518 SYNTAX Unsigned32 (1..2147483647) 520 SmfRssaID ::= TEXTUAL-CONVENTION 521 STATUS current 522 DESCRIPTION 523 "An index that identifies through reference to a specific 524 RSSA algorithms ... 525 " 526 SYNTAX INTEGER { 527 cF(1), 528 sMPR(2), 529 eCDS(3), 530 mprCDS(4) 531 -- future(5-127) 532 -- noStdAction(128-239) 533 -- experimental(240-255) 534 } 536 -- 537 -- Top-Level Object Identifier Assignments 538 -- 540 smfMIBNotifications OBJECT IDENTIFIER ::= { manetSmfMIB 0 } 541 smfMIBObjects OBJECT IDENTIFIER ::= { manetSmfMIB 1 } 542 smfMIBConformance OBJECT IDENTIFIER ::= { manetSmfMIB 2 } 544 -- 545 -- smfMIBObjects Assignments: 546 -- smfCapabilitiesGroup - 1 547 -- smfConfigurationGroup - 2 548 -- smfStateGroup - 3 549 -- smfPerformanceGroup - 4 550 -- 552 -- 553 -- smfCapabilitiesGroup 554 -- 555 -- This group contains the SMF objects that identify specific 556 -- capabilities within this device related to SMF functions. 557 -- 559 smfCapabilitiesGroup OBJECT IDENTIFIER ::= { smfMIBObjects 1 } 561 -- 562 -- SMF Operational Mode Capabilities Table 563 -- 565 smfOpModeCapabilitiesTable OBJECT-TYPE 566 SYNTAX SEQUENCE OF SmfOpModeCapabilitiesEntry 567 MAX-ACCESS not-accessible 568 STATUS current 569 DESCRIPTION 570 "The smfOpModeCapabilitiesTable contains ... 571 " 572 ::= { smfCapabilitiesGroup 1 } 574 smfOpModeCapabilitiesEntry OBJECT-TYPE 575 SYNTAX SmfOpModeCapabilitiesEntry 576 MAX-ACCESS not-accessible 577 STATUS current 578 DESCRIPTION 579 "Information about a particular operational 580 mode. 581 " 583 INDEX { smfOpModeCapabilitiesID } 584 ::= { smfOpModeCapabilitiesTable 1 } 586 SmfOpModeCapabilitiesEntry ::= SEQUENCE { 587 smfOpModeCapabilitiesID SmfOpModeID, 588 smfOpModeCapabilitiesName SnmpAdminString, 589 smfOpModeCapabilitiesReference SnmpAdminString 590 } 592 smfOpModeCapabilitiesID OBJECT-TYPE 593 SYNTAX SmfOpModeID 594 MAX-ACCESS not-accessible 595 STATUS current 596 DESCRIPTION 597 "The index for this entry. This object identifies 598 the particular operational mode for this device. 599 " 600 ::= { smfOpModeCapabilitiesEntry 1 } 602 smfOpModeCapabilitiesName OBJECT-TYPE 603 SYNTAX SnmpAdminString 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The textual name of this operational 608 mode. 609 " 610 ::= { smfOpModeCapabilitiesEntry 2 } 612 smfOpModeCapabilitiesReference OBJECT-TYPE 613 SYNTAX SnmpAdminString 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "This object contains a reference to the document that 618 defines this operational mode. 619 " 620 ::= { smfOpModeCapabilitiesEntry 3 } 622 -- 623 -- SMF RSSA Capabilities Table 624 -- 626 smfRssaCapabilitiesTable OBJECT-TYPE 627 SYNTAX SEQUENCE OF SmfRssaCapabilitiesEntry 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "The smfRssaCapabilitiesTable contains ... 632 " 633 ::= { smfCapabilitiesGroup 2 } 635 smfRssaCapabilitiesEntry OBJECT-TYPE 636 SYNTAX SmfRssaCapabilitiesEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "Information about a particular algorithm." 641 INDEX { smfRssaCapabilitiesID } 642 ::= { smfRssaCapabilitiesTable 1 } 644 SmfRssaCapabilitiesEntry ::= SEQUENCE { 645 smfRssaCapabilitiesID SmfRssaID, 646 smfRssaCapabilitiesName SnmpAdminString, 647 smfRssaCapabilitiesReference SnmpAdminString 648 } 650 smfRssaCapabilitiesID OBJECT-TYPE 651 SYNTAX SmfRssaID 652 MAX-ACCESS not-accessible 653 STATUS current 654 DESCRIPTION 655 "The index for this entry. This object identifies 656 the particular algorithm in this MIB module." 657 ::= { smfRssaCapabilitiesEntry 1 } 659 smfRssaCapabilitiesName OBJECT-TYPE 660 SYNTAX SnmpAdminString 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "The textual name of this algorithm. 665 " 666 ::= { smfRssaCapabilitiesEntry 2 } 668 smfRssaCapabilitiesReference OBJECT-TYPE 669 SYNTAX SnmpAdminString 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "This object contains a reference to the document that 674 defines this algorithm. 675 " 676 ::= { smfRssaCapabilitiesEntry 3 } 678 -- 679 -- smfConfigurationGroup 680 -- 681 -- This group contains the SMF objects that configure specific 682 -- options that determine the overall performance and operation 683 -- of the multicast forwarding process for the router device 684 -- and its interfaces. 685 -- 687 smfConfigurationGroup OBJECT IDENTIFIER ::= { smfMIBObjects 2 } 689 smfAdminStatus OBJECT-TYPE 690 SYNTAX Status 691 MAX-ACCESS read-write 692 STATUS current 693 DESCRIPTION 694 "The configured status of the SMF process 695 on this device. Enabled(1) means that 696 SMF is configured to run on this device. 697 Disabled(2) mean that the SMF process 698 is configured off." 699 ::= { smfConfigurationGroup 1 } 701 smfConfiguredOpMode OBJECT-TYPE 702 SYNTAX INTEGER { 703 withNHDP(1), 704 cdsAwareRouting(2), 705 crossLayer(3), 706 other(4) 707 } 708 MAX-ACCESS read-write 709 STATUS current 710 DESCRIPTION 711 "The SMF RSS node operational mode. 713 The value withNHDP(1) indicates ... 714 The value cdsAwareRouting(2) indicates ... 715 The value crossLayer(3) indicates... ." 716 ::= { smfConfigurationGroup 2 } 718 smfConfiguredRssa OBJECT-TYPE 719 SYNTAX SmfRssaID 720 MAX-ACCESS read-write 721 STATUS current 722 DESCRIPTION 723 "The SMF RSS currently operational algorithm. 725 The value cf(1) indicates ... 727 The value experimental(240-255) indicates... ." 728 ::= { smfConfigurationGroup 3 } 730 smfRssaMember OBJECT-TYPE 731 SYNTAX INTEGER { 732 potential(1), 733 always(2), 734 never(3) 735 } 736 MAX-ACCESS read-write 737 STATUS current 738 DESCRIPTION 739 "The RSSA downselects a set of forwarders for 740 multicast forwarding. Sometimes it is useful 741 to force an agent to be included or excluded 742 from the resulting RSS. This object is a 743 switch to allow for this behavior. 745 The value potential(1) allows the selected 746 RSSA to determine if this agent is included 747 or excluded from the RSS. 749 The value always(1) forces the selected 750 RSSA include this agent in the RSS. 752 The value never(3) forces the selected 753 RSSA to exclude this agent from the RSS." 754 ::= { smfConfigurationGroup 4 } 756 smfIpv4Dpd OBJECT-TYPE 757 SYNTAX INTEGER { 758 identificationBased(1), 759 hashBased(2) 760 } 761 MAX-ACCESS read-write 762 STATUS current 763 DESCRIPTION 764 "The current method for IPv4 duplicate packet 765 detection. 766 The value identificationBased(1) 767 indicates... 769 The value 'hashBased(2) indicates... ." 770 ::= { smfConfigurationGroup 5 } 772 smfIpv6Dpd OBJECT-TYPE 773 SYNTAX INTEGER { 774 identificationBased(1), 775 hashBased(2) 776 } 777 MAX-ACCESS read-write 778 STATUS current 779 DESCRIPTION 780 "The current method for IPv6 duplicate packet 781 detection. 782 The value identificationBased(1) 783 indicates... 785 The value 'hashBased(2) indicates... ." 786 ::= { smfConfigurationGroup 6 } 788 smfMaxPktLifetime OBJECT-TYPE 789 SYNTAX Integer32 (0..65535) 790 UNITS "Seconds" 791 MAX-ACCESS read-write 792 STATUS current 793 DESCRIPTION 794 "The estimate of the network packet 795 traversal time. 796 " 797 DEFVAL { 60 } 798 ::= { smfConfigurationGroup 7 } 800 smfDpdMaxMemorySize OBJECT-TYPE 801 SYNTAX Integer32 (0..65535) 802 UNITS "Kilo-Bytes" 803 MAX-ACCESS read-write 804 STATUS current 805 DESCRIPTION 806 "The locally reserved memory for storage 807 of cached DPD records for both IPv4 and 808 IPv6 methods. 809 " 810 DEFVAL { 1024 } 811 ::= { smfConfigurationGroup 8 } 813 smfDpdEntryMaxLifetime OBJECT-TYPE 814 SYNTAX Integer32 (0..65525) 815 UNITS "Seconds" 816 MAX-ACCESS read-write 817 STATUS current 818 DESCRIPTION 819 "The maximum lifetime of a cached DPD 820 record in the local device storage. 822 " 823 DEFVAL { 600 } 824 ::= { smfConfigurationGroup 9 } 826 -- 827 -- Configuration of messages to be included in 828 -- NHDP message exchanges in support of SMF 829 -- operations. 830 -- 832 smfNhdpRssaMesgTLVIncluded OBJECT-TYPE 833 SYNTAX TruthValue 834 MAX-ACCESS read-write 835 STATUS current 836 DESCRIPTION 837 "Indicates whether the associated NHDP messages 838 include the RSSA Message TLV, or not. This 839 is an optional SMF operational setting. 840 The value true(1) indicates that this TLV is 841 included; the value false(2) indicates that it 842 is not included." 843 ::= { smfConfigurationGroup 10 } 845 smfNhdpRssaAddrBlockTLVIncluded OBJECT-TYPE 846 SYNTAX TruthValue 847 MAX-ACCESS read-write 848 STATUS current 849 DESCRIPTION 850 "Indicates whether the associated NHDP messages 851 include the RSSA Address Block TLV, or not. 852 This is an optional SMF operational setting. 853 The value true(1) indicates that this TLV is 854 included; the value false(2) indicates that it 855 is not included." 856 ::= { smfConfigurationGroup 11 } 858 smfNhdpRouterPriorityTLVIncluded OBJECT-TYPE 859 SYNTAX TruthValue 860 MAX-ACCESS read-write 861 STATUS current 862 DESCRIPTION 863 "Indicates whether the associated NHDP messages 864 include the RSSA Router Priority TLV, or not. 865 This is an optional SMF operational setting. 866 The value true(1) indicates that this TLV is 867 included; the value false(2) indicates that it 868 is not included." 870 ::= { smfConfigurationGroup 12 } 872 -- 873 -- Table identifying configured multicast addresses to be forwarded. 874 -- 876 smfConfiguredAddrForwardingTable OBJECT-TYPE 877 SYNTAX SEQUENCE OF SmfConfiguredAddrForwardingEntry 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "The (conceptual) table containing information on multicast 882 addresses which are to be forwarded by the SMF process. 884 Entries in this table are configured. As well, addresses 885 to be forwarded by the SMF device can be dynamically 886 discovered by other means. The corresponding state 887 table, 888 smfDiscoveredAddrForwardingTable contains 889 these additional, dynamically discovered address for 890 forwarding. 892 Each row is associated with a range of multicast 893 addresses, and ranges for different rows must be disjoint. 894 " 895 ::= { smfConfigurationGroup 13 } 897 smfConfiguredAddrForwardingEntry OBJECT-TYPE 898 SYNTAX SmfConfiguredAddrForwardingEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "An entry (conceptual row) containing the information on a 903 particular multicast scope." 904 INDEX { smfConfiguredAddrForwardingAddrType, 905 smfConfiguredAddrForwardingFirstAddr } 906 ::= { smfConfiguredAddrForwardingTable 1 } 908 SmfConfiguredAddrForwardingEntry ::= SEQUENCE { 909 smfConfiguredAddrForwardingAddrType InetAddressType, 910 smfConfiguredAddrForwardingFirstAddr InetAddress, 911 smfConfiguredAddrForwardingLastAddr InetAddress, 912 smfConfiguredAddrForwardingStatus RowStatus 913 } 915 smfConfiguredAddrForwardingAddrType OBJECT-TYPE 916 SYNTAX InetAddressType 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 "The type of the addresses in the multicast forwarding 921 range. Legal values correspond to the subset of 922 address families for which multicast address allocation 923 is supported." 924 ::= { smfConfiguredAddrForwardingEntry 1 } 926 smfConfiguredAddrForwardingFirstAddr OBJECT-TYPE 927 SYNTAX InetAddress (SIZE(0..20)) 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "The first address in the multicast scope range. The type 932 of this address is determined by the value of the 933 smfConfiguredAddrForwardingAddrType object." 934 ::= { smfConfiguredAddrForwardingEntry 2 } 936 smfConfiguredAddrForwardingLastAddr OBJECT-TYPE 937 SYNTAX InetAddress (SIZE(0..20)) 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "The last address in the multicast scope range. 942 The type of this address is determined by the 943 value of the smfConfiguredAddrForwardingAddrType 944 object." 945 ::= { smfConfiguredAddrForwardingEntry 3 } 947 smfConfiguredAddrForwardingStatus OBJECT-TYPE 948 SYNTAX RowStatus 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "The status of this row, by which new entries may be 953 created, or old entries deleted from this table. If write 954 access is supported, the other writable objects in this 955 table may be modified even while the status is `active'." 956 ::= { smfConfiguredAddrForwardingEntry 4 } 958 -- 959 -- SMF Interfaces Configuration Table 960 -- 962 smfInterfaceTable OBJECT-TYPE 963 SYNTAX SEQUENCE OF SmfInterfaceEntry 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The SMF Interface Table describes the SMF 968 interfaces that are participating in the 969 SMF packet forwarding process. The ifIndex is 970 from the interfaces group defined in the 971 Interfaces Group MIB. 972 " 973 REFERENCE 974 "RFC 2863 - The Interfaces Group MIB, McCloghrie, 975 K., and F. Kastenholtz, June 2000." 976 ::= { smfConfigurationGroup 14 } 978 smfInterfaceEntry OBJECT-TYPE 979 SYNTAX SmfInterfaceEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "The SMF interface entry describes one SMF 984 interface as indexed by its ifIndex." 985 INDEX { smfIfIndex } 986 ::= { smfInterfaceTable 1 } 988 SmfInterfaceEntry ::= 989 SEQUENCE { 990 smfIfIndex InterfaceIndexOrZero, 991 smfIfAdminStatus Status, 992 smfIfRowStatus RowStatus 993 } 995 smfIfIndex OBJECT-TYPE 996 SYNTAX InterfaceIndexOrZero 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "The ifIndex for this SMF interface." 1001 ::= { smfInterfaceEntry 1 } 1003 smfIfAdminStatus OBJECT-TYPE 1004 SYNTAX Status 1005 MAX-ACCESS read-create 1006 STATUS current 1007 DESCRIPTION 1008 "The SMF interface's administrative status. 1009 The value 'enabled' denotes that the interface 1010 is running the SMF forwarding process. 1012 The value 'disabled' denotes that the interface is 1013 external to the SMF forwarding process. 1014 " 1015 ::= { smfInterfaceEntry 2 } 1017 smfIfRowStatus OBJECT-TYPE 1018 SYNTAX RowStatus 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "This object permits management of the table 1023 by facilitating actions such as row creation, 1024 construction, and destruction. The value of 1025 this object has no effect on whether other 1026 objects in this conceptual row can be 1027 modified." 1028 ::= { smfInterfaceEntry 3 } 1030 -- 1031 -- smfStateGroup 1032 -- 1033 -- Contains information describing the current state of the SMF 1034 -- process such as the current inclusion in the RS or not. 1035 -- 1037 smfStateGroup OBJECT IDENTIFIER ::= { smfMIBObjects 3 } 1039 smfNodeRsStatusIncluded OBJECT-TYPE 1040 SYNTAX TruthValue 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "The current status of the SMF node in the context of 1045 the MANETs relay set. A value of true(1) indicates 1046 that the node is currently part of the MANET Relay 1047 Set. A value of false(2) indicates that the node 1048 is currently not part of the MANET Relay Set." 1049 ::= { smfStateGroup 1 } 1051 smfDpdMemoryOverflow OBJECT-TYPE 1052 SYNTAX Counter32 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "The number of times that the memory for caching 1057 records for DPD overran and records had to be flushed. 1059 The number of records to be flushed upon a buffer 1060 overflow is an implementation specific decision. 1061 " 1062 ::= { smfStateGroup 2 } 1064 -- 1065 -- Dynamically Discovered Multicast Addr Table 1066 -- 1068 smfDiscoveredAddrForwardingTable OBJECT-TYPE 1069 SYNTAX SEQUENCE OF SmfDiscoveredAddrForwardingEntry 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "The (conceptual) table containing information on multicast 1074 addresses which are to be forwarded by the SMF process. 1076 Entries in this table are configured. As well, addresses 1077 to be forwarded by the SMF device can be dynamically 1078 discovered by other means. The corresponding state 1079 table, smfDiscoveredAddrForwardingTable contains 1080 these additional, dynamically discovered address for 1081 forwarding. 1083 Each row is associated with a range of 1084 multicast addresses, and ranges for different rows 1085 must be disjoint. 1086 " 1087 ::= { smfStateGroup 3 } 1089 smfDiscoveredAddrForwardingEntry OBJECT-TYPE 1090 SYNTAX SmfDiscoveredAddrForwardingEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "An entry (conceptual row) containing the information on a 1095 particular multicast scope." 1096 INDEX { smfDiscoveredAddrForwardingAddrType, 1097 smfDiscoveredAddrForwardingFirstAddr } 1098 ::= { smfDiscoveredAddrForwardingTable 1 } 1100 SmfDiscoveredAddrForwardingEntry ::= SEQUENCE { 1101 smfDiscoveredAddrForwardingAddrType InetAddressType, 1102 smfDiscoveredAddrForwardingFirstAddr InetAddress, 1103 smfDiscoveredAddrForwardingLastAddr InetAddress, 1104 smfDiscoveredAddrForwardingStatus RowStatus 1106 } 1108 smfDiscoveredAddrForwardingAddrType OBJECT-TYPE 1109 SYNTAX InetAddressType 1110 MAX-ACCESS not-accessible 1111 STATUS current 1112 DESCRIPTION 1113 "The type of the addresses in the multicast forwarding 1114 range. Legal values correspond to the subset of 1115 address families for which multicast address allocation 1116 is supported." 1117 ::= { smfDiscoveredAddrForwardingEntry 1 } 1119 smfDiscoveredAddrForwardingFirstAddr OBJECT-TYPE 1120 SYNTAX InetAddress (SIZE(0..20)) 1121 MAX-ACCESS not-accessible 1122 STATUS current 1123 DESCRIPTION 1124 "The first address in the multicast scope range. The type 1125 of this address is determined by the value of the 1126 smfConfiguredAddrForwardingAddrType object." 1127 ::= { smfDiscoveredAddrForwardingEntry 2 } 1129 smfDiscoveredAddrForwardingLastAddr OBJECT-TYPE 1130 SYNTAX InetAddress (SIZE(0..20)) 1131 MAX-ACCESS read-create 1132 STATUS current 1133 DESCRIPTION 1134 "The last address in the multicast scope range. 1135 The type of this address is determined by the 1136 value of the smfConfiguredAddrForwardingAddrType 1137 object." 1138 ::= { smfDiscoveredAddrForwardingEntry 3 } 1140 smfDiscoveredAddrForwardingStatus OBJECT-TYPE 1141 SYNTAX RowStatus 1142 MAX-ACCESS read-create 1143 STATUS current 1144 DESCRIPTION 1145 "The status of this row, by which new entries may be 1146 created, or old entries deleted from this table. If write 1147 access is supported, the other writable objects in this 1148 table may be modified even while the status is `active'." 1149 ::= { smfDiscoveredAddrForwardingEntry 4 } 1151 -- 1152 -- SMF Neighbor Table 1153 -- 1155 smfNeighborTable OBJECT-TYPE 1156 SYNTAX SEQUENCE OF SmfNeighborEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "The SMF NeighborTable describes the 1161 current neighbor nodes, their address 1162 and SMF RSSA and the interface on which 1163 they can be reached." 1164 REFERENCE 1165 "Simplified Multicast Forwarding for MANET 1166 (SMF), Macker, J., February 2008. 1167 Section 7: SMF Neighborhood Discovery 1168 Requirements." 1169 ::= { smfStateGroup 4 } 1171 smfNeighborEntry OBJECT-TYPE 1172 SYNTAX SmfNeighborEntry 1173 MAX-ACCESS not-accessible 1174 STATUS current 1175 DESCRIPTION 1176 "The SMF Neighbor Table contains the 1177 set of one-hop neighbors, the interface 1178 they are reachable on and the SMF RSSA 1179 they are currently running." 1180 INDEX { smfNeighborIpAddrType, 1181 smfNeighborIpAddr, 1182 smfNeighborPrefixLen } 1183 ::= { smfNeighborTable 1 } 1185 SmfNeighborEntry ::= 1186 SEQUENCE { 1187 smfNeighborIpAddrType InetAddressType, 1188 smfNeighborIpAddr InetAddress, 1189 smfNeighborPrefixLen InetAddressPrefixLength, 1190 smfNeighborRSSA SmfRssaID, 1191 smfNeighborNextHopInterface InterfaceIndexOrZero 1192 } 1194 smfNeighborIpAddrType OBJECT-TYPE 1195 SYNTAX InetAddressType 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "The neighbor IP address type." 1201 ::= { smfNeighborEntry 1 } 1203 smfNeighborIpAddr OBJECT-TYPE 1204 SYNTAX InetAddress 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "The neighbor Inet IPv4 or IPv6 address." 1209 ::= { smfNeighborEntry 2 } 1211 smfNeighborPrefixLen OBJECT-TYPE 1212 SYNTAX InetAddressPrefixLength 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "The prefix length. This is a decimal value that 1217 indicates the number of contiguous, higher-order 1218 bits of the address that make up the network 1219 portion of the address." 1220 ::= { smfNeighborEntry 3 } 1222 smfNeighborRSSA OBJECT-TYPE 1223 SYNTAX SmfRssaID 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The current RSSA running on the neighbor. 1228 The list is identical to that described 1229 above for the smfRssa object." 1230 ::= { smfNeighborEntry 4 } 1232 smfNeighborNextHopInterface OBJECT-TYPE 1233 SYNTAX InterfaceIndexOrZero 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The interface ifIndex over which the 1238 neighbor is reachable in one-hop." 1239 ::= { smfNeighborEntry 5 } 1241 -- 1242 -- SMF Performance Group 1243 -- 1244 -- Contains objects which help to characterize the 1245 -- performance of the SMF RSSA process, such as statistics 1246 -- counters. There are two types of SMF RSSA statistics: 1247 -- global counters and per interface counters. 1248 -- 1250 smfPerformanceGroup OBJECT IDENTIFIER ::= { smfMIBObjects 4 } 1252 smfGlobalPerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 1 } 1254 -- 1255 -- IPv4 packet counters 1256 -- 1258 smfIpv4MultiPktsRecvTotal OBJECT-TYPE 1259 SYNTAX Counter32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "A counter of the total number of 1264 multicast IPv4 packets received by the 1265 device." 1266 ::= { smfGlobalPerfGroup 1 } 1268 smfIpv4MultiPktsForwardedTotal OBJECT-TYPE 1269 SYNTAX Counter32 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "A counter of the total number of 1274 multicast IPv4 packets forwarded by the 1275 device." 1276 ::= { smfGlobalPerfGroup 2 } 1278 smfIpv4DuplMultiPktsDetectedTotal OBJECT-TYPE 1279 SYNTAX Counter32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "A counter of the total number of duplicate 1284 multicast IPv4 packets detected by the 1285 device." 1286 ::= { smfGlobalPerfGroup 3 } 1288 smfIpv4DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1289 SYNTAX Counter32 1290 MAX-ACCESS read-only 1291 STATUS current 1292 DESCRIPTION 1293 "A counter of the total number of dropped 1294 multicast IPv4 packets by the 1295 device due to TTL exceeded." 1296 ::= { smfGlobalPerfGroup 4 } 1298 smfIpv4TTLLargerThanPreviousTotal OBJECT-TYPE 1299 SYNTAX Counter32 1300 MAX-ACCESS read-only 1301 STATUS current 1302 DESCRIPTION 1303 "A counter of the total number of IPv4 packets 1304 recieved which have a TTL larger than that 1305 of a previously recived identical packet. 1306 " 1307 ::= { smfGlobalPerfGroup 5 } 1309 -- 1310 -- IPv6 packet counters 1311 -- 1313 smfIpv6MultiPktsRecvTotal OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "A counter of the total number of 1319 multicast IPv6 packets received by the 1320 device." 1321 ::= { smfGlobalPerfGroup 6 } 1323 smfIpv6MultiPktsForwardedTotal OBJECT-TYPE 1324 SYNTAX Counter32 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "A counter of the total number of 1329 multicast IPv6 packets forwarded by the 1330 device." 1331 ::= { smfGlobalPerfGroup 7 } 1333 smfIpv6DuplMultiPktsDetectedTotal OBJECT-TYPE 1334 SYNTAX Counter32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "A counter of the total number of duplicate 1339 multicast IPv6 packets detected by the 1340 device." 1341 ::= { smfGlobalPerfGroup 8 } 1342 smfIpv6DroppedMultiPktsTTLExceededTotal OBJECT-TYPE 1343 SYNTAX Counter32 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "A counter of the total number of dropped 1348 multicast IPv6 packets by the 1349 device due to TTL exceeded." 1350 ::= { smfGlobalPerfGroup 9 } 1352 smfIpv6TTLLargerThanPreviousTotal OBJECT-TYPE 1353 SYNTAX Counter32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "A counter of the total number of IPv6 packets 1358 recieved which have a TTL larger than that 1359 of a previously recived identical packet. 1360 " 1361 ::= { smfGlobalPerfGroup 10 } 1363 smfIpv6HAVAssistsReqdTotal OBJECT-TYPE 1364 SYNTAX Counter32 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "A counter of the total number of IPv6 packets 1369 recieved which required the HAV assist for DPD. 1370 " 1371 ::= { smfGlobalPerfGroup 11 } 1373 smfIpv6DpdHeaderInsertionsTotal OBJECT-TYPE 1374 SYNTAX Counter32 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "A counter of the total number of IPv6 packets 1379 recieved which the device inserted the 1380 DPD header option. 1381 " 1382 ::= { smfGlobalPerfGroup 12 } 1384 -- 1385 -- Per SMF Interface Performance Table 1386 -- 1388 smfInterfacePerfGroup OBJECT IDENTIFIER ::= { smfPerformanceGroup 2 } 1389 smfIpv4InterfacePerfTable OBJECT-TYPE 1390 SYNTAX SEQUENCE OF SmfIpv4InterfacePerfEntry 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "The SMF Interface Performance Table 1395 describes the SMF statistics per 1396 interface." 1397 ::= { smfInterfacePerfGroup 1 } 1399 smfIpv4InterfacePerfEntry OBJECT-TYPE 1400 SYNTAX SmfIpv4InterfacePerfEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "The SMF Interface Performance entry 1405 describes the statistics for a particular 1406 node interface." 1407 INDEX { smfIpv4IfPerfIfIndex } 1408 ::= { smfIpv4InterfacePerfTable 1 } 1410 SmfIpv4InterfacePerfEntry ::= 1411 SEQUENCE { 1412 smfIpv4IfPerfIfIndex InterfaceIndexOrZero, 1413 smfIpv4MultiPktsRecvPerIf Counter32, 1414 smfIpv4MultiPktsForwardedPerIf Counter32, 1415 smfIpv4DuplMultiPktsDetectedPerIf Counter32, 1416 smfIpv4DroppedMultiPktsTTLExceededPerIf Counter32, 1417 smfIpv4TTLLargerThanPreviousPerIf Counter32 1418 } 1420 smfIpv4IfPerfIfIndex OBJECT-TYPE 1421 SYNTAX InterfaceIndexOrZero 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "The ifIndex for this node interface 1426 that is collecting this set of 1427 performance management statistics." 1428 ::= { smfIpv4InterfacePerfEntry 1 } 1430 smfIpv4MultiPktsRecvPerIf OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "A counter of the number of 1436 multicast IP packets received by the 1437 device on this interface." 1438 ::= { smfIpv4InterfacePerfEntry 2 } 1440 smfIpv4MultiPktsForwardedPerIf OBJECT-TYPE 1441 SYNTAX Counter32 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "A counter of the number of 1446 multicast IP packets forwarded by the 1447 device on this interface." 1448 ::= { smfIpv4InterfacePerfEntry 3 } 1450 smfIpv4DuplMultiPktsDetectedPerIf OBJECT-TYPE 1451 SYNTAX Counter32 1452 MAX-ACCESS read-only 1453 STATUS current 1454 DESCRIPTION 1455 "A counter of the number of duplicate 1456 multicast IP packets detected by the 1457 device on this interface." 1458 ::= { smfIpv4InterfacePerfEntry 4 } 1460 smfIpv4DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1461 SYNTAX Counter32 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "A counter of the total number of dropped 1466 multicast IPv4 packets by the 1467 device due to TTL exceeded." 1468 ::= { smfIpv4InterfacePerfEntry 5 } 1470 smfIpv4TTLLargerThanPreviousPerIf OBJECT-TYPE 1471 SYNTAX Counter32 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "A counter of the total number of IPv4 packets 1476 recieved which have a TTL larger than that 1477 of a previously recived identical packet. 1478 " 1479 ::= { smfIpv4InterfacePerfEntry 6 } 1481 smfIpv6InterfacePerfTable OBJECT-TYPE 1482 SYNTAX SEQUENCE OF SmfIpv6InterfacePerfEntry 1483 MAX-ACCESS not-accessible 1484 STATUS current 1485 DESCRIPTION 1486 "The SMF Interface Performance Table 1487 describes the SMF statistics per 1488 interface." 1489 ::= { smfInterfacePerfGroup 2 } 1491 smfIpv6InterfacePerfEntry OBJECT-TYPE 1492 SYNTAX SmfIpv6InterfacePerfEntry 1493 MAX-ACCESS not-accessible 1494 STATUS current 1495 DESCRIPTION 1496 "The SMF Interface Performance entry 1497 describes the statistics for a particular 1498 node interface." 1499 INDEX { smfIpv6IfPerfIfIndex } 1500 ::= { smfIpv6InterfacePerfTable 1 } 1502 SmfIpv6InterfacePerfEntry ::= 1503 SEQUENCE { 1504 smfIpv6IfPerfIfIndex InterfaceIndexOrZero, 1505 smfIpv6MultiPktsRecvPerIf Counter32, 1506 smfIpv6MultiPktsForwardedPerIf Counter32, 1507 smfIpv6DuplMultiPktsDetectedPerIf Counter32, 1508 smfIpv6DroppedMultiPktsTTLExceededPerIf Counter32, 1509 smfIpv6TTLLargerThanPreviousPerIf Counter32, 1510 smfIpv6HAVAssistsReqdPerIf Counter32, 1511 smfIpv6DpdHeaderInsertionsPerIf Counter32 1512 } 1514 smfIpv6IfPerfIfIndex OBJECT-TYPE 1515 SYNTAX InterfaceIndexOrZero 1516 MAX-ACCESS not-accessible 1517 STATUS current 1518 DESCRIPTION 1519 "The ifIndex for this node interface 1520 that is collecting this set of 1521 performance management statistics. 1523 For packets generated locally at 1524 this node, performance counters 1525 are assigned to the loopback 1526 interface. 1527 " 1528 ::= { smfIpv6InterfacePerfEntry 1 } 1530 smfIpv6MultiPktsRecvPerIf OBJECT-TYPE 1531 SYNTAX Counter32 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "A counter of the number of 1536 multicast IP packets received by the 1537 device on this interface." 1538 ::= { smfIpv6InterfacePerfEntry 2 } 1540 smfIpv6MultiPktsForwardedPerIf OBJECT-TYPE 1541 SYNTAX Counter32 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "A counter of the number of 1546 multicast IP packets forwarded by the 1547 device on this interface." 1548 ::= { smfIpv6InterfacePerfEntry 3 } 1550 smfIpv6DuplMultiPktsDetectedPerIf OBJECT-TYPE 1551 SYNTAX Counter32 1552 MAX-ACCESS read-only 1553 STATUS current 1554 DESCRIPTION 1555 "A counter of the number of duplicate 1556 multicast IP packets detected by the 1557 device on this interface." 1558 ::= { smfIpv6InterfacePerfEntry 4 } 1560 smfIpv6DroppedMultiPktsTTLExceededPerIf OBJECT-TYPE 1561 SYNTAX Counter32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "A counter of the number of dropped 1566 multicast IP packets by the 1567 device on this interface due to TTL 1568 exceeded." 1569 ::= { smfIpv6InterfacePerfEntry 5 } 1571 smfIpv6TTLLargerThanPreviousPerIf OBJECT-TYPE 1572 SYNTAX Counter32 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "A counter of the total number of IPv6 packets 1577 recieved which have a TTL larger than that 1578 of a previously recived identical packet. 1579 " 1581 ::= { smfIpv6InterfacePerfEntry 6 } 1583 smfIpv6HAVAssistsReqdPerIf OBJECT-TYPE 1584 SYNTAX Counter32 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "A counter of the total number of IPv6 packets 1589 recieved which required the HAV assist for DPD. 1590 " 1591 ::= { smfIpv6InterfacePerfEntry 7 } 1593 smfIpv6DpdHeaderInsertionsPerIf OBJECT-TYPE 1594 SYNTAX Counter32 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "A counter of the total number of IPv6 packets 1599 recieved which the device inserted the 1600 DPD header option. 1601 " 1602 ::= { smfIpv6InterfacePerfEntry 8 } 1604 -- 1605 -- Notifications 1606 -- 1608 -- Note: What notifications do we want for this MIB? 1610 -- 1611 -- Compliance Statements 1612 -- 1614 -- Note: need to update the Compliance section once the mib 1615 -- objects stablize. 1617 smfCompliances OBJECT IDENTIFIER ::= { smfMIBConformance 1 } 1618 smfMIBGroups OBJECT IDENTIFIER ::= { smfMIBConformance 2 } 1620 smfBasicCompliance MODULE-COMPLIANCE 1621 STATUS current 1622 DESCRIPTION "The basic implementation requirements for 1623 managed network entities that implement 1624 the SMF RSSA process." 1625 MODULE -- this module 1626 MANDATORY-GROUPS { smfCapabObjectsGroup, 1627 smfConfigObjectsGroup } 1628 ::= { smfCompliances 1 } 1630 smfFullCompliance MODULE-COMPLIANCE 1631 STATUS current 1632 DESCRIPTION "The full implementation requirements for 1633 managed network entities that implement 1634 the SMF RSSA process." 1635 MODULE -- this module 1636 MANDATORY-GROUPS { smfCapabObjectsGroup, 1637 smfConfigObjectsGroup, 1638 smfStateObjectsGroup, 1639 smfPerfObjectsGroup 1640 } 1641 ::= { smfCompliances 2 } 1643 -- 1644 -- Units of Conformance 1645 -- 1647 smfCapabObjectsGroup OBJECT-GROUP 1648 OBJECTS { 1649 smfOpModeCapabilitiesName, 1650 smfOpModeCapabilitiesReference, 1652 smfRssaCapabilitiesName, 1653 smfRssaCapabilitiesReference 1654 } 1655 STATUS current 1656 DESCRIPTION 1657 "Set of SMF configuration objects implemented 1658 in this module." 1659 ::= { smfMIBGroups 1 } 1661 smfConfigObjectsGroup OBJECT-GROUP 1662 OBJECTS { 1663 smfAdminStatus, 1664 smfConfiguredOpMode, 1665 smfConfiguredRssa, 1666 smfRssaMember, 1667 smfIpv4Dpd, 1668 smfIpv6Dpd, 1669 smfMaxPktLifetime, 1670 smfDpdMaxMemorySize, 1671 smfDpdEntryMaxLifetime, 1672 smfNhdpRssaMesgTLVIncluded, 1673 smfNhdpRssaAddrBlockTLVIncluded, 1674 smfNhdpRouterPriorityTLVIncluded, 1676 smfConfiguredAddrForwardingLastAddr, 1677 smfConfiguredAddrForwardingStatus, 1679 smfIfAdminStatus, 1680 smfIfRowStatus 1681 } 1682 STATUS current 1683 DESCRIPTION 1684 "Set of SMF configuration objects implemented 1685 in this module." 1686 ::= { smfMIBGroups 2 } 1688 smfStateObjectsGroup OBJECT-GROUP 1689 OBJECTS { 1690 smfNodeRsStatusIncluded, 1691 smfDpdMemoryOverflow, 1693 smfDiscoveredAddrForwardingLastAddr, 1694 smfDiscoveredAddrForwardingStatus, 1696 smfNeighborRSSA, 1697 smfNeighborNextHopInterface 1698 } 1699 STATUS current 1700 DESCRIPTION 1701 "Set of SMF state objects implemented 1702 in this module." 1703 ::= { smfMIBGroups 3 } 1705 smfPerfObjectsGroup OBJECT-GROUP 1706 OBJECTS { 1707 smfIpv4MultiPktsRecvTotal, 1708 smfIpv4MultiPktsForwardedTotal, 1709 smfIpv4DuplMultiPktsDetectedTotal, 1710 smfIpv4DroppedMultiPktsTTLExceededTotal, 1711 smfIpv4TTLLargerThanPreviousTotal, 1713 smfIpv6MultiPktsRecvTotal, 1714 smfIpv6MultiPktsForwardedTotal, 1715 smfIpv6DuplMultiPktsDetectedTotal, 1716 smfIpv6DroppedMultiPktsTTLExceededTotal, 1717 smfIpv6TTLLargerThanPreviousTotal, 1718 smfIpv6HAVAssistsReqdTotal, 1719 smfIpv6DpdHeaderInsertionsTotal, 1721 smfIpv4MultiPktsRecvPerIf, 1722 smfIpv4MultiPktsForwardedPerIf, 1723 smfIpv4DuplMultiPktsDetectedPerIf, 1724 smfIpv4DroppedMultiPktsTTLExceededPerIf, 1725 smfIpv4TTLLargerThanPreviousPerIf, 1727 smfIpv6MultiPktsRecvPerIf, 1728 smfIpv6MultiPktsForwardedPerIf, 1729 smfIpv6DuplMultiPktsDetectedPerIf, 1730 smfIpv6DroppedMultiPktsTTLExceededPerIf, 1731 smfIpv6TTLLargerThanPreviousPerIf, 1732 smfIpv6HAVAssistsReqdPerIf, 1733 smfIpv6DpdHeaderInsertionsPerIf 1734 } 1735 STATUS current 1736 DESCRIPTION 1737 "Set of SMF performance objects implemented 1738 in this module by total and per interface." 1739 ::= { smfMIBGroups 4 } 1741 END 1743 8. Security Considerations 1745 [TODO] Each specification that defines one or more MIB modules MUST 1746 contain a section that discusses security considerations relevant to 1747 those modules. This section MUST be patterned after the latest 1748 approved template (available at 1749 http://www.ops.ietf.org/mib-security.html). Remember that the 1750 objective is not to blindly copy text from the template, but rather 1751 to think and evaluate the risks/vulnerabilities and then state/ 1752 document the result of this evaluation. 1754 [TODO] if you have any read-write and/or read-create objects, please 1755 include the following boilerplate paragraph. 1757 There are a number of management objects defined in this MIB module 1758 with a MAX-ACCESS clause of read-write and/or read-create. Such 1759 objects may be considered sensitive or vulnerable in some network 1760 environments. The support for SET operations in a non-secure 1761 environment without proper protection can have a negative effect on 1762 network operations. These are the tables and objects and their 1763 sensitivity/vulnerability: 1765 o [TODO] writable MIB objects that could be especially disruptive if 1766 abused MUST be explicitly listed by name and the associated 1767 security risks MUST be spelled out; RFC 2669 has a very good 1768 example. 1770 o [TODO] list the writable tables and objects and state why they are 1771 sensitive. 1773 [TODO] else if there are no read-write objects in your MIB module, 1774 use the following boilerplate paragraph. 1776 There are no management objects defined in this MIB module that have 1777 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1778 MIB module is implemented correctly, then there is no risk that an 1779 intruder can alter or create any management objects of this MIB 1780 module via direct SNMP SET operations. 1782 [TODO] if you have any sensitive readable objects, please include the 1783 following boilerplate paragraph. 1785 Some of the readable objects in this MIB module (i.e., objects with a 1786 MAX-ACCESS other than not-accessible) may be considered sensitive or 1787 vulnerable in some network environments. It is thus important to 1788 control even GET and/or NOTIFY access to these objects and possibly 1789 to even encrypt the values of these objects when sending them over 1790 the network via SNMP. These are the tables and objects and their 1791 sensitivity/vulnerability: 1793 o [TODO] you must explicitly list by name any readable objects that 1794 are sensitive or vulnerable and the associated security risks MUST 1795 be spelled out (for instance, if they might reveal customer 1796 information or violate personal privacy laws such as those of the 1797 European Union if exposed to unauthorized parties) 1799 o [TODO] list the tables and objects and state why they are 1800 sensitive. 1802 [TODO] discuss what security the protocol used to carry the 1803 information should have. The following three boilerplate paragraphs 1804 should not be changed without very good reason. Changes will almost 1805 certainly require justification during IESG review. 1807 SNMP versions prior to SNMPv3 did not include adequate security. 1808 Even if the network itself is secure (for example by using IPSec), 1809 even then, there is no control as to who on the secure network is 1810 allowed to access and GET/SET (read/change/create/delete) the objects 1811 in this MIB module. 1813 It is RECOMMENDED that implementers consider the security features as 1814 provided by the SNMPv3 framework (see [RFC3410], section 8), 1815 including full support for the SNMPv3 cryptographic mechanisms (for 1816 authentication and privacy). 1818 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1819 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1820 enable cryptographic security. It is then a customer/operator 1821 responsibility to ensure that the SNMP entity giving access to an 1822 instance of this MIB module is properly configured to give access to 1823 the objects only to those principals (users) that have legitimate 1824 rights to indeed GET or SET (change/create/delete) them. 1826 9. IANA Considerations 1828 [TODO] In order to comply with IESG policy as set forth in 1829 http://www.ietf.org/ID-Checklist.html, every Internet-Draft that is 1830 submitted to the IESG for publication MUST contain an IANA 1831 Considerations section. The requirements for this section vary 1832 depending what actions are required of the IANA. see RFC4181 section 1833 3.5 for more information on writing an IANA clause for a MIB module 1834 document. 1836 [TODO] select an option and provide the necessary details. 1838 Option #1: 1840 The MIB module in this document uses the following IANA-assigned 1841 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1843 Descriptor OBJECT IDENTIFIER value 1844 ---------- ----------------------- 1846 sampleMIB { mib-2 XXX } 1848 Option #2: 1850 Editor's Note (to be removed prior to publication): the IANA is 1851 requested to assign a value for "XXX" under the 'mib-2' subtree and 1852 to record the assignment in the SMI Numbers registry. When the 1853 assignment has been made, the RFC Editor is asked to replace "XXX" 1854 (here and in the MIB module) with the assigned value and to remove 1855 this note. 1857 Note well: prior to official assignment by the IANA, a draft document 1858 MUST use placeholders (such as "XXX" above) rather than actual 1859 numbers. See RFC4181 Section 4.5 for an example of how this is done 1860 in a draft MIB module. 1862 Option #3: 1864 This memo includes no request to IANA. 1866 10. Contributors 1868 This MIB document uses the template authored by D. Harrington which 1869 is based on contributions from the MIB Doctors, especially Juergen 1870 Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. 1872 11. Acknowledgements 1874 12. References 1876 12.1. Normative References 1878 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1879 Interfaces Group MIB", RFC 2863, June 2000. 1881 [RFC3418] Presuhn, R., "Management Information Base (MIB) 1882 for the Simple Network Management Protocol 1883 (SNMP)", STD 62, RFC 3418, December 2002. 1885 [RFC2119] Bradner, S., "Key words for use in RFCs to 1886 Indicate Requirement Levels", BCP 14, RFC 2119, 1887 March 1997. 1889 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1890 Schoenwaelder, Ed., "Structure of Management 1891 Information Version 2 (SMIv2)", STD 58, 1892 RFC 2578, April 1999. 1894 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1895 Schoenwaelder, Ed., "Textual Conventions for 1896 SMIv2", STD 58, RFC 2579, April 1999. 1898 [RFC2580] McCloghrie, K., Perkins, D., and J. 1899 Schoenwaelder, "Conformance Statements for 1900 SMIv2", STD 58, RFC 2580, April 1999. 1902 [I-D.ietf-manet-smf] Macker, J. and S. Team, "Simplified Multicast 1903 Forwarding for MANET", draft-ietf-manet-smf-08 1904 (work in progress), November 2008. 1906 12.2. Informative References 1908 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1909 Stewart, "Introduction and Applicability 1910 Statements for Internet-Standard Management 1911 Framework", RFC 3410, December 2002. 1913 Appendix A. Change Log 1915 Not applicable to draft 00 1917 1. 1919 Appendix B. Open Issues 1921 This section contains the set of open issues related to the 1922 development and design of the SMF-MIB. This section will not be 1923 present in the final version of the MIB and will be removed once all 1924 the open issues have been resolved. 1926 1. Clarify handling of the NHDP TLV message inclusions? 1928 2. Can we develop a capabilities table for the supported RSSA 1929 algorithms? And, if so, can each supported RSSA have a 1930 different set of configuration parameters? 1932 3. Is the Gateway Filter table appropriate for this MIB or should 1933 it be handled in a separate MIB worked elsewhere? How should 1934 this table be indexed and how should it represent the ordering 1935 of the rules (or chains)? Should this be greatly simplified? 1936 How do we handle null values in the rules? --- This has been 1937 removed from the draft-ietf-smf-mib-00 version of the MIB. It 1938 is probably more appropriate for a seperate MIB worked within a 1939 security focused working group. It is a good construct however, 1940 e.g., defining an IPTABLES-MIB. 1942 4. Is it useful to track the effectiveness of the coverage of the 1943 current RSSA? Is it possible to track this? 1945 5. Complete notification group. 1947 6. Complete conformance group. 1949 7. Work on the relationship to other MIBs, IF-MIB, NHDP-MIB. 1951 8. Update the text of the document to reflect the final state of 1952 the MIB. 1954 9. Identify all objects requiring non-volatile storage in their 1955 DESCRIPTION clauses. 1957 10. Incorporate parameter relationship conditions into their 1958 DESCRIPTION clauses. 1960 11. Complete the security analysis and section. 1962 12. Cleanup all the [TODOs] from the MIB template. 1964 Appendix C. 1966 *************************************************************** 1967 * Note to the RFC Editor (to be removed prior to publication) * 1968 * * 1969 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 1970 * of the MIB module point to this draft and are to be * 1971 * assigned by the RFC Editor. * 1972 * * 1973 * 2) The reference to RFCXXX2 throughout this document point * 1974 * to the current draft-ietf-manet-smf-xx.txt. This * 1975 * need to be replaced with the XXX RFC number. * 1976 * * 1977 *************************************************************** 1979 Authors' Addresses 1981 Robert G. Cole 1982 Johns Hopkins University 1983 11100 Johns Hopkins Road, Room 257 1984 Laurel, Maryland 21073 1985 USA 1987 Phone: +1 443 778 6951 1988 EMail: robert.cole@jhuapl.edu 1989 URI: http://www.cs.jhu.edu/~rgcole/ 1991 Joseph Macker 1992 Naval Research Laboratory 1993 Washington, D.C. 20375 1994 USA 1996 EMail: macker@itd.nrl.navy.mil 1998 Brian Adamson 1999 Naval Research Laboratory 2000 Washington, D.C. 20375 2001 USA 2003 EMail: adamson@itd.nrl.navy.mil 2004 Sean Harnedy 2005 Booz Allen Hamilton 2006 333 City Boulevard West 2007 Orange, CA 92868 2008 USA 2010 EMail: harnedy_sean@bah.com