idnits 2.17.1 draft-ietf-nemo-mib-02.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 on line 1418. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1395. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1402. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1408. ** 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 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 (October 21, 2006) is 6396 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 108 == Missing Reference: 'NEMO' is mentioned on line 117, but not defined == Unused Reference: 'RFC4001' is defined on line 1323, but no explicit reference was found in the text == Unused Reference: 'RFC2011bis' is defined on line 1327, but no explicit reference was found in the text == Unused Reference: 'RFC4295' is defined on line 1331, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) == Outdated reference: A later version (-06) exists of draft-ietf-nemo-terminology-01 == Outdated reference: A later version (-06) exists of draft-ietf-nemo-requirements-02 Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 8 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: April 24, 2007 Glenn M. Keeni 5 Cyber Solutions 6 Kazuhide Koide 7 Tohoku University 8 Kenichi Nagami 9 INTEC NetCore 10 October 21, 2006 12 NEMO Management Information Base 13 draft-ietf-nemo-mib-02 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 April 24, 2007. 40 Copyright Notice 42 Copyright (C) The Internet Society (2006). 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 . . . . . . . . . . . . . . . . . . . . . 30 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30 63 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 64 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 65 8.1. Normative References . . . . . . . . . . . . . . . . . . . 31 66 8.2. Informative References . . . . . . . . . . . . . . . . . . 32 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 68 Intellectual Property and Copyright Statements . . . . . . . . . . 34 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 [10] 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 [NEMO]. 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 chanages 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 Gauge32, Counter64, 160 OBJECT-TYPE, NOTIFICATION-TYPE 161 FROM SNMPv2-SMI 162 TEXTUAL-CONVENTION, 163 TruthValue, DateAndTime 164 FROM SNMPv2-TC 165 SnmpAdminString 166 FROM SNMP-FRAMEWORK-MIB 167 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 168 FROM SNMPv2-CONF 169 InetAddressType, InetAddress, InetAddressPrefixLength 170 FROM INET-ADDRESS-MIB 171 InterfaceIndex 172 FROM IF-MIB 173 mip6Mn 174 FROM MOBILEIPV6-MIB 175 ; 177 nemoMIB MODULE-IDENTITY 178 LAST-UPDATED "200507160000Z" -- 16th July, 2005 179 ORGANIZATION "IETF NEMO Working Group" 180 CONTACT-INFO 181 " Sri Gundavelli 182 Postal: Cisco Systems 183 170 W.Tasman Drive, 184 San Jose, CA 95134 185 USA 186 Tel: +1-408-527-6109 187 Email: sgundave@cisco.com 189 Glenn Mansfield Keeni 190 Postal: Cyber Solutions Inc. 191 6-6-3, Minami Yoshinari 192 Aoba-ku, Sendai, Japan 989-3204. 193 Tel: +81-22-303-4012 194 Fax: +81-22-303-4015 195 E-mail: glenn@cysols.com 197 Kenichi Nagami 198 Postal: INTEC NetCore Inc. 199 1-3-3, Shin-suna 200 Koto-ku, Tokyo, 135-0075 201 Japan 202 Tel: +81-3-5665-5069 203 E-mail: nagami@inetcore.com 205 Kazuhide Koide 206 Postal: Tohoku University 207 Katahira Campus 208 Sendai 209 Japan 210 Tel: +81-22-217-5454 211 E-mail: koide@shiratori.riec.tohoku.ac.jp 213 Support Group E-mail: nemo@ietf.org" 215 DESCRIPTION 216 "The MIB module for monitoring a NEMO entity. 218 Copyright (C) The Internet Society 2004. This 219 version of this MIB module is part of RFC XXXX; 220 see the RFC itself for full legal notices. 221 " 222 -- RFC Ed.: replace XXXX with actual RFC number and remove this 223 -- note 225 REVISION "200507160000Z" -- 16th July 2005 226 DESCRIPTION "Initial version, published as RFC XXXX." 228 -- RFC Ed.: replace XXXX with actual RFC number and remove this 229 -- note 231 ::= { mib-2 XXX } -- will be assigned by IANA 233 -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' 234 -- subtree and record the assignment in the SMI Numbers 235 -- registry. 236 -- 237 -- RFC Ed.: When the above assignment has been made, please 238 -- remove the above note 239 -- replace "XXX" here with the assigned value and 240 -- remove this note. 242 -- The NEMO MIB has the following 5 primary groups 244 nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 } 245 nemoSystem OBJECT IDENTIFIER ::= { nemoMIB 1 } 246 nemoConfiguration OBJECT IDENTIFIER ::= { nemoMIB 2 } 247 nemoStats OBJECT IDENTIFIER ::= { nemoMIB 3 } 248 nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 4 } 250 -- The nemoConfiguration group has the following sub groups 252 nemoRegistration OBJECT IDENTIFIER ::= { nemoConfiguration 1 } 254 -- The nemoStats group has the following sub groups 256 nemoHomeAgentDiscovery OBJECT IDENTIFIER ::= { nemoStats 1 } 257 nemoBindingRegCounters OBJECT IDENTIFIER ::= { nemoStats 2 } 258 nemoRoamingCounters OBJECT IDENTIFIER ::= { nemoStats 3 } 260 -- Textual Conventions 261 NemoStatus ::= TEXTUAL-CONVENTION 262 STATUS current 263 DESCRIPTION 264 "This object represents the state of the NEMO 265 entity. The entity could be at home, isolated, 266 roaming or in unknown state. 267 " 268 SYNTAX INTEGER { 269 isolated (1), 270 roaming (2), 271 home (3), 272 unknown (4) 273 } 275 -- 276 -- 277 -- nemoSystem group 278 -- 279 -- 281 nemoRoamingStatus OBJECT-TYPE 282 SYNTAX NemoStatus 283 MAX-ACCESS read-only 284 STATUS current 285 DESCRIPTION 286 "Indicates the current status of the mobile router. 287 The status indicates if the mobile router is at 288 home, roaming, isolated or in an unknown state. 289 " 290 REFERENCE 291 "RFC3963 : Section 3" 292 ::= { nemoSystem 1 } 294 nemoRegisteredUpTime OBJECT-TYPE 295 SYNTAX Gauge32 296 UNITS "seconds" 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The time (in seconds) for which the mobile router 301 has been up and registered with its home agent. 302 " 303 REFERENCE 304 "RFC3963 : Section 6.4" 305 ::= { nemoSystem 2 } 307 nemoLastAcceptedRegTime OBJECT-TYPE 308 SYNTAX DateAndTime 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The timestamp when the last registration was 313 accepted by the home agent. 314 " 315 REFERENCE 316 "RFC3963 : Section 6.6" 317 ::= { nemoSystem 3 } 319 nemoLastRejectedRegTime OBJECT-TYPE 320 SYNTAX DateAndTime 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The timestamp when the last registration was 325 rejected by the home agent. 326 " 327 REFERENCE 328 "RFC3963 : Section 6.6" 329 ::= { nemoSystem 4 } 331 nemoTimeSinceLastRoamed OBJECT-TYPE 332 SYNTAX Gauge32 333 UNITS "seconds" 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The time elapsed (in seconds) since the last time 338 the mobile router roamed. 339 " 340 REFERENCE 341 "RFC3963 : Section 6.6" 342 ::= { nemoSystem 5 } 344 nemoRegHomeAgentAddressType OBJECT-TYPE 345 SYNTAX InetAddressType 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "The address type of the nemoRegHomeAgentAddress 350 that follows. 351 " 352 REFERENCE 353 "RFC3963 : Section 3" 354 ::= { nemoSystem 6 } 356 nemoRegHomeAgentAddress OBJECT-TYPE 357 SYNTAX InetAddress 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The home agent address of the mobile router which 362 was used in the last accepted registration. 363 " 364 REFERENCE 365 "RFC3963 : Section 3" 367 ::= { nemoSystem 7 } 369 nemoRegHomeAddressType OBJECT-TYPE 370 SYNTAX InetAddressType 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The address type of the nemoRegHomeAddress that 375 follows. 376 " 377 REFERENCE 378 "RFC3963 : Section 3" 379 ::= { nemoSystem 8 } 381 nemoRegHomeAddress OBJECT-TYPE 382 SYNTAX InetAddress 383 MAX-ACCESS read-only 384 STATUS current 385 DESCRIPTION 386 "The home address of the mobile router which is 387 used in the last accepted registration. 388 " 389 REFERENCE 390 "RFC3963 : Section 3" 391 ::= { nemoSystem 9 } 393 nemoRegHomeAddressPrefixLength OBJECT-TYPE 394 SYNTAX InetAddressPrefixLength 395 MAX-ACCESS read-only 396 STATUS current 397 DESCRIPTION 398 "The prefix length of the home address that the 399 mobile router is using for roaming. 400 " 401 REFERENCE 402 "RFC3963 : Section 3" 403 ::= { nemoSystem 10 } 405 nemoRegCareofAddressType OBJECT-TYPE 406 SYNTAX InetAddressType 407 MAX-ACCESS read-only 408 STATUS current 409 DESCRIPTION 410 "The address type of the nemoRegCareofAddress that 411 follows. 412 " 413 REFERENCE 414 "RFC3963 : Section 3" 415 ::= { nemoSystem 11 } 417 nemoRegCareofAddress OBJECT-TYPE 418 SYNTAX InetAddress 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 "The care-of address of the mobile router which is 423 used in the last accepted registration. 424 " 425 REFERENCE 426 "RFC3963 : Section 3" 427 ::= { nemoSystem 12 } 429 nemoRegCareofAddressPrefixLength OBJECT-TYPE 430 SYNTAX InetAddressPrefixLength 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The prefix length of the care-of Address that the 435 mobile router currently is using for roaming. 436 " 437 REFERENCE 438 "RFC3963 : Section 3" 439 ::= { nemoSystem 13 } 441 nemoActiveRoamingIfIndex OBJECT-TYPE 442 SYNTAX InterfaceIndex 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The interface index of the current active 447 roaming interface. 448 " 449 REFERENCE 450 "RFC3963 : Section 5.5" 451 ::= { nemoSystem 14 } 453 nemoEstablishedHomeTunnelIfIndex OBJECT-TYPE 454 SYNTAX InterfaceIndex 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The interface index of the tunnel established 459 between the mobile router and the home agent 460 for NEMO traffic. 461 " 462 REFERENCE 463 "RFC3963 : Section 5.5" 464 ::= { nemoSystem 15 } 466 -- 467 -- 468 -- nemoConfiguration group 469 -- 470 -- 472 -- 473 -- nemoRegistration sub group 474 -- 476 nemoHomeRegLifeTime OBJECT-TYPE 477 SYNTAX Gauge32 (4..262143) 478 MAX-ACCESS read-write 479 STATUS current 480 DESCRIPTION 481 "The lifetime requested by the mobile router (in 482 seconds) in the Binding registration. It is 483 between 4 and 262143 secs. 484 " 485 ::= { nemoRegistration 1 } 487 nemoHomeRegRetryCount OBJECT-TYPE 488 SYNTAX Gauge32 489 MAX-ACCESS read-write 490 STATUS current 491 DESCRIPTION 492 "The maximum number of registration attempts 493 allowed for the mobile router. 494 " 495 ::= { nemoRegistration 2 } 497 nemoHomeRegRetryDelay OBJECT-TYPE 498 SYNTAX Gauge32 499 MAX-ACCESS read-write 500 STATUS current 501 DESCRIPTION 502 "The delay time between successive registration 503 attempts by the mobile router(in seconds). 504 " 505 ::= { nemoRegistration 3 } 507 nemoHomeRegExtendBeforeExpiry OBJECT-TYPE 508 SYNTAX Gauge32 509 MAX-ACCESS read-write 510 STATUS current 511 DESCRIPTION 512 "The time before the registration extension is 513 attempted (in seconds) by the mobile router. 514 " 515 ::= { nemoRegistration 4 } 517 nemoDynamicHADiscovery OBJECT-TYPE 518 SYNTAX TruthValue 519 MAX-ACCESS read-write 520 STATUS current 521 DESCRIPTION 522 "This object indicates whether or not the mobile 523 router should attempt to make dynamic home agent 524 address discovery(DHAAD). 525 " 526 ::= { nemoRegistration 5 } 528 nemoHomeAddressIdentifierType OBJECT-TYPE 529 SYNTAX BITS { 530 eui64 (0), 531 random (1) 532 } 533 MAX-ACCESS read-write 534 STATUS current 535 DESCRIPTION 536 "The type of the nemoHomeAddressIdentifier 537 that follows. 538 " 539 ::= { nemoRegistration 6 } 541 nemoHomeAddressIdentifierInetType OBJECT-TYPE 542 SYNTAX InetAddressType 543 MAX-ACCESS read-write 544 STATUS current 545 DESCRIPTION 546 "The InetAddressType of the 547 nemoHomeAddressIdentifier that follows. 548 " 549 ::= { nemoRegistration 7 } 551 nemoHomeAddressIdentifier OBJECT-TYPE 552 SYNTAX InetAddress 553 MAX-ACCESS read-write 554 STATUS current 555 DESCRIPTION 556 "The unicast routable address assigned to the 557 mobile router. This is used as the permanent 558 address of the mobile router in the sense that it 559 remains unchanged regardless of the mobile 560 router's current point ofattachment. 561 The type of the address represented by this object 562 is specified by the corresponding 563 nemoHomeAddressType object. 564 " 565 ::= { nemoRegistration 8 } 567 nemoHomeIfIndex OBJECT-TYPE 568 SYNTAX InterfaceIndex 569 MAX-ACCESS read-write 570 STATUS current 571 DESCRIPTION 572 "The interface index of the mobile router where the 573 home address is configured. 574 " 575 ::= { nemoRegistration 9 } 577 nemoPrefixRegMode OBJECT-TYPE 578 SYNTAX BITS { 579 implicitMode (0), 580 explicitMode (1) 581 } 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION 585 "This object indicates if the mobile router will 586 explicitly register all the prefixes. 588 " 589 ::= { nemoRegistration 10 } 591 nemoRegisterConnectedPrefixes OBJECT-TYPE 592 SYNTAX TruthValue 593 MAX-ACCESS read-write 594 STATUS current 595 DESCRIPTION 596 "This object indicates if the mobile router will 597 register all the connected prefixes. 598 " 599 ::= { nemoRegistration 11 } 601 nemoHomeNetworkPrefixTable OBJECT-TYPE 602 SYNTAX SEQUENCE OF NemoHomeNetworkPrefixEntry 603 MAX-ACCESS not-accessible 604 STATUS current 605 DESCRIPTION 606 "A table representing the potential home networks 607 that the mobile router can use 608 " 609 ::= { nemoRegistration 12 } 611 nemoHomeNetworkPrefixEntry OBJECT-TYPE 612 SYNTAX NemoHomeNetworkPrefixEntry 613 MAX-ACCESS not-accessible 614 STATUS current 615 DESCRIPTION 616 "An entry in the binding cache table. It represents 617 a single home network entry 619 Implementors need to be aware that if the total 620 number of octets in nemoHomeNetworkPrefix 621 exceeds 113 then OIDs of column 622 instances in this row will have more than 128 623 sub-identifiers and cannot be accessed using 624 SNMPv1, SNMPv2c, or SNMPv3. 625 " 626 INDEX { nemoHomeNetworkPrefixType, nemoHomeNetworkPrefix, 627 nemoHomeNetworkPrefixLength } 628 ::= { nemoHomeNetworkPrefixTable 1 } 630 NemoHomeNetworkPrefixEntry ::= 631 SEQUENCE { 632 nemoHomeNetworkPrefixType InetAddressType, 633 nemoHomeNetworkPrefix InetAddress, 634 nemoHomeNetworkPrefixLength InetAddressPrefixLength, 635 nemoHomeNetworkPrefixLifeTime Gauge32 636 } 638 nemoHomeNetworkPrefixType OBJECT-TYPE 639 SYNTAX InetAddressType 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "The InetAddressType of the nemoHomeNetworkPrefix 644 that follows. 645 " 646 ::= { nemoHomeNetworkPrefixEntry 1 } 648 nemoHomeNetworkPrefix OBJECT-TYPE 649 SYNTAX InetAddress 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "The prefix of the home network which is configured 654 for the mobile router. 655 " 656 ::= { nemoHomeNetworkPrefixEntry 2 } 658 nemoHomeNetworkPrefixLength OBJECT-TYPE 659 SYNTAX InetAddressPrefixLength 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "The length of the home network prefix which 664 is configured for the mobile router. 665 " 666 ::= { nemoHomeNetworkPrefixEntry 3 } 668 nemoHomeNetworkPrefixLifeTime OBJECT-TYPE 669 SYNTAX Gauge32 (4..262143) 670 MAX-ACCESS read-write 671 STATUS current 672 DESCRIPTION 673 "The lifetime requested by the mobile router (in 674 seconds) in the Binding registration. It is 675 between 4 and 262143 secs. 677 " 678 ::= { nemoHomeNetworkPrefixEntry 4 } 680 -- 681 -- nemoPrefixTable 682 -- 684 nemoPrefixTable OBJECT-TYPE 685 SYNTAX SEQUENCE OF NemoPrefixEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "A table representing the NEMO prefixes. 690 " 691 ::= { nemoConfiguration 2 } 693 nemoPrefixEntry OBJECT-TYPE 694 SYNTAX NemoPrefixEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "An entry in the binding cache table. It represents 699 a single Binding Update. 701 Implementors need to be aware that if the total 702 number of octets in nemoPrefix 703 exceeds 114 then OIDs of column 704 instances in this row will have more than 128 705 sub-identifiers and cannot be accessed using 706 SNMPv1, SNMPv2c, or SNMPv3. 707 " 708 INDEX { nemoPrefixType, nemoPrefix, nemoPrefixLength } 709 ::= { nemoPrefixTable 1 } 711 NemoPrefixEntry ::= 712 SEQUENCE { 713 nemoPrefixType InetAddressType, 714 nemoPrefix InetAddress, 715 nemoPrefixLength InetAddressPrefixLength, 716 nemoPrefixLifeTime Gauge32 717 } 719 nemoPrefixType OBJECT-TYPE 720 SYNTAX InetAddressType 721 MAX-ACCESS not-accessible 722 STATUS current 723 DESCRIPTION 724 "The InetAddressType of the nemoPrefix 725 that follows. 726 " 727 ::= { nemoPrefixEntry 1 } 729 nemoPrefix OBJECT-TYPE 730 SYNTAX InetAddress 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "The mobile network prefix that is delegated to the 735 mobile router and advertised in the mobile 736 network. The type of the address represented by 737 this object is specified by the corresponding 738 nemoPrefixType object. 739 " 740 ::= { nemoPrefixEntry 2 } 742 nemoPrefixLength OBJECT-TYPE 743 SYNTAX InetAddressPrefixLength 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "The prefix length of the mobile network prefix. 748 " 749 ::= { nemoPrefixEntry 3 } 751 nemoPrefixLifeTime OBJECT-TYPE 752 SYNTAX Gauge32 753 UNITS "seconds" 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The lifetime (in seconds) granted to the mobile 758 router for this registration. 759 " 760 ::= { nemoPrefixEntry 4 } 762 -- 763 -- nemoRoamingIfTable 764 -- 766 nemoRoamingIfTable OBJECT-TYPE 767 SYNTAX SEQUENCE OF NemoRoamingIfEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "A table representing the roaming interfaces. 772 Each entry represents a configured roaming 773 interface with the roaming characterstics. 774 " 775 ::= { nemoConfiguration 3 } 777 nemoRoamingIfEntry OBJECT-TYPE 778 SYNTAX NemoRoamingIfEntry 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "An entry in the roaming interface table. It 783 represents a single roaming interface entry. 784 " 785 INDEX { nemoRoamingIfIndex, nemoRoamingIfPriority } 786 ::= { nemoRoamingIfTable 1 } 788 NemoRoamingIfEntry ::= 789 SEQUENCE { 790 nemoRoamingIfIndex InterfaceIndex, 791 nemoRoamingIfPriority Unsigned32, 792 nemoRoamingIfDescription SnmpAdminString, 793 nemoRoamingIfRoamHoldDownTime Gauge32 794 } 796 nemoRoamingIfIndex OBJECT-TYPE 797 SYNTAX InterfaceIndex 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "The index of the interface that will be used for 802 roaming to foreign networks in the mobile router. 803 " 804 ::= { nemoRoamingIfEntry 1 } 806 nemoRoamingIfPriority OBJECT-TYPE 807 SYNTAX Unsigned32 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "The priority configured to the interface. 812 This value will be configured between 0 and 255. 813 " 814 ::= { nemoRoamingIfEntry 2 } 816 nemoRoamingIfDescription OBJECT-TYPE 817 SYNTAX SnmpAdminString 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "The description of the interface that will be used 822 for roaming to foreign networks in the mobile 823 router. 824 " 825 ::= { nemoRoamingIfEntry 3 } 827 nemoRoamingIfRoamHoldDownTime OBJECT-TYPE 828 SYNTAX Gauge32 829 UNITS "seconds" 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "This object indicates the time for which hold on 834 to the interface. This value is configured to 835 avoid interface flapping. 836 " 837 ::= { nemoRoamingIfEntry 4 } 839 --- 840 --- 841 --- nemoStats group 842 --- 843 --- 845 -- 846 -- Dynamic Home Agent discovery protocol related counters 847 -- 849 nemoDHAADRequests OBJECT-TYPE 850 SYNTAX Counter32 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The total number of dynamic home agent address 855 discovery requests sent by the mobile router. 856 " 857 REFERENCE 858 "RFC3963 : Section 7.1." 859 ::= { nemoHomeAgentDiscovery 1 } 861 nemoDHAADRepliesWNemoSupport OBJECT-TYPE 862 SYNTAX Counter32 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The total number of dynamic home agent address 867 discovery replies sent by the home agent with NEMO 868 support. 869 " 870 REFERENCE 871 "RFC3963 : Section 7.2." 872 ::= { nemoHomeAgentDiscovery 2 } 874 nemoDHAADRepliesWONemoSupport OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The total number of dynamic home agent address 880 discovery replies sent by the home agent without 881 NEMO support. 882 " 883 REFERENCE 884 "RFC3963 : Section 7.2." 885 ::= { nemoHomeAgentDiscovery 3 } 887 nemoDHAADDiscoveryTimeouts OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "The total number of dynamic home agent address 893 discovery requested by the mobile router and that 894 was timeout. 895 " 897 ::= { nemoHomeAgentDiscovery 4 } 899 -- 900 -- nemoStats:nemoBindingRegcounters 901 -- 903 nemoBindingAcksWONemoSupport OBJECT-TYPE 904 SYNTAX Counter32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The total number of Binding Acks without the 909 NEMO support received by the mobile router. 911 Discontinuities in the value of this counter can 912 occur at re-initialization of the mobile router. 913 " 914 REFERENCE 915 "RFC3963 : Section 5.3." 916 ::= { nemoBindingRegCounters 1 } 918 nemoBindingAckNotHomeRegn OBJECT-TYPE 919 SYNTAX Counter32 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The total number of Binding Update requests 924 rejected by the home agent with the status code 925 in the Binding Acknowledgment indicating 926 'Not Home Registration' 928 Discontinuities in the value of this counter can 929 occur at re-initialization of the mobile router. 930 " 931 REFERENCE 932 "RFC3963 : Section 6.2." 933 ::= { nemoBindingRegCounters 2 } 935 nemoBindingRegTypeChanged OBJECT-TYPE 936 SYNTAX Counter32 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "The total number of Binding Update requests 941 rejected by the home agent with status code 942 in the Binding Acknowledgement indicating 943 'Registration type change disallowed' (Code 139). 945 Discontinuities in the value of this counter can 946 occur at re-initialization of the mobile router. 947 " 948 REFERENCE 949 "RFC3963 : Section 6.2" 950 ::= { nemoBindingRegCounters 3 } 952 nemoOpNotSupported OBJECT-TYPE 953 SYNTAX Counter32 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "The total number of Binding Update requests 958 rejected by the home agent with status code in the 959 Binding Acknowledgement indicating 960 'Mobile Router Operation not permitted' 961 (Code 140). 963 Discontinuities in the value of this counter can 964 occur at re-initialization of the mobile router. 965 " 966 REFERENCE 967 "RFC3963 : Section 6.6" 968 ::= { nemoBindingRegCounters 4 } 970 nemoInvalidPrefix OBJECT-TYPE 971 SYNTAX Counter32 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "The total number of Binding Update requests 976 rejected by the home agent with status code in the 977 Binding Acknowledgement indicating 'Invalid 978 Prefix' (Code 141). 980 Discontinuities in the value of this counter can 981 occur at re-initialization of the mobile router. 982 " 983 REFERENCE 984 "RFC3963 : Section 6.6." 985 ::= { nemoBindingRegCounters 5 } 987 nemoNotAuthorizedForPrefix OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The total number of Binding Update requests 993 rejected by the home agent with status code in the 994 Binding Acknowledgement indicating 'Not Authorized 995 for Prefix' (Code 142). 997 Discontinuities in the value of this counter can 998 occur at re-initialization of the mobile router. 999 " 1000 REFERENCE 1001 "RFC3963 : Section 6.6." 1002 ::= { nemoBindingRegCounters 6 } 1004 nemoForwardingSetupFailed OBJECT-TYPE 1005 SYNTAX Counter32 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The total number of Binding Update requests 1010 rejected by the home agent with status code in the 1011 Binding Acknowledgement indicating 'Forwarding 1012 Setup failed' (Code 143). 1014 Discontinuities in the value of this counter can 1015 occur at re-initialization of the mobile router. 1016 " 1017 REFERENCE 1018 "RFC3963 : Section 6.6." 1019 ::= { nemoBindingRegCounters 7 } 1021 -- 1022 -- nemoStats:nemoRoamingCounters 1023 -- 1025 nemoMovedHome OBJECT-TYPE 1026 SYNTAX Counter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "Number of times the mobile router has detected 1031 movement from a foreign network to its home 1032 network. 1033 Discontinuities in the value of this counter can 1034 occur at re-initialization of the mobile router. 1035 " 1036 ::= { nemoRoamingCounters 1 } 1038 nemoMovedOutofHome OBJECT-TYPE 1039 SYNTAX Counter32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "Number of times the mobile router has detected 1044 movement from to a foreign network from the home 1045 network, has reconstructed its care-of address and 1046 has initiated the care-of address registration 1047 process. 1048 Discontinuities in the value of this counter can 1049 occur at re-initialization of the mobile router. 1050 " 1052 ::= { nemoRoamingCounters 2 } 1054 nemoMovedFNtoFN OBJECT-TYPE 1055 SYNTAX Counter32 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "Number of times the mobile router has detected 1060 movement from to a foreign network from the home 1061 network, has reconstructed its care-of address and 1062 has initiated the care-of address registration 1063 process. 1064 Discontinuities in the value of this counter can 1065 occur at re-initialization of the mobile router. 1066 " 1067 ::= { nemoRoamingCounters 3 } 1069 nemoBetterIfDetected OBJECT-TYPE 1070 SYNTAX Counter32 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "Number of times the NEMO entity has found roaming 1075 interface with better priority. 1076 Discontinuities in the value of this counter can 1077 occur at re-initialization of the mobile router. 1078 " 1079 ::= { nemoRoamingCounters 4 } 1081 -- 1082 -- 1083 -- nemoNotifications 1084 -- 1085 -- 1087 nemoHomeTunnelEstablished NOTIFICATION-TYPE 1088 OBJECTS { 1089 nemoActiveRoamingIfIndex, 1090 nemoEstablishedHomeTunnelIfIndex, 1091 nemoRegCareofAddressType, 1092 nemoRegCareofAddress 1093 } 1094 STATUS current 1095 DESCRIPTION 1096 "This notification is sent by the mobile router 1097 every time the tunnel is established between the 1098 home agent and the mobile router. 1099 " 1100 REFERENCE 1101 "RFC3963 : Section 5.5" 1102 ::= { nemoNotifications 1 } 1104 nemoHomeTunnelReleased NOTIFICATION-TYPE 1105 OBJECTS { 1106 nemoActiveRoamingIfIndex, 1107 nemoEstablishedHomeTunnelIfIndex, 1108 nemoRegCareofAddressType, 1109 nemoRegCareofAddress 1110 } 1111 STATUS current 1112 DESCRIPTION 1113 "This notification is sent by the mobile router 1114 every time the tunnel is deleted between the home 1115 agent and the mobile router. 1116 " 1117 REFERENCE 1118 "RFC3963 : Section 5.5" 1119 ::= { nemoNotifications 2} 1121 -- Conformance information 1122 nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 } 1123 nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 } 1125 -- Units of conformance 1126 nemoSystemGroup OBJECT-GROUP 1127 OBJECTS { 1128 nemoRoamingStatus, 1129 nemoRegisteredUpTime, 1130 nemoLastAcceptedRegTime, 1131 nemoLastRejectedRegTime, 1132 nemoTimeSinceLastRoamed, 1133 nemoRegHomeAgentAddressType, 1134 nemoRegHomeAgentAddress, 1135 nemoRegHomeAddressType, 1136 nemoRegHomeAddress, 1137 nemoRegHomeAddressPrefixLength, 1138 nemoRegCareofAddressType, 1139 nemoRegCareofAddress, 1140 nemoRegCareofAddressPrefixLength, 1141 nemoActiveRoamingIfIndex, 1142 nemoEstablishedHomeTunnelIfIndex 1143 } 1144 STATUS current 1145 DESCRIPTION 1146 " A collection of objects for basic NEMO 1147 monitoring." 1148 ::= { nemoGroups 1 } 1150 nemoConfigurationGroup OBJECT-GROUP 1151 OBJECTS { 1152 nemoHomeRegLifeTime, 1153 nemoHomeRegRetryCount, 1154 nemoHomeRegRetryDelay, 1155 nemoHomeRegExtendBeforeExpiry, 1156 nemoDynamicHADiscovery, 1157 nemoHomeAddressIdentifierType, 1158 nemoHomeAddressIdentifierInetType, 1159 nemoHomeAddressIdentifier, 1160 nemoHomeIfIndex, 1161 nemoPrefixRegMode, 1162 nemoRegisterConnectedPrefixes, 1163 -- nemoHomeNetworkPrefixType, 1164 -- nemoHomeNetworkPrefix, 1165 -- nemoHomeNetworkPrefixLength, 1166 nemoHomeNetworkPrefixLifeTime, 1167 nemoPrefixLifeTime, 1168 -- nemoRoamingIfIndex, 1169 -- nemoRoamingIfPriority, 1170 nemoRoamingIfDescription, 1171 nemoRoamingIfRoamHoldDownTime, 1172 nemoDHAADRequests, 1173 nemoDHAADRepliesWNemoSupport, 1174 nemoDHAADRepliesWONemoSupport, 1175 nemoDHAADDiscoveryTimeouts 1176 } 1177 STATUS current 1178 DESCRIPTION 1179 " A collection of objects for basic NEMO 1180 configuration monitoring." 1181 ::= { nemoGroups 2 } 1183 nemoStatsGroup OBJECT-GROUP 1184 OBJECTS { 1185 nemoBindingUpdates, 1186 nemoBindingAcks, 1187 nemoBindingAcksWONemoSupport, 1188 nemoBindingAckNotHomeRegn, 1189 nemoBindingRegTypeChanged, 1190 nemoOpNotSupported, 1191 nemoInvalidPrefix, 1192 nemoNotAuthorizedForPrefix, 1193 nemoForwardingSetupFailed, 1194 nemoMovedHome, 1195 nemoMovedOutofHome, 1196 nemoMovedFNtoFN, 1197 nemoBetterIfDetected 1199 } 1200 STATUS current 1201 DESCRIPTION 1202 " A collection of objects for basic NEMO 1203 monitoring. 1204 " 1205 ::= { nemoGroups 3 } 1207 nemoNotificationGroup NOTIFICATION-GROUP 1208 NOTIFICATIONS { 1209 nemoHomeTunnelEstablished, 1210 nemoHomeTunnelReleased 1211 } 1212 STATUS current 1213 DESCRIPTION 1214 "A collection of notifications from a home agent 1215 or correspondent node to the Manager about the 1216 tunnel status of the mobile router. 1217 " 1218 ::= { nemoGroups 4 } 1220 -- Compliance statements 1221 nemoCoreCompliance MODULE-COMPLIANCE 1222 STATUS current 1223 DESCRIPTION 1224 "The compliance statement for SNMP entities 1225 which implement the MOBILEIPV6-MIB. 1226 There are a number of INDEX objects that cannot be 1227 represented in the form of OBJECT clauses in 1228 SMIv2, but for which there are compliance 1229 requirements, expressed in OBJECT clause form in 1230 this 1231 description: 1232 -- OBJECT nemoBindingHomeAddressType 1233 -- SYNTAX InetAddressType { ipv6(2) } 1234 -- DESCRIPTION 1235 -- This MIB module requires support for global 1236 -- ipv6 addresses for the nemoBindingHomeAddress 1237 -- object. 1238 -- 1239 " 1240 MODULE -- this module 1241 MANDATORY-GROUPS { nemoSystemGroup, 1242 nemoConfigurationGroup, 1243 nemoStatsGroup, 1244 nemoNotificationGroup 1245 } 1247 ::= { nemoCompliances 1 } 1249 END 1251 5. IANA Considerations 1253 IANA should assign a base arc in the mib-2 (standards track) OID tree 1254 for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB. 1256 6. Security Considerations 1258 There are a number of management objects defined in this MIB module 1259 with a MAX-ACCESS clause of read-write. Such objects may be 1260 considered sensitive or vulnerable in some network environments. The 1261 support for SET operations in a non-secure environment without proper 1262 protection can have a negative effect on network operations. These 1263 are the tables and objects and their sensitivity/vulnerability: 1265 Some of the readable objects in this MIB module (i.e., objects with a 1266 MAX-ACCESS other than not-accessible) may be considered sensitive or 1267 vulnerable in some network environments. It is thus important to 1268 control even GET and/or NOTIFY access to these objects and possibly 1269 to even encrypt the values of these objects when sending them over 1270 the network via SNMP. These are the tables and objects and their 1271 sensitivity/vulnerability: 1273 SNMP versions prior to SNMPv3 did not include adequate security. 1274 Even if the network itself is secure (for example by using IPSec), 1275 even then, there is no control as to who on the secure network is 1276 allowed to access and GET/SET (read/change/create/delete) the objects 1277 in this MIB module. 1279 It is RECOMMENDED that implementers consider the security features as 1280 provided by the SNMPv3 framework (see [RFC3410], section 8), 1281 including full support for the SNMPv3 cryptographic mechanisms (for 1282 authentication and privacy). 1284 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1285 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1286 enable cryptographic security. It is then a customer/operator 1287 responsibility to ensure that the SNMP entity giving access to an 1288 instance of this MIB module is properly configured to give access to 1289 the objects only to those principals (users) that have legitimate 1290 rights to indeed GET or SET (change/create/delete) them. 1292 7. Acknowledgments 1294 The authors would like to thank T.J Kniveton and Thierry Ernst for 1295 their inputs to the document and also would like to thank Kent Leung 1296 and Pascal Thubert for their inputs on Mobile Router implementations. 1298 8. References 1300 8.1. Normative References 1302 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 1303 Requirements Levels, BCP 14, RFC 2119, March 1997. 1305 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1306 Rose, M. and S. Waldbusser, Structure of Management Information 1307 Version 2 (SMIv2), STD 58, RFC 2578, April 1999. 1309 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1310 Rose, M. and S. Waldbusser, Textual Conventions for SMIv2, STD 58, 1311 RFC 2579, April 1999. 1313 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1314 Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58, 1315 RFC 2580, April 1999. 1317 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in 1318 IPv6q RFC 3775, June 2004. 1320 [RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, 1321 Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005. 1323 [RFC4001] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder, 1324 J., Textual Conventions for Internet Network Addresses, RFC 4001, 1325 February 2005. 1327 [RFC2011bis] Routhier, S., Management Information Base for the 1328 Internet Protocol (IP), work in progress (currently 1329 draft-ietf-ipv6-rfc2011-update-10.txt). 1331 [RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The 1332 Mobile IPv6 MIB, RFC 4295, April 2006. 1334 8.2. Informative References 1336 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1337 Introduction and Applicability Statements for Internet-Standard 1338 Management Framework, RFC 3410, December 2002. 1340 [NEMOTERM] T. Ernst and H.-Y. Lach., Network Mobility Support 1341 Terminology, work in progress (currently 1342 draft-ietf-nemo-terminology-01.txt). 1344 [NEMOGOAL] T. Ernst. Network Mobility Support Goals and 1345 Requirements, work in progress (currently 1346 draft-ietf-nemo-requirements-02.txt). 1348 Authors' Addresses 1350 Sri Gundavelli 1351 Cisco Systems 1352 170 West Tasman Drive 1353 San Jose, CA 95134 1354 USA 1356 Phone: +1-408-527-6109 1357 Email: sgundave@cisco.com 1359 Glenn Mansfield Keeni 1360 Cyber Solutions 1361 6-6-3 Minami Yoshinari 1362 Aoba-ku, Sendai 989-3204, 1363 Japan 1365 Phone: +81-22-303-4012 1366 Email: glenn@cysols.com 1368 Kazuhide Koide 1369 Tohoku University 1370 Katahira Campus 1371 Sendai, 1372 Japan 1374 Phone: +81-22-217-5454 1375 Email: koide@shiratori.riec.tohoku.ac.jp 1377 Kenichi Nagami 1378 INTEC NetCore 1379 1-3-3, Shin-suna 1380 Koto-ku, Tokyo, 135-0075, 1381 Japan 1383 Phone: +81-3-5665-5069 1384 Email: nagami@inetcore.com 1386 Intellectual Property Statement 1388 The IETF takes no position regarding the validity or scope of any 1389 Intellectual Property Rights or other rights that might be claimed to 1390 pertain to the implementation or use of the technology described in 1391 this document or the extent to which any license under such rights 1392 might or might not be available; nor does it represent that it has 1393 made any independent effort to identify any such rights. Information 1394 on the procedures with respect to rights in RFC documents can be 1395 found in BCP 78 and BCP 79. 1397 Copies of IPR disclosures made to the IETF Secretariat and any 1398 assurances of licenses to be made available, or the result of an 1399 attempt made to obtain a general license or permission for the use of 1400 such proprietary rights by implementers or users of this 1401 specification can be obtained from the IETF on-line IPR repository at 1402 http://www.ietf.org/ipr. 1404 The IETF invites any interested party to bring to its attention any 1405 copyrights, patents or patent applications, or other proprietary 1406 rights that may cover technology that may be required to implement 1407 this standard. Please address the information to the IETF at 1408 ietf-ipr@ietf.org. 1410 Disclaimer of Validity 1412 This document and the information contained herein are provided on an 1413 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1414 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1415 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1416 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1417 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1418 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1420 Copyright Statement 1422 Copyright (C) The Internet Society (2006). This document is subject 1423 to the rights, licenses and restrictions contained in BCP 78, and 1424 except as set forth therein, the authors retain all their rights. 1426 Acknowledgment 1428 Funding for the RFC Editor function is currently provided by the 1429 Internet Society.