idnits 2.17.1 draft-ietf-mext-nemo-mib-06.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? -- It seems you're using the 'non-IETF stream' Licence Notice instead 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 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 (January 31, 2009) is 5558 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) ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MEXT Working Group Sri Gundavelli 3 Internet-Draft Cisco 4 Intended status: Standards Track Glenn M. Keeni 5 Expires: August 4, 2009 Cyber Solutions 6 Kazuhide Koide 7 Tohoku University 8 Kenichi Nagami 9 INTEC NetCore 10 January 31, 2009 12 NEMO Management Information Base 13 draft-ietf-mext-nemo-mib-06 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 August 4, 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 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. 50 Abstract 52 This memo defines a portion of the Management Information Base (MIB), 53 the network mobility support (NEMO) MIB, for use with network 54 management protocols in the Internet community. In particular, the 55 NEMO MIB will be used to monitor and control a Mobile IPv6 node with 56 NEMO functionality. 58 Table of Contents 60 1. The Internet-Standard Management Framework . . . . . . . . . . 3 61 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3 63 2.2. Relationship to other MIB modules . . . . . . . . . . . . 3 64 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 65 2.4. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2.5. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . 5 67 2.6. IANA Considerations . . . . . . . . . . . . . . . . . . . 41 68 2.7. Security Considerations . . . . . . . . . . . . . . . . . 41 69 2.8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 42 70 2.9. References . . . . . . . . . . . . . . . . . . . . . . . . 42 71 2.10. Normative References . . . . . . . . . . . . . . . . . . . 42 72 2.11. Informative References . . . . . . . . . . . . . . . . . . 43 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 75 1. The Internet-Standard Management Framework 77 For a detailed overview of the documents that describe the current 78 Internet-Standard Management Framework, please refer to section 7 of 79 RFC 3410 [RFC3410]. 81 Managed objects are accessed via a virtual information store, termed 82 the Management Information Base or MIB. MIB objects are generally 83 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a MIB 87 module that is compliant to the SMIv2, which is described in STD 58, 88 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 89 [RFC2580]. 91 2. Overview 93 2.1. The Mobile IPv6 Protocol and NEMO entities 95 Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes 96 to remain reachable while moving around in the IPv6 Internet. 97 Network Mobility Basic Support (NEMO) [RFC3963] is an extension to 98 the Mobile IPv6 protocol which facilitates the movement of an entire 99 network. The goals of Network Mobility support and related 100 terminology are discussed in [RFC4886] and [RFC4885], respectively. 102 Typically mobile routers implement NEMO functionality for achieving 103 network mobility. However, a mobile router may also function as a 104 mobile node. In the context of this document, an entity that 105 implements the NEMO protocol is a NEMO entity. 107 This document defines a set of managed objects (MOs) that can be used 108 to monitor and control NEMO entities. 110 2.2. Relationship to other MIB modules 112 This document focuses on the management of a NEMO entity. It is 113 assumed that implementations will support ifTable from IF-MIB 114 [RFC2863]. The MOBILEIPV6-MIB [RFC4295] defines the managed objects 115 for a mobile node. Implementations supporting both the mobile node 116 and NEMO functionality SHOULD implement the managed objects defined 117 for the NEMO entities and mobile nodes from both the MOBILEIPV6-MIB 118 and NEMO-MIB. NEMO-MIB uses the textual conventions defined in the 119 INET-ADDRESS-MIB [RFC4001]. 121 2.3. Terminology 123 The terminology used in this document is consistent with the 124 definitions used in the Mobile IPv6 protocol specification [RFC3775] 125 and the NEMO Basic Support specification [RFC3963]. 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 129 "OPTIONAL" in this document are to be interpreted as described in BCP 130 14, RFC 2119 [RFC2119]. 132 2.4. MIB Design 134 The NEMO MIB comprises of the following groups of definitions: 136 - nemoCore: a generic group containing objects that are common to all 137 the NEMO entities. 139 - nemoHa: this group models the home agent service. It is composed 140 of objects specific to the services and associated advertisement 141 parameters offered by the home agent on each of its links. It also 142 contains objects pertaining to the maintenance of the home agent list 143 on each of the links on which the service is offered. 145 - nemoMr: this group models the mobile router service. It is 146 composed of objects specific to the Dynamic Home Agent discovery 147 function and related parameters. It also contains objects that 148 record the movement of the mobile router. 150 - nemoNotifications: defines the set of notifications that will be 151 used to asynchronously monitor the NEMO entities. 153 The tables contained in the above groups are as follows: 155 nemoBindingCacheTable : models the binding cache on the home agent 156 and correspondent node. It contains details of the Binding Update 157 requests that have been received and accepted. 159 nemoMrEgressIfTable : contains information on the configured egress 160 interfaces. 162 nemoMrBLTable : models the Binding Update List on the mobile router. 163 It contains information about the registration requests sent by the 164 mobile router and the corresponding results. 166 nemoHaCounterTable : contains registration statistics for all mobile 167 routers registered with the home agent. 169 nemoHaMobileNetworkPrefixTable : contains the list of the mobile 170 network prefixes that are maintained by the home agent. 172 2.5. The NEMO MIB 174 NEMO-MIB DEFINITIONS ::= BEGIN 175 IMPORTS 176 MODULE-IDENTITY, mib-2, Unsigned32, Counter32, 177 Gauge32, 178 OBJECT-TYPE, NOTIFICATION-TYPE 179 FROM SNMPv2-SMI 180 TEXTUAL-CONVENTION, 181 TruthValue, DateAndTime, TimeStamp 182 FROM SNMPv2-TC 183 SnmpAdminString 184 FROM SNMP-FRAMEWORK-MIB 185 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 186 FROM SNMPv2-CONF 187 InetAddressType, InetAddress, InetAddressPrefixLength 188 FROM INET-ADDRESS-MIB 189 InterfaceIndex 190 FROM IF-MIB 191 mip6BindingHomeAddressType, mip6BindingHomeAddress, 192 mip6MnBLEntry, mip6BindingCacheEntry, 193 mip6MnBLCOAType, mip6MnBLCOA 194 FROM MOBILEIPV6-MIB 195 ; 197 nemoMIB MODULE-IDENTITY 198 LAST-UPDATED "200901310000Z" -- 31st January, 2009 199 ORGANIZATION "IETF MEXT Working Group" 200 CONTACT-INFO 201 " Sri Gundavelli 202 Postal: Cisco 203 170 W.Tasman Drive, 204 San Jose, CA 95134 205 USA 206 Tel: +1-408-527-6109 207 Email: sgundave@cisco.com 208 Glenn Mansfield Keeni 209 Postal: Cyber Solutions Inc. 210 6-6-3, Minami Yoshinari 211 Aoba-ku, Sendai, Japan 989-3204. 212 Tel: +81-22-303-4012 213 Fax: +81-22-303-4015 214 E-mail: glenn@cysols.com 216 Kenichi Nagami 217 Postal: INTEC NetCore Inc. 218 1-3-3, Shin-suna 219 Koto-ku, Tokyo, 135-0075 220 Japan 221 Tel: +81-3-5665-5069 222 E-mail: nagami@inetcore.com 224 Kazuhide Koide 225 Postal: Tohoku University 226 Research Institute of Electrical Communication, 227 Tohoku University. 228 2-1-1 Katahira, Aoba-ku, 229 Sendai, Miyagi, Japan 980-8577. 230 Tel: +81-22-217-5455 231 E-mail: koide@shiratori.riec.tohoku.ac.jp 233 Support Group E-mail: mext@ietf.org 234 " 236 DESCRIPTION 237 "The MIB module for monitoring a NEMO entity. 239 Copyright (c) 2009 IETF Trust and the persons 240 identified as the document authors. All rights 241 reserved. 243 This version of this MIB module is part of 244 RFC XXXX; see the RFC itself for full legal 245 notices. 246 " 247 -- RFC Ed.: replace XXXX with actual RFC number and remove this 248 -- note 249 REVISION "200901310000Z" -- 31st January 2009 250 DESCRIPTION "Initial version, published as RFC XXXX." 252 -- RFC Ed.: replace XXXX with actual RFC number and remove this 253 -- note 255 ::= { mib-2 YYY } -- will be assigned by IANA 257 -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' 258 -- subtree and record the assignment in the SMI Numbers 259 -- registry. 260 -- 261 -- RFC Ed.: When the above assignment has been made, please 262 -- remove the above note 263 -- replace "YYY" here with the assigned value and 264 -- remove this note. 266 -- The NEMO MIB has the following primary groups 268 nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } 269 nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 } 270 nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 2 } 271 nemoCore OBJECT IDENTIFIER ::= { nemoObjects 1 } 272 nemoMr OBJECT IDENTIFIER ::= { nemoObjects 2 } 273 nemoCn OBJECT IDENTIFIER ::= { nemoObjects 3 } 274 nemoHa OBJECT IDENTIFIER ::= { nemoObjects 4 } 276 -- The sub groups 278 nemoSystem OBJECT IDENTIFIER ::= { nemoCore 1 } 279 nemoBindings OBJECT IDENTIFIER ::= { nemoCore 2 } 280 nemoConfiguration OBJECT IDENTIFIER ::= { nemoCore 3 } 281 nemoStats OBJECT IDENTIFIER ::= { nemoCore 4 } 283 nemoMrSystem OBJECT IDENTIFIER ::= { nemoMr 1 } 284 nemoMrConf OBJECT IDENTIFIER ::= { nemoMr 2 } 285 nemoMrRegistration OBJECT IDENTIFIER ::= { nemoMr 3 } 286 nemoMrGlobalStats OBJECT IDENTIFIER ::= { nemoMr 4 } 288 nemoHaAdvertisement OBJECT IDENTIFIER ::= { nemoHa 1 } 289 nemoHaStats OBJECT IDENTIFIER ::= { nemoHa 2 } 290 nemoHaRegistration OBJECT IDENTIFIER ::= { nemoHa 3 } 291 nemoHaGlobalStats OBJECT IDENTIFIER ::= { nemoHaStats 1 } 293 -- Textual Conventions 294 NemoBURequestRejectionCode ::= TEXTUAL-CONVENTION 295 STATUS current 296 DESCRIPTION 297 "The value of the status field in the Binding 298 Acknowledgment message when the Binding Update 299 was rejected for NEMO specific reasons. 300 " 301 REFERENCE 302 "RFC 3963 : Section 4.2" 303 SYNTAX INTEGER { 304 mobileRouterOperationNotPermitted (140), 305 invalidPrefix (141), 306 notAuthorizedForPrefix (142), 307 forwardingSetupFailed (143) 308 } 310 -- 311 -- 312 -- nemoSystem group 313 -- 314 -- 316 nemoCapabilities OBJECT-TYPE 317 SYNTAX BITS { 318 mobileRouter (0), 319 homeAgentSupport (1) 320 } 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "This object indicates the NEMO functions that 325 are supported by this managed entity. Multiple 326 NEMO functions may be supported by a single 327 entity. 328 " 329 REFERENCE 330 "RFC 3963 : Section 3" 331 ::= { nemoSystem 1 } 333 nemoStatus OBJECT-TYPE 334 SYNTAX INTEGER { enabled(1), disabled(2) } 335 MAX-ACCESS read-write 336 STATUS current 337 DESCRIPTION 338 "This object indicates whether the NEMO 339 function is enabled for the managed entity. If it 340 is enabled, the agent discovery and registration 341 functions will be operational. 342 Changing the status from enabled(1) to disabled(2) 343 will terminate the agent discovery and registration 344 functions. On the other hand, changing the status 345 from disabled(2) to enabled(1) will start the agent 346 discovery and registration functions. 348 The value of this object MUST remain unchanged 349 across reboots of the managed entity. 350 " 351 ::= { nemoSystem 2 } 353 nemoCounterDiscontinuityTime OBJECT-TYPE 354 SYNTAX TimeStamp 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The value of sysUpTime on the most recent occasion 359 at which any one or more of this NEMO entity's 360 counters viz, counters with OID prefix 'nemoMrConf' 361 or 'nemoMrRegnCounters' or 'nemoMrGlobalStats' 362 or 'nemoHaGlobalStats' suffered a discontinuity. 363 If no such discontinuities have occurred since the 364 last re-initialization of the local management 365 subsystem, then this object will have a zero value. 366 " 367 ::= { nemoStats 1 } 368 -- 369 -- 370 -- nemoConfiguration group 371 -- 372 -- 374 nemoMrBLTable OBJECT-TYPE 375 SYNTAX SEQUENCE OF NemoMrBLEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "This table corresponds to the Binding Update List 380 (BL) that includes NEMO related information and 381 is maintained by the mobile router. The table 382 holds a row for every binding that the mobile 383 router has established or is trying to establish. 384 Entries from the table are deleted as the lifetime 385 of the binding expires. 386 " 387 REFERENCE 388 "RFC 3775 : Section 4.5, 11.1, RFC 3963 : Section 5.2" 389 ::= { nemoMrRegistration 1 } 391 nemoMrBLEntry OBJECT-TYPE 392 SYNTAX NemoMrBLEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "An entry pertaining to nemo-related information 397 contained in a Binding Update sent by a nemo-enabled 398 mobile router to its home agent. 399 " 400 AUGMENTS {mip6MnBLEntry} 401 ::= { nemoMrBLTable 1 } 403 NemoMrBLEntry ::= SEQUENCE { 404 nemoMrBLMode INTEGER, 405 nemoMrBLMrFlag TruthValue, 406 nemoMrBLHomeAddressPrefixLength InetAddressPrefixLength, 407 nemoMrBLCareofAddressPrefixLength InetAddressPrefixLength, 408 nemoMrBLActiveEgressIfIndex InterfaceIndex, 409 nemoMrBLEstablishedHomeTunnelIfIndex InterfaceIndex 410 } 411 nemoMrBLMode OBJECT-TYPE 412 SYNTAX INTEGER { 413 implicitMode (1), 414 explicitMode (2) 415 } 416 MAX-ACCESS read-only 417 STATUS current 418 DESCRIPTION 419 "implicitMode(1): the Mobile Network Prefix Option 420 is not included in the Binding Update by the mobile 421 router. 422 explicitMode(2): the mobile router included one or 423 more Mobile Network Prefix Options in the Binding 424 Update. 425 " 426 REFERENCE 427 "RFC 3963 : Section 5.2" 428 ::= { nemoMrBLEntry 1 } 430 nemoMrBLMrFlag OBJECT-TYPE 431 SYNTAX TruthValue 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "true(1): the mobile router sent the Binding Update 436 with Mobile Router Flag set. 437 false(2): the mobile router did not send the binding 438 update with Mobile Router Flag set. This implies that 439 the mobile router is acting as a mobile node. 440 " 441 REFERENCE 442 "RFC 3963 : Section 4.1, 5.1" 443 ::= { nemoMrBLEntry 2 } 445 nemoMrBLHomeAddressPrefixLength OBJECT-TYPE 446 SYNTAX InetAddressPrefixLength 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The prefix length of the mobile router's home network. 451 " 452 REFERENCE 453 "RFC 3963 : Section 3" 454 ::= { nemoMrBLEntry 3 } 456 nemoMrBLCareofAddressPrefixLength OBJECT-TYPE 457 SYNTAX InetAddressPrefixLength 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The prefix length of the care-of Address of the 462 mobile router. 463 " 464 REFERENCE 465 "RFC 3963 : Section 3" 466 ::= { nemoMrBLEntry 4 } 468 nemoMrBLActiveEgressIfIndex OBJECT-TYPE 469 SYNTAX InterfaceIndex 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "The interface index of the currently active 474 egress interface. 475 " 476 REFERENCE 477 "RFC 3963 : Section 5.5" 478 ::= { nemoMrBLEntry 5 } 480 nemoMrBLEstablishedHomeTunnelIfIndex OBJECT-TYPE 481 SYNTAX InterfaceIndex 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "The interface index of the tunnel established 486 between the mobile router and the home agent 487 for NEMO traffic. 488 " 489 REFERENCE 490 "RFC 3963 : Section 5.5" 491 ::= { nemoMrBLEntry 6 } 493 -- Mobile Router Registration Group Counters 495 nemoMrRegnCounters OBJECT IDENTIFIER ::= { nemoMrRegistration 2 } 497 nemoMrMobilityMessagesSent OBJECT-TYPE 498 SYNTAX Counter32 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "The total number of mobility messages, i.e. IPv6 503 datagrams with Mobility Header, sent by the mobile 504 node. This will include Binding Updates sent by a 505 mobile router with the Mobile Router Flag set. 506 Discontinuities in the value of this counter can 507 occur at re-initialization of the management system, 508 and at other times as indicated by the value of 509 nemoCounterDiscontinuityTime. 510 " 511 REFERENCE 512 "RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1" 513 ::= { nemoMrRegnCounters 1 } 515 nemoMrMobilityMessagesRecd OBJECT-TYPE 516 SYNTAX Counter32 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "The total number of mobility messages, i.e. IPv6 521 datagrams with Mobility Header, received by the 522 mobile node. This will include Binding 523 Acknowledgements with Mobile Router Flag set, that 524 are sent to a mobile router. 525 Discontinuities in the value of this counter can 526 occur at re-initialization of the management system, 527 and at other times as indicated by the value of 528 nemoCounterDiscontinuityTime. 529 " 530 REFERENCE 531 "RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1, 4.2" 532 ::= { nemoMrRegnCounters 2 } 534 nemoMrPrefixRegMode OBJECT-TYPE 535 SYNTAX INTEGER { 536 implicitMode (1), 537 explicitMode (2) 538 } 539 MAX-ACCESS read-write 540 STATUS current 541 DESCRIPTION 542 "This object indicates the mode in which the mobile 543 network prefixes will be registered with the home 544 agent. 545 implicitMode(1): the Mobile Network Prefix Option will 546 not be included in the Binding Update by the mobile 547 router. 548 explicitMode(2): the mobile router will include one or 549 more Mobile Network Prefix Options in the Binding 550 Update. 551 The value of this object MUST remain unchanged 552 across reboots of the managed entity. 553 " 554 REFERENCE 555 "RFC 3963 : Section 5.2" 557 ::= { nemoMrRegistration 3 } 559 nemoHaMobileNetworkPrefixTable OBJECT-TYPE 560 SYNTAX SEQUENCE OF NemoHaMobileNetworkPrefixEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "This table contains the mobile network prefixes 565 that the home agent maintains for the Mobile Router. 566 The mobile network prefixes in this table are 567 registered by Binding Updates or are manually 568 pre-configured. 569 " 570 REFERENCE 571 "RFC 3963 : Section 6.1.2" 572 ::= { nemoHaRegistration 1 } 574 nemoHaMobileNetworkPrefixEntry OBJECT-TYPE 575 SYNTAX NemoHaMobileNetworkPrefixEntry 576 MAX-ACCESS not-accessible 577 STATUS current 578 DESCRIPTION 579 "An entry for a mobile network prefix. 581 The instances of the columnar objects in this entry 582 pertain to an interface for a particular value of 583 mip6BindingHomeAddressType, mip6BindingHomeAddress, 584 and nemoHaMobileNetworkPrefixSeqNo. 585 The nemoHaMobileNetworkPrefixSeqNo object is used to 586 distinguish between multiple instances of 587 the mobile network prefix in the same Binding Update 588 for the same set of mip6BindingHomeAddressType and 589 mip6BindingHomeAddress. 590 There is no upper-bound on the maximum number of 591 mobile network prefixes in a Binding Update but, for 592 practical purposes, the upper bound of the value 593 nemoHaMobileNetworkPrefixSeqNo is set to 1024. 595 Implementers need to be aware that if the total 596 number of octets in mip6BindingHomeAddress 597 exceeds 112, then OIDs of column 598 instances in this row will have more than 128 599 sub-identifiers and cannot be accessed using 600 SNMPv1, SNMPv2c, or SNMPv3. 601 " 602 INDEX { mip6BindingHomeAddressType, 603 mip6BindingHomeAddress, 604 nemoHaMobileNetworkPrefixSeqNo 605 } 606 ::= { nemoHaMobileNetworkPrefixTable 1 } 608 NemoHaMobileNetworkPrefixEntry ::= SEQUENCE { 609 nemoHaMobileNetworkPrefixSeqNo Unsigned32, 610 nemoHaMobileNetworkPrefixType InetAddressType, 611 nemoHaMobileNetworkPrefix InetAddress, 612 nemoHaMobileNetworkPrefixLength Unsigned32, 613 nemoHaMobileNetworkPrefixSource INTEGER 614 } 616 nemoHaMobileNetworkPrefixSeqNo OBJECT-TYPE 617 SYNTAX Unsigned32 (1..1024) 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "A Binding Update may have multiple mobile network 622 prefixes. 623 This object along with mip6BindingHomeAddressType, 624 and mip6BindingHomeAddress uniquely identifies a 625 row containing a single mobile network prefix for 626 a mobile router in this table. 627 " 628 REFERENCE 629 "RFC 3963 : Section 2, 6.1, 6.2" 630 ::= { nemoHaMobileNetworkPrefixEntry 1 } 632 nemoHaMobileNetworkPrefixType OBJECT-TYPE 633 SYNTAX InetAddressType 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "The address type for the mobile network prefix 638 that follows. 639 " 640 ::= { nemoHaMobileNetworkPrefixEntry 2 } 642 nemoHaMobileNetworkPrefix OBJECT-TYPE 643 SYNTAX InetAddress 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "A mobile network prefix related to the 648 corresponding Binding Update. 650 The type of the address represented by this object 651 is specified by the corresponding 652 nemoHaMobileNetworkPrefixType object. 653 " 654 REFERENCE 655 "RFC 3963 : Section 2 , 6.1, 6.2" 656 ::= { nemoHaMobileNetworkPrefixEntry 3 } 658 nemoHaMobileNetworkPrefixLength OBJECT-TYPE 659 SYNTAX Unsigned32 (0..128) 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "The length of the prefix specified by the corresponding 664 nemoHaMobileNetworkPrefix Object. 665 " 666 REFERENCE 667 "RFC 3963 : Section 4.3, 6.1, 6.2" 668 ::= { nemoHaMobileNetworkPrefixEntry 4 } 670 nemoHaMobileNetworkPrefixSource OBJECT-TYPE 671 SYNTAX INTEGER { 672 configured (1), 673 bindingUpdate (2) 674 } 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The information source of the mobile network prefix 680 configured with the Binding Update. 681 configured(1) indicates that mobile network prefix 682 has been manually pre-configured. 683 bindingUpdate(2) indicates that the information is 684 introduced to the home agent by the mobile network 685 prefix option in the Binding Updates received by the 686 home agent. 687 " 688 REFERENCE 689 "RFC 3963 : Section 4.3, 6.1, 6.2" 690 ::= { nemoHaMobileNetworkPrefixEntry 5 } 692 nemoBindingCacheTable OBJECT-TYPE 693 SYNTAX SEQUENCE OF NemoBindingCacheEntry 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "This table models the Binding Cache 698 that includes NEMO related information and 699 is maintained by the home agent. 700 Entries in this table are not required to survive 701 a reboot of the home agent. 702 " 703 REFERENCE 704 "RFC 3775 : Section 4.5, 9.1, 10.1, 705 RFC 3963 : Section 6.1" 706 ::= { nemoBindings 1 } 708 nemoBindingCacheEntry OBJECT-TYPE 709 SYNTAX NemoBindingCacheEntry 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "An entry containing additional information related 714 to nemo-enabled entries in the binding cache table 715 of the home agent. 716 " 717 AUGMENTS {mip6BindingCacheEntry} 718 ::= { nemoBindingCacheTable 1 } 720 NemoBindingCacheEntry ::= SEQUENCE { 721 nemoBindingMrFlag TruthValue, 722 nemoBindingMrMode INTEGER 723 } 725 nemoBindingMrFlag OBJECT-TYPE 726 SYNTAX TruthValue 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "true(1) indicates that the binding cache entry is from 731 an entity acting as a mobile router. 732 false(2) implies that the binding cache entry is from 733 an entity acting as a mobile node. 734 " 735 REFERENCE 736 "RFC 3963 : Section 6.1.1, 6.2" 737 ::= { nemoBindingCacheEntry 1 } 739 nemoBindingMrMode OBJECT-TYPE 740 SYNTAX INTEGER { 741 implicitMode(1), 742 explicitMode(2) 743 } 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "implicitMode(1): the Mobile Network Prefix Option is 748 not included in the Binding Update by the mobile 749 router. 750 explicitMode(2): the mobile router included one or 751 more Mobile Network Prefix Options in the Binding 752 Update. 753 " 754 REFERENCE 755 "RFC 3963 : Section 5.2, 6.1.1, 6.2" 756 ::= { nemoBindingCacheEntry 2 } 758 -- 759 -- nemoMrEgressIfTable 760 -- 761 nemoMrEgressIfTable OBJECT-TYPE 762 SYNTAX SEQUENCE OF NemoMrEgressIfEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "A table representing the egress interfaces that 767 will be used by the mobile router for roaming to 768 foreign networks. Each entry in this table 769 represents a configured egress interface. 770 " 771 ::= { nemoMrSystem 1 } 773 nemoMrEgressIfEntry OBJECT-TYPE 774 SYNTAX NemoMrEgressIfEntry 775 MAX-ACCESS not-accessible 776 STATUS current 777 DESCRIPTION 778 "An entry in the egress interface table. It 779 represents a single egress interface entry. 780 " 781 INDEX { nemoMrEgressIfIndex } 782 ::= { nemoMrEgressIfTable 1 } 784 NemoMrEgressIfEntry ::= 785 SEQUENCE { 786 nemoMrEgressIfIndex InterfaceIndex, 787 nemoMrEgressIfPriority Unsigned32, 788 nemoMrEgressIfDescription SnmpAdminString, 789 nemoMrEgressIfRoamHoldDownTime Gauge32 790 } 792 nemoMrEgressIfIndex OBJECT-TYPE 793 SYNTAX InterfaceIndex 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "The index of the interface on the mobile router. 798 " 799 ::= { nemoMrEgressIfEntry 1 } 801 nemoMrEgressIfPriority OBJECT-TYPE 802 SYNTAX Unsigned32 (0..255) 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "The priority configured to the egress interface. 807 This value will be configured to a value between 0 808 and 255. 809 " 810 ::= { nemoMrEgressIfEntry 2 } 812 nemoMrEgressIfDescription OBJECT-TYPE 813 SYNTAX SnmpAdminString 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "A human-readable textual description of the egress 818 interface on the mobile router. 819 " 820 ::= { nemoMrEgressIfEntry 3 } 822 nemoMrEgressIfRoamHoldDownTime OBJECT-TYPE 823 SYNTAX Gauge32 824 UNITS "seconds" 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "This object indicates the time for which the 829 egress interface will be held down during roaming 830 to avoid interface flapping. 831 " 832 ::= { nemoMrEgressIfEntry 4 } 834 nemoMrDiscoveryRequests OBJECT-TYPE 835 SYNTAX Counter32 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "Total number of Modified Dynamic Home Agent Address 840 Discovery Requests, with Mobile Router Support Flag 841 set, sent by the mobile router. 842 Discontinuities in the value of this counter can 843 occur at re-initialization of the management system, 844 and at other times as indicated by the value of 845 nemoCounterDiscontinuityTime. 846 " 847 REFERENCE 848 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.1" 849 ::= { nemoMrConf 1 } 851 nemoMrDiscoveryReplies OBJECT-TYPE 852 SYNTAX Counter32 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "Total number of Modified Dynamic Home Agent Address 857 Discovery Replies, with Mobile Router Support Flag 858 set, received by the mobile router. 859 Discontinuities in the value of this counter can 860 occur at re-initialization of the management system, 861 and at other times as indicated by the value of 862 nemoCounterDiscontinuityTime. 863 " 864 REFERENCE 865 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2" 866 ::= { nemoMrConf 2 } 868 nemoMrDiscoveryRepliesRouterFlagZero OBJECT-TYPE 869 SYNTAX Counter32 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "Total number of Modified Dynamic Home Agent Address 874 Discovery Replies with Mobile Router Support Flag set 875 to 0 although the flag in the corresponding request 876 is set to 1. 877 It implies that there is no home agent that supports 878 Mobile Router functionality in the home network. 879 Discontinuities in the value of this counter can 880 occur at re-initialization of the management system, 881 and at other times as indicated by the value of 882 nemoCounterDiscontinuityTime. 883 " 884 REFERENCE 885 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2" 886 ::= { nemoMrConf 3 } 888 nemoMrMovedHome OBJECT-TYPE 889 SYNTAX Counter32 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "Number of times the mobile router has detected 894 movement from a foreign network to its home 895 network. 896 Discontinuities in the value of this counter can 897 occur at re-initialization of the management system, 898 and at other times as indicated by the value of 899 nemoCounterDiscontinuityTime. 900 " 901 REFERENCE 902 "RFC 3963 : Section 3." 903 ::= { nemoMrConf 4 } 905 nemoMrMovedOutofHome OBJECT-TYPE 906 SYNTAX Counter32 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "Number of times the mobile router has detected 911 movement to a foreign network from the home 912 network, has acquired a care-of address and 913 has initiated the care-of address registration 914 process. 915 Discontinuities in the value of this counter can 916 occur at re-initialization of the management system, 917 and at other times as indicated by the value of 918 nemoCounterDiscontinuityTime. 919 " 920 REFERENCE 921 "RFC 3963 : Section 3." 922 ::= { nemoMrConf 5 } 924 nemoMrMovedFNtoFN OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "Number of times the mobile router has detected 930 movement to/from a foreign network from/to another 931 foreign network. Note that 'movement' implies 932 movement in layer 3, i.e. the mobile routers care-of 933 address changed and it initiated the care-of address 934 registration process. 935 If there are multiple egress interfaces, this counter 936 counts the total number of movements. 937 The movement as a mobile node of the mobile entity 938 is not counted. 939 Discontinuities in the value of this counter can 940 occur at re-initialization of the management system, 941 and at other times as indicated by the value of 942 nemoCounterDiscontinuityTime. 943 " 944 REFERENCE 945 "RFC 3963 : Section 3." 946 ::= { nemoMrConf 6 } 948 nemoMrBetterIfDetected OBJECT-TYPE 949 SYNTAX Counter32 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Number of times the NEMO entity has found an egress 954 interface with better priority. 955 Discontinuities in the value of this counter can 956 occur at re-initialization of the management system, 957 and at other times as indicated by the value of 958 nemoCounterDiscontinuityTime. 959 " 960 ::= { nemoMrConf 7 } 962 -- 963 -- nemoStats:nemoMrGlobalStats 964 -- 966 nemoMrBindingAcksWONemoSupport OBJECT-TYPE 967 SYNTAX Counter32 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The total number of Binding Acknowledgements without 972 NEMO support received by the mobile router. 974 Discontinuities in the value of this counter can 975 occur at re-initialization of the management system, 976 and at other times as indicated by the value of 977 nemoCounterDiscontinuityTime. 979 " 980 REFERENCE 981 "RFC 3963 : Section 5.3." 982 ::= { nemoMrGlobalStats 1 } 984 nemoMrBindingAcksRegTypeChangeDisallowed OBJECT-TYPE 985 SYNTAX Counter32 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "The total number of Binding Acknowledgements 990 received by the mobile router with status code 991 indicating 992 'Registration type change disallowed' (Code 139). 994 Discontinuities in the value of this counter can 995 occur at re-initialization of the management system, 996 and at other times as indicated by the value of 997 nemoCounterDiscontinuityTime. 998 " 999 REFERENCE 1000 "RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2" 1001 ::= { nemoMrGlobalStats 2 } 1003 nemoMrBindingAcksOperationNotPermitted OBJECT-TYPE 1004 SYNTAX Counter32 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "The total number of Binding Acknowledgement 1009 received by the mobile router with status code 1010 indicating 1011 'Mobile Router Operation not permitted' 1012 (Code 140). 1014 Discontinuities in the value of this counter can 1015 occur at re-initialization of the management system, 1016 and at other times as indicated by the value of 1017 nemoCounterDiscontinuityTime. 1018 " 1019 REFERENCE 1020 "RFC 3963 : Section 6.6" 1021 ::= { nemoMrGlobalStats 3 } 1023 nemoMrBindingAcksInvalidPrefix OBJECT-TYPE 1024 SYNTAX Counter32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The total number of Binding Acknowledgement 1029 received by the mobile router with status code 1030 indicating 'Invalid Prefix' (Code 141). 1032 Discontinuities in the value of this counter can 1033 occur at re-initialization of the management system, 1034 and at other times as indicated by the value of 1035 nemoCounterDiscontinuityTime. 1036 " 1037 REFERENCE 1038 "RFC 3963 : Section 6.6." 1039 ::= { nemoMrGlobalStats 4 } 1041 nemoMrBindingAcksNotAuthorizedForPrefix OBJECT-TYPE 1042 SYNTAX Counter32 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "The total number of Binding Acknowledgements 1047 received by the mobile router with status code 1048 indicating 1049 'Not Authorized for Prefix' (Code 142). 1051 Discontinuities in the value of this counter can 1052 occur at re-initialization of the management system, 1053 and at other times as indicated by the value of 1054 nemoCounterDiscontinuityTime. 1055 " 1056 REFERENCE 1057 "RFC 3963 : Section 6.6." 1058 ::= { nemoMrGlobalStats 5 } 1060 nemoMrBindingAcksForwardingSetupFailed OBJECT-TYPE 1061 SYNTAX Counter32 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The total number of Binding Acknowledgements 1066 received by the mobile router with status code 1067 indicating 'Forwarding Setup failed' (Code 143). 1069 Discontinuities in the value of this counter can 1070 occur at re-initialization of the management system, 1071 and at other times as indicated by the value of 1072 nemoCounterDiscontinuityTime. 1073 " 1074 REFERENCE 1075 "RFC 3963 : Section 6.6." 1076 ::= { nemoMrGlobalStats 6 } 1078 nemoMrBindingAcksOtherError OBJECT-TYPE 1079 SYNTAX Counter32 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "The total number of Binding Acknowledgements 1084 received by the mobile router (Mobile Router Flag is 1085 set) with status code other than 1086 successfully processed , --(Code 0 ) 1087 mobileRouterOperationNotPermitted (1), --(Code 140) 1088 invalidPrefix (2), --(Code 141) 1089 notAuthorizedForPrefix (3), --(Code 142) 1090 forwardingSetupFailed (4). --(Code 143) 1092 Discontinuities in the value of this counter can 1093 occur at re-initialization of the management system, 1094 and at other times as indicated by the value of 1095 nemoCounterDiscontinuityTime. 1096 " 1097 REFERENCE 1098 "RFC 3963 : Section 6.6." 1099 ::= { nemoMrGlobalStats 7 } 1101 -- 1102 -- nemoStats:nemoHaGlobalStats 1103 -- 1105 nemoHaBUAcksWONemoSupport OBJECT-TYPE 1106 SYNTAX Counter32 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "The total number of Binding Acknowledgements 1111 without NEMO support sent by the home agent. 1113 Discontinuities in the value of this counter can 1114 occur at re-initialization of the management system, 1115 and at other times as indicated by the value of 1116 nemoCounterDiscontinuityTime. 1117 " 1118 REFERENCE 1119 "RFC 3963 : Section 5.3" 1120 ::= { nemoHaGlobalStats 1 } 1122 nemoHaBUAcksRegTypeChangeDisallowed OBJECT-TYPE 1123 SYNTAX Counter32 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "The total number of Binding Update requests 1128 rejected by the home agent with status code 1129 in the Binding Acknowledgement indicating 1130 'Registration type change disallowed' (Code 139). 1132 Discontinuities in the value of this counter can 1133 occur at re-initialization of the management system, 1134 and at other times as indicated by the value of 1135 nemoCounterDiscontinuityTime. 1136 " 1137 REFERENCE 1138 "RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2" 1139 ::= { nemoHaGlobalStats 2 } 1141 nemoHaBUAcksOperationNotPermitted OBJECT-TYPE 1142 SYNTAX Counter32 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The total number of Binding Update requests 1147 rejected by the home agent with status code in 1148 the Binding Acknowledgement indicating 1149 'Mobile Router Operation not permitted' 1150 (Code 140). 1152 Discontinuities in the value of this counter can 1153 occur at re-initialization of the management system, 1154 and at other times as indicated by the value of 1155 nemoCounterDiscontinuityTime. 1156 " 1157 REFERENCE 1158 "RFC 3963 : Section 6.6" 1159 ::= { nemoHaGlobalStats 3 } 1161 nemoHaBUAcksInvalidPrefix OBJECT-TYPE 1162 SYNTAX Counter32 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "The total number of Binding Update requests 1167 rejected by the home agent with status code in 1168 the Binding Acknowledgement indicating 1169 'Invalid Prefix' (Code 141). 1171 Discontinuities in the value of this counter can 1172 occur at re-initialization of the management system, 1173 and at other times as indicated by the value of 1174 nemoCounterDiscontinuityTime. 1175 " 1176 REFERENCE 1177 "RFC 3963 : Section 6.6" 1178 ::= { nemoHaGlobalStats 4 } 1180 nemoHaBUAcksNotAuthorizedForPrefix OBJECT-TYPE 1181 SYNTAX Counter32 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The total number of Binding Update requests 1186 rejected by the home agent with status code in 1187 the Binding Acknowledgement indicating 1188 'Not Authorized for Prefix' (Code 142). 1190 Discontinuities in the value of this counter can 1191 occur at re-initialization of the management system, 1192 and at other times as indicated by the value of 1193 nemoCounterDiscontinuityTime. 1194 " 1195 REFERENCE 1196 "RFC 3963 : Section 6.6" 1197 ::= { nemoHaGlobalStats 5 } 1199 nemoHaBUAcksForwardingSetupFailed OBJECT-TYPE 1200 SYNTAX Counter32 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "The total number of Binding Update requests 1205 rejected by the home agent with status code in 1206 the Binding Acknowledgement indicating 1207 'Forwarding Setup failed' (Code 143). 1209 Discontinuities in the value of this counter can 1210 occur at re-initialization of the management system, 1211 and at other times as indicated by the value of 1212 nemoCounterDiscontinuityTime. 1213 " 1214 REFERENCE 1215 "RFC 3963 : Section 6.6" 1216 ::= { nemoHaGlobalStats 6 } 1218 nemoHaBUAcksOtherError OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The total number of Binding Update requests 1224 from mobile routers (Mobile Router Flag is 1225 set) rejected by the home agent with status code 1226 other than 1227 mobileRouterOperationNotPermitted (140), 1228 invalidPrefix (141), 1229 notAuthorizedForPrefix (142), 1230 forwardingSetupFailed (143). 1232 Discontinuities in the value of this counter can 1233 occur at re-initialization of the management system, 1234 and at other times as indicated by the value of 1235 nemoCounterDiscontinuityTime. 1236 " 1237 REFERENCE 1238 "RFC 3963 : Section 6.6." 1239 ::= { nemoHaGlobalStats 7 } 1241 nemoHaCounterTable OBJECT-TYPE 1242 SYNTAX SEQUENCE OF NemoHaCounterEntry 1243 MAX-ACCESS not-accessible 1244 STATUS current 1245 DESCRIPTION 1246 "A table containing registration statistics for all 1247 mobile routers registered with the home agent. 1248 " 1249 ::= { nemoHaStats 2 } 1251 nemoHaCounterEntry OBJECT-TYPE 1252 SYNTAX NemoHaCounterEntry 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "Home agent registration statistics for a mobile 1257 router. 1259 Implementors need to be aware that if the total 1260 number of octets in mip6BindingHomeAddress 1261 exceeds 113 then OIDs of column instances in 1262 this row will have more than 128 sub-identifiers and 1263 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1264 " 1265 INDEX { mip6BindingHomeAddressType, 1266 mip6BindingHomeAddress 1267 } 1268 ::= { nemoHaCounterTable 1 } 1270 NemoHaCounterEntry ::= SEQUENCE { 1271 nemoHaBURequestsAccepted Counter32, 1272 nemoHaBURequestsDenied Counter32, 1273 nemoHaBCEntryCreationTime DateAndTime, 1274 nemoHaBUAcceptedTime DateAndTime, 1275 nemoHaBURejectionTime DateAndTime, 1276 nemoHaRecentBURejectionCode NemoBURequestRejectionCode, 1277 nemoHaCtrDiscontinuityTime TimeStamp 1278 } 1280 nemoHaBURequestsAccepted OBJECT-TYPE 1281 SYNTAX Counter32 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "Total number of Binding Update requests from the 1286 mobile router accepted by the home agent. 1287 Discontinuities in the value of this counter can 1288 occur at re-initialization of the management system, 1289 and at other times as indicated by the value of 1290 nemoHaCtrDiscontinuityTime. 1291 " 1292 ::= { nemoHaCounterEntry 1 } 1294 nemoHaBURequestsDenied OBJECT-TYPE 1295 SYNTAX Counter32 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "Total number of Binding Update requests from the 1300 mobile router rejected by the home agent. 1301 Discontinuities in the value of this counter can 1302 occur at re-initialization of the management system, 1303 and at other times as indicated by the value of 1304 nemoHaCtrDiscontinuityTime. 1305 " 1306 ::= { nemoHaCounterEntry 2 } 1308 nemoHaBCEntryCreationTime OBJECT-TYPE 1309 SYNTAX DateAndTime (SIZE (11)) 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "The time when the current Binding Cache entry was 1314 created for the mobile router. An implementation 1315 MUST return all 11 bytes of the DateAndTime 1316 textual-convention so that a manager may retrieve 1317 the offset from GMT time. 1318 " 1319 ::= { nemoHaCounterEntry 3 } 1321 nemoHaBUAcceptedTime OBJECT-TYPE 1322 SYNTAX DateAndTime (SIZE (11)) 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "The time at which the last Binding Update was 1327 accepted by the home agent for this mobile router. 1328 An implementation MUST return all 11 bytes of the 1329 DateAndTime textual-convention so that a manager 1330 may retrieve the offset from GMT time. 1331 " 1332 ::= { nemoHaCounterEntry 4 } 1334 nemoHaBURejectionTime OBJECT-TYPE 1335 SYNTAX DateAndTime (SIZE (11)) 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "The time at which the last Binding Update was 1340 rejected by the home agent for this mobile router. 1341 If there have been no rejections then this object 1342 will be inaccessible. An implementation MUST 1343 return all 11 bytes of the DateAndTime 1344 textual-convention so that a manager may retrieve 1345 the offset from GMT time. 1346 " 1347 ::= { nemoHaCounterEntry 5 } 1349 nemoHaRecentBURejectionCode OBJECT-TYPE 1350 SYNTAX NemoBURequestRejectionCode 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The Status code (>= 128) in the latest Binding 1355 Acknowledgment indicating a rejection, sent to this 1356 mobile router. 1357 In case a Binding Update request is rejected and a 1358 Binding Acknowledgment is not sent to this mobile 1359 router then this will be the value of the Status 1360 code that corresponds to the reason of the rejection. 1361 If there have been no Binding Update request 1362 rejections then this object will be inaccessible. 1363 " 1364 ::= { nemoHaCounterEntry 6 } 1366 nemoHaCtrDiscontinuityTime OBJECT-TYPE 1367 SYNTAX TimeStamp 1368 MAX-ACCESS read-only 1369 STATUS current 1370 DESCRIPTION 1371 "The value of sysUpTime on the most recent occasion 1372 at which any one or more of counters in this row 1373 viz, instances of 'nemoHaBURequestsAccepted' and 1374 'nemoHaBURequestsDenied' suffered a discontinuity. 1375 If no such discontinuity has occurred since the 1376 last re-initialization of the local management 1377 subsystem, then this object will have a zero value. 1378 " 1379 ::= { nemoHaCounterEntry 7 } 1381 -- 1382 -- 1383 -- nemoNotifications 1384 -- 1385 -- 1387 nemoHomeTunnelEstablished NOTIFICATION-TYPE 1388 OBJECTS { 1389 nemoMrBLActiveEgressIfIndex, 1390 nemoMrBLEstablishedHomeTunnelIfIndex, 1391 mip6MnBLCOAType, 1392 mip6MnBLCOA, 1393 nemoMrBLHomeAddressPrefixLength, 1394 nemoMrBLCareofAddressPrefixLength 1395 } 1397 STATUS current 1398 DESCRIPTION 1399 "This notification is sent by the mobile router 1400 every time the tunnel is established between the 1401 home agent and the mobile router. 1402 " 1403 REFERENCE 1404 "RFC 3963 : Section 5.5" 1405 ::= { nemoNotifications 1 } 1407 nemoHomeTunnelReleased NOTIFICATION-TYPE 1408 OBJECTS { 1409 nemoMrBLActiveEgressIfIndex, 1410 nemoMrBLEstablishedHomeTunnelIfIndex, 1411 mip6MnBLCOAType, 1412 mip6MnBLCOA, 1413 nemoMrBLHomeAddressPrefixLength, 1414 nemoMrBLCareofAddressPrefixLength 1415 } 1416 STATUS current 1417 DESCRIPTION 1418 "This notification is sent by the mobile router 1419 every time the tunnel is deleted between the home 1420 agent and the mobile router. 1421 " 1422 REFERENCE 1423 "RFC 3963 : Section 5.5" 1424 ::= { nemoNotifications 2} 1426 -- Conformance information 1427 nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } 1428 nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } 1430 -- Units of conformance 1431 nemoSystemGroup OBJECT-GROUP 1432 OBJECTS { 1433 nemoCapabilities, 1434 nemoStatus 1435 } 1436 STATUS current 1437 DESCRIPTION 1438 " A collection of objects for basic NEMO 1439 monitoring." 1440 ::= { nemoGroups 1 } 1442 nemoBindingCacheGroup OBJECT-GROUP 1443 OBJECTS { 1444 nemoBindingMrFlag, 1445 nemoBindingMrMode 1446 } 1447 STATUS current 1448 DESCRIPTION 1449 " A collection of objects for monitoring the 1450 NEMO extensions of the Binding Cache." 1451 ::= { nemoGroups 2 } 1453 nemoStatsGroup OBJECT-GROUP 1454 OBJECTS { 1455 nemoCounterDiscontinuityTime 1456 } 1457 STATUS current 1458 DESCRIPTION 1459 " A collection of objects for 1460 monitoring NEMO statistics." 1461 ::= { nemoGroups 3 } 1463 nemoMrConfGroup OBJECT-GROUP 1464 OBJECTS { 1465 nemoMrEgressIfPriority, 1466 nemoMrEgressIfDescription, 1467 nemoMrEgressIfRoamHoldDownTime, 1468 nemoMrDiscoveryRequests, 1469 nemoMrDiscoveryReplies, 1470 nemoMrDiscoveryRepliesRouterFlagZero, 1471 nemoMrMovedHome, 1472 nemoMrMovedOutofHome, 1473 nemoMrMovedFNtoFN, 1474 nemoMrBetterIfDetected 1475 } 1476 STATUS current 1477 DESCRIPTION 1478 " A collection of objects for monitoring 1479 the configuration-related information on 1480 the mobile router. 1481 " 1482 ::= { nemoGroups 4 } 1484 nemoMrRegistrationGroup OBJECT-GROUP 1485 OBJECTS { 1486 nemoMrBLMode, 1487 nemoMrBLMrFlag, 1488 nemoMrBLHomeAddressPrefixLength, 1489 nemoMrBLCareofAddressPrefixLength, 1490 nemoMrBLActiveEgressIfIndex, 1491 nemoMrBLEstablishedHomeTunnelIfIndex, 1492 nemoMrMobilityMessagesSent, 1493 nemoMrMobilityMessagesRecd, 1494 nemoMrPrefixRegMode, 1495 nemoMrBindingAcksWONemoSupport, 1496 nemoMrBindingAcksRegTypeChangeDisallowed, 1497 nemoMrBindingAcksOperationNotPermitted, 1498 nemoMrBindingAcksInvalidPrefix, 1499 nemoMrBindingAcksNotAuthorizedForPrefix, 1500 nemoMrBindingAcksForwardingSetupFailed, 1501 nemoMrBindingAcksOtherError 1502 } 1503 STATUS current 1504 DESCRIPTION 1505 " A collection of objects for monitoring 1506 the registration details and statistics for 1507 the mobile router. 1508 " 1509 ::= { nemoGroups 5 } 1511 nemoHaSystemGroup OBJECT-GROUP 1512 OBJECTS { 1513 nemoHaMobileNetworkPrefixType, 1514 nemoHaMobileNetworkPrefix, 1515 nemoHaMobileNetworkPrefixLength, 1516 nemoHaMobileNetworkPrefixSource 1517 } 1518 STATUS current 1519 DESCRIPTION 1520 " A collection of objects for basic NEMO 1521 configuration monitoring at the home agent." 1522 ::= { nemoGroups 6 } 1524 nemoHaStatsGroup OBJECT-GROUP 1525 OBJECTS { 1526 nemoHaBURequestsAccepted, 1527 nemoHaBURequestsDenied, 1528 nemoHaBCEntryCreationTime, 1529 nemoHaBUAcceptedTime, 1530 nemoHaBURejectionTime, 1531 nemoHaRecentBURejectionCode, 1532 nemoHaCtrDiscontinuityTime 1533 } 1534 STATUS current 1535 DESCRIPTION 1536 " A collection of objects for monitoring 1537 NEMO registration-related statistics pertaining to 1538 the mobile routers registered with the home agent. 1539 " 1540 ::= { nemoGroups 7 } 1542 nemoHaGlobalStatsGroup OBJECT-GROUP 1543 OBJECTS { 1544 nemoHaBUAcksWONemoSupport, 1545 nemoHaBUAcksRegTypeChangeDisallowed, 1546 nemoHaBUAcksOperationNotPermitted, 1547 nemoHaBUAcksInvalidPrefix, 1548 nemoHaBUAcksNotAuthorizedForPrefix, 1549 nemoHaBUAcksForwardingSetupFailed, 1550 nemoHaBUAcksOtherError 1551 } 1552 STATUS current 1553 DESCRIPTION 1554 " A collection of objects for monitoring basic 1555 NEMO advertisement and registration statistics 1556 on a home agent." 1557 ::= { nemoGroups 8 } 1559 nemoNotificationGroup NOTIFICATION-GROUP 1560 NOTIFICATIONS { 1561 nemoHomeTunnelEstablished, 1562 nemoHomeTunnelReleased 1563 } 1564 STATUS current 1565 DESCRIPTION 1566 "A collection of notifications from a home agent 1567 or correspondent node to the Manager about the 1568 tunnel status of the mobile router. 1569 " 1570 ::= { nemoGroups 9 } 1572 -- Compliance statements 1573 nemoCoreCompliance MODULE-COMPLIANCE 1574 STATUS current 1575 DESCRIPTION 1576 "The compliance statement for SNMP entities 1577 which implement the NEMO-MIB. 1578 " 1579 MODULE -- this module 1580 MANDATORY-GROUPS { nemoSystemGroup 1581 } 1582 ::= { nemoCompliances 1 } 1584 nemoCompliance2 MODULE-COMPLIANCE 1585 STATUS current 1586 DESCRIPTION 1587 "The compliance statement for SNMP entities 1588 which implement the NEMO-MIB and support 1589 monitoring of the Binding Cache. 1590 There are a number of INDEX objects that cannot be 1591 represented in the form of OBJECT clauses in SMIv2, 1592 but for which there are compliance requirements, 1593 expressed in OBJECT clause form in this description: 1594 -- OBJECT mip6BindingHomeAddressType 1595 -- SYNTAX InetAddressType { ipv6(2) } 1596 -- DESCRIPTION 1597 -- This MIB module requires support for global 1598 -- ipv6 addresses for the mip6BindingHomeAddress 1599 -- object. 1600 -- 1601 -- OBJECT mip6BindingHomeAddress 1602 -- SYNTAX InetAddress (SIZE(16)) 1603 -- DESCRIPTION 1604 -- This MIB module requires support for global 1605 -- ipv6 addresses for the mip6BindingHomeAddress 1606 -- object. 1607 -- 1608 " 1609 MODULE -- this module 1610 MANDATORY-GROUPS { nemoSystemGroup, 1611 nemoBindingCacheGroup 1612 } 1613 ::= { nemoCompliances 2 } 1615 nemoCoreReadOnlyCompliance MODULE-COMPLIANCE 1616 STATUS current 1617 DESCRIPTION 1618 "The compliance statement for SNMP entities 1619 which implement the NEMO-MIB without support 1620 for read-write (i.e., in read-only mode). 1621 " 1622 MODULE -- this module 1623 MANDATORY-GROUPS { nemoSystemGroup 1624 } 1625 OBJECT nemoStatus 1626 MIN-ACCESS read-only 1627 DESCRIPTION 1628 "Write access is not required." 1629 ::= { nemoCompliances 3 } 1631 nemoReadOnlyCompliance2 MODULE-COMPLIANCE 1632 STATUS current 1633 DESCRIPTION 1634 "The compliance statement for SNMP entities 1635 which implement the NEMO-MIB without support 1636 for read-write (i.e., in read-only mode) and 1637 support monitoring of the Binding Cache. 1638 There are a number of INDEX objects that cannot be 1639 represented in the form of OBJECT clauses in SMIv2, 1640 but for which there are compliance requirements, 1641 expressed in OBJECT clause form in this description: 1642 -- OBJECT mip6BindingHomeAddressType 1643 -- SYNTAX InetAddressType { ipv6(2) } 1644 -- DESCRIPTION 1645 -- This MIB module requires support for global 1646 -- ipv6 addresses for the mip6BindingHomeAddress 1647 -- object. 1648 -- 1649 -- OBJECT mip6BindingHomeAddress 1650 -- SYNTAX InetAddress (SIZE(16)) 1651 -- DESCRIPTION 1652 -- This MIB module requires support for global 1653 -- ipv6 addresses for the mip6BindingHomeAddress 1654 -- object. 1655 -- 1656 " 1657 MODULE -- this module 1658 MANDATORY-GROUPS { nemoSystemGroup, 1659 nemoBindingCacheGroup 1660 } 1661 OBJECT nemoStatus 1662 MIN-ACCESS read-only 1663 DESCRIPTION 1664 "Write access is not required." 1665 ::= { nemoCompliances 4 } 1667 nemoMrCompliance MODULE-COMPLIANCE 1668 STATUS current 1669 DESCRIPTION 1670 "The compliance statement for SNMP entities 1671 which implement the NEMO-MIB for monitoring 1672 configuration-related information, registration 1673 details and statistics on a mobile router. 1674 There are a number of INDEX objects that cannot be 1675 represented in the form of OBJECT clauses in SMIv2, 1676 but for which there are compliance requirements, 1677 expressed in OBJECT clause form in this description: 1678 -- OBJECT mip6MnHomeAddressType 1679 -- SYNTAX InetAddressType { ipv6(2) } 1680 -- DESCRIPTION 1681 -- This MIB module requires support for global 1682 -- ipv6 addresses for the mip6MnHomeAddress 1683 -- object. 1684 -- 1685 -- OBJECT mip6MnHomeAddress 1686 -- SYNTAX InetAddress (SIZE(16)) 1687 -- DESCRIPTION 1688 -- This MIB module requires support for global 1689 -- ipv6 addresses for the mip6MnHomeAddress 1690 -- object. 1691 -- 1692 -- OBJECT mip6MnBLNodeAddressType 1693 -- SYNTAX InetAddressType { ipv6(2) } 1694 -- DESCRIPTION 1695 -- This MIB module requires support for global 1696 -- ipv6 addresses for the mip6MnBLNodeAddress 1697 -- object. 1698 -- 1699 -- OBJECT mip6MnBLNodeAddress 1700 -- SYNTAX InetAddress (SIZE(16)) 1701 -- DESCRIPTION 1702 -- This MIB module requires support for global 1703 -- ipv6 addresses for the mip6MnBLNodeAddress 1704 -- object. 1705 " 1706 MODULE -- this module 1707 MANDATORY-GROUPS { nemoStatsGroup, 1708 nemoMrConfGroup, 1709 nemoMrRegistrationGroup 1710 } 1711 ::= { nemoCompliances 5 } 1713 nemoMrReadOnlyCompliance2 MODULE-COMPLIANCE 1714 STATUS current 1715 DESCRIPTION 1716 "The compliance statement for SNMP entities 1717 which implement the NEMO-MIB without support 1718 for read-write (i.e., in read-only mode) and 1719 support for monitoring configuration-related 1720 information, registration details and statistics 1721 on a mobile router. 1722 There are a number of INDEX objects that cannot be 1723 represented in the form of OBJECT clauses in SMIv2, 1724 but for which there are compliance requirements, 1725 expressed in OBJECT clause form in this description: 1726 -- OBJECT mip6MnHomeAddressType 1727 -- SYNTAX InetAddressType { ipv6(2) } 1728 -- DESCRIPTION 1729 -- This MIB module requires support for global 1730 -- ipv6 addresses for the mip6MnHomeAddress 1731 -- object. 1732 -- 1733 -- OBJECT mip6MnHomeAddress 1734 -- SYNTAX InetAddress (SIZE(16)) 1735 -- DESCRIPTION 1736 -- This MIB module requires support for global 1737 -- ipv6 addresses for the mip6MnHomeAddress 1738 -- object. 1739 -- 1740 -- OBJECT mip6MnBLNodeAddressType 1741 -- SYNTAX InetAddressType { ipv6(2) } 1742 -- DESCRIPTION 1743 -- This MIB module requires support for global 1744 -- ipv6 addresses for the mip6MnBLNodeAddress 1745 -- object. 1746 -- 1747 -- OBJECT mip6MnBLNodeAddress 1748 -- SYNTAX InetAddress (SIZE(16)) 1749 -- DESCRIPTION 1750 -- This MIB module requires support for global 1751 -- ipv6 addresses for the mip6MnBLNodeAddress 1752 -- object. 1753 " 1754 MODULE -- this module 1755 MANDATORY-GROUPS { nemoStatsGroup, 1756 nemoMrConfGroup, 1757 nemoMrRegistrationGroup 1758 } 1760 OBJECT nemoMrPrefixRegMode 1761 MIN-ACCESS read-only 1762 DESCRIPTION 1763 "Write access is not required." 1764 ::= { nemoCompliances 6 } 1766 nemoHaCoreCompliance MODULE-COMPLIANCE 1767 STATUS current 1768 DESCRIPTION 1769 "The compliance statement for SNMP entities 1770 which implement the NEMO-MIB for configuration 1771 monitoring at the home agent. 1772 There are a number of INDEX objects that cannot be 1773 represented in the form of OBJECT clauses in SMIv2, 1774 but for which there are compliance requirements, 1775 expressed in OBJECT clause form in this description: 1777 -- OBJECT mip6BindingHomeAddressType 1778 -- SYNTAX InetAddressType { ipv6(2) } 1779 -- DESCRIPTION 1780 -- This MIB module requires support for global 1781 -- ipv6 addresses for the mip6BindingHomeAddress 1782 -- object. 1783 -- 1784 -- OBJECT mip6BindingHomeAddress 1785 -- SYNTAX InetAddress (SIZE(16)) 1786 -- DESCRIPTION 1787 -- This MIB module requires support for global 1788 -- ipv6 addresses for the mip6BindingHomeAddress 1789 -- object. 1790 -- 1791 " 1792 MODULE -- this module 1793 MANDATORY-GROUPS { nemoHaSystemGroup 1794 } 1795 ::= { nemoCompliances 7 } 1797 nemoHaCompliance2 MODULE-COMPLIANCE 1798 STATUS current 1799 DESCRIPTION 1800 "The compliance statement for SNMP entities 1801 which implement the NEMO-MIB with support for 1802 monitoring of the home agent functionality 1803 specifically the home-agent-registration-related 1804 statistics. 1805 There are a number of INDEX objects that cannot be 1806 represented in the form of OBJECT clauses in SMIv2, 1807 but for which there are compliance requirements, 1808 expressed in OBJECT clause form in this description: 1809 -- OBJECT mip6BindingHomeAddressType 1810 -- SYNTAX InetAddressType { ipv6(2) } 1811 -- DESCRIPTION 1812 -- This MIB module requires support for global 1813 -- ipv6 addresses for the mip6BindingHomeAddress 1814 -- object. 1815 -- 1816 -- OBJECT mip6BindingHomeAddress 1817 -- SYNTAX InetAddress (SIZE(16)) 1818 -- DESCRIPTION 1819 -- This MIB module requires support for global 1820 -- ipv6 addresses for the mip6BindingHomeAddress 1821 -- object. 1822 -- 1823 " 1824 MODULE -- this module 1825 MANDATORY-GROUPS { nemoHaSystemGroup, 1826 nemoHaStatsGroup, 1827 nemoHaGlobalStatsGroup 1828 } 1829 ::= { nemoCompliances 8 } 1831 nemoNotificationCompliance MODULE-COMPLIANCE 1832 STATUS current 1833 DESCRIPTION 1834 "The compliance statement for SNMP entities 1835 which implement the NEMO-MIB and support 1836 Notification from home agent. 1837 " 1838 MODULE -- this module 1839 MANDATORY-GROUPS { nemoNotificationGroup 1840 } 1841 ::= { nemoCompliances 9 } 1843 END 1845 2.6. IANA Considerations 1847 IANA should assign a base arc in the mib-2 (standards track) OID tree 1848 for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB. 1850 2.7. Security Considerations 1852 There are a number of management objects defined in this MIB module 1853 with a MAX-ACCESS clause of read-write. Such objects may be 1854 considered sensitive or vulnerable in some network environments. The 1855 support for SET operations in a non-secure environment without proper 1856 protection can have a negative effect on network operations. These 1857 are the tables and objects and their sensitivity/vulnerability: 1858 nemoStatus: The value of this object is used to enable or disable the 1859 NEMO functionality on a NEMO entity. Access to this MO may be abused 1860 to disrupt the communication that depends on NEMO. 1861 nemoMrPrefixRegMode: The value of this object is used to control the 1862 mode in which mobile network prefixes will be registered with the 1863 home agent. Access to this object may be abused to disrupt the 1864 setting up of mobile network prefixes. 1866 Some of the readable objects in this MIB module (i.e., objects with a 1867 MAX-ACCESS other than not-accessible) may be considered sensitive or 1868 vulnerable in some network environments. It is thus important to 1869 control even GET and/or NOTIFY access to these objects and possibly 1870 to even encrypt the values of these objects when sending them over 1871 the network via SNMP. These are the tables and objects and their 1872 sensitivity/vulnerability: 1874 nemoHaMobileNetworkPrefixType 1876 nemoHaMobileNetworkPrefix 1878 nemoHaMobileNetworkPrefixLength The above address-related objects may 1879 be considered to be particularly sensitive and/or private. The 1880 mobile network prefix-related objects reveal the configuration of the 1881 mobile router and as such may be considered to be sensitive. 1883 SNMP versions prior to SNMPv3 did not include adequate security. 1884 Even if the network itself is secure (for example by using IPSec), 1885 even then, there is no control as to who on the secure network is 1886 allowed to access and GET/SET (read/change/create/delete) the objects 1887 in this MIB module. 1889 It is RECOMMENDED that implementers consider the security features as 1890 provided by the SNMPv3 framework (see [RFC3410], section 8), 1891 including full support for the SNMPv3 cryptographic mechanisms (for 1892 authentication and privacy). 1894 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1895 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1896 enable cryptographic security. It is then a customer/operator 1897 responsibility to ensure that the SNMP entity giving access to an 1898 instance of this MIB module is properly configured to give access to 1899 the objects only to those principals (users) that have legitimate 1900 rights to indeed GET or SET (change/create/delete) them. 1902 2.8. Acknowledgments 1904 The authors would like to thank Alex Petrescu, Pascal Thubert, Kent 1905 Leung, T.J Kniveton and Thierry Ernst for their review comments on 1906 this document. 1908 2.9. References 1910 2.10. Normative References 1912 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 1913 Requirements Levels, BCP 14, RFC 2119, March 1997. 1915 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1916 Rose, M. and S. Waldbusser, Structure of Management Information 1917 Version 2 (SMIv2), STD 58, RFC 2578, April 1999. 1919 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1920 Rose, M. and S. Waldbusser, Textual Conventions for SMIv2, STD 58, 1921 RFC 2579, April 1999. 1923 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1924 Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58, 1925 RFC 2580, April 1999. 1927 [RFC2863] McCloghrie, K., and Kastenholz., F., The Interfaces Group 1928 MIB, RFC 2863, June 2000. 1930 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in 1931 IPv6 RFC 3775, June 2004. 1933 [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, 1934 Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005. 1936 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and Schoenwaelder, 1937 J., Textual Conventions for Internet Network Addresses, RFC 4001, 1938 February 2005. 1940 [RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The 1941 Mobile IPv6 MIB, RFC 4295, April 2006. 1943 2.11. Informative References 1945 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1946 Introduction and Applicability Statements for Internet-Standard 1947 Management Framework, RFC 3410, December 2002. 1949 [RFC4885] T. Ernst and H.-Y. Lach., Network Mobility Support 1950 Terminology, RFC 4885, July 2007. 1952 [RFC4886] T. Ernst. Network Mobility Support Goals and Requirements, 1953 RFC 4886, July 2007. 1955 Authors' Addresses 1957 Sri Gundavelli 1958 Cisco 1959 170 West Tasman Drive 1960 San Jose, CA 95134 1961 USA 1963 Phone: +1-408-527-6109 1964 Email: sgundave@cisco.com 1966 Glenn Mansfield Keeni 1967 Cyber Solutions 1968 6-6-3 Minami Yoshinari, Aoba-ku 1969 Sendai 989-3204, 1970 Japan 1972 Phone: +81-22-303-4012 1973 Email: glenn@cysols.com 1975 Kazuhide Koide 1976 Tohoku University 1977 2-1-1 Katahira, Aoba-ku 1978 Sendai 980-8577, 1979 Japan 1981 Phone: +81-22-217-5455 1982 Email: koide@shiratori.riec.tohoku.ac.jp 1984 Kenichi Nagami 1985 INTEC NetCore 1986 1-3-3, Shin-suna 1987 Koto-ku, Tokyo, 135-0075, 1988 Japan 1990 Phone: +81-3-5665-5069 1991 Email: nagami@inetcore.com