idnits 2.17.1 draft-ietf-mext-nemo-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1987. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1998. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2005. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2011. 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 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 (November 21, 2008) is 5625 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 (==), 7 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: May 25, 2009 Cyber Solutions 6 Kazuhide Koide 7 Tohoku University 8 Kenichi Nagami 9 INTEC NetCore 10 November 21, 2008 12 NEMO Management Information Base 13 draft-ietf-mext-nemo-mib-03 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on May 25, 2009. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB), 43 the network mobility support (NEMO) MIB, for use with network 44 management protocols in the Internet community. In particular, the 45 NEMO MIB will be used to monitor and control a Mobile IPv6 node with 46 NEMO functionality. 48 Table of Contents 50 1. The Internet-Standard Management Framework . . . . . . . . . . 3 51 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3 53 2.2. Implementation Guidance . . . . . . . . . . . . . . . . . 3 54 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 55 2.4. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . 4 56 2.5. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . 5 57 2.6. IANA Considerations . . . . . . . . . . . . . . . . . . . 41 58 2.7. Security Considerations . . . . . . . . . . . . . . . . . 41 59 2.8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 42 60 2.9. References . . . . . . . . . . . . . . . . . . . . . . . . 42 61 2.10. Normative References . . . . . . . . . . . . . . . . . . . 42 62 2.11. Informative References . . . . . . . . . . . . . . . . . . 43 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 64 Intellectual Property and Copyright Statements . . . . . . . . . . 45 66 1. The Internet-Standard Management Framework 68 For a detailed overview of the documents that describe the current 69 Internet-Standard Management Framework, please refer to section 7 of 70 RFC 3410 [RFC3410]. 72 Managed objects are accessed via a virtual information store, termed 73 the Management Information Base or MIB. MIB objects are generally 74 accessed through the Simple Network Management Protocol (SNMP). 76 Objects in the MIB are defined using the mechanisms defined in the 77 Structure of Management Information (SMI). This memo specifies a MIB 78 module that is compliant to the SMIv2, which is described in STD 58, 79 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 80 [RFC2580]. 82 2. Overview 84 2.1. The Mobile IPv6 Protocol and NEMO entities 86 Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes 87 to remain reachable while moving around in the IPv6 Internet. 88 Network Mobility Basic Support (NEMO) [RFC3963] is an extension to 89 the Mobile IPv6 protocol which facilitates the movement of an entire 90 network. The goals of Network Mobility support and related 91 terminology are discussed in [RFC4886] and [RFC4885], respectively. 93 Typically mobile routers implement NEMO functionality for achieving 94 network mobility. However, a mobile router may also function as a 95 mobile node. In the context of this document, an entity that 96 implements the NEMO protocol is a NEMO entity. 98 This document defines a set of managed objects (MOs) that can be used 99 to monitor and control NEMO entities. 101 2.2. Implementation Guidance 103 This document focuses on the management of a NEMO entity. The 104 MIPv6MIB [RFC4295] defines the managed objects for a mobile node. 105 Implementations supporting both the mobile node and NEMO 106 functionality SHOULD implement the managed objects defined for the 107 NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB. 109 2.3. Terminology 111 The terminology used in this document is consistent with the 112 definitions used in the Mobile IPv6 protocol specification [RFC3775] 113 and the NEMO Basic Support specification [RFC3963]. 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in BCP 118 14, RFC 2119 [RFC2119]. 120 2.4. MIB Design 122 The NEMO MIB comprises of the following groups of definitions: 124 - nemoCore: a generic group containing objects that are common to all 125 the NEMO entities. 127 - nemoHa: this group models the home agent service. It is composed 128 of objects specific to the services and associated advertisement 129 parameters offered by the home agent on each of its links. It also 130 contains objects pertaining to the maintenance of the home agent list 131 on each of the links on which the service is offered. 133 - nemoMr: this group models the mobile router service. It is 134 composed of objects specific to the Dynamic Home Agent discovery 135 function and related parameters. It also contains objects that 136 record the movement of the mobile router. 138 - nemoNotifications: defines the set of notifications that will be 139 used to asynchronously monitor the NEMO entities. 141 The tables contained in the above groups are as follows: 143 nemoBindingCacheTable : models the binding cache on the home agent 144 and correspondent node. It contains details of the Binding Update 145 requests that have been received and accepted. 147 nemoMrEgressIfTable : contains information on the configured egress 148 interfaces. 150 nemoMrBLTable : models the Binding Update List on the mobile router. 151 It contains information about the registration requests sent by the 152 mobile router and the corresponding results. 154 nemoHaCounterTable : contains registration statistics for all mobile 155 routers registered with the home agent. 157 nemoHaMobileNetworkPrefixTable : contains the list of the mobile 158 network prefixes that are maintained by the home agent. 160 2.5. The NEMO MIB 162 NEMO-MIB DEFINITIONS ::= BEGIN 163 IMPORTS 164 MODULE-IDENTITY, mib-2, Unsigned32, Counter32, 165 Integer32, Gauge32, 166 -- Counter64, 167 OBJECT-TYPE, NOTIFICATION-TYPE 168 FROM SNMPv2-SMI 169 TEXTUAL-CONVENTION, 170 TruthValue, DateAndTime, TimeStamp 171 FROM SNMPv2-TC 172 SnmpAdminString 173 FROM SNMP-FRAMEWORK-MIB 174 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 175 FROM SNMPv2-CONF 176 InetAddressType, InetAddress, InetAddressPrefixLength 177 FROM INET-ADDRESS-MIB 178 InterfaceIndex 179 FROM IF-MIB 180 mip6BindingHomeAddressType, mip6BindingHomeAddress, 181 mip6MnBLEntry, mip6BindingCacheEntry, 182 -- mip6MnHomeAddressType, mip6MnHomeAddress, 183 mip6MnBLCOAType, mip6MnBLCOA 184 FROM MOBILEIPV6-MIB 185 ; 187 nemoMIB MODULE-IDENTITY 188 LAST-UPDATED "200811160000Z" -- 16th November, 2008 189 ORGANIZATION "IETF MEXT Working Group" 190 CONTACT-INFO 191 " Sri Gundavelli 192 Postal: Cisco 193 170 W.Tasman Drive, 194 San Jose, CA 95134 195 USA 196 Tel: +1-408-527-6109 197 Email: sgundave@cisco.com 199 Glenn Mansfield Keeni 201 Postal: Cyber Solutions Inc. 202 6-6-3, Minami Yoshinari 203 Aoba-ku, Sendai, Japan 989-3204. 204 Tel: +81-22-303-4012 205 Fax: +81-22-303-4015 206 E-mail: glenn@cysols.com 208 Kenichi Nagami 209 Postal: INTEC NetCore Inc. 210 1-3-3, Shin-suna 211 Koto-ku, Tokyo, 135-0075 212 Japan 213 Tel: +81-3-5665-5069 214 E-mail: nagami@inetcore.com 216 Kazuhide Koide 217 Postal: Tohoku University 218 Research Institute of Electrical Communication, 219 Tohoku University. 220 2-1-1 Katahira, Aoba-ku, 221 Sendai, Miyagi, Japan 980-8577. 222 Tel: +81-22-217-5455 223 E-mail: koide@shiratori.riec.tohoku.ac.jp 225 Support Group E-mail: mext@ietf.org 226 " 228 DESCRIPTION 229 "The MIB module for monitoring a NEMO entity. 231 Copyright (C) The IETF Trust (2008). This 232 version of this MIB module is part of RFC XXXX; 233 see the RFC itself for full legal notices. 234 " 235 -- RFC Ed.: replace XXXX with actual RFC number and remove this 236 -- note 238 REVISION "200811160000Z" -- 16th November 2008 239 DESCRIPTION "Initial version, published as RFC XXXX." 241 -- RFC Ed.: replace XXXX with actual RFC number and remove this 242 -- note 244 ::= { mib-2 YYY } -- will be assigned by IANA 246 -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' 247 -- subtree and record the assignment in the SMI Numbers 248 -- registry. 249 -- 250 -- RFC Ed.: When the above assignment has been made, please 251 -- remove the above note 252 -- replace "YYY" here with the assigned value and 253 -- remove this note. 255 -- The NEMO MIB has the following primary groups 257 nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } 258 nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 } 259 nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 3 } 260 nemoCore OBJECT IDENTIFIER ::= { nemoObjects 1 } 261 nemoMr OBJECT IDENTIFIER ::= { nemoObjects 2 } 262 nemoCn OBJECT IDENTIFIER ::= { nemoObjects 3 } 263 nemoHa OBJECT IDENTIFIER ::= { nemoObjects 4 } 265 -- The sub groups 267 nemoSystem OBJECT IDENTIFIER ::= { nemoCore 1 } 268 nemoBindings OBJECT IDENTIFIER ::= { nemoCore 2 } 269 nemoConfiguration OBJECT IDENTIFIER ::= { nemoCore 3 } 270 nemoStats OBJECT IDENTIFIER ::= { nemoCore 4 } 272 nemoMrSystem OBJECT IDENTIFIER ::= { nemoMr 1 } 273 nemoMrConf OBJECT IDENTIFIER ::= { nemoMr 2 } 274 nemoMrRegistration OBJECT IDENTIFIER ::= { nemoMr 3 } 275 nemoMrGlobalStats OBJECT IDENTIFIER ::= { nemoMr 4 } 277 nemoHaAdvertisement OBJECT IDENTIFIER ::= { nemoHa 1 } 278 nemoHaStats OBJECT IDENTIFIER ::= { nemoHa 2 } 279 nemoHaRegistration OBJECT IDENTIFIER ::= { nemoHa 3 } 280 nemoHaGlobalStats OBJECT IDENTIFIER ::= { nemoHaStats 1 } 281 -- Textual Conventions 282 NemoBURequestRejectionCode ::= TEXTUAL-CONVENTION 283 STATUS current 284 DESCRIPTION 285 "The value of the status field in the Binding 286 Acknowledgment message when the Binding Update 287 was rejected for NEMO specific reasons. 288 " 289 REFERENCE 290 "RFC 3963 : Section 4.2" 291 SYNTAX INTEGER { 292 mobileRouterOperationNotPermitted (1), --(Code 140) 293 invalidPrefix (2), --(Code 141) 294 notAuthorizedForPrefix (3), --(Code 142) 295 forwardingSetupFailed (4) --(Code 143) 296 } 298 -- 299 -- 300 -- nemoSystem group 301 -- 302 -- 304 nemoCapabilities OBJECT-TYPE 305 SYNTAX BITS { 306 mobileRouter (0), 307 homeAgentSupport (1) 308 } 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "This object indicates the NEMO functions that 313 are supported by this managed entity. Multiple 314 NEMO functions may be supported by a single 315 entity. 316 " 317 REFERENCE 318 "RFC 3963 : Section 3" 319 ::= { nemoSystem 1 } 321 nemoStatus OBJECT-TYPE 322 SYNTAX INTEGER { enabled(1), disabled(2) } 323 MAX-ACCESS read-write 324 STATUS current 325 DESCRIPTION 326 "This object indicates whether the NEMO 327 function is enabled for the managed entity. If it 328 is enabled, the agent discovery and registration 329 functions will be operational. 330 Changing the status from enabled(1) to disabled(2) 331 will terminate the agent discovery and registration 332 functions. On the other hand, changing the status 333 from disabled(2) to enabled(1) will start the agent 334 discovery and registration functions. 336 The value of this object SHOULD remain unchanged 337 across reboots of the managed entity. 338 " 339 ::= { nemoSystem 2 } 341 nemoCounterDiscontinuityTime OBJECT-TYPE 342 SYNTAX TimeStamp 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The value of sysUpTime on the most recent occasion 347 at which any one or more of this NEMO entity's 348 counters viz, counters with OID prefix 'nemoMrConf' 349 or 'nemoMrRegnCounters' or 'nemoMrGlobalStats' 350 or 'nemoHaGlobalStats' suffered a discontinuity. 351 If no such discontinuities have occurred since the 352 last re-initialization of the local management 353 subsystem, then this object will have a zero value. 354 " 355 ::= { nemoStats 1 } 356 -- 357 -- 358 -- nemoConfiguration group 359 -- 360 -- 362 nemoMrBLTable OBJECT-TYPE 363 SYNTAX SEQUENCE OF NemoMrBLEntry 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "This table corresponds to the Binding Update List 368 (BL) that includes NEMO related information and 369 is maintained by the mobile router. The table 370 holds a row for every binding that the mobile 371 router has established or is trying to establish. 372 Entries from the table are deleted as the lifetime 373 of the binding expires. 375 " 376 REFERENCE 377 "RFC 3775 : Section 4.5, 11.1, RFC 3963 : Section 5.2" 378 ::= { nemoMrRegistration 1 } 380 nemoMrBLEntry OBJECT-TYPE 381 SYNTAX NemoMrBLEntry 382 MAX-ACCESS not-accessible 383 STATUS current 384 DESCRIPTION 385 "An entry pertaining to nemo-related information 386 contained in a Binding Update sent by a nemo-enabled 387 mobile router to its home agent. 388 " 389 AUGMENTS {mip6MnBLEntry} 390 ::= { nemoMrBLTable 1 } 392 NemoMrBLEntry ::= SEQUENCE { 393 nemoMrBLMode INTEGER, 394 nemoMrBLMrFlag TruthValue, 395 nemoMrBLHomeAddressPrefixLength InetAddressPrefixLength, 396 nemoMrBLCareofAddressPrefixLength InetAddressPrefixLength, 397 nemoMrBLActiveEgressIfIndex InterfaceIndex, 398 nemoMrBLEstablishedHomeTunnelIfIndex InterfaceIndex 399 } 400 nemoMrBLMode OBJECT-TYPE 401 SYNTAX INTEGER { 402 implicitMode (1), 403 explicitMode (2) 404 } 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "implicitMode(1): the Mobile Network Prefix Option 409 is not included in the Binding Update by the mobile 410 router. 411 explicitMode(2): the mobile router included one or 412 more Mobile Network Prefix Options in the Binding 413 Update. 414 " 415 REFERENCE 416 "RFC 3963 : Section 5.2" 417 ::= { nemoMrBLEntry 1 } 419 nemoMrBLMrFlag OBJECT-TYPE 420 SYNTAX TruthValue 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "true(1): the mobile router sent the Binding Update 425 with Mobile Router Flag set. 426 false(0): the mobile router did not send the binding 427 update with Mobile Router Flag set. This implies that 428 the mobile router is acting as a mobile node. 429 " 430 REFERENCE 431 "RFC 3963 : Section 4.1, 5.1" 432 ::= { nemoMrBLEntry 2 } 434 nemoMrBLHomeAddressPrefixLength OBJECT-TYPE 435 SYNTAX InetAddressPrefixLength 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The prefix length of the mobile router's home network. 440 " 441 REFERENCE 442 "RFC 3963 : Section 3" 443 ::= { nemoMrBLEntry 3 } 445 nemoMrBLCareofAddressPrefixLength OBJECT-TYPE 446 SYNTAX InetAddressPrefixLength 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The prefix length of the care-of Address of the 451 mobile router. 452 " 453 REFERENCE 454 "RFC 3963 : Section 3" 455 ::= { nemoMrBLEntry 4 } 457 nemoMrBLActiveEgressIfIndex OBJECT-TYPE 458 SYNTAX InterfaceIndex 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The interface index of the currently active 463 egress interface. 464 " 465 REFERENCE 466 "RFC 3963 : Section 5.5" 468 ::= { nemoMrBLEntry 5 } 470 nemoMrBLEstablishedHomeTunnelIfIndex OBJECT-TYPE 471 SYNTAX InterfaceIndex 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The interface index of the tunnel established 476 between the mobile router and the home agent 477 for NEMO traffic. 478 " 479 REFERENCE 480 "RFC 3963 : Section 5.5" 481 ::= { nemoMrBLEntry 6 } 483 -- Mobile Router Registration Group Counters 485 nemoMrRegnCounters OBJECT IDENTIFIER ::= { nemoMrRegistration 2 } 487 nemoMrMobilityMessagesSent OBJECT-TYPE 488 SYNTAX Counter32 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "The total number of mobility messages, i.e. IPv6 493 datagrams with Mobility Header, sent by the mobile 494 node. This will include Binding Updates sent by a 495 mobile router with the Mobile Router Flag set. 496 Discontinuities in the value of this counter can 497 occur at re-initialization of the management system, 498 and at other times as indicated by the value of 499 nemoCounterDiscontinuityTime. 500 " 501 REFERENCE 502 "RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1" 503 ::= { nemoMrRegnCounters 1 } 505 nemoMrMobilityMessagesRecd OBJECT-TYPE 506 SYNTAX Counter32 507 MAX-ACCESS read-only 508 STATUS current 509 DESCRIPTION 510 "The total number of mobility messages, i.e. IPv6 511 datagrams with Mobility Header, received by the 512 mobile node. This will include Binding 513 Acknowledgements with Mobile Router Flag set, that 514 are sent to a mobile router. 516 Discontinuities in the value of this counter can 517 occur at re-initialization of the management system, 518 and at other times as indicated by the value of 519 nemoCounterDiscontinuityTime. 520 " 521 REFERENCE 522 "RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1, 4.2" 523 ::= { nemoMrRegnCounters 2 } 525 nemoMrPrefixRegMode OBJECT-TYPE 526 SYNTAX INTEGER { 527 implicitMode (1), 528 explicitMode (2) 529 } 530 MAX-ACCESS read-write 531 STATUS current 532 DESCRIPTION 533 "This object indicates the mode in which the mobile 534 network prefixes will be registered with the home 535 agent. 536 implicitMode(1): the Mobile Network Prefix Option will 537 not be included in the Binding Update by the mobile 538 router. 539 explicitMode(2): the mobile router will include one or 540 more Mobile Network Prefix Options in the Binding 541 Update. 542 " 543 REFERENCE 544 "RFC 3963 : Section 5.2" 546 ::= { nemoMrRegistration 3 } 548 nemoHaMobileNetworkPrefixTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF NemoHaMobileNetworkPrefixEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "This table contains the mobile network prefixes 554 that the home agent maintains for the Mobile Router. 555 The mobile network prefixes in this table are 556 registered by Binding Updates or are manually 557 pre-configured. 558 " 559 REFERENCE 560 "RFC 3963 : Section 6.1.2" 561 ::= { nemoHaRegistration 1 } 563 nemoHaMobileNetworkPrefixEntry OBJECT-TYPE 564 SYNTAX NemoHaMobileNetworkPrefixEntry 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "An entry for a mobile network prefix. 570 The instances of the columnar objects in this entry 571 pertain to an interface for a particular value of 572 mip6BindingHomeAddressType, mip6BindingHomeAddress, 573 and nemoHaMobileNetworkPrefixSeqNo. 574 The nemoHaMobileNetworkPrefixSeqNo object is used to 575 distinguish between multiple instances of 576 the mobile network prefix in the same Binding Update 577 for the same set of mip6BindingHomeAddressType and 578 mip6BindingHomeAddress. 579 There is no upper-bound on the maximum number of 580 mobile network prefixes in a Binding Update but, for 581 practical purposes, the upper bound of the value 582 nemoHaMobileNetworkPrefixSeqNo is set to 1024. 584 Implementers need to be aware that if the total 585 number of octets in mip6BindingHomeAddress 586 exceeds 112, then OIDs of column 587 instances in this row will have more than 128 588 sub-identifiers and cannot be accessed using 589 SNMPv1, SNMPv2c, or SNMPv3. 590 " 591 INDEX { mip6BindingHomeAddressType, 592 mip6BindingHomeAddress, 593 nemoHaMobileNetworkPrefixSeqNo 594 } 595 ::= { nemoHaMobileNetworkPrefixTable 1 } 597 NemoHaMobileNetworkPrefixEntry ::= SEQUENCE { 598 nemoHaMobileNetworkPrefixSeqNo Integer32, 599 nemoHaMobileNetworkPrefixType InetAddressType, 600 nemoHaMobileNetworkPrefix InetAddress, 601 nemoHaMobileNetworkPrefixLength Unsigned32, 602 nemoHaMobileNetworkPrefixSource INTEGER 603 } 605 nemoHaMobileNetworkPrefixSeqNo OBJECT-TYPE 606 SYNTAX Integer32 (1..1024) 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "A Binding Update may have multiple mobile network 611 prefixes. 612 This object along with mip6BindingHomeAddressType, 613 and mip6BindingHomeAddress uniquely identifies a 614 row containing a single mobile network prefix for 615 a mobile router in this table. 616 " 617 REFERENCE 618 "RFC 3963 : Section 2, 6.1, 6.2" 619 ::= { nemoHaMobileNetworkPrefixEntry 1 } 621 nemoHaMobileNetworkPrefixType OBJECT-TYPE 622 SYNTAX InetAddressType 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The address type for the mobile network prefix 627 that follows. 628 " 629 ::= { nemoHaMobileNetworkPrefixEntry 2 } 631 nemoHaMobileNetworkPrefix OBJECT-TYPE 632 SYNTAX InetAddress 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "A mobile network prefix related to the 637 corresponding Binding Update. 639 The type of the address represented by this object 640 is specified by the corresponding 641 nemoHaMobileNetworkPrefixType object. 642 " 643 REFERENCE 644 "RFC 3963 : Section 2 , 6.1, 6.2" 645 ::= { nemoHaMobileNetworkPrefixEntry 3 } 647 nemoHaMobileNetworkPrefixLength OBJECT-TYPE 648 SYNTAX Unsigned32 (0..128) 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "The length of the prefix specified by the corresponding 653 nemoHaMobileNetworkPrefix Object. 654 " 655 REFERENCE 656 "RFC 3963 : Section 4.3, 6.1, 6.2" 658 ::= { nemoHaMobileNetworkPrefixEntry 4 } 660 nemoHaMobileNetworkPrefixSource OBJECT-TYPE 661 SYNTAX INTEGER { 662 configured (1), 663 bindingUpdate (2) 664 } 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The information source of the mobile network prefix 670 configured with the Binding Update. 671 configured(1) indicates that mobile network prefix 672 has been manually pre-configured. 673 bindingUpdate(2) indicates that the information is 674 introduced to the home agent by the mobile network 675 prefix option in the Binding Updates received by the 676 home agent. 677 " 678 REFERENCE 679 "RFC 3963 : Section 4.3, 6.1, 6.2" 680 ::= { nemoHaMobileNetworkPrefixEntry 5 } 682 nemoBindingCacheTable OBJECT-TYPE 683 SYNTAX SEQUENCE OF NemoBindingCacheEntry 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "This table models the Binding Cache 688 that includes NEMO related information and 689 is maintained by the home agent. 690 Entries in this table are not required to survive 691 a reboot of the home agent. 692 " 693 REFERENCE 694 "RFC 3775 : Section 4.5, 9.1, 10.1, 695 RFC 3963 : Section 6.1" 696 ::= { nemoBindings 1 } 698 nemoBindingCacheEntry OBJECT-TYPE 699 SYNTAX NemoBindingCacheEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "An entry containing additional information related 704 to nemo-enabled entries in the binding cache table 705 of the home agent. 706 " 707 AUGMENTS {mip6BindingCacheEntry} 708 ::= { nemoBindingCacheTable 1 } 710 NemoBindingCacheEntry ::= SEQUENCE { 711 nemoBindingMrFlag TruthValue, 712 nemoBindingMrMode INTEGER 713 } 715 nemoBindingMrFlag OBJECT-TYPE 716 SYNTAX TruthValue 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "true(1) indicates that the binding cache entry is from 721 an entity acting as a mobile router. 722 false(0) implies that the binding cache entry is from 723 an entity acting as a mobile node. 724 " 725 REFERENCE 726 "RFC 3963 : Section 6.1.1, 6.2" 727 ::= { nemoBindingCacheEntry 1 } 729 nemoBindingMrMode OBJECT-TYPE 730 SYNTAX INTEGER { 731 implicitMode(1), 732 explicitMode(2) 733 } 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "implicitMode(1): the Mobile Network Prefix Option is 738 not included in the Binding Update by the mobile 739 router. 740 explicitMode(2): the mobile router included one or 741 more Mobile Network Prefix Options in the Binding 742 Update. 743 " 744 REFERENCE 745 "RFC 3963 : Section 5.2, 6.1.1, 6.2" 746 ::= { nemoBindingCacheEntry 2 } 748 -- 749 -- nemoMrEgressIfTable 750 -- 751 nemoMrEgressIfTable OBJECT-TYPE 752 SYNTAX SEQUENCE OF NemoMrEgressIfEntry 753 MAX-ACCESS not-accessible 754 STATUS current 755 DESCRIPTION 756 "A table representing the egress interfaces that 757 will be used by the mobile router for roaming to 758 foreign networks. Each entry in this table 759 represents a configured egress interface. 760 " 761 ::= { nemoMrSystem 1 } 763 nemoMrEgressIfEntry OBJECT-TYPE 764 SYNTAX NemoMrEgressIfEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "An entry in the egress interface table. It 769 represents a single egress interface entry. 770 " 771 INDEX { nemoMrEgressIfIndex, nemoMrEgressIfPriority } 772 ::= { nemoMrEgressIfTable 1 } 774 NemoMrEgressIfEntry ::= 775 SEQUENCE { 776 nemoMrEgressIfIndex InterfaceIndex, 777 nemoMrEgressIfPriority Unsigned32, 778 nemoMrEgressIfDescription SnmpAdminString, 779 nemoMrEgressIfRoamHoldDownTime Gauge32 780 } 782 nemoMrEgressIfIndex OBJECT-TYPE 783 SYNTAX InterfaceIndex 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "The index of the interface on the mobile router. 788 " 789 ::= { nemoMrEgressIfEntry 1 } 791 nemoMrEgressIfPriority OBJECT-TYPE 792 SYNTAX Unsigned32 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "The priority configured to the egress interface. 797 This value will be configured to a value between 0 798 and 255. 799 " 800 ::= { nemoMrEgressIfEntry 2 } 802 nemoMrEgressIfDescription OBJECT-TYPE 803 SYNTAX SnmpAdminString 804 MAX-ACCESS read-write 805 STATUS current 806 DESCRIPTION 807 "The description of the egress interface on the 808 mobile router, that will be used for roaming to 809 foreign networks. 810 " 811 ::= { nemoMrEgressIfEntry 3 } 813 nemoMrEgressIfRoamHoldDownTime OBJECT-TYPE 814 SYNTAX Gauge32 815 UNITS "seconds" 816 MAX-ACCESS read-write 817 STATUS current 818 DESCRIPTION 819 "This object indicates the time for which the 820 egress interface will be held down during roaming 821 to avoid interface flapping. 822 " 823 ::= { nemoMrEgressIfEntry 4 } 825 nemoMrDiscoveryRequests OBJECT-TYPE 826 SYNTAX Counter32 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "Total number of Modified Dynamic Home Agent Address 831 Discovery Requests, with Mobile Router Support Flag 832 set, sent by the mobile router. 833 Discontinuities in the value of this counter can 834 occur at re-initialization of the management system, 835 and at other times as indicated by the value of 836 nemoCounterDiscontinuityTime. 837 " 838 REFERENCE 839 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.1" 841 ::= { nemoMrConf 1 } 843 nemoMrDiscoveryReplies OBJECT-TYPE 844 SYNTAX Counter32 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "Total number of Modified Dynamic Home Agent Address 849 Discovery Replies, with Mobile Router Support Flag 850 set, received by the mobile router. 851 Discontinuities in the value of this counter can 852 occur at re-initialization of the management system, 853 and at other times as indicated by the value of 854 nemoCounterDiscontinuityTime. 855 " 856 REFERENCE 857 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2" 858 ::= { nemoMrConf 2 } 860 nemoMrDiscoveryRepliesRouterFlagZero OBJECT-TYPE 861 SYNTAX Counter32 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "Total number of Modified Dynamic Home Agent Address 866 Discovery Replies with Mobile Router Support Flag set 867 to 0 although the flag in the corresponding request 868 is set to 1. 869 It implies that there is no home agent that supports 870 Mobile Router functionality in the home network. 871 Discontinuities in the value of this counter can 872 occur at re-initialization of the management system, 873 and at other times as indicated by the value of 874 nemoCounterDiscontinuityTime. 875 " 876 REFERENCE 877 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2" 878 ::= { nemoMrConf 3 } 880 nemoMrMovedHome OBJECT-TYPE 881 SYNTAX Counter32 882 MAX-ACCESS read-only 883 STATUS current 884 DESCRIPTION 885 "Number of times the mobile router has detected 886 movement from a foreign network to its home 887 network. 889 Discontinuities in the value of this counter can 890 occur at re-initialization of the management system, 891 and at other times as indicated by the value of 892 nemoCounterDiscontinuityTime. 893 " 894 REFERENCE 895 "RFC 3963 : Section 3." 896 ::= { nemoMrConf 4 } 898 nemoMrMovedOutofHome OBJECT-TYPE 899 SYNTAX Counter32 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "Number of times the mobile router has detected 904 movement to a foreign network from the home 905 network, has acquired a care-of address and 906 has initiated the care-of address registration 907 process. 908 Discontinuities in the value of this counter can 909 occur at re-initialization of the management system, 910 and at other times as indicated by the value of 911 nemoCounterDiscontinuityTime. 912 " 913 REFERENCE 914 "RFC 3963 : Section 3." 915 ::= { nemoMrConf 5 } 917 nemoMrMovedFNtoFN OBJECT-TYPE 918 SYNTAX Counter32 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "Number of times the mobile router has detected 923 movement to/from a foreign network from/to another 924 foreign network. Note that 'movement' implies 925 movement in layer 3, i.e. the mobile routers care-of 926 address changed and it initiated the care-of address 927 registration process. 928 If there are multiple egress interfaces, this counter 929 counts the total number of movements. 930 The movement as a mobile node of the mobile entity 931 is not counted. 932 Discontinuities in the value of this counter can 933 occur at re-initialization of the management system, 934 and at other times as indicated by the value of 935 nemoCounterDiscontinuityTime. 936 " 937 REFERENCE 938 "RFC 3963 : Section 3." 939 ::= { nemoMrConf 6 } 941 nemoMrBetterIfDetected OBJECT-TYPE 942 SYNTAX Counter32 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "Number of times the NEMO entity has found an egress 947 interface with better priority. 948 Discontinuities in the value of this counter can 949 occur at re-initialization of the management system, 950 and at other times as indicated by the value of 951 nemoCounterDiscontinuityTime. 952 " 953 ::= { nemoMrConf 7 } 955 -- 956 -- nemoStats:nemoMrGlobalStats 957 -- 959 nemoMrBindingAcksWONemoSupport OBJECT-TYPE 960 SYNTAX Counter32 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "The total number of Binding Acknowledgements without 965 NEMO support received by the mobile router. 967 Discontinuities in the value of this counter can 968 occur at re-initialization of the management system, 969 and at other times as indicated by the value of 970 nemoCounterDiscontinuityTime. 971 " 972 REFERENCE 973 "RFC 3963 : Section 5.3." 974 ::= { nemoMrGlobalStats 1 } 976 nemoMrBindingAcksRegTypeChangeDisallowed OBJECT-TYPE 977 SYNTAX Counter32 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "The total number of Binding Acknowledgements 982 received by the mobile router with status code 983 indicating 984 'Registration type change disallowed' (Code 139). 986 Discontinuities in the value of this counter can 987 occur at re-initialization of the management system, 988 and at other times as indicated by the value of 989 nemoCounterDiscontinuityTime. 990 " 991 REFERENCE 992 "RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2" 993 ::= { nemoMrGlobalStats 2 } 995 nemoMrBindingAcksOperationNotPermitted OBJECT-TYPE 996 SYNTAX Counter32 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The total number of Binding Acknowledgement 1001 received by the mobile router with status code 1002 indicating 1003 'Mobile Router Operation not permitted' 1004 (Code 140). 1006 Discontinuities in the value of this counter can 1007 occur at re-initialization of the management system, 1008 and at other times as indicated by the value of 1009 nemoCounterDiscontinuityTime. 1010 " 1011 REFERENCE 1012 "RFC 3963 : Section 6.6" 1013 ::= { nemoMrGlobalStats 3 } 1015 nemoMrBindingAcksInvalidPrefix OBJECT-TYPE 1016 SYNTAX Counter32 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "The total number of Binding Acknowledgement 1021 received by the mobile router with status code 1022 indicating 'Invalid Prefix' (Code 141). 1024 Discontinuities in the value of this counter can 1025 occur at re-initialization of the management system, 1026 and at other times as indicated by the value of 1027 nemoCounterDiscontinuityTime. 1028 " 1029 REFERENCE 1030 "RFC 3963 : Section 6.6." 1031 ::= { nemoMrGlobalStats 4 } 1033 nemoMrBindingAcksNotAuthorizedForPrefix OBJECT-TYPE 1034 SYNTAX Counter32 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The total number of Binding Acknowledgements 1039 received by the mobile router with status code 1040 indicating 1041 'Not Authorized for Prefix' (Code 142). 1043 Discontinuities in the value of this counter can 1044 occur at re-initialization of the management system, 1045 and at other times as indicated by the value of 1046 nemoCounterDiscontinuityTime. 1047 " 1048 REFERENCE 1049 "RFC 3963 : Section 6.6." 1050 ::= { nemoMrGlobalStats 5 } 1052 nemoMrBindingAcksForwardingSetupFailed OBJECT-TYPE 1053 SYNTAX Counter32 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The total number of Binding Acknowledgements 1058 received by the mobile router with status code 1059 indicating 'Forwarding Setup failed' (Code 143). 1061 Discontinuities in the value of this counter can 1062 occur at re-initialization of the management system, 1063 and at other times as indicated by the value of 1064 nemoCounterDiscontinuityTime. 1065 " 1066 REFERENCE 1067 "RFC 3963 : Section 6.6." 1068 ::= { nemoMrGlobalStats 6 } 1070 nemoMrBindingAcksOtherError OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The total number of Binding Acknowledgements 1076 received by the mobile router (Mobile Router Flag is 1077 set) with status code other than 1078 successfully processed , --(Code 0 ) 1079 mobileRouterOperationNotPermitted (1), --(Code 140) 1080 invalidPrefix (2), --(Code 141) 1081 notAuthorizedForPrefix (3), --(Code 142) 1082 forwardingSetupFailed (4). --(Code 143) 1084 Discontinuities in the value of this counter can 1085 occur at re-initialization of the management system, 1086 and at other times as indicated by the value of 1087 nemoCounterDiscontinuityTime. 1088 " 1089 REFERENCE 1090 "RFC 3963 : Section 6.6." 1091 ::= { nemoMrGlobalStats 7 } 1093 -- 1094 -- nemoStats:nemoHaGlobalStats 1095 -- 1097 nemoHaBindingAcksWONemoSupport OBJECT-TYPE 1098 SYNTAX Counter32 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "The total number of Binding Acknowledgements 1103 without NEMO support sent by the home agent. 1105 Discontinuities in the value of this counter can 1106 occur at re-initialization of the management system, 1107 and at other times as indicated by the value of 1108 nemoCounterDiscontinuityTime. 1109 " 1110 REFERENCE 1111 "RFC 3963 : Section 5.3" 1112 ::= { nemoHaGlobalStats 1 } 1114 nemoHaBindingAcksRegTypeChangeDisallowed OBJECT-TYPE 1115 SYNTAX Counter32 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION 1119 "The total number of Binding Update requests 1120 rejected by the home agent with status code 1121 in the Binding Acknowledgement indicating 1122 'Registration type change disallowed' (Code 139). 1124 Discontinuities in the value of this counter can 1125 occur at re-initialization of the management system, 1126 and at other times as indicated by the value of 1127 nemoCounterDiscontinuityTime. 1128 " 1129 REFERENCE 1130 "RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2" 1131 ::= { nemoHaGlobalStats 2 } 1133 nemoHaBindingAcksOperationNotPermitted OBJECT-TYPE 1134 SYNTAX Counter32 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "The total number of Binding Update requests 1139 rejected by the home agent with status code in 1140 the Binding Acknowledgement indicating 1141 'Mobile Router Operation not permitted' 1142 (Code 140). 1144 Discontinuities in the value of this counter can 1145 occur at re-initialization of the management system, 1146 and at other times as indicated by the value of 1147 nemoCounterDiscontinuityTime. 1148 " 1149 REFERENCE 1150 "RFC 3963 : Section 6.6" 1151 ::= { nemoHaGlobalStats 3 } 1153 nemoHaBindingAcksInvalidPrefix OBJECT-TYPE 1154 SYNTAX Counter32 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The total number of Binding Update requests 1159 rejected by the home agent with status code in 1160 the Binding Acknowledgement indicating 1161 'Invalid Prefix' (Code 141). 1163 Discontinuities in the value of this counter can 1164 occur at re-initialization of the management system, 1165 and at other times as indicated by the value of 1166 nemoCounterDiscontinuityTime. 1167 " 1168 REFERENCE 1169 "RFC 3963 : Section 6.6" 1170 ::= { nemoHaGlobalStats 4 } 1172 nemoHaBindingAcksNotAuthorizedForPrefix OBJECT-TYPE 1173 SYNTAX Counter32 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "The total number of Binding Update requests 1178 rejected by the home agent with status code in 1179 the Binding Acknowledgement indicating 1180 'Not Authorized for Prefix' (Code 142). 1182 Discontinuities in the value of this counter can 1183 occur at re-initialization of the management system, 1184 and at other times as indicated by the value of 1185 nemoCounterDiscontinuityTime. 1186 " 1187 REFERENCE 1188 "RFC 3963 : Section 6.6" 1189 ::= { nemoHaGlobalStats 5 } 1191 nemoHaBindingAcksForwardingSetupFailed OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The total number of Binding Update requests 1197 rejected by the home agent with status code in 1198 the Binding Acknowledgement indicating 1199 'Forwarding Setup failed' (Code 143). 1201 Discontinuities in the value of this counter can 1202 occur at re-initialization of the management system, 1203 and at other times as indicated by the value of 1204 nemoCounterDiscontinuityTime. 1205 " 1206 REFERENCE 1207 "RFC 3963 : Section 6.6" 1208 ::= { nemoHaGlobalStats 6 } 1210 nemoHaBindingAcksOtherError OBJECT-TYPE 1211 SYNTAX Counter32 1212 MAX-ACCESS read-only 1213 STATUS current 1214 DESCRIPTION 1215 "The total number of Binding Update requests 1216 from mobile routers (Mobile Router Flag is 1217 set) rejected by the home agent with status code 1218 other than 1219 mobileRouterOperationNotPermitted (1), --(Code 140) 1220 invalidPrefix (2), --(Code 141) 1221 notAuthorizedForPrefix (3), --(Code 142) 1222 forwardingSetupFailed (4). --(Code 143) 1224 Discontinuities in the value of this counter can 1225 occur at re-initialization of the management system, 1226 and at other times as indicated by the value of 1227 nemoCounterDiscontinuityTime. 1228 " 1229 REFERENCE 1230 "RFC 3963 : Section 6.6." 1231 ::= { nemoHaGlobalStats 7 } 1233 nemoHaCounterTable OBJECT-TYPE 1234 SYNTAX SEQUENCE OF NemoHaCounterEntry 1235 MAX-ACCESS not-accessible 1236 STATUS current 1237 DESCRIPTION 1238 "A table containing registration statistics for all 1239 mobile routers registered with the home agent. 1240 " 1241 ::= { nemoHaStats 2 } 1243 nemoHaCounterEntry OBJECT-TYPE 1244 SYNTAX NemoHaCounterEntry 1245 MAX-ACCESS not-accessible 1246 STATUS current 1247 DESCRIPTION 1248 "Home agent registration statistics for a mobile 1249 router. 1251 Implementors need to be aware that if the total 1252 number of octets in mip6BindingHomeAddress 1253 exceeds 113 then OIDs of column instances in 1254 this row will have more than 128 sub-identifiers and 1255 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1256 " 1257 INDEX { mip6BindingHomeAddressType, 1258 mip6BindingHomeAddress 1259 } 1260 ::= { nemoHaCounterTable 1 } 1262 NemoHaCounterEntry ::= SEQUENCE { 1263 nemoHaBURequestsAccepted Counter32, 1264 nemoHaBURequestsDenied Counter32, 1265 nemoHaBCEntryCreationTime DateAndTime, 1266 nemoHaBUAcceptedTime DateAndTime, 1267 nemoHaBURejectionTime DateAndTime, 1268 nemoHaRecentBURejectionCode NemoBURequestRejectionCode, 1269 nemoHaCtrDiscontinuityTime TimeStamp 1270 } 1272 nemoHaBURequestsAccepted OBJECT-TYPE 1273 SYNTAX Counter32 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Total number of Binding Update requests from the 1278 mobile router accepted by the home agent. 1279 Discontinuities in the value of this counter can 1280 occur at re-initialization of the management system, 1281 and at other times as indicated by the value of 1282 nemoHaCtrDiscontinuityTime. 1283 " 1284 ::= { nemoHaCounterEntry 1 } 1286 nemoHaBURequestsDenied OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "Total number of Binding Update requests from the 1292 mobile router rejected by the home agent. 1293 Discontinuities in the value of this counter can 1294 occur at re-initialization of the management system, 1295 and at other times as indicated by the value of 1296 nemoHaCtrDiscontinuityTime. 1297 " 1298 ::= { nemoHaCounterEntry 2 } 1300 nemoHaBCEntryCreationTime OBJECT-TYPE 1301 SYNTAX DateAndTime 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "The time when the current Binding Cache entry was 1306 created for the mobile router. 1307 " 1308 ::= { nemoHaCounterEntry 3 } 1310 nemoHaBUAcceptedTime OBJECT-TYPE 1311 SYNTAX DateAndTime 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The time at which the last Binding Update was 1316 accepted by the home agent for this mobile router. 1317 " 1318 ::= { nemoHaCounterEntry 4 } 1320 nemoHaBURejectionTime OBJECT-TYPE 1321 SYNTAX DateAndTime 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "The time at which the last Binding Update was 1326 rejected by the home agent for this mobile router. 1327 If there have been no rejections then this object 1328 will be inaccessible. 1329 " 1330 ::= { nemoHaCounterEntry 5 } 1332 nemoHaRecentBURejectionCode OBJECT-TYPE 1333 SYNTAX NemoBURequestRejectionCode 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "The Status code (>= 128) in the latest Binding 1338 Acknowledgment indicating a rejection, sent to this 1339 mobile router. 1340 In case a Binding Update request is rejected and a 1341 Binding Acknowledgment is not sent to this mobile 1342 router then this will be the value of the Status 1343 code that corresponds to the reason of the rejection. 1344 If there have been no Binding Update request 1345 rejections then this object will be inaccessible. 1346 " 1347 ::= { nemoHaCounterEntry 6 } 1349 nemoHaCtrDiscontinuityTime OBJECT-TYPE 1350 SYNTAX TimeStamp 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The value of sysUpTime on the most recent occasion 1355 at which any one or more of counters in this row 1356 viz, instances of 'nemoHaBURequestsAccepted' and 1357 'nemoHaBURequestsDenied' suffered a discontinuity. 1358 If no such discontinuity has occurred since the 1359 last re-initialization of the local management 1360 subsystem, then this object will have a zero value. 1361 " 1362 ::= { nemoHaCounterEntry 7 } 1364 -- 1365 -- 1366 -- nemoNotifications 1367 -- 1368 -- 1370 nemoHomeTunnelEstablished NOTIFICATION-TYPE 1371 OBJECTS { 1372 nemoMrBLActiveEgressIfIndex, 1373 nemoMrBLEstablishedHomeTunnelIfIndex, 1374 mip6MnBLCOAType, 1375 mip6MnBLCOA, 1376 nemoMrBLHomeAddressPrefixLength, 1377 nemoMrBLCareofAddressPrefixLength 1378 } 1379 STATUS current 1380 DESCRIPTION 1381 "This notification is sent by the mobile router 1382 every time the tunnel is established between the 1383 home agent and the mobile router. 1384 " 1385 REFERENCE 1386 "RFC 3963 : Section 5.5" 1387 ::= { nemoNotifications 1 } 1389 nemoHomeTunnelReleased NOTIFICATION-TYPE 1390 OBJECTS { 1391 nemoMrBLActiveEgressIfIndex, 1392 nemoMrBLEstablishedHomeTunnelIfIndex, 1393 mip6MnBLCOAType, 1394 mip6MnBLCOA, 1395 nemoMrBLHomeAddressPrefixLength, 1396 nemoMrBLCareofAddressPrefixLength 1397 } 1398 STATUS current 1399 DESCRIPTION 1400 "This notification is sent by the mobile router 1401 every time the tunnel is deleted between the home 1402 agent and the mobile router. 1403 " 1404 REFERENCE 1405 "RFC 3963 : Section 5.5" 1406 ::= { nemoNotifications 2} 1408 -- Conformance information 1409 nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } 1410 nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } 1412 -- Units of conformance 1413 nemoSystemGroup OBJECT-GROUP 1414 OBJECTS { 1415 nemoCapabilities, 1416 nemoStatus 1417 } 1418 STATUS current 1419 DESCRIPTION 1420 " A collection of objects for basic NEMO 1421 monitoring." 1422 ::= { nemoGroups 1 } 1424 nemoBindingCacheGroup OBJECT-GROUP 1425 OBJECTS { 1426 nemoBindingMrFlag, 1427 nemoBindingMrMode 1428 } 1429 STATUS current 1430 DESCRIPTION 1431 " A collection of objects for monitoring the 1432 NEMO extensions of the Binding Cache." 1433 ::= { nemoGroups 2 } 1435 nemoStatsGroup OBJECT-GROUP 1436 OBJECTS { 1437 nemoCounterDiscontinuityTime 1438 } 1439 STATUS current 1440 DESCRIPTION 1441 " A collection of objects for 1442 monitoring NEMO statistics." 1443 ::= { nemoGroups 3 } 1445 nemoMrConfGroup OBJECT-GROUP 1446 OBJECTS { 1447 nemoMrEgressIfDescription, 1448 nemoMrEgressIfRoamHoldDownTime, 1449 nemoMrDiscoveryRequests, 1450 nemoMrDiscoveryReplies, 1451 nemoMrDiscoveryRepliesRouterFlagZero, 1452 nemoMrMovedHome, 1453 nemoMrMovedOutofHome, 1454 nemoMrMovedFNtoFN, 1455 nemoMrBetterIfDetected 1456 } 1457 STATUS current 1458 DESCRIPTION 1459 " A collection of objects for monitoring 1460 the configuration-related information on 1461 the mobile router. 1462 " 1463 ::= { nemoGroups 4 } 1465 nemoMrRegistrationGroup OBJECT-GROUP 1466 OBJECTS { 1467 nemoMrBLMode, 1468 nemoMrBLMrFlag, 1469 nemoMrBLHomeAddressPrefixLength, 1470 nemoMrBLCareofAddressPrefixLength, 1471 nemoMrBLActiveEgressIfIndex, 1472 nemoMrBLEstablishedHomeTunnelIfIndex, 1473 nemoMrMobilityMessagesSent, 1474 nemoMrMobilityMessagesRecd, 1475 nemoMrPrefixRegMode, 1476 nemoMrBindingAcksWONemoSupport, 1477 nemoMrBindingAcksRegTypeChangeDisallowed, 1478 nemoMrBindingAcksOperationNotPermitted, 1479 nemoMrBindingAcksInvalidPrefix, 1480 nemoMrBindingAcksNotAuthorizedForPrefix, 1481 nemoMrBindingAcksForwardingSetupFailed, 1482 nemoMrBindingAcksOtherError 1483 } 1484 STATUS current 1485 DESCRIPTION 1486 " A collection of objects for monitoring 1487 the registration details and statistics for 1488 the mobile router. 1489 " 1490 ::= { nemoGroups 5 } 1492 nemoHaSystemGroup OBJECT-GROUP 1493 OBJECTS { 1494 nemoHaMobileNetworkPrefixType, 1495 nemoHaMobileNetworkPrefix, 1496 nemoHaMobileNetworkPrefixLength, 1497 nemoHaMobileNetworkPrefixSource 1498 } 1499 STATUS current 1500 DESCRIPTION 1501 " A collection of objects for basic NEMO 1502 configuration monitoring at the home agent." 1503 ::= { nemoGroups 6 } 1505 nemoHaStatsGroup OBJECT-GROUP 1506 OBJECTS { 1507 nemoHaBURequestsAccepted, 1508 nemoHaBURequestsDenied, 1509 nemoHaBCEntryCreationTime, 1510 nemoHaBUAcceptedTime, 1511 nemoHaBURejectionTime, 1512 nemoHaRecentBURejectionCode, 1513 nemoHaCtrDiscontinuityTime 1514 } 1515 STATUS current 1516 DESCRIPTION 1517 " A collection of objects for monitoring 1518 NEMO registration-related statistics on the 1519 home agent. 1520 " 1521 ::= { nemoGroups 7 } 1523 nemoHaGlobalStatsGroup OBJECT-GROUP 1524 OBJECTS { 1525 nemoHaBindingAcksWONemoSupport, 1526 nemoHaBindingAcksRegTypeChangeDisallowed, 1527 nemoHaBindingAcksOperationNotPermitted, 1528 nemoHaBindingAcksInvalidPrefix, 1529 nemoHaBindingAcksNotAuthorizedForPrefix, 1530 nemoHaBindingAcksForwardingSetupFailed, 1531 nemoHaBindingAcksOtherError 1532 } 1533 STATUS current 1534 DESCRIPTION 1535 " A collection of objects for monitoring basic 1536 NEMO advertisement and registration statistics 1537 on a home agent." 1538 ::= { nemoGroups 8 } 1540 nemoNotificationGroup NOTIFICATION-GROUP 1541 NOTIFICATIONS { 1542 nemoHomeTunnelEstablished, 1543 nemoHomeTunnelReleased 1544 } 1545 STATUS current 1546 DESCRIPTION 1547 "A collection of notifications from a home agent 1548 or correspondent node to the Manager about the 1549 tunnel status of the mobile router. 1550 " 1551 ::= { nemoGroups 9 } 1553 -- Compliance statements 1554 nemoCoreCompliance MODULE-COMPLIANCE 1555 STATUS current 1556 DESCRIPTION 1557 "The compliance statement for SNMP entities 1558 which implement the NEMO-MIB. 1559 " 1560 MODULE -- this module 1561 MANDATORY-GROUPS { nemoSystemGroup 1562 } 1563 ::= { nemoCompliances 1 } 1565 nemoCompliance2 MODULE-COMPLIANCE 1566 STATUS current 1567 DESCRIPTION 1568 "The compliance statement for SNMP entities 1569 which implement the NEMO-MIB and support 1570 monitoring of the Binding Cache. 1571 There are a number of INDEX objects that cannot be 1572 represented in the form of OBJECT clauses in SMIv2, 1573 but for which there are compliance requirements, 1574 expressed in OBJECT clause form in this description: 1575 -- OBJECT mip6BindingHomeAddressType 1576 -- SYNTAX InetAddressType { ipv6(2) } 1577 -- DESCRIPTION 1578 -- This MIB module requires support for global 1579 -- ipv6 addresses for the mip6BindingHomeAddress 1580 -- object. 1582 -- 1583 -- OBJECT mip6BindingHomeAddress 1584 -- SYNTAX InetAddress (SIZE(16)) 1585 -- DESCRIPTION 1586 -- This MIB module requires support for global 1587 -- ipv6 addresses for the mip6BindingHomeAddress 1588 -- object. 1589 -- 1590 " 1591 MODULE -- this module 1592 MANDATORY-GROUPS { nemoSystemGroup, 1593 nemoBindingCacheGroup 1594 } 1595 ::= { nemoCompliances 2 } 1597 nemoCoreReadOnlyCompliance MODULE-COMPLIANCE 1598 STATUS current 1599 DESCRIPTION 1600 "The compliance statement for SNMP entities 1601 which implement the NEMO-MIB without support 1602 for read-write (i.e., in read-only mode). 1603 " 1604 MODULE -- this module 1605 MANDATORY-GROUPS { nemoSystemGroup 1606 } 1607 OBJECT nemoStatus 1608 MIN-ACCESS read-only 1609 DESCRIPTION 1610 "Write access is not required." 1611 ::= { nemoCompliances 3 } 1613 nemoReadOnlyCompliance2 MODULE-COMPLIANCE 1614 STATUS current 1615 DESCRIPTION 1616 "The compliance statement for SNMP entities 1617 which implement the NEMO-MIB without support 1618 for read-write (i.e., in read-only mode) and 1619 support monitoring of the Binding Cache. 1620 There are a number of INDEX objects that cannot be 1621 represented in the form of OBJECT clauses in SMIv2, 1622 but for which there are compliance requirements, 1623 expressed in OBJECT clause form in this description: 1624 -- OBJECT mip6BindingHomeAddressType 1625 -- SYNTAX InetAddressType { ipv6(2) } 1626 -- DESCRIPTION 1627 -- This MIB module requires support for global 1628 -- ipv6 addresses for the mip6BindingHomeAddress 1629 -- object. 1631 -- 1632 -- OBJECT mip6BindingHomeAddress 1633 -- SYNTAX InetAddress (SIZE(16)) 1634 -- DESCRIPTION 1635 -- This MIB module requires support for global 1636 -- ipv6 addresses for the mip6BindingHomeAddress 1637 -- object. 1638 -- 1639 " 1640 MODULE -- this module 1641 MANDATORY-GROUPS { nemoSystemGroup, 1642 nemoBindingCacheGroup 1643 } 1644 OBJECT nemoStatus 1645 MIN-ACCESS read-only 1646 DESCRIPTION 1647 "Write access is not required." 1648 ::= { nemoCompliances 4 } 1650 nemoMrCompliance MODULE-COMPLIANCE 1651 STATUS current 1652 DESCRIPTION 1653 "The compliance statement for SNMP entities 1654 which implement the NEMO-MIB for monitoring 1655 configuration-related information, registration 1656 details and statistics on a mobile router. 1657 There are a number of INDEX objects that cannot be 1658 represented in the form of OBJECT clauses in SMIv2, 1659 but for which there are compliance requirements, 1660 expressed in OBJECT clause form in this description: 1661 -- OBJECT mip6MnHomeAddressType 1662 -- SYNTAX InetAddressType { ipv6(2) } 1663 -- DESCRIPTION 1664 -- This MIB module requires support for global 1665 -- ipv6 addresses for the mip6MnHomeAddress 1666 -- object. 1667 -- 1668 -- OBJECT mip6MnHomeAddress 1669 -- SYNTAX InetAddress (SIZE(16)) 1670 -- DESCRIPTION 1671 -- This MIB module requires support for global 1672 -- ipv6 addresses for the mip6MnHomeAddress 1673 -- object. 1674 -- 1675 -- OBJECT mip6MnBLNodeAddressType 1676 -- SYNTAX InetAddressType { ipv6(2) } 1677 -- DESCRIPTION 1678 -- This MIB module requires support for global 1679 -- ipv6 addresses for the mip6MnBLNodeAddress 1680 -- object. 1681 -- 1682 -- OBJECT mip6MnBLNodeAddress 1683 -- SYNTAX InetAddress (SIZE(16)) 1684 -- DESCRIPTION 1685 -- This MIB module requires support for global 1686 -- ipv6 addresses for the mip6MnBLNodeAddress 1687 -- object. 1688 " 1689 MODULE -- this module 1690 MANDATORY-GROUPS { nemoStatsGroup, 1691 nemoMrConfGroup, 1692 nemoMrRegistrationGroup 1693 } 1694 ::= { nemoCompliances 5 } 1696 nemoMrReadOnlyCompliance2 MODULE-COMPLIANCE 1697 STATUS current 1698 DESCRIPTION 1699 "The compliance statement for SNMP entities 1700 which implement the NEMO-MIB without support 1701 for read-write (i.e., in read-only mode) and 1702 support for monitoring configuration-related 1703 information, registration details and statistics 1704 on a mobile router. 1705 There are a number of INDEX objects that cannot be 1706 represented in the form of OBJECT clauses in SMIv2, 1707 but for which there are compliance requirements, 1708 expressed in OBJECT clause form in this description: 1709 -- OBJECT mip6MnHomeAddressType 1710 -- SYNTAX InetAddressType { ipv6(2) } 1711 -- DESCRIPTION 1712 -- This MIB module requires support for global 1713 -- ipv6 addresses for the mip6MnHomeAddress 1714 -- object. 1715 -- 1716 -- OBJECT mip6MnHomeAddress 1717 -- SYNTAX InetAddress (SIZE(16)) 1718 -- DESCRIPTION 1719 -- This MIB module requires support for global 1720 -- ipv6 addresses for the mip6MnHomeAddress 1721 -- object. 1722 -- 1723 -- OBJECT mip6MnBLNodeAddressType 1724 -- SYNTAX InetAddressType { ipv6(2) } 1725 -- DESCRIPTION 1726 -- This MIB module requires support for global 1727 -- ipv6 addresses for the mip6MnBLNodeAddress 1728 -- object. 1729 -- 1730 -- OBJECT mip6MnBLNodeAddress 1731 -- SYNTAX InetAddress (SIZE(16)) 1732 -- DESCRIPTION 1733 -- This MIB module requires support for global 1734 -- ipv6 addresses for the mip6MnBLNodeAddress 1735 -- object. 1736 " 1737 MODULE -- this module 1738 MANDATORY-GROUPS { nemoStatsGroup, 1739 nemoMrConfGroup, 1740 nemoMrRegistrationGroup 1741 } 1742 OBJECT nemoMrEgressIfDescription 1743 MIN-ACCESS read-only 1744 DESCRIPTION 1745 "Write access is not required." 1747 OBJECT nemoMrEgressIfRoamHoldDownTime 1748 MIN-ACCESS read-only 1749 DESCRIPTION 1750 "Write access is not required." 1752 OBJECT nemoMrPrefixRegMode 1753 MIN-ACCESS read-only 1754 DESCRIPTION 1755 "Write access is not required." 1756 ::= { nemoCompliances 6 } 1758 nemoHaCoreCompliance MODULE-COMPLIANCE 1759 STATUS current 1760 DESCRIPTION 1761 "The compliance statement for SNMP entities 1762 which implement the NEMO-MIB for configuration 1763 monitoring at the home agent. 1764 There are a number of INDEX objects that cannot be 1765 represented in the form of OBJECT clauses in SMIv2, 1766 but for which there are compliance requirements, 1767 expressed in OBJECT clause form in this description: 1768 -- OBJECT mip6BindingHomeAddressType 1769 -- SYNTAX InetAddressType { ipv6(2) } 1770 -- DESCRIPTION 1771 -- This MIB module requires support for global 1772 -- ipv6 addresses for the mip6BindingHomeAddress 1773 -- object. 1774 -- 1775 -- OBJECT mip6BindingHomeAddress 1776 -- SYNTAX InetAddress (SIZE(16)) 1777 -- DESCRIPTION 1778 -- This MIB module requires support for global 1779 -- ipv6 addresses for the mip6BindingHomeAddress 1780 -- object. 1781 -- 1782 " 1783 MODULE -- this module 1784 MANDATORY-GROUPS { nemoHaSystemGroup 1785 } 1786 ::= { nemoCompliances 7 } 1788 nemoHaCompliance2 MODULE-COMPLIANCE 1789 STATUS current 1790 DESCRIPTION 1791 "The compliance statement for SNMP entities 1792 which implement the NEMO-MIB with support for 1793 monitoring of the home agent functionality 1794 specifically the home-agent-registration-related 1795 statistics. 1796 There are a number of INDEX objects that cannot be 1797 represented in the form of OBJECT clauses in SMIv2, 1798 but for which there are compliance requirements, 1799 expressed in OBJECT clause form in this description: 1800 -- OBJECT mip6BindingHomeAddressType 1801 -- SYNTAX InetAddressType { ipv6(2) } 1802 -- DESCRIPTION 1803 -- This MIB module requires support for global 1804 -- ipv6 addresses for the mip6BindingHomeAddress 1805 -- object. 1806 -- 1807 -- OBJECT mip6BindingHomeAddress 1808 -- SYNTAX InetAddress (SIZE(16)) 1809 -- DESCRIPTION 1810 -- This MIB module requires support for global 1811 -- ipv6 addresses for the mip6BindingHomeAddress 1812 -- object. 1813 -- 1814 " 1815 MODULE -- this module 1816 MANDATORY-GROUPS { nemoHaSystemGroup, 1817 nemoHaStatsGroup, 1818 nemoHaGlobalStatsGroup 1819 } 1820 ::= { nemoCompliances 8 } 1822 nemoNotificationCompliance MODULE-COMPLIANCE 1823 STATUS current 1824 DESCRIPTION 1825 "The compliance statement for SNMP entities 1826 which implement the NEMO-MIB and support 1827 Notification from home agent. 1828 " 1829 MODULE -- this module 1830 MANDATORY-GROUPS { nemoNotificationGroup 1831 } 1832 ::= { nemoCompliances 9 } 1834 END 1836 2.6. IANA Considerations 1838 IANA should assign a base arc in the mib-2 (standards track) OID tree 1839 for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB. 1841 2.7. Security Considerations 1843 There are a number of management objects defined in this MIB module 1844 with a MAX-ACCESS clause of read-write. Such objects may be 1845 considered sensitive or vulnerable in some network environments. The 1846 support for SET operations in a non-secure environment without proper 1847 protection can have a negative effect on network operations. These 1848 are the tables and objects and their sensitivity/vulnerability: 1849 nemoStatus: The value of this object is used to enable or disable the 1850 NEMO functionality on a NEMO entity. Access to this MO may be abused 1851 to disrupt the communication that depends on NEMO. 1852 nemoMrPrefixRegMode: The value of this object is used to control the 1853 mode in which mobile network prefixes will be registered with the 1854 home agent. Access to this object may be abused to disrupt the 1855 setting up of mobile network prefixes. 1857 Some of the readable objects in this MIB module (i.e., objects with a 1858 MAX-ACCESS other than not-accessible) may be considered sensitive or 1859 vulnerable in some network environments. It is thus important to 1860 control even GET and/or NOTIFY access to these objects and possibly 1861 to even encrypt the values of these objects when sending them over 1862 the network via SNMP. These are the tables and objects and their 1863 sensitivity/vulnerability: The address-related objects in this MIB 1864 may be considered to be particularly sensitive and/or private. The 1865 mobile network prefix- related objects reveal the configuration of 1866 the mobile router. This information may be considered to be private 1867 and sensitive and must be carefully handled. 1868 nemoHaMobileNetworkPrefixType nemoHaMobileNetworkPrefix 1869 nemoHaMobileNetworkPrefixLength 1871 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 and Thierry Ernst for their review comments on 1894 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 1973 Full Copyright Statement 1975 Copyright (C) The IETF Trust (2008). 1977 This document is subject to the rights, licenses and restrictions 1978 contained in BCP 78, and except as set forth therein, the authors 1979 retain all their rights. 1981 This document and the information contained herein are provided on an 1982 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1983 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1984 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1985 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1986 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1987 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1989 Intellectual Property 1991 The IETF takes no position regarding the validity or scope of any 1992 Intellectual Property Rights or other rights that might be claimed to 1993 pertain to the implementation or use of the technology described in 1994 this document or the extent to which any license under such rights 1995 might or might not be available; nor does it represent that it has 1996 made any independent effort to identify any such rights. Information 1997 on the procedures with respect to rights in RFC documents can be 1998 found in BCP 78 and BCP 79. 2000 Copies of IPR disclosures made to the IETF Secretariat and any 2001 assurances of licenses to be made available, or the result of an 2002 attempt made to obtain a general license or permission for the use of 2003 such proprietary rights by implementers or users of this 2004 specification can be obtained from the IETF on-line IPR repository at 2005 http://www.ietf.org/ipr. 2007 The IETF invites any interested party to bring to its attention any 2008 copyrights, patents or patent applications, or other proprietary 2009 rights that may cover technology that may be required to implement 2010 this standard. Please address the information to the IETF at 2011 ietf-ipr@ietf.org.