idnits 2.17.1 draft-ietf-nemo-mib-01.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 21. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1490. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1501. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1508. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1514. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 1482), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 46. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 39 longer pages, the longest (page 2) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 16, 2005) is 6857 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) -- Looks like a reference, but probably isn't: '10' on line 107 == Missing Reference: 'NEMO' is mentioned on line 116, but not defined == Unused Reference: 'RFC4001' is defined on line 1414, but no explicit reference was found in the text == Unused Reference: 'RFC2011bis' is defined on line 1418, but no explicit reference was found in the text == Unused Reference: 'MIPv6MIB' is defined on line 1422, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) ** Obsolete normative reference: RFC 2011 (Obsoleted by RFC 4293) -- Possible downref: Non-RFC (?) normative reference: ref. 'MIPv6MIB' Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 9 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 Systems 4 Expires: January 15, 2006 Glenn M. Keeni 5 Cyber Solutions 6 Kazuhide Koide 7 Tohoku University 8 Kenichi Nagami 9 INTEC NetCore 11 July 16, 2005 13 NEMO Management Information Base 14 16 Status of this Memo 18 By submitting this Internet-Draft, each author represents that any 19 applicable patent or other IPR claims of which he or she is aware 20 have been or will be disclosed, and any of which he or she becomes 21 aware will be disclosed, in accordance with Section 6 of BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This document is a product of the nemo Working Group. Comments should 40 be addressed to the authors or the mailing list at nemo@ietf.org 42 This Internet-Draft will expire on January 15, 2006 44 Copyright Notice 46 Copyright (C) The Internet Society (2005). All Rights Reserved. 48 Abstract 50 This memo defines a portion of the Management Information Base (MIB), 51 the network mobility support (NEMO) MIB, for use with network 52 management protocols in the Internet community. In particular, the 53 NEMO MIB will be used to monitor and control a mobile ipv6 node with 54 NEMO functionality. 56 Table of Contents 58 1. The Internet-Standard Management Framework .................... 3 59 2. Overview ...................................................... 3 60 3. MIB Design .................................................... 4 61 4. The NEMO MIB .................................................. 5 62 5. Security Considerations .......................................32 63 6. IANA Considerations ...........................................32 64 7. Acknowledgments ...............................................33 65 8. References ....................................................34 66 9. Authors' Addresses ............................................36 67 10. Full Copyright Statement ......................................37 69 1. The Internet-Standard Management Framework 71 For a detailed overview of the documents that describe the current 72 Internet-Standard Management Framework, please refer to section 7 of 73 RFC 3410 [RFC3410]. 75 Managed objects are accessed via a virtual information store, termed 76 the Management Information Base or MIB. MIB objects are generally 77 accessed through the Simple Network Management Protocol (SNMP). 79 Objects in the MIB are defined using the mechanisms defined in the 80 Structure of Management Information (SMI). This memo specifies a MIB 81 module that is compliant to the SMIv2, which is described in STD 58, 82 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 83 [RFC2580]. 85 2. Overview 87 2.1 The Mobile IPv6 Protocol and NEMO entities. 89 Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes 90 to remain reachable while moving around in the IPv6 Internet. Network 91 Mobility Basic Support (NEMO) [RFC3963] is an extension to the Mobile 92 IPv6 protocol which facilitates the movement of an entire network. 93 The goals of Network Mobility support and related terminology are 94 discussed in [NEMOGOAL] and [NEMOTERM], respectively. 96 Typically mobile routers implement NEMO functionality for achieving 97 network mobility. However, a mobile router may also function as a 98 mobile node. In the context of this document, an entity that 99 implements the NEMO protocol is a NEMO entity. 101 This document defines a set of managed objects (MOs) that can be used 102 to monitor and control NEMO entities. 104 2.2 Implementation Guidance 106 This document focuses on the management of a NEMO entity. The 107 MIPv6MIB [10] defines the managed objects for a mobile node. 108 Implementations supporting both the mobile node and NEMO 109 functionality SHOULD implement the managed objects defined for the 110 NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB. 112 2.3 Terminology. 114 The terminology used in this document is consistent with the 115 definitions used in the Mobile IPv6 protocol specification[RFC3775] 116 and the NEMO Basic Support specification [NEMO]. 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 120 "OPTIONAL" in this document are to be interpreted as described in BCP 121 14, RFC 2119 [RFC2119]. 123 3. MIB Design 125 The NEMO MIB comprises of the following primary groups: 127 - nemoSystem 128 - nemoConfiguration 129 - nemoStats 130 - nemoNotifications 131 - nemoConformance 133 The nemoSystem group provides the general information of the NEMO 134 entity. The objects in this group cover the current home registration 135 state. 137 The nemoConfiguration group contains information relevant to the 138 implementation and operation of the NEMO protocol. 140 The nemoStats group defines the statistics related to the NEMO 141 protocol operations. 143 The nemoNotifications group defines the notifications generated by 144 the NEMO entity in response to the operationally interesting state 145 chanages in the NEMO protocol. 147 The nemoConformance group identifies the managed objects that needs 148 to be implemented for conforming to this draft. 150 4. The NEMO MIB 152 NEMO-MIB DEFINITIONS ::= BEGIN 153 IMPORTS 154 MODULE-IDENTITY, mib-2, Unsigned32, Counter32, 155 Gauge32, Counter64, 156 OBJECT-TYPE, NOTIFICATION-TYPE 157 FROM SNMPv2-SMI 158 TEXTUAL-CONVENTION, 159 TruthValue, DateAndTime 160 FROM SNMPv2-TC 161 SnmpAdminString 162 FROM SNMP-FRAMEWORK-MIB 163 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 164 FROM SNMPv2-CONF 165 InetAddressType, InetAddress, InetAddressPrefixLength 166 FROM INET-ADDRESS-MIB 167 InterfaceIndex 168 FROM IF-MIB 169 mip6Mn 170 FROM MOBILEIPV6-MIB 171 ; 173 nemoMIB MODULE-IDENTITY 174 LAST-UPDATED "200507160000Z" -- 16th July, 2005 175 ORGANIZATION "IETF NEMO Working Group" 176 CONTACT-INFO 177 " Sri Gundavelli 178 Postal: Cisco Systems 179 170 W.Tasman Drive, 180 San Jose, CA 95134 181 USA 182 Tel: +1-408-527-6109 183 Email: sgundave@cisco.com 185 Glenn Mansfield Keeni 186 Postal: Cyber Solutions Inc. 187 6-6-3, Minami Yoshinari 188 Aoba-ku, Sendai, Japan 989-3204. 189 Tel: +81-22-303-4012 190 Fax: +81-22-303-4015 192 E-mail: glenn@cysols.com 194 Kenichi Nagami 195 Postal: INTEC NetCore Inc. 196 1-3-3, Shin-suna 197 Koto-ku, Tokyo, 135-0075 198 Japan 199 Tel: +81-3-5665-5069 200 E-mail: nagami@inetcore.com 202 Kazuhide Koide 203 Postal: Tohoku University 204 Katahira Campus 205 Sendai 206 Japan 207 Tel: +81-22-217-5454 208 E-mail: koide@shiratori.riec.tohoku.ac.jp 210 Support Group E-mail: nemo@ietf.org" 212 DESCRIPTION 213 "The MIB module for monitoring a NEMO entity. 215 Copyright (C) The Internet Society 2004. This 216 version of this MIB module is part of RFC XXXX; 217 see the RFC itself for full legal notices. 218 " 219 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 221 REVISION "200507160000Z" -- 16th July 2005 222 DESCRIPTION "Initial version, published as RFC XXXX." 224 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 226 ::= { mib-2 XXX } -- will be assigned by IANA 228 -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' 229 -- subtree and record the assignment in the SMI Numbers registry. 231 -- RFC Ed.: When the above assignment has been made, please 232 -- remove the above note 233 -- replace "XXX" here with the assigned value and 234 -- remove this note. 236 -- The NEMO MIB has the following 5 primary groups 238 nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } 239 nemoSystem OBJECT IDENTIFIER ::= { nemoMIB 1 } 240 nemoConfiguration OBJECT IDENTIFIER ::= { nemoMIB 2 } 241 nemoStats OBJECT IDENTIFIER ::= { nemoMIB 3 } 242 nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 4 } 244 -- The nemoConfiguration group has the following sub groups 246 nemoRegistration OBJECT IDENTIFIER ::= { nemoConfiguration 1 } 248 -- The nemoStats group has the following sub groups 250 nemoHomeAgentDiscovery OBJECT IDENTIFIER ::= { nemoStats 1 } 251 nemoTotalTraffic OBJECT IDENTIFIER ::= { nemoStats 2 } 252 nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 3 } 253 nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 4 } 255 -- Textual Conventions 256 NemoStatus ::= TEXTUAL-CONVENTION 257 STATUS current 258 DESCRIPTION 259 "This object represents the state of the NEMO entity. 260 The entity could be at home, isolated, roaming or in 261 unknown state. 262 " 263 SYNTAX INTEGER { 264 isolated (1), 265 roaming (2), 266 home (3), 267 unknown (4) 268 } 270 -- NemoPrefixRegMode ::= TEXTUAL-CONVENTION 271 -- STATUS current 272 -- DESCRIPTION 273 -- "This object represents the state of the NEMO entity. 274 -- The entity could be at home, isolated, roaming or in 275 -- unknown state. 276 -- " 277 -- SYNTAX INTEGER { 278 -- implicitmode (1), 279 -- explicitmode (2) 280 -- } 282 -- 283 -- 284 -- nemoSystem group 285 -- 286 -- 288 nemoRoamingStatus OBJECT-TYPE 289 SYNTAX NemoStatus 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "Indicates the current status of the mobile router. 294 The status indicates if the mobile router is at home, 295 roaming isolated or in an unknown state. 296 " 297 ::= { nemoSystem 1 } 299 nemoRegisteredUpTime OBJECT-TYPE 300 SYNTAX Gauge32 301 UNITS "seconds" 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "The time (in seconds) for which the mobile router 306 has been up and registered with its home agent. 307 " 308 ::= { nemoSystem 2 } 310 nemoLastAcceptedRegTime OBJECT-TYPE 311 SYNTAX DateAndTime 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "The timestamp when the last registration was accepted 316 by the home agent. 317 " 318 ::= { nemoSystem 3 } 320 nemoLastRejectedRegTime OBJECT-TYPE 321 SYNTAX DateAndTime 322 MAX-ACCESS read-only 323 STATUS current 324 DESCRIPTION 325 "The timestamp when the last registration was rejected 326 by the home agent. 327 " 328 ::= { nemoSystem 4 } 330 nemoTimeSinceLastRoamed OBJECT-TYPE 331 SYNTAX Gauge32 332 UNITS "seconds" 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The time elapsed (in seconds) since the last time the 337 mobile router roamed. 338 " 339 ::= { nemoSystem 5 } 341 nemoRegHomeAgentAddressType OBJECT-TYPE 342 SYNTAX InetAddressType 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The address type of the nemoRegHomeAgentAddress that 347 follows. 348 " 349 ::= { nemoSystem 6 } 351 nemoRegHomeAgentAddress OBJECT-TYPE 352 SYNTAX InetAddress 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The home agent address of the mobile router which 357 was used in the last accepted registration. 359 " 360 ::= { nemoSystem 7 } 362 nemoRegHomeAddressType OBJECT-TYPE 363 SYNTAX InetAddressType 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The address type of the nemoRegHomeAddress that 368 follows. 369 " 370 ::= { nemoSystem 8 } 372 nemoRegHomeAddress OBJECT-TYPE 373 SYNTAX InetAddress 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The home address of the mobile router which is used 378 in the last accepted registration. 379 " 380 ::= { nemoSystem 9 } 382 nemoRegHomeAddressPrefixLength OBJECT-TYPE 383 SYNTAX InetAddressPrefixLength 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The prefix length of the home address that the 388 mobile router is using for roaming. 389 " 390 ::= { nemoSystem 10 } 392 nemoRegCareofAddressType OBJECT-TYPE 393 SYNTAX InetAddressType 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The address type of the nemoRegCareofAddress that 398 follows. 399 " 400 ::= { nemoSystem 11 } 402 nemoRegCareofAddress OBJECT-TYPE 403 SYNTAX InetAddress 404 MAX-ACCESS read-only 405 STATUS current 406 DESCRIPTION 407 "The care-of address of the mobile router which is 408 used in the last accepted registration. 409 " 410 ::= { nemoSystem 12 } 412 nemoRegCareofAddressPrefixLength OBJECT-TYPE 413 SYNTAX InetAddressPrefixLength 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The prefix length of the care-of Address that the 418 mobile router currently is using for roaming. 419 " 420 ::= { nemoSystem 13 } 422 nemoActiveRoamingIfIndex OBJECT-TYPE 423 SYNTAX InterfaceIndex 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The interface index of the current active 428 roaming interface. 429 " 430 ::= { nemoSystem 14 } 432 nemoEstablishedHomeTunnelIfIndex OBJECT-TYPE 433 SYNTAX InterfaceIndex 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The interface index of the tunnel established 438 between the mobile router and the home agent 439 for NEMO traffic. 440 " 441 ::= { nemoSystem 15 } 443 -- 444 -- 445 -- nemoConfiguration group 446 -- 447 -- 449 -- 450 -- nemoRegistration sub group 451 -- 453 nemoHomeRegLifeTime OBJECT-TYPE 454 SYNTAX Gauge32 (4..262143) 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "The lifetime requested by the mobile router (in 459 seconds) in the Binding registration. It is between 460 4 and 262143 secs. 461 " 462 ::= { nemoRegistration 1 } 464 nemoHomeRegRetryCount OBJECT-TYPE 465 SYNTAX Gauge32 466 MAX-ACCESS read-write 467 STATUS current 468 DESCRIPTION 469 "The maximum number of registration attempts 470 allowed for the mobile router. 471 " 472 ::= { nemoRegistration 2 } 474 nemoHomeRegRetryDelay OBJECT-TYPE 475 SYNTAX Gauge32 476 MAX-ACCESS read-write 477 STATUS current 478 DESCRIPTION 479 "The delay time between successive registration 480 attempts by the mobile router(in seconds). 481 " 482 ::= { nemoRegistration 3 } 484 nemoHomeRegExtendBeforeExpiry OBJECT-TYPE 485 SYNTAX Gauge32 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "The time before the registration extension is 490 attempted (in seconds) by the mobile router. 491 " 492 ::= { nemoRegistration 4 } 494 nemoDynamicHADiscovery OBJECT-TYPE 495 SYNTAX TruthValue 496 MAX-ACCESS read-write 497 STATUS current 498 DESCRIPTION 499 "This object indicates whether or not the mobile 500 router should attempt to make dynamic home agent 501 address discovery(DHAAD). 502 " 503 ::= { nemoRegistration 5 } 505 nemoHomeAddressIdentifierType OBJECT-TYPE 506 SYNTAX BITS { 507 eui64 (0), 508 random (1) 509 } 510 MAX-ACCESS read-write 511 STATUS current 512 DESCRIPTION 513 "The type of the nemoHomeAddressIdentifier 514 that follows. 515 " 516 ::= { nemoRegistration 6 } 518 nemoHomeAddressIdentifierInetType OBJECT-TYPE 519 SYNTAX InetAddressType 520 MAX-ACCESS read-write 521 STATUS current 522 DESCRIPTION 523 "The InetAddressType of the nemoHomeAddressIdentifier 524 that follows. 525 " 526 ::= { nemoRegistration 7 } 528 nemoHomeAddressIdentifier OBJECT-TYPE 529 SYNTAX InetAddress 530 MAX-ACCESS read-write 531 STATUS current 532 DESCRIPTION 533 "The unicast routable address assigned to the mobile 534 router. This is used as the permanent address of 535 the mobile router in the sense that it remains 536 unchanged regardless of the mobile router's current 537 point ofattachment. 538 The type of the address represented by this object 539 is specified by the corresponding nemoHomeAddressType 540 object. 541 " 542 ::= { nemoRegistration 8 } 544 nemoHomeIfIndex OBJECT-TYPE 545 SYNTAX InterfaceIndex 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The interface index of the mobile router where the 550 home address is configured. 551 " 552 ::= { nemoRegistration 9 } 554 nemoPrefixRegMode OBJECT-TYPE 555 SYNTAX BITS { 556 implicitMode (0), 557 explicitMode (1) 558 } 559 MAX-ACCESS read-write 560 STATUS current 561 DESCRIPTION 562 "This object indicates if the mobile router will 563 explicitly register all the prefixes. 564 " 565 ::= { nemoRegistration 10 } 567 nemoRegisterConnectedPrefixes OBJECT-TYPE 568 SYNTAX TruthValue 569 MAX-ACCESS read-write 570 STATUS current 571 DESCRIPTION 572 "This object indicates if the mobile router will 573 register all the connected prefixes. 574 " 575 ::= { nemoRegistration 11 } 577 nemoHomeNetworkPrefixTable OBJECT-TYPE 578 SYNTAX SEQUENCE OF NemoHomeNetworkPrefixEntry 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "A table representing the potential home networks 583 that the mobile router can use 584 " 585 ::= { nemoRegistration 12 } 587 nemoHomeNetworkPrefixEntry OBJECT-TYPE 588 SYNTAX NemoHomeNetworkPrefixEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "An entry in the binding cache table. It represents a 593 single home network entry 595 Implementors need to be aware that if the total 596 number of octets in nemoHomeNetworkPrefix 597 exceeds 113 then OIDs of column 598 instances in this row will have more than 128 599 sub-identifiers and cannot be accessed using 600 SNMPv1, SNMPv2c, or SNMPv3. 601 " 602 INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix, 603 nemoHomeNetworkPrefixLength } 604 ::= { nemoHomeNetworkPrefixTable 1 } 606 NemoHomeNetworkPrefixEntry ::= 607 SEQUENCE { 608 nemoHomeNetworkPrefixType InetAddressType, 609 nemoHomeNetworkPrefix InetAddress, 610 nemoHomeNetworkPrefixLength InetAddressPrefixLength, 611 nemoHomeNetworkPrefixLifeTime Gauge32 612 } 614 nemoHomeNetworkPrefixType OBJECT-TYPE 615 SYNTAX InetAddressType 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "The InetAddressType of the nemoHomeNetworkPrefix 620 that follows. 621 " 623 ::= { nemoHomeNetworkPrefixEntry 1 } 625 nemoHomeNetworkPrefix OBJECT-TYPE 626 SYNTAX InetAddress 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "The prefix of the home network which is configured 631 for the mobile router. 632 " 633 ::= { nemoHomeNetworkPrefixEntry 2 } 635 nemoHomeNetworkPrefixLength OBJECT-TYPE 636 SYNTAX InetAddressPrefixLength 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "The length of the home network prefix which 641 is configured for the mobile router. 642 " 643 ::= { nemoHomeNetworkPrefixEntry 3 } 645 nemoHomeNetworkPrefixLifeTime OBJECT-TYPE 646 SYNTAX Gauge32 (4..262143) 647 MAX-ACCESS read-write 648 STATUS current 649 DESCRIPTION 650 "The lifetime requested by the mobile router (in 651 seconds) in the Binding registration. It is between 652 4 and 262143 secs. 653 " 654 ::= { nemoHomeNetworkPrefixEntry 4 } 656 -- 657 -- nemoPrefixTable 658 -- 660 nemoPrefixTable OBJECT-TYPE 661 SYNTAX SEQUENCE OF NemoPrefixEntry 662 MAX-ACCESS not-accessible 663 STATUS current 664 DESCRIPTION 665 "A table representing the NEMO prefixes. 666 " 667 ::= { nemoConfiguration 2 } 669 nemoPrefixEntry OBJECT-TYPE 670 SYNTAX NemoPrefixEntry 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "An entry in the binding cache table. It represents a 675 single Binding Update. 677 Implementors need to be aware that if the total 678 number of octets in nemoPrefix 679 exceeds 114 then OIDs of column 680 instances in this row will have more than 128 681 sub-identifiers and cannot be accessed using 682 SNMPv1, SNMPv2c, or SNMPv3. 683 " 684 INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength } 685 ::= { nemoPrefixTable 1 } 687 NemoPrefixEntry ::= 688 SEQUENCE { 689 nemoPrefixType InetAddressType, 690 nemoPrefix InetAddress, 691 nemoPrefixLength InetAddressPrefixLength, 692 nemoPrefixLifeTime Gauge32 693 } 695 nemoPrefixType OBJECT-TYPE 696 SYNTAX InetAddressType 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The InetAddressType of the nemoPrefix 701 that follows. 702 " 703 ::= { nemoPrefixEntry 1 } 705 nemoPrefix OBJECT-TYPE 706 SYNTAX InetAddress 707 MAX-ACCESS not-accessible 708 STATUS current 709 DESCRIPTION 710 "The mobile network prefix that is delegated to the 711 mobile router and advertised in the mobile network. 712 The type of the address represented by this object 713 is specified by the corresponding 714 nemoPrefixType object. 715 " 716 ::= { nemoPrefixEntry 2 } 718 nemoPrefixLength OBJECT-TYPE 719 SYNTAX InetAddressPrefixLength 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "The prefix length of the mobile network prefix. 724 " 725 ::= { nemoPrefixEntry 3 } 727 nemoPrefixLifeTime OBJECT-TYPE 728 SYNTAX Gauge32 729 UNITS "seconds" 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The lifetime (in seconds) granted to the mobile 734 router for this registration. 735 " 736 ::= { nemoPrefixEntry 4 } 738 -- 739 -- nemoRoamingIfTable 740 -- 742 nemoRoamingIfTable OBJECT-TYPE 743 SYNTAX SEQUENCE OF NemoRoamingIfEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "A table representing the roaming interfaces. 748 Each entry represents a configured roaming interface 749 with the roaming characterstics. 750 " 751 ::= { nemoConfiguration 3 } 753 nemoRoamingIfEntry OBJECT-TYPE 754 SYNTAX NemoRoamingIfEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "An entry in the roaming interface table. It 759 represents a single roaming interface entry. 760 " 761 INDEX { nemoRoamingIfIndex, nemoRoamingIfPriority } 762 ::= { nemoRoamingIfTable 1 } 764 NemoRoamingIfEntry ::= 765 SEQUENCE { 766 nemoRoamingIfIndex InterfaceIndex, 767 nemoRoamingIfPriority Unsigned32, 768 nemoRoamingIfDescription SnmpAdminString, 769 nemoRoamingIfRoamHoldDownTime Gauge32 770 } 772 nemoRoamingIfIndex OBJECT-TYPE 773 SYNTAX InterfaceIndex 774 MAX-ACCESS not-accessible 775 STATUS current 776 DESCRIPTION 777 "The index of the interface that will be used for 778 roaming to foreign networks in the mobile router. 779 " 780 ::= { nemoRoamingIfEntry 1 } 782 nemoRoamingIfPriority OBJECT-TYPE 783 SYNTAX Unsigned32 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "The priority configured to the interface. 788 This value will be configured between 0 and 255. 789 " 790 ::= { nemoRoamingIfEntry 2 } 792 nemoRoamingIfDescription OBJECT-TYPE 793 SYNTAX SnmpAdminString 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "The description of the interface that will be used 798 for roaming to foreign networks in the mobile router. 799 " 800 ::= { nemoRoamingIfEntry 3 } 802 nemoRoamingIfRoamHoldDownTime OBJECT-TYPE 803 SYNTAX Gauge32 804 UNITS "seconds" 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "This object indicates the time for which hold on to 809 the interface. 810 This value is configured to avoid interface flapping. 811 " 812 ::= { nemoRoamingIfEntry 4 } 814 --- 815 --- 816 --- nemoStats group 817 --- 818 --- 820 -- 821 -- Dynamic Home Agent discovery protocol related counters 822 -- 824 nemoDHAADRequests OBJECT-TYPE 825 SYNTAX Counter32 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "The total number of dynamic home agent address 830 discovery requests sent by the mobile router. 831 " 832 ::= { nemoHomeAgentDiscovery 1 } 834 nemoDHAADRepliesWNemoSupport OBJECT-TYPE 835 SYNTAX Counter32 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The total number of dynamic home agent address 840 discovery replies sent by the home agent with NEMO 841 support. 842 " 843 ::= { nemoHomeAgentDiscovery 2 } 845 nemoDHAADRepliesWONemoSupport OBJECT-TYPE 846 SYNTAX Counter32 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The total number of dynamic home agent address 851 discovery replies sent by the home agent without 852 NEMO support. 853 " 854 ::= { nemoHomeAgentDiscovery 3 } 856 nemoDHAADDiscoveryTimeouts OBJECT-TYPE 857 SYNTAX Counter32 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The total number of dynamic home agent address 862 discovery requested by the mobile router and that 863 was timeout. 864 " 865 ::= { nemoHomeAgentDiscovery 4 } 867 -- 868 -- nemoStats:nemoTotalTraffic 869 -- 871 nemoInOctets OBJECT-TYPE 872 SYNTAX Counter32 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "The total number of octets in the IPv6 datagrams 877 received by the nodes in the NEMO networks. 879 Discontinuities in the value of this counter can 880 occur at re-initialization of the mobile router. 881 " 882 ::= { nemoTotalTraffic 1 } 884 nemoHCInOctets OBJECT-TYPE 885 SYNTAX Counter64 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "The total number of octets in the IPv6 datagrams 890 received by the NEMO networks. 892 This object is a 64-bit version of nemoInOctets. 893 Discontinuities in the value of this counter can 894 occur at re-initialization of the mobile router. 895 " 896 ::= { nemoTotalTraffic 2 } 898 nemoInPackets OBJECT-TYPE 899 SYNTAX Counter32 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The total number of octets in the IPv6 datagrams 904 received by the nodes in the NEMO networks. 906 Discontinuities in the value of this counter can 907 occur at re-initialization of the mobile router. 908 " 909 ::= { nemoTotalTraffic 3 } 911 nemoHCInPackets OBJECT-TYPE 912 SYNTAX Counter64 913 MAX-ACCESS read-only 914 STATUS current 915 DESCRIPTION 916 "The total number of IPv6 packets received by 917 the nodes in the NEMO networks. 919 This object is a 64-bit version of nemoInOctets. 920 Discontinuities in the value of this counter can 921 occur at re-initialization of the mobile router. 922 " 923 ::= { nemoTotalTraffic 4 } 925 nemoOutOctets OBJECT-TYPE 926 SYNTAX Counter32 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "The total number of octets in the IPv6 datagrams 931 sent by the nodes in the NEMO networks. 933 Discontinuities in the value of this counter can 934 occur at re-initialization of the mobile router. 935 " 936 ::= { nemoTotalTraffic 5 } 938 nemoHCOutOctets OBJECT-TYPE 939 SYNTAX Counter64 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The total number of octets in the IPv6 datagrams 944 sent by the NEMO networks. 946 This object is a 64-bit version of nemoInOctets. 947 Discontinuities in the value of this counter can 948 occur at re-initialization of the mobile router. 949 " 950 ::= { nemoTotalTraffic 6 } 952 nemoOutPackets OBJECT-TYPE 953 SYNTAX Counter32 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "The total number of octets in the IPv6 datagrams 958 sent by the nodes in the NEMO networks. 960 Discontinuities in the value of this counter can 961 occur at re-initialization of the mobile router. 962 " 963 ::= { nemoTotalTraffic 7 } 965 nemoHCOutPackets OBJECT-TYPE 966 SYNTAX Counter64 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "The total number of IPv6 packets sent by the nodes 971 in the NEMO networks. 973 This object is a 64-bit version of nemoInOctets. 974 Discontinuities in the value of this counter can 975 occur at re-initialization of the mobile router. 976 " 977 ::= { nemoTotalTraffic 8 } 979 -- 980 -- nemoStats:nemoBindingRegcounters 981 -- 983 nemoBindingUpdates OBJECT-TYPE 984 SYNTAX Counter32 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "The total number of Binding Updates sent by the 989 mobile router. 991 Discontinuities in the value of this counter can 992 occur at re-initialization of the mobile router. 993 " 994 ::= { nemoBindingRegCounters 1 } 996 nemoBindingAcks OBJECT-TYPE 997 SYNTAX Counter32 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The total number of Binding Acknowledgements 1002 received by the mobile router. 1004 Discontinuities in the value of this counter can 1005 occur at re-initialization of the mobile router. 1006 " 1007 ::= { nemoBindingRegCounters 2 } 1009 nemoBindingAcksWONemoSupport OBJECT-TYPE 1010 SYNTAX Counter32 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "The total number of Binding Acks without the 1015 NEMO support received by the mobile router. 1017 Discontinuities in the value of this counter can 1018 occur at re-initialization of the mobile router. 1019 " 1020 ::= { nemoBindingRegCounters 3 } 1022 nemoBindingAckNotHomeRegn OBJECT-TYPE 1023 SYNTAX Counter32 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "The total number of Binding Update requests 1028 rejected by the home agent with the status code 1029 in the Binding Acknowledgment indicating 1030 'Not Home Registration' 1032 Discontinuities in the value of this counter can 1033 occur at re-initialization of the mobile router. 1034 " 1035 ::= { nemoBindingRegCounters 4 } 1037 nemoBindingRegTypeChanged OBJECT-TYPE 1038 SYNTAX Counter32 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "Discontinuities in the value of this counter can 1043 occur at re-initialization of the mobile router. 1044 " 1045 ::= { nemoBindingRegCounters 5 } 1047 nemoOpNotSupported OBJECT-TYPE 1048 SYNTAX Counter32 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "The total number of Binding Update requests rejected 1053 by the home agent with status code in the 1054 Binding Acknowledgement indicating 1055 'Mobile Router Operation not permitted' (Code 140). 1057 Discontinuities in the value of this counter can 1058 occur at re-initialization of the mobile router. 1059 " 1060 ::= { nemoBindingRegCounters 6 } 1062 nemoInvalidPrefix OBJECT-TYPE 1063 SYNTAX Counter32 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "The total number of Binding Update requests rejected 1068 by the home agent with status code in the Binding 1069 Acknowledgement indicating 'Invalid Prefix' 1070 (Code 141). 1072 Discontinuities in the value of this counter can 1073 occur at re-initialization of the mobile router. 1074 " 1075 ::= { nemoBindingRegCounters 7 } 1077 nemoNotAuthorizedForPrefix OBJECT-TYPE 1078 SYNTAX Counter32 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "The total number of Binding Update requests rejected 1083 by the home agent with status code in the Binding 1084 Acknowledgement indicating 'Not Authorized for 1085 Prefix' (Code 142). 1087 Discontinuities in the value of this counter can 1088 occur at re-initialization of the mobile router. 1089 " 1090 ::= { nemoBindingRegCounters 8 } 1092 nemoForwardingSetupFailed OBJECT-TYPE 1093 SYNTAX Counter32 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "The total number of Binding Update requests rejected 1098 by the home agent with status code in the Binding 1099 Acknowledgement indicating 'Forwarding Setup failed' 1100 (Code 143). 1102 Discontinuities in the value of this counter can 1103 occur at re-initialization of the mobile router. 1104 " 1105 ::= { nemoBindingRegCounters 9 } 1107 -- 1108 -- nemoStats:nemoRoamingCounters 1109 -- 1111 nemoMovedHome OBJECT-TYPE 1112 SYNTAX Counter32 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "Number of times the mobile router has detected 1117 movement from a foreign network to its home 1118 network. 1119 Discontinuities in the value of this counter can 1120 occur at re-initialization of the mobile router. 1121 " 1122 ::= { nemoRoamingCounters 1 } 1124 nemoMovedOutofHome OBJECT-TYPE 1125 SYNTAX Counter32 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "Number of times the mobile router has detected 1130 movement from to a foreign network from the home 1131 network, has reconstructed its care-of address and 1132 has initiated the care-of address registration 1133 process. 1134 Discontinuities in the value of this counter can 1135 occur at re-initialization of the mobile router. 1137 " 1138 ::= { nemoRoamingCounters 2 } 1140 nemoMovedFNtoFN OBJECT-TYPE 1141 SYNTAX Counter32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "Number of times the mobile router has detected 1146 movement from to a foreign network from the home 1147 network, has reconstructed its care-of address and 1148 has initiated the care-of address registration 1149 process. 1150 Discontinuities in the value of this counter can 1151 occur at re-initialization of the mobile router. 1152 " 1153 ::= { nemoRoamingCounters 3 } 1155 nemoBetterIfDetected OBJECT-TYPE 1156 SYNTAX Counter32 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION 1160 "Number of times the NEMO entity has found roaming 1161 interface with better priority. 1162 Discontinuities in the value of this counter can 1163 occur at re-initialization of the mobile router. 1164 " 1165 ::= { nemoRoamingCounters 4 } 1167 -- 1168 -- 1169 -- nemoNotifications 1170 -- 1171 -- 1173 nemoHomeTunnelEstablished NOTIFICATION-TYPE 1174 OBJECTS { 1175 nemoActiveRoamingIfIndex, 1176 nemoEstablishedHomeTunnelIfIndex, 1177 nemoRegCareofAddressType, 1178 nemoRegCareofAddress 1179 } 1180 STATUS current 1181 DESCRIPTION 1182 "This notification is sent by the mobile router every 1183 time the tunnel is established between the home agent 1184 and the mobile router. 1185 " 1186 ::= { nemoNotifications 1 } 1188 nemoHomeTunnelReleased NOTIFICATION-TYPE 1189 OBJECTS { 1190 nemoActiveRoamingIfIndex, 1191 nemoEstablishedHomeTunnelIfIndex, 1192 nemoRegCareofAddressType, 1193 nemoRegCareofAddress 1194 } 1195 STATUS current 1196 DESCRIPTION 1197 "This notification is sent by the mobile router every 1198 time the tunnel is deleted between the home agent and 1199 the mobile router. 1200 " 1201 ::= { nemoNotifications 2} 1203 -- Conformance information 1204 nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } 1205 nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } 1207 -- Units of conformance 1208 nemoSystemGroup OBJECT-GROUP 1209 OBJECTS { 1210 nemoRoamingStatus, 1211 nemoRegisteredUpTime, 1212 nemoLastAcceptedRegTime, 1213 nemoLastRejectedRegTime, 1214 nemoTimeSinceLastRoamed, 1215 nemoRegHomeAgentAddressType, 1216 nemoRegHomeAgentAddress, 1217 nemoRegHomeAddressType, 1218 nemoRegHomeAddress, 1219 nemoRegHomeAddressPrefixLength, 1220 nemoRegCareofAddressType, 1221 nemoRegCareofAddress, 1222 nemoRegCareofAddressPrefixLength, 1223 nemoActiveRoamingIfIndex, 1224 nemoEstablishedHomeTunnelIfIndex 1226 } 1227 STATUS current 1228 DESCRIPTION 1229 " A collection of objects for basic NEMO 1230 monitoring." 1231 ::= { nemoGroups 1 } 1233 nemoConfigurationGroup OBJECT-GROUP 1234 OBJECTS { 1235 nemoHomeRegLifeTime, 1236 nemoHomeRegRetryCount, 1237 nemoHomeRegRetryDelay, 1238 nemoHomeRegExtendBeforeExpiry, 1239 nemoDynamicHADiscovery, 1240 nemoHomeAddressIdentifierType, 1241 nemoHomeAddressIdentifierInetType, 1242 nemoHomeAddressIdentifier, 1243 nemoHomeIfIndex, 1244 nemoPrefixRegMode, 1245 nemoRegisterConnectedPrefixes, 1246 -- nemoHomeNetworkPrefixType, 1247 -- nemoHomeNetworkPrefix, 1248 -- nemoHomeNetworkPrefixLength, 1249 nemoHomeNetworkPrefixLifeTime, 1250 nemoPrefixLifeTime, 1251 -- nemoRoamingIfIndex, 1252 -- nemoRoamingIfPriority, 1253 nemoRoamingIfDescription, 1254 nemoRoamingIfRoamHoldDownTime, 1255 nemoDHAADRequests, 1256 nemoDHAADRepliesWNemoSupport, 1257 nemoDHAADRepliesWONemoSupport, 1258 nemoDHAADDiscoveryTimeouts 1259 } 1260 STATUS current 1261 DESCRIPTION 1262 " A collection of objects for basic NEMO 1263 configuration monitoring." 1264 ::= { nemoGroups 2 } 1266 nemoStatsGroup OBJECT-GROUP 1267 OBJECTS { 1268 nemoInOctets, 1269 nemoHCInOctets, 1270 nemoInPackets, 1271 nemoHCInPackets, 1272 nemoOutOctets, 1273 nemoHCOutOctets, 1274 nemoOutPackets, 1275 nemoHCOutPackets, 1276 nemoBindingUpdates, 1277 nemoBindingAcks, 1278 nemoBindingAcksWONemoSupport, 1279 nemoBindingAckNotHomeRegn, 1280 nemoBindingRegTypeChanged, 1281 nemoOpNotSupported, 1282 nemoInvalidPrefix, 1283 nemoNotAuthorizedForPrefix, 1284 nemoForwardingSetupFailed, 1285 nemoMovedHome, 1286 nemoMovedOutofHome, 1287 nemoMovedFNtoFN, 1288 nemoBetterIfDetected 1289 } 1290 STATUS current 1291 DESCRIPTION 1292 " A collection of objects for basic NEMO 1293 monitoring. 1294 " 1295 ::= { nemoGroups 3 } 1297 nemoNotificationGroup NOTIFICATION-GROUP 1298 NOTIFICATIONS { 1299 nemoHomeTunnelEstablished, 1300 nemoHomeTunnelReleased 1301 } 1302 STATUS current 1303 DESCRIPTION 1304 "A collection of notifications from a home agent 1305 or correspondent node to the Manager about the 1306 tunnel status of the mobile router. 1307 " 1308 ::= { nemoGroups 4 } 1310 -- Compliance statements 1311 nemoCoreCompliance MODULE-COMPLIANCE 1312 STATUS current 1313 DESCRIPTION 1314 "The compliance statement for SNMP entities 1315 which implement the MOBILEIPV6-MIB. 1316 There are a number of INDEX objects that cannot be 1317 represented in the form of OBJECT clauses in SMIv2, 1318 but for which there are compliance requirements, 1319 expressed in OBJECT clause form in this description: 1320 -- OBJECT nemoBindingHomeAddressType 1321 -- SYNTAX InetAddressType { ipv6(2) } 1322 -- DESCRIPTION 1323 -- This MIB module requires support for global 1324 -- ipv6 addresses for the nemoBindingHomeAddress 1325 -- object. 1326 -- 1327 " 1328 MODULE -- this module 1329 MANDATORY-GROUPS { nemoSystemGroup, 1330 nemoConfigurationGroup, 1331 nemoStatsGroup, 1332 nemoNotificationGroup 1333 } 1335 ::= { nemoCompliances 1 } 1337 END 1339 5. Security Considerations 1341 There are a number of management objects defined in this MIB module 1342 with a MAX-ACCESS clause of read-write. Such objects may be 1343 considered sensitive or vulnerable in some network environments. The 1344 support for SET operations in a non-secure environment without proper 1345 protection can have a negative effect on network operations. These 1346 are the tables and objects and their sensitivity/vulnerability: 1348 Some of the readable objects in this MIB module (i.e., objects with a 1349 MAX-ACCESS other than not-accessible) may be considered sensitive or 1350 vulnerable in some network environments. It is thus important to 1351 control even GET and/or NOTIFY access to these objects and possibly 1352 to even encrypt the values of these objects when sending them over 1353 the network via SNMP. These are the tables and objects and their 1354 sensitivity/vulnerability: 1356 SNMP versions prior to SNMPv3 did not include adequate security. 1357 Even if the network itself is secure (for example by using IPSec), 1358 even then, there is no control as to who on the secure network is 1359 allowed to access and GET/SET (read/change/create/delete) the objects 1360 in this MIB module. 1362 It is RECOMMENDED that implementers consider the security features as 1363 provided by the SNMPv3 framework (see [RFC3410], section 8), 1364 including full support for the SNMPv3 cryptographic mechanisms (for 1365 authentication and privacy). 1367 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1368 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1369 enable cryptographic security. It is then a customer/operator 1370 responsibility to ensure that the SNMP entity giving access to an 1371 instance of this MIB module is properly configured to give access to 1372 the objects only to those principals (users) that have legitimate 1373 rights to indeed GET or SET (change/create/delete) them. 1375 6. IANA Considerations 1377 IANA should assign a base arc in the mib-2 (standards track) OID tree 1378 for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB. 1380 7. Acknowledgments 1382 The authors would like to thank T.J Kniveton and Thierry Ernst for 1383 their inputs to the document and also would like to thank Kent Leung 1384 and Pascal Thubert for their discussions Mobile Router 1385 implementations. 1387 8. References 1389 8.1 Normative References 1391 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 1392 Requirements Levels, BCP 14, RFC 2119, March 1997. 1394 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1395 Rose, M. and S. Waldbusser, Structure of Management 1396 Information Version 2 (SMIv2), STD 58, RFC 2578, 1397 April 1999. 1399 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1400 Rose, M. and S. Waldbusser, Textual Conventions for 1401 SMIv2, STD 58, RFC 2579, April 1999. 1403 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1404 Rose, M. and S. Waldbusser, Conformance Statements 1405 for SMIv2, STD 58, RFC 2580, April 1999. 1407 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility 1408 Support in IPv6q RFC 3775, June 2004. 1410 [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. 1411 Devarapalli, Network Mobility (NEMO) Basic Support 1412 Protocol, RFC 3963, Jan 2005. 1414 [RFC4001] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder, 1415 J., Textual Conventions for Internet Network 1416 Addresses, RFC 4001, February 2005. 1418 [RFC2011bis] Routhier, S., Management Information Base for the 1419 Internet Protocol (IP), work in progress (currently 1420 ). 1422 [MIPv6MIB] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, 1423 The Mobile IPv6 MIB, work in progress (currently 1424 ). 1426 8.2 Informative References 1427 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1428 Introduction and Applicability Statements for 1429 Internet-Standard Management Framework, RFC 3410, 1430 December 2002. 1432 [NEMOTERM] T. Ernst and H.-Y. Lach., Network Mobility Support 1433 Terminology, work in progress (currently 1434 ). 1436 [NEMOGOAL] T. Ernst. Network Mobility Support Goals and 1437 Requirements, work in progress (currently 1438 ). 1440 9. Authors' Addresses 1442 Sri Gundavelli 1443 Cisco Systems 1444 170 W.Tasman Drive, 1445 San Jose, CA 95134 1446 USA 1448 Phone: +1-408-527-6109 1449 Email: sgundave@cisco.com 1451 Glenn Mansfield Keeni 1452 Cyber Solutions Inc. 1453 6-6-3 Minami Yoshinari 1454 Aoba-ku, Sendai 989-3204 1455 Japan 1457 Phone: +81-22-303-4012 1458 EMail: glenn@cysols.com 1460 Kenichi Nagami 1461 INTEC NetCore Inc. 1462 1-3-3, Shin-suna 1463 Koto-ku, Tokyo, 135-0075 1464 Japan 1466 Phone: +81-3-5665-5069 1467 E-mail: nagami@inetcore.com 1469 Kazuhide Koide 1470 Tohoku University 1471 Katahira Campus 1472 Sendai 1473 Japan 1475 Phone: +81-22-217-5454 1476 E-mail: koide@shiratori.riec.tohoku.ac.jp 1478 10. Full Copyright Statement 1480 Copyright (C) The Internet Society (2005). This document is subject 1481 to the rights, licenses and restrictions contained in BCP 78, and 1482 except as set forth therein, the authors retain all their rights. 1484 This document and the information contained herein are provided on an 1485 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1486 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 1487 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 1488 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1489 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1490 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1492 Intellectual Property 1494 The IETF takes no position regarding the validity or scope of any 1495 Intellectual Property Rights or other rights that might be claimed 1496 to pertain to the implementation or use of the technology 1497 described in this document or the extent to which any license 1498 under such rights might or might not be available; nor does it 1499 represent that it has made any independent effort to identify any 1500 such rights. Information on the procedures with respect to 1501 rights in RFC documents can be found in BCP 78 and BCP 79. 1503 Copies of IPR disclosures made to the IETF Secretariat and any 1504 assurances of licenses to be made available, or the result of an 1505 attempt made to obtain a general license or permission for the use 1506 of such proprietary rights by implementers or users of this 1507 specification can be obtained from the IETF on-line IPR repository 1508 at http://www.ietf.org/ipr. 1510 The IETF invites any interested party to bring to its attention 1511 any copyrights, patents or patent applications, or other 1512 proprietary rights that may cover technology that may be required 1513 to implement this standard. Please address the information to the 1514 IETF at ietf-ipr@ietf.org. 1516 Acknowledgement 1518 Funding for the RFC Editor function is currently provided by the 1519 Internet Society.