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