idnits 2.17.1 draft-ietf-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 1806. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1817. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1824. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1830. 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 (July 09, 2007) is 6129 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 NEMO Working Group Sri Gundavelli 3 Internet-Draft Cisco 4 Intended status: Standards Track Glenn M. Keeni 5 Expires: January 10, 2008 Cyber Solutions 6 Kazuhide Koide 7 Tohoku University 8 Kenichi Nagami 9 INTEC NetCore 10 July 09, 2007 12 NEMO Management Information Base 13 draft-ietf-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 January 10, 2008. 40 Copyright Notice 42 Copyright (C) The IETF Trust (2007). 44 Abstract 46 This memo defines a portion of the Management Information Base (MIB), 47 the network mobility support (NEMO) MIB, for use with network 48 management protocols in the Internet community. In particular, the 49 NEMO MIB will be used to monitor and control a mobile ipv6 node with 50 NEMO functionality. 52 Table of Contents 54 1. The Internet-Standard Management Framework . . . . . . . . . . 3 55 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. The Mobile IPv6 Protocol and NEMO entities . . . . . . . . 3 57 2.2. Implementation Guidance . . . . . . . . . . . . . . . . . 3 58 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 59 3. MIB Design . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 4. The NEMO MIB . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 39 63 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 65 8.1. Normative References . . . . . . . . . . . . . . . . . . . 40 66 8.2. Informative References . . . . . . . . . . . . . . . . . . 40 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 68 Intellectual Property and Copyright Statements . . . . . . . . . . 42 70 1. The Internet-Standard Management Framework 72 For a detailed overview of the documents that describe the current 73 Internet-Standard Management Framework, please refer to section 7 of 74 RFC 3410 [RFC3410]. 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. MIB objects are generally 78 accessed through the Simple Network Management Protocol (SNMP). 80 Objects in the MIB are defined using the mechanisms defined in the 81 Structure of Management Information (SMI). This memo specifies a MIB 82 module that is compliant to the SMIv2, which is described in STD 58, 83 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 84 [RFC2580]. 86 2. Overview 88 2.1. The Mobile IPv6 Protocol and NEMO entities 90 Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes 91 to remain reachable while moving around in the IPv6 Internet. 92 Network Mobility Basic Support (NEMO) [RFC3963] is an extension to 93 the Mobile IPv6 protocol which facilitates the movement of an entire 94 network. The goals of Network Mobility support and related 95 terminology are discussed in [NEMOGOAL] and [NEMOTERM], respectively. 97 Typically mobile routers implement NEMO functionality for achieving 98 network mobility. However, a mobile router may also function as a 99 mobile node. In the context of this document, an entity that 100 implements the NEMO protocol is a NEMO entity. 102 This document defines a set of managed objects (MOs) that can be used 103 to monitor and control NEMO entities. 105 2.2. Implementation Guidance 107 This document focuses on the management of a NEMO entity. The 108 MIPv6MIB [RFC4295] defines the managed objects for a mobile node. 109 Implementations supporting both the mobile node and NEMO 110 functionality SHOULD implement the managed objects defined for the 111 NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB. 113 2.3. Terminology 115 The terminology used in this document is consistent with the 116 definitions used in the Mobile IPv6 protocol specification[RFC3775] 117 and the NEMO Basic Support specification [RFC3963]. 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 121 "OPTIONAL" in this document are to be interpreted as described in BCP 122 14, RFC 2119 [RFC2119]. 124 3. MIB Design 126 The NEMO MIB comprises of the following primary groups: 128 o nemoSystem 130 o nemoConfiguration 132 o nemoStats 134 o nemoNotifications 136 o nemoConformance 138 The nemoSystem group provides the general information of the NEMO 139 entity. The objects in this group cover the current home 140 registration state. 142 The nemoConfiguration group contains information relevant to the 143 implementation and operation of the NEMO protocol. 145 The nemoStats group defines the statistics related to the NEMO 146 protocol operations. 148 The nemoNotifications group defines the notifications generated by 149 the NEMO entity in response to the operationally interesting state 150 changes in the NEMO protocol. 152 The nemoConformance group identifies the managed objects that needs 153 to be implemented for conforming to this draft. 155 4. The NEMO MIB 156 NEMO-MIB DEFINITIONS ::= BEGIN 157 IMPORTS 158 MODULE-IDENTITY, mib-2, Unsigned32, Counter32, 159 Integer32, Gauge32, 160 -- Counter64, 161 OBJECT-TYPE, NOTIFICATION-TYPE 162 FROM SNMPv2-SMI 163 TEXTUAL-CONVENTION, 164 TruthValue, DateAndTime 165 FROM SNMPv2-TC 166 SnmpAdminString 167 FROM SNMP-FRAMEWORK-MIB 168 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 169 FROM SNMPv2-CONF 170 InetAddressType, InetAddress, InetAddressPrefixLength 171 FROM INET-ADDRESS-MIB 172 InterfaceIndex 173 FROM IF-MIB 174 mip6BindingHomeAddressType, mip6BindingHomeAddress, 175 mip6HaListEntry, mip6MnBLEntry, mip6BindingCacheEntry 176 FROM MOBILEIPV6-MIB 177 ; 179 nemoMIB MODULE-IDENTITY 180 LAST-UPDATED "200703040000Z" -- 4th March, 2007 181 ORGANIZATION "IETF NEMO Working Group" 182 CONTACT-INFO 183 " Sri Gundavelli 184 Postal: Cisco 185 170 W.Tasman Drive, 186 San Jose, CA 95134 187 USA 188 Tel: +1-408-527-6109 189 Email: sgundave@cisco.com 191 Glenn Mansfield Keeni 192 Postal: Cyber Solutions Inc. 193 6-6-3, Minami Yoshinari 194 Aoba-ku, Sendai, Japan 989-3204. 195 Tel: +81-22-303-4012 196 Fax: +81-22-303-4015 197 E-mail: glenn@cysols.com 199 Kenichi Nagami 201 Postal: INTEC NetCore Inc. 202 1-3-3, Shin-suna 203 Koto-ku, Tokyo, 135-0075 204 Japan 205 Tel: +81-3-5665-5069 206 E-mail: nagami@inetcore.com 208 Kazuhide Koide 209 Postal: Tohoku University 210 Katahira Campus 211 Sendai 212 Japan 213 Tel: +81-22-217-5454 214 E-mail: koide@shiratori.riec.tohoku.ac.jp 216 Support Group E-mail: nemo@ietf.org" 218 DESCRIPTION 219 "The MIB module for monitoring a NEMO entity. 221 Copyright (C) The IETF Trust (2007). This 222 version of this MIB module is part of RFC XXXX; 223 see the RFC itself for full legal notices. 224 " 225 -- RFC Ed.: replace XXXX with actual RFC number and remove this 226 -- note 228 REVISION "200703040000Z" -- 4th March 2007 229 DESCRIPTION "Initial version, published as RFC XXXX." 231 -- RFC Ed.: replace XXXX with actual RFC number and remove this 232 -- note 234 ::= { mib-2 YYY } -- will be assigned by IANA 236 -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' 237 -- subtree and record the assignment in the SMI Numbers 238 -- registry. 239 -- 240 -- RFC Ed.: When the above assignment has been made, please 241 -- remove the above note 242 -- replace "YYY" here with the assigned value and 243 -- remove this note. 245 -- The NEMO MIB has the following 5 primary groups 247 nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } 248 nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 } 249 nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 3 } 250 nemoCore OBJECT IDENTIFIER ::= { nemoObjects 1 } 251 nemoMr OBJECT IDENTIFIER ::= { nemoObjects 2 } 252 nemoCn OBJECT IDENTIFIER ::= { nemoObjects 3 } 253 nemoHa OBJECT IDENTIFIER ::= { nemoObjects 4 } 255 -- The sub groups 257 nemoSystem OBJECT IDENTIFIER ::= { nemoCore 1 } 258 nemoBindings OBJECT IDENTIFIER ::= { nemoCore 2 } 259 nemoConfiguration OBJECT IDENTIFIER ::= { nemoCore 3 } 260 nemoStats OBJECT IDENTIFIER ::= { nemoCore 4 } 262 nemoMrSystem OBJECT IDENTIFIER ::= { nemoMr 1 } 263 nemoMrConf OBJECT IDENTIFIER ::= { nemoMr 2 } 264 nemoMrRegistration OBJECT IDENTIFIER ::= { nemoMr 3 } 266 nemoHaAdvertisement OBJECT IDENTIFIER ::= { nemoHa 1 } 268 -- The nemoConfiguration group has the following sub groups 270 nemoRegistration OBJECT IDENTIFIER ::= { nemoConfiguration 1 } 272 -- The nemoStats group has the following sub groups 274 nemoHomeAgentDiscovery OBJECT IDENTIFIER ::= { nemoStats 1 } 275 nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 2 } 276 nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 3 } 277 -- Textual Conventions 278 NemoStatus ::= TEXTUAL-CONVENTION 279 STATUS current 280 DESCRIPTION 281 "This object represents the state of the NEMO 282 entity. The entity could be at home, isolated, 283 roaming or in unknown state. 284 " 285 SYNTAX INTEGER { 286 isolated (1), 287 roaming (2), 288 home (3), 289 unknown (4) 290 } 292 -- 293 -- 294 -- nemoSystem group 295 -- 296 -- 298 nemoRoamingStatus OBJECT-TYPE 299 SYNTAX NemoStatus 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "Indicates the current status of the mobile router. 304 The status indicates if the mobile router is at 305 home, roaming, isolated or in an unknown state. 306 " 307 REFERENCE 308 "RFC3963 : Section 3" 309 ::= { nemoSystem 1 } 311 nemoRegisteredUpTime OBJECT-TYPE 312 SYNTAX Gauge32 313 UNITS "seconds" 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The time (in seconds) for which the mobile router 318 has been up and registered with its home agent. 319 " 320 REFERENCE 321 "RFC3963 : Section 6.4" 323 ::= { nemoSystem 2 } 325 nemoLastAcceptedRegTime OBJECT-TYPE 326 SYNTAX DateAndTime 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "The timestamp when the last registration was 331 accepted by the home agent. 332 " 333 REFERENCE 334 "RFC3963 : Section 6.6" 335 ::= { nemoSystem 3 } 337 nemoLastRejectedRegTime OBJECT-TYPE 338 SYNTAX DateAndTime 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The timestamp when the last registration was 343 rejected by the home agent. 344 " 345 REFERENCE 346 "RFC3963 : Section 6.6" 347 ::= { nemoSystem 4 } 349 nemoTimeSinceLastRoamed OBJECT-TYPE 350 SYNTAX Gauge32 351 UNITS "seconds" 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The time elapsed (in seconds) since the last time 356 the mobile router roamed. 357 " 358 REFERENCE 359 "RFC3963 : Section 6.6" 360 ::= { nemoSystem 5 } 362 nemoRegHomeAgentAddressType OBJECT-TYPE 363 SYNTAX InetAddressType 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The address type of the nemoRegHomeAgentAddress 368 that follows. 369 " 370 REFERENCE 371 "RFC3963 : Section 3" 372 ::= { nemoSystem 6 } 374 nemoRegHomeAgentAddress OBJECT-TYPE 375 SYNTAX InetAddress 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "The home agent address of the mobile router which 380 was used in the last accepted registration. 381 " 382 REFERENCE 383 "RFC3963 : Section 3" 384 ::= { nemoSystem 7 } 386 nemoRegHomeAddressType OBJECT-TYPE 387 SYNTAX InetAddressType 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The address type of the nemoRegHomeAddress that 392 follows. 393 " 394 REFERENCE 395 "RFC3963 : Section 3" 396 ::= { nemoSystem 8 } 398 nemoRegHomeAddress OBJECT-TYPE 399 SYNTAX InetAddress 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The home address of the mobile router which is 404 used in the last accepted registration. 405 " 406 REFERENCE 407 "RFC3963 : Section 3" 408 ::= { nemoSystem 9 } 410 nemoRegHomeAddressPrefixLength OBJECT-TYPE 411 SYNTAX InetAddressPrefixLength 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The prefix length of the home address that the 416 mobile router is using for roaming. 417 " 418 REFERENCE 419 "RFC3963 : Section 3" 420 ::= { nemoSystem 10 } 422 nemoRegCareofAddressType OBJECT-TYPE 423 SYNTAX InetAddressType 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The address type of the nemoRegCareofAddress that 428 follows. 429 " 430 REFERENCE 431 "RFC3963 : Section 3" 432 ::= { nemoSystem 11 } 434 nemoRegCareofAddress OBJECT-TYPE 435 SYNTAX InetAddress 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The care-of address of the mobile router which is 440 used in the last accepted registration. 441 " 442 REFERENCE 443 "RFC3963 : Section 3" 444 ::= { nemoSystem 12 } 446 nemoRegCareofAddressPrefixLength OBJECT-TYPE 447 SYNTAX InetAddressPrefixLength 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The prefix length of the care-of Address that the 452 mobile router currently is using for roaming. 453 " 454 REFERENCE 455 "RFC3963 : Section 3" 457 ::= { nemoSystem 13 } 459 nemoActiveRoamingIfIndex OBJECT-TYPE 460 SYNTAX InterfaceIndex 461 MAX-ACCESS read-only 462 STATUS current 463 DESCRIPTION 464 "The interface index of the current active 465 roaming interface. 466 " 467 REFERENCE 468 "RFC3963 : Section 5.5" 469 ::= { nemoSystem 14 } 471 nemoEstablishedHomeTunnelIfIndex OBJECT-TYPE 472 SYNTAX InterfaceIndex 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The interface index of the tunnel established 477 between the mobile router and the home agent 478 for NEMO traffic. 479 " 480 REFERENCE 481 "RFC3963 : Section 5.5" 482 ::= { nemoSystem 15 } 484 -- 485 -- 486 -- nemoConfiguration group 487 -- 488 -- 490 -- 491 -- nemoRegistration sub group 492 -- 494 nemoHomeRegLifeTime OBJECT-TYPE 495 SYNTAX Gauge32 (4..262143) 496 MAX-ACCESS read-write 497 STATUS current 498 DESCRIPTION 499 "The lifetime requested by the mobile router (in 500 seconds) in the Binding registration. It is 501 between 4 and 262143 secs. 503 " 504 ::= { nemoRegistration 1 } 506 nemoHomeRegRetryCount OBJECT-TYPE 507 SYNTAX Gauge32 508 MAX-ACCESS read-write 509 STATUS current 510 DESCRIPTION 511 "The maximum number of registration attempts 512 allowed for the mobile router. 513 " 514 ::= { nemoRegistration 2 } 516 nemoHomeRegRetryDelay OBJECT-TYPE 517 SYNTAX Gauge32 518 MAX-ACCESS read-write 519 STATUS current 520 DESCRIPTION 521 "The delay time between successive registration 522 attempts by the mobile router(in seconds). 523 " 524 ::= { nemoRegistration 3 } 526 nemoHomeRegExtendBeforeExpiry OBJECT-TYPE 527 SYNTAX Gauge32 528 MAX-ACCESS read-write 529 STATUS current 530 DESCRIPTION 531 "The time before the registration extension is 532 attempted (in seconds) by the mobile router. 533 " 534 ::= { nemoRegistration 4 } 536 nemoDynamicHADiscovery OBJECT-TYPE 537 SYNTAX TruthValue 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 "This object indicates whether or not the mobile 542 router should attempt to make dynamic home agent 543 address discovery(DHAAD). 544 " 545 ::= { nemoRegistration 5 } 547 nemoHomeAddressIdentifierType OBJECT-TYPE 548 SYNTAX BITS { 549 eui64 (0), 550 random (1) 551 } 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "The type of the nemoHomeAddressIdentifier 556 that follows. 557 " 558 ::= { nemoRegistration 6 } 560 nemoHomeAddressIdentifierInetType OBJECT-TYPE 561 SYNTAX InetAddressType 562 MAX-ACCESS read-write 563 STATUS current 564 DESCRIPTION 565 "The InetAddressType of the 566 nemoHomeAddressIdentifier that follows. 567 " 568 ::= { nemoRegistration 7 } 570 nemoHomeAddressIdentifier OBJECT-TYPE 571 SYNTAX InetAddress 572 MAX-ACCESS read-write 573 STATUS current 574 DESCRIPTION 575 "The unicast routable address assigned to the 576 mobile router. This is used as the permanent 577 address of the mobile router in the sense that it 578 remains unchanged regardless of the mobile 579 router's current point of attachment. 580 The type of the address represented by this object 581 is specified by the corresponding 582 nemoHomeAddressIdentifierInetType object. 583 " 584 ::= { nemoRegistration 8 } 586 nemoHomeIfIndex OBJECT-TYPE 587 SYNTAX InterfaceIndex 588 MAX-ACCESS read-write 589 STATUS current 590 DESCRIPTION 591 "The interface index of the mobile router where the 592 home address is configured. 594 " 595 ::= { nemoRegistration 9 } 597 nemoPrefixRegMode OBJECT-TYPE 598 SYNTAX BITS { 599 other (0), 600 implicitMode (1), 601 explicitMode (2) 602 } 603 MAX-ACCESS read-write 604 STATUS current 605 DESCRIPTION 606 "This object indicates if the mobile router will 607 explicitly register all the prefixes. 608 " 609 REFERENCE 610 "RFC 3963 : Section 5.2" 612 ::= { nemoRegistration 10 } 614 nemoRegisterConnectedPrefixes OBJECT-TYPE 615 SYNTAX TruthValue 616 MAX-ACCESS read-write 617 STATUS current 618 DESCRIPTION 619 "This object indicates if the mobile router will 620 register all the connected prefixes. 621 " 622 ::= { nemoRegistration 11 } 624 nemoHomeNetworkPrefixTable OBJECT-TYPE 625 SYNTAX SEQUENCE OF NemoHomeNetworkPrefixEntry 626 MAX-ACCESS not-accessible 627 STATUS current 628 DESCRIPTION 629 "A table representing the potential home networks 630 that the mobile router can use 631 " 632 ::= { nemoRegistration 12 } 634 nemoHomeNetworkPrefixEntry OBJECT-TYPE 635 SYNTAX NemoHomeNetworkPrefixEntry 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "An entry in the binding cache table. It represents 640 a single home network entry 642 Implementers need to be aware that if the total 643 number of octets in nemoHomeNetworkPrefix 644 exceeds 113 then OIDs of column 645 instances in this row will have more than 128 646 sub-identifiers and cannot be accessed using 647 SNMPv1, SNMPv2c, or SNMPv3. 648 " 649 INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix, 650 nemoHomeNetworkPrefixLength } 651 ::= { nemoHomeNetworkPrefixTable 1 } 653 NemoHomeNetworkPrefixEntry ::= 654 SEQUENCE { 655 nemoHomeNetworkPrefixType InetAddressType, 656 nemoHomeNetworkPrefix InetAddress, 657 nemoHomeNetworkPrefixLength InetAddressPrefixLength, 658 nemoHomeNetworkPrefixLifeTime Gauge32 659 } 661 nemoHomeNetworkPrefixType OBJECT-TYPE 662 SYNTAX InetAddressType 663 MAX-ACCESS not-accessible 664 STATUS current 665 DESCRIPTION 666 "The InetAddressType of the nemoHomeNetworkPrefix 667 that follows. 668 " 669 ::= { nemoHomeNetworkPrefixEntry 1 } 671 nemoHomeNetworkPrefix OBJECT-TYPE 672 SYNTAX InetAddress 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION 676 "The prefix of the home network which is configured 677 for the mobile router. 678 " 679 ::= { nemoHomeNetworkPrefixEntry 2 } 681 nemoHomeNetworkPrefixLength OBJECT-TYPE 682 SYNTAX InetAddressPrefixLength 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "The length of the home network prefix which 687 is configured for the mobile router. 688 " 689 ::= { nemoHomeNetworkPrefixEntry 3 } 691 nemoHomeNetworkPrefixLifeTime OBJECT-TYPE 692 SYNTAX Gauge32 (4..262143) 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 "The lifetime requested by the mobile router (in 697 seconds) in the Binding registration. It is 698 between 4 and 262143 secs. 699 " 700 ::= { nemoHomeNetworkPrefixEntry 4 } 702 -- 703 -- nemoPrefixTable 704 -- 706 nemoPrefixTable OBJECT-TYPE 707 SYNTAX SEQUENCE OF NemoPrefixEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "A table representing the NEMO prefixes. 712 " 713 REFERENCE 714 "RFC 3963 : Section 6.1.2" 716 ::= { nemoConfiguration 2 } 718 nemoPrefixEntry OBJECT-TYPE 719 SYNTAX NemoPrefixEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "An entry in the binding cache table. It represents 724 a single Binding Update. 726 Implementers need to be aware that if the total 727 number of octets in nemoPrefix 728 exceeds 114 then OIDs of column 729 instances in this row will have more than 128 730 sub-identifiers and cannot be accessed using 731 SNMPv1, SNMPv2c, or SNMPv3. 732 " 733 INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress, 734 nemoPrefixType, nemoPrefix, nemoPrefixLength } 735 ::= { nemoPrefixTable 1 } 737 NemoPrefixEntry ::= 738 SEQUENCE { 739 nemoPrefixType InetAddressType, 740 nemoPrefix InetAddress, 741 nemoPrefixLength InetAddressPrefixLength, 742 nemoPrefixLifeTime Gauge32 743 } 745 nemoPrefixType OBJECT-TYPE 746 SYNTAX InetAddressType 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "The InetAddressType of the nemoPrefix 751 that follows. 752 " 753 ::= { nemoPrefixEntry 1 } 755 nemoPrefix OBJECT-TYPE 756 SYNTAX InetAddress 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "The mobile network prefix that is delegated to the 761 mobile router and advertised in the mobile 762 network. The type of the address represented by 763 this object is specified by the corresponding 764 nemoPrefixType object. 765 " 766 REFERENCE 767 "RFC 3963 : Section 6.1.2" 769 ::= { nemoPrefixEntry 2 } 771 nemoPrefixLength OBJECT-TYPE 772 SYNTAX InetAddressPrefixLength 773 MAX-ACCESS not-accessible 774 STATUS current 775 DESCRIPTION 776 "The prefix length of the mobile network prefix. 777 " 778 ::= { nemoPrefixEntry 3 } 780 nemoPrefixLifeTime OBJECT-TYPE 781 SYNTAX Gauge32 782 UNITS "seconds" 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "The lifetime (in seconds) granted to the mobile 787 router for this registration. 788 " 789 ::= { nemoPrefixEntry 4 } 791 -- 792 -- nemoRoamingIfTable 793 -- 795 nemoRoamingIfTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF NemoRoamingIfEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "A table representing the roaming interfaces. 801 Each entry represents a configured roaming 802 interface with the roaming characteristics. 803 " 804 ::= { nemoConfiguration 3 } 806 nemoRoamingIfEntry OBJECT-TYPE 807 SYNTAX NemoRoamingIfEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "An entry in the roaming interface table. It 812 represents a single roaming interface entry. 813 " 814 INDEX { nemoRoamingIfIndex, nemoRoamingIfPriority } 815 ::= { nemoRoamingIfTable 1 } 817 NemoRoamingIfEntry ::= 818 SEQUENCE { 819 nemoRoamingIfIndex InterfaceIndex, 820 nemoRoamingIfPriority Unsigned32, 821 nemoRoamingIfDescription SnmpAdminString, 822 nemoRoamingIfRoamHoldDownTime Gauge32 823 } 825 nemoRoamingIfIndex OBJECT-TYPE 826 SYNTAX InterfaceIndex 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "The index of the interface that will be used for 831 roaming to foreign networks in the mobile router. 832 " 833 ::= { nemoRoamingIfEntry 1 } 835 nemoRoamingIfPriority OBJECT-TYPE 836 SYNTAX Unsigned32 837 MAX-ACCESS not-accessible 838 STATUS current 839 DESCRIPTION 840 "The priority configured to the interface. 841 This value will be configured between 0 and 255. 842 " 843 ::= { nemoRoamingIfEntry 2 } 845 nemoRoamingIfDescription OBJECT-TYPE 846 SYNTAX SnmpAdminString 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The description of the interface that will be used 851 for roaming to foreign networks in the mobile 852 router. 853 " 854 ::= { nemoRoamingIfEntry 3 } 856 nemoRoamingIfRoamHoldDownTime OBJECT-TYPE 857 SYNTAX Gauge32 858 UNITS "seconds" 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "This object indicates the time for which hold on 863 to the interface. This value is configured to 864 avoid interface flapping. 865 " 866 ::= { nemoRoamingIfEntry 4 } 868 nemoHaListTable OBJECT-TYPE 869 SYNTAX SEQUENCE OF NemoHaListEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "This table models the Home Agents List that contains 874 the list of all routers that are acting as 875 home agents with NEMO functionality on 876 each of the interfaces on which the home agent service 877 is offered by this router. 878 " 879 REFERENCE 880 "RFC 3963 : Section 7.2, 7.3" 881 ::= { nemoHaAdvertisement 1 } 883 nemoHaListEntry OBJECT-TYPE 884 SYNTAX NemoHaListEntry 885 MAX-ACCESS not-accessible 886 STATUS current 887 DESCRIPTION 888 "An entry containing additional information about a 889 home agent that is offering NEMO service. 890 " 891 AUGMENTS { mip6HaListEntry } 892 ::= { nemoHaListTable 1 } 894 NemoHaListEntry ::= SEQUENCE { 895 nemoHaSupportsMr TruthValue 896 } 898 nemoHaSupportsMr OBJECT-TYPE 899 SYNTAX TruthValue 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "true(1) if the home agent supports mobile router and 904 sent the home agent information with Mobile Router 905 Flag. 906 false(0) implies that the home agent only supports 907 mobile node. 908 " 909 REFERENCE 910 "RFC 3963 : Section 7.3" 911 ::= { nemoHaListEntry 1 } 913 nemoMrBLTable OBJECT-TYPE 914 SYNTAX SEQUENCE OF NemoMrBLEntry 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION 918 "This table corresponds to the Binding Update List(BL) 919 that includes NEMO related information and 920 is maintained by the mobile router. 921 Entries from the table are deleted as 922 the lifetime of the binding expires. 923 " 924 REFERENCE 925 "RFC 3775 : Section 4.5, 11.1, RFC 3963 : Section 5.2" 926 ::= { nemoMrRegistration 1 } 928 nemoMrBLEntry OBJECT-TYPE 929 SYNTAX NemoMrBLEntry 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "An entry containing additional information contained 934 in a Binding Update sent by a NEMO enabled mobile 935 router to its home agent. 936 " 937 AUGMENTS {mip6MnBLEntry} 938 ::= { nemoMrBLTable 1 } 940 NemoMrBLEntry ::= SEQUENCE { 941 nemoMrBLMode BITS, 942 nemoMrBLMrFlag TruthValue 943 } 945 nemoMrBLMode OBJECT-TYPE 946 SYNTAX BITS { 947 implicitMode (0), 948 explicitMode (1) 949 } 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "This object indicates the mode of mobile router 954 to tell the home agent to determine which prefixes 955 belong to the mobile router. 956 " 957 REFERENCE 958 "RFC 3963 : Section 5.2" 959 ::= { nemoMrBLEntry 1 } 961 nemoMrBLMrFlag OBJECT-TYPE 962 SYNTAX TruthValue 963 MAX-ACCESS read-only 964 STATUS current 965 DESCRIPTION 966 "true(1) if the mobile router sent the binding update 967 with Mobile Router Flag that indicates to the home 968 agent that the binging update is from a mobile router. 969 false(0) implies that the mobile router is behaving 970 as a mobile node. 971 " 972 REFERENCE 973 "RFC 3963 : Section 4.1, 5.1" 974 ::= { nemoMrBLEntry 2 } 976 nemoBindingCacheTable OBJECT-TYPE 977 SYNTAX SEQUENCE OF NemoBindingCacheEntry 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION 981 "This table models the Binding Cache 982 that includes NEMO related information and 983 is maintained by the mobile router. 984 Entries in this table are not required to survive 985 a reboot of the Home Agent. 986 " 987 REFERENCE 988 "RFC 3775 : Section 4.5, 9.1, 10.1, 989 RFC 3963 : Section 6.1" 990 ::= { nemoBindings 1 } 992 nemoBindingCacheEntry OBJECT-TYPE 993 SYNTAX NemoBindingCacheEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "An entry containing additional information related 998 to nemo-enabled entries in the binding cache table 999 of the Home Agent. 1000 " 1001 AUGMENTS {mip6BindingCacheEntry} 1002 ::= { nemoBindingCacheTable 1 } 1004 NemoBindingCacheEntry ::= SEQUENCE { 1005 nemoBindingMrFlag TruthValue, 1006 nemoBindingMrMode BITS 1007 } 1009 nemoBindingMrFlag OBJECT-TYPE 1010 SYNTAX TruthValue 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "true(1) if the home agent accepted the binding update 1015 with Mobile Router Flag from a mobile router. 1016 false(0) implies that the binding cache is from 1017 a mobile node. 1018 " 1019 REFERENCE 1020 "RFC 3963 : Section 6.1.1, 6.2" 1021 ::= { nemoBindingCacheEntry 1 } 1023 nemoBindingMrMode OBJECT-TYPE 1024 SYNTAX BITS { 1025 implicitMode(0), 1026 explicitMode(1) 1027 } 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "This object indicates the mode of mobile router 1032 to tell the home agent to determine which prefixes 1033 belong to the mobile router. 1034 " 1035 REFERENCE 1036 "RFC 3963 : Section 5.2, 6.1.1, 6.2" 1037 ::= { nemoBindingCacheEntry 2 } 1039 nemoHaPrefixTable OBJECT-TYPE 1040 SYNTAX SEQUENCE OF NemoHaPrefixEntry 1041 MAX-ACCESS not-accessible 1042 STATUS current 1043 DESCRIPTION 1044 "This table contains the mobile network prefixes 1045 that the home agent maintains for the Mobile Router. 1046 " 1047 REFERENCE 1048 "RFC 3963 : Section 6.1" 1049 ::= { nemoMrRegistration 2 } 1051 nemoHaPrefixEntry OBJECT-TYPE 1052 SYNTAX NemoHaPrefixEntry 1053 MAX-ACCESS not-accessible 1054 STATUS current 1055 DESCRIPTION 1056 "This entry represents the mobile network prefixes 1057 that are maintained by the home agent. 1058 There are two method that the home agent studies 1059 the mobile network prefixes. 1060 In implicit mode, the mobile network prefixes is 1061 configured by any method(ex. pre-defined) for 1062 corresponding Mobile Router. 1063 In explicit mode, the binding update from the mobile 1064 router contains the mobile network prefix list. 1065 The home agent maintains Prefix Table that contains 1066 the home address of the mobile router for verifying 1067 the prefix list from the mobile router. 1069 This entry contains only the mobile network prefixes 1070 that are registered by the corresponding binding 1071 update. It does not include the prefixes studied 1072 through the dynamic routing process between the home 1073 agent and the mobile router. 1075 The instances of the columnar objects in this entry 1076 pertain to an interface for a particular value of 1077 mip6BindingHomeAddressType, mip6BindingHomeAddress, 1078 and nemoHaPrefixSeqNo. 1079 The nemoHaPrefixSeqNo object is used to 1080 distinguish between multiple instances of 1081 the mobile network prefix on the same binding update 1082 for the same set of 1083 mip6BindingHomeAddressType, mip6BindingHomeAddress. 1084 There is no upper-bound on the maximum number of 1085 mobile network prefixes on a binding update but, for 1086 practical purposes, the upper bound of the value 1087 nemoHaPrefixSeqNo is set to 1024. 1089 Implementers need to be aware that if the total 1090 number of octets in mip6BindingHomeAddress 1091 exceeds 111, then OIDs of column 1092 instances in this row will have more than 128 1093 sub-identifiers and cannot be accessed using 1094 SNMPv1, SNMPv2c, or SNMPv3. 1095 " 1096 INDEX { mip6BindingHomeAddressType, 1097 mip6BindingHomeAddress, 1098 nemoHaPrefixSeqNo 1099 } 1100 ::= { nemoHaPrefixTable 1 } 1102 NemoHaPrefixEntry ::= SEQUENCE { 1103 nemoHaPrefixSeqNo Integer32, 1104 nemoHaPrefixType InetAddressType, 1105 nemoHaPrefix InetAddress, 1106 nemoHaPrefixLength Unsigned32, 1107 nemoHaPrefixSource BITS 1108 } 1110 nemoHaPrefixSeqNo OBJECT-TYPE 1111 SYNTAX Integer32 (1..1024) 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "The index that along with mip6BindingHomeAddressType, 1116 and mip6BindingHomeAddress uniquely identifies this 1117 row. 1118 One binding update has some mobile network prefixes. 1119 So when we describe the prefix list corresponding to 1120 the binding cache, it will be needed as a sub index. 1121 " 1122 REFERENCE 1123 "RFC 3963 : Section 6.1.1, 6.1.2" 1124 ::= { nemoHaPrefixEntry 1 } 1126 nemoHaPrefixType OBJECT-TYPE 1127 SYNTAX InetAddressType 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "The address type for the mobile network prefix 1132 that follows. 1133 " 1134 REFERENCE 1135 "RFC 3963 : Section 6.1, 6.2" 1136 ::= { nemoHaPrefixEntry 2 } 1138 nemoHaPrefix OBJECT-TYPE 1139 SYNTAX InetAddress 1140 MAX-ACCESS read-only 1141 STATUS current 1142 DESCRIPTION 1143 "A mobile network prefix related to the 1144 corresponding Binding Update. 1146 The type of the address represented by this object 1147 is specified by the corresponding 1148 nemoHaPrefixType object. 1149 " 1150 REFERENCE 1151 "RFC 3963 : Section 6.1, 6.2" 1152 ::= { nemoHaPrefixEntry 3 } 1154 nemoHaPrefixLength OBJECT-TYPE 1155 SYNTAX Unsigned32 (0..128) 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "The length of the prefix specified by the corresponding 1160 nemoHaPrefix Object. 1161 " 1162 REFERENCE 1163 "RFC 3963 : Section 6.1, 6.2" 1164 ::= { nemoHaPrefixEntry 4 } 1166 nemoHaPrefixSource OBJECT-TYPE 1167 SYNTAX BITS{ 1168 configured (0), 1169 bindingUpdate (1) 1170 } 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "The information source of the mobile network prefix 1175 configured with the binding update. 1176 Configured(1) represents that the information is 1177 introduced to the home agent without binding update. 1178 Binding Update(2) represents that the information is 1179 introduced to the home agent by the mobile network 1180 prefix option in the binding update and verified 1181 by the Prefix Table that the home agent maintains 1182 for each home addresses of the mobile router. 1183 " 1185 REFERENCE 1186 "RFC 3963 : Section 6.1, 6.2" 1187 ::= { nemoHaPrefixEntry 5 } 1189 nemoMrDiscoveryRequests OBJECT-TYPE 1190 SYNTAX Counter32 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "Total number of Modified Dynamic Home Agent Address 1195 Discovery Requests with Mobile Router Flag 1196 sent by the mobile router. 1197 Discontinuities in the value of this counter can 1198 occur at re-initialization of the management system, 1199 and at other times as indicated by the value of 1200 mip6CounterDiscontinuityTime. 1201 " 1202 REFERENCE 1203 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.1" 1204 ::= { nemoMrConf 1 } 1206 nemoMrDiscoveryReplies OBJECT-TYPE 1207 SYNTAX Counter32 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "Total number of Modified Dynamic Home Agent Address 1212 Discovery Replies with Mobile Router Flag is set to 1 1213 received by the mobile router. 1214 Discontinuities in the value of this counter can 1215 occur at re-initialization of the management system, 1216 and at other times as indicated by the value of 1217 mip6CounterDiscontinuityTime. 1218 " 1219 REFERENCE 1220 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2" 1221 ::= { nemoMrConf 2 } 1223 nemoMrDiscoveryRepliesRouterFlagZero OBJECT-TYPE 1224 SYNTAX Counter32 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "Total number of Modified Dynamic Home Agent Address 1229 Discovery Replies with Mobile Router Flag is set to 0 1230 although the flag in the corresponding request 1231 is set to 1. 1232 It implies that there is no home agent that supports 1233 Mobile Router in the home network. 1234 Discontinuities in the value of this counter can 1235 occur at re-initialization of the management system, 1236 and at other times as indicated by the value of 1237 mip6CounterDiscontinuityTime. 1238 " 1239 REFERENCE 1240 "RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.3" 1241 ::= { nemoMrConf 3 } 1243 --- 1244 --- 1245 --- nemoStats group 1246 --- 1247 --- 1249 -- 1250 -- Dynamic Home Agent discovery protocol related counters 1251 -- 1253 nemoDHAADRequests OBJECT-TYPE 1254 SYNTAX Counter32 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The total number of dynamic home agent address 1259 discovery requests sent by the mobile router 1260 with the Mobile Router Support Flag (R) set. 1261 " 1262 REFERENCE 1263 "RFC3963 : Section 7.1." 1264 ::= { nemoHomeAgentDiscovery 1 } 1266 nemoDHAADRepliesWNemoSupport OBJECT-TYPE 1267 SYNTAX Counter32 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "The total number of dynamic home agent address 1272 discovery replies sent by the home agent with 1273 Mobile Router Support Flag (R) set. 1274 " 1275 REFERENCE 1276 "RFC3963 : Section 7.2." 1277 ::= { nemoHomeAgentDiscovery 2 } 1279 nemoDHAADRepliesWONemoSupport OBJECT-TYPE 1280 SYNTAX Counter32 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "The total number of dynamic home agent address 1285 discovery replies sent by the home agent without 1286 NEMO support i.e the Mobile Router Support Flag 1287 set to 0. 1288 " 1289 REFERENCE 1290 "RFC3963 : Section 7.2." 1291 ::= { nemoHomeAgentDiscovery 3 } 1293 nemoDHAADDiscoveryTimeouts OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "The total number of dynamic home agent address 1299 discovery requests sent by the mobile router 1300 with the Mobile Router Support Flag (R) set, 1301 that did not receive any response. 1302 " 1303 ::= { nemoHomeAgentDiscovery 4 } 1305 -- 1306 -- nemoStats:nemoBindingRegcounters 1307 -- 1309 nemoBindingAcksWONemoSupport OBJECT-TYPE 1310 SYNTAX Counter32 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "The total number of Binding Acks without the 1315 NEMO support received by the mobile router. 1317 Discontinuities in the value of this counter can 1318 occur at re-initialization of the mobile router. 1319 " 1320 REFERENCE 1321 "RFC3963 : Section 5.3." 1322 ::= { nemoBindingRegCounters 1 } 1324 nemoBindingAckNotHomeRegn OBJECT-TYPE 1325 SYNTAX Counter32 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The total number of Binding Update requests 1330 rejected by the home agent with the status code 1331 in the Binding Acknowledgment indicating 1332 'Not Home Registration' 1334 Discontinuities in the value of this counter can 1335 occur at re-initialization of the mobile router. 1336 " 1337 REFERENCE 1338 "RFC3963 : Section 6.2." 1339 ::= { nemoBindingRegCounters 2 } 1341 nemoBindingRegTypeChanged OBJECT-TYPE 1342 SYNTAX Counter32 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The total number of Binding Update requests 1347 rejected by the home agent with status code 1348 in the Binding Acknowledgement indicating 1349 'Registration type change disallowed' (Code 139). 1351 Discontinuities in the value of this counter can 1352 occur at re-initialization of the mobile router. 1353 " 1354 REFERENCE 1355 "RFC3963 : Section 6.2" 1356 ::= { nemoBindingRegCounters 3 } 1358 nemoOpNotSupported OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The total number of Binding Update requests 1364 rejected by the home agent with status code in the 1365 Binding Acknowledgement indicating 1366 'Mobile Router Operation not permitted' 1367 (Code 140). 1369 Discontinuities in the value of this counter can 1370 occur at re-initialization of the mobile router. 1371 " 1372 REFERENCE 1373 "RFC3963 : Section 6.6" 1374 ::= { nemoBindingRegCounters 4 } 1376 nemoInvalidPrefix OBJECT-TYPE 1377 SYNTAX Counter32 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "The total number of Binding Update requests 1382 rejected by the home agent with status code in the 1383 Binding Acknowledgement indicating 'Invalid 1384 Prefix' (Code 141). 1386 Discontinuities in the value of this counter can 1387 occur at re-initialization of the mobile router. 1388 " 1389 REFERENCE 1390 "RFC3963 : Section 6.6." 1391 ::= { nemoBindingRegCounters 5 } 1393 nemoNotAuthorizedForPrefix OBJECT-TYPE 1394 SYNTAX Counter32 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "The total number of Binding Update requests 1399 rejected by the home agent with status code in the 1400 Binding Acknowledgement indicating 'Not Authorized 1401 for Prefix' (Code 142). 1403 Discontinuities in the value of this counter can 1404 occur at re-initialization of the mobile router. 1405 " 1406 REFERENCE 1407 "RFC3963 : Section 6.6." 1408 ::= { nemoBindingRegCounters 6 } 1410 nemoForwardingSetupFailed OBJECT-TYPE 1411 SYNTAX Counter32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The total number of Binding Update requests 1416 rejected by the home agent with status code in the 1417 Binding Acknowledgement indicating 'Forwarding 1418 Setup failed' (Code 143). 1420 Discontinuities in the value of this counter can 1421 occur at re-initialization of the mobile router. 1422 " 1423 REFERENCE 1424 "RFC3963 : Section 6.6." 1425 ::= { nemoBindingRegCounters 7 } 1427 -- 1428 -- nemoStats:nemoRoamingCounters 1429 -- 1431 nemoMovedHome OBJECT-TYPE 1432 SYNTAX Counter32 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "Number of times the mobile router has detected 1437 movement from a foreign network to its home 1438 network. 1439 Discontinuities in the value of this counter can 1440 occur at re-initialization of the mobile router. 1441 " 1442 ::= { nemoRoamingCounters 1 } 1444 nemoMovedOutofHome OBJECT-TYPE 1445 SYNTAX Counter32 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "Number of times the mobile router has detected 1450 movement to a foreign network from the home 1451 network, has acquired a care-of address and 1452 has initiated the care-of address registration 1453 process. 1454 Discontinuities in the value of this counter can 1455 occur at re-initialization of the mobile router. 1456 " 1457 REFERENCE 1458 "RFC3963 : Section 3." 1459 ::= { nemoRoamingCounters 2 } 1461 nemoMovedFNtoFN OBJECT-TYPE 1462 SYNTAX Counter32 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "Number of times the mobile router has detected 1467 movement from to a foreign network from the home 1468 network, has reconstructed its care-of address and 1469 has initiated the care-of address registration 1470 process. 1471 Discontinuities in the value of this counter can 1472 occur at re-initialization of the mobile router. 1473 " 1474 ::= { nemoRoamingCounters 3 } 1476 nemoBetterIfDetected OBJECT-TYPE 1477 SYNTAX Counter32 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "Number of times the NEMO entity has found roaming 1482 interface with better priority. 1483 Discontinuities in the value of this counter can 1484 occur at re-initialization of the mobile router. 1485 " 1486 ::= { nemoRoamingCounters 4 } 1488 -- 1489 -- 1490 -- nemoNotifications 1491 -- 1492 -- 1494 nemoHomeTunnelEstablished NOTIFICATION-TYPE 1495 OBJECTS { 1496 nemoActiveRoamingIfIndex, 1497 nemoEstablishedHomeTunnelIfIndex, 1498 nemoRegCareofAddressType, 1499 nemoRegCareofAddress 1500 } 1501 STATUS current 1502 DESCRIPTION 1503 "This notification is sent by the mobile router 1504 every time the tunnel is established between the 1505 home agent and the mobile router. 1506 " 1507 REFERENCE 1508 "RFC3963 : Section 5.5" 1509 ::= { nemoNotifications 1 } 1511 nemoHomeTunnelReleased NOTIFICATION-TYPE 1512 OBJECTS { 1513 nemoActiveRoamingIfIndex, 1514 nemoEstablishedHomeTunnelIfIndex, 1515 nemoRegCareofAddressType, 1516 nemoRegCareofAddress 1517 } 1518 STATUS current 1519 DESCRIPTION 1520 "This notification is sent by the mobile router 1521 every time the tunnel is deleted between the home 1522 agent and the mobile router. 1523 " 1524 REFERENCE 1525 "RFC3963 : Section 5.5" 1526 ::= { nemoNotifications 2} 1528 -- Conformance information 1529 nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } 1530 nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } 1532 -- Units of conformance 1533 nemoSystemGroup OBJECT-GROUP 1534 OBJECTS { 1535 nemoRoamingStatus, 1536 nemoRegisteredUpTime, 1537 nemoLastAcceptedRegTime, 1538 nemoLastRejectedRegTime, 1539 nemoTimeSinceLastRoamed, 1540 nemoRegHomeAgentAddressType, 1541 nemoRegHomeAgentAddress, 1542 nemoRegHomeAddressType, 1543 nemoRegHomeAddress, 1544 nemoRegHomeAddressPrefixLength, 1545 nemoRegCareofAddressType, 1546 nemoRegCareofAddress, 1547 nemoRegCareofAddressPrefixLength, 1548 nemoActiveRoamingIfIndex, 1549 nemoEstablishedHomeTunnelIfIndex 1550 } 1551 STATUS current 1552 DESCRIPTION 1553 " A collection of objects for basic NEMO 1554 monitoring." 1555 ::= { nemoGroups 1 } 1557 nemoConfigurationGroup OBJECT-GROUP 1558 OBJECTS { 1559 nemoHomeRegLifeTime, 1560 nemoHomeRegRetryCount, 1561 nemoHomeRegRetryDelay, 1562 nemoHomeRegExtendBeforeExpiry, 1563 nemoDynamicHADiscovery, 1564 nemoHomeAddressIdentifierType, 1565 nemoHomeAddressIdentifierInetType, 1566 nemoHomeAddressIdentifier, 1567 nemoHomeIfIndex, 1568 nemoPrefixRegMode, 1569 nemoRegisterConnectedPrefixes, 1570 -- nemoHomeNetworkPrefixType, 1571 -- nemoHomeNetworkPrefix, 1572 -- nemoHomeNetworkPrefixLength, 1573 nemoHomeNetworkPrefixLifeTime, 1574 nemoPrefixLifeTime, 1575 -- nemoRoamingIfIndex, 1576 -- nemoRoamingIfPriority, 1577 nemoRoamingIfDescription, 1578 nemoRoamingIfRoamHoldDownTime, 1579 nemoDHAADRequests, 1580 nemoDHAADRepliesWNemoSupport, 1581 nemoDHAADRepliesWONemoSupport, 1582 nemoDHAADDiscoveryTimeouts, 1583 nemoHaSupportsMr, 1584 nemoMrBLMode, 1585 nemoMrBLMrFlag, 1586 nemoBindingMrFlag, 1587 nemoBindingMrMode, 1588 nemoHaPrefixType, 1589 nemoHaPrefix, 1590 nemoHaPrefixLength, 1591 nemoHaPrefixSource, 1592 nemoMrDiscoveryRequests, 1593 nemoMrDiscoveryReplies, 1594 nemoMrDiscoveryRepliesRouterFlagZero 1595 } 1596 STATUS current 1597 DESCRIPTION 1598 " A collection of objects for basic NEMO 1599 configuration monitoring." 1600 ::= { nemoGroups 2 } 1602 nemoStatsGroup OBJECT-GROUP 1603 OBJECTS { 1604 nemoBindingAcksWONemoSupport, 1605 nemoBindingAckNotHomeRegn, 1606 nemoBindingRegTypeChanged, 1607 nemoOpNotSupported, 1608 nemoInvalidPrefix, 1609 nemoNotAuthorizedForPrefix, 1610 nemoForwardingSetupFailed, 1611 nemoMovedHome, 1612 nemoMovedOutofHome, 1613 nemoMovedFNtoFN, 1614 nemoBetterIfDetected 1615 } 1616 STATUS current 1617 DESCRIPTION 1618 " A collection of objects for basic NEMO 1619 monitoring. 1620 " 1621 ::= { nemoGroups 3 } 1623 nemoNotificationGroup NOTIFICATION-GROUP 1624 NOTIFICATIONS { 1625 nemoHomeTunnelEstablished, 1626 nemoHomeTunnelReleased 1627 } 1628 STATUS current 1629 DESCRIPTION 1630 "A collection of notifications from a home agent 1631 or correspondent node to the Manager about the 1632 tunnel status of the mobile router. 1633 " 1634 ::= { nemoGroups 4 } 1636 -- Compliance statements 1637 nemoCoreCompliance MODULE-COMPLIANCE 1638 STATUS current 1639 DESCRIPTION 1640 "The compliance statement for SNMP entities 1641 which implement the MOBILEIPV6-MIB. 1642 There are a number of INDEX objects that cannot be 1643 represented in the form of OBJECT clauses in 1644 SMIv2, but for which there are compliance 1645 requirements, expressed in OBJECT clause form in 1646 this 1647 description: 1648 -- OBJECT nemoBindingHomeAddressType 1649 -- SYNTAX InetAddressType { ipv6(2) } 1650 -- DESCRIPTION 1651 -- This MIB module requires support for global 1652 -- ipv6 addresses for the nemoBindingHomeAddress 1653 -- object. 1654 -- 1655 " 1656 MODULE -- this module 1657 MANDATORY-GROUPS { nemoSystemGroup, 1658 nemoConfigurationGroup, 1659 nemoStatsGroup, 1660 nemoNotificationGroup 1661 } 1663 ::= { nemoCompliances 1 } 1665 END 1667 5. IANA Considerations 1669 IANA should assign a base arc in the mib-2 (standards track) OID tree 1670 for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB. 1672 6. Security Considerations 1674 There are a number of management objects defined in this MIB module 1675 with a MAX-ACCESS clause of read-write. Such objects may be 1676 considered sensitive or vulnerable in some network environments. The 1677 support for SET operations in a non-secure environment without proper 1678 protection can have a negative effect on network operations. These 1679 are the tables and objects and their sensitivity/vulnerability: 1681 Some of the readable objects in this MIB module (i.e., objects with a 1682 MAX-ACCESS other than not-accessible) may be considered sensitive or 1683 vulnerable in some network environments. It is thus important to 1684 control even GET and/or NOTIFY access to these objects and possibly 1685 to even encrypt the values of these objects when sending them over 1686 the network via SNMP. These are the tables and objects and their 1687 sensitivity/vulnerability: 1689 SNMP versions prior to SNMPv3 did not include adequate security. 1690 Even if the network itself is secure (for example by using IPSec), 1691 even then, there is no control as to who on the secure network is 1692 allowed to access and GET/SET (read/change/create/delete) the objects 1693 in this MIB module. 1695 It is RECOMMENDED that implementers consider the security features as 1696 provided by the SNMPv3 framework (see [RFC3410], section 8), 1697 including full support for the SNMPv3 cryptographic mechanisms (for 1698 authentication and privacy). 1700 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1701 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1702 enable cryptographic security. It is then a customer/operator 1703 responsibility to ensure that the SNMP entity giving access to an 1704 instance of this MIB module is properly configured to give access to 1705 the objects only to those principals (users) that have legitimate 1706 rights to indeed GET or SET (change/create/delete) them. 1708 7. Acknowledgments 1710 The authors would like to thank T.J Kniveton and Thierry Ernst for 1711 their review comments on this document. 1713 8. References 1714 8.1. Normative References 1716 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 1717 Requirements Levels, BCP 14, RFC 2119, March 1997. 1719 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1720 Rose, M. and S. Waldbusser, Structure of Management Information 1721 Version 2 (SMIv2), STD 58, RFC 2578, April 1999. 1723 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1724 Rose, M. and S. Waldbusser, Textual Conventions for SMIv2, STD 58, 1725 RFC 2579, April 1999. 1727 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1728 Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58, 1729 RFC 2580, April 1999. 1731 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in 1732 IPv6q RFC 3775, June 2004. 1734 [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, 1735 Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005. 1737 [RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The 1738 Mobile IPv6 MIB, RFC 4295, April 2006. 1740 8.2. Informative References 1742 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1743 Introduction and Applicability Statements for Internet-Standard 1744 Management Framework, RFC 3410, December 2002. 1746 [NEMOTERM] T. Ernst and H.-Y. Lach., Network Mobility Support 1747 Terminology, work in progress (currently 1748 draft-ietf-nemo-terminology-06.txt). 1750 [NEMOGOAL] T. Ernst. Network Mobility Support Goals and 1751 Requirements, work in progress (currently 1752 draft-ietf-nemo-requirements-06.txt). 1754 Authors' Addresses 1756 Sri Gundavelli 1757 Cisco 1758 170 West Tasman Drive 1759 San Jose, CA 95134 1760 USA 1762 Phone: +1-408-527-6109 1763 Email: sgundave@cisco.com 1765 Glenn Mansfield Keeni 1766 Cyber Solutions 1767 6-6-3 Minami Yoshinari 1768 Aoba-ku, Sendai 989-3204, 1769 Japan 1771 Phone: +81-22-303-4012 1772 Email: glenn@cysols.com 1774 Kazuhide Koide 1775 Tohoku University 1776 Katahira Campus 1777 Sendai, 1778 Japan 1780 Phone: +81-22-217-5454 1781 Email: koide@shiratori.riec.tohoku.ac.jp 1783 Kenichi Nagami 1784 INTEC NetCore 1785 1-3-3, Shin-suna 1786 Koto-ku, Tokyo, 135-0075, 1787 Japan 1789 Phone: +81-3-5665-5069 1790 Email: nagami@inetcore.com 1792 Full Copyright Statement 1794 Copyright (C) The IETF Trust (2007). 1796 This document is subject to the rights, licenses and restrictions 1797 contained in BCP 78, and except as set forth therein, the authors 1798 retain all their rights. 1800 This document and the information contained herein are provided on an 1801 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1802 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1803 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1804 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1805 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1806 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1808 Intellectual Property 1810 The IETF takes no position regarding the validity or scope of any 1811 Intellectual Property Rights or other rights that might be claimed to 1812 pertain to the implementation or use of the technology described in 1813 this document or the extent to which any license under such rights 1814 might or might not be available; nor does it represent that it has 1815 made any independent effort to identify any such rights. Information 1816 on the procedures with respect to rights in RFC documents can be 1817 found in BCP 78 and BCP 79. 1819 Copies of IPR disclosures made to the IETF Secretariat and any 1820 assurances of licenses to be made available, or the result of an 1821 attempt made to obtain a general license or permission for the use of 1822 such proprietary rights by implementers or users of this 1823 specification can be obtained from the IETF on-line IPR repository at 1824 http://www.ietf.org/ipr. 1826 The IETF invites any interested party to bring to its attention any 1827 copyrights, patents or patent applications, or other proprietary 1828 rights that may cover technology that may be required to implement 1829 this standard. Please address the information to the IETF at 1830 ietf-ipr@ietf.org. 1832 Acknowledgment 1834 Funding for the RFC Editor function is provided by the IETF 1835 Administrative Support Activity (IASA).