idnits 2.17.1 draft-glenn-netlmm-pmipv6-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 18 instances of too long lines in the document, the longest one being 7 characters in excess of 72. == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 12, 2009) is 5401 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) == Missing Reference: 'PMIPv6' is mentioned on line 98, but not defined == Missing Reference: 'RFC4831' is mentioned on line 130, but not defined == Missing Reference: 'RFC4295' is mentioned on line 154, but not defined == Missing Reference: 'RFC2863' is mentioned on line 154, but not defined == Missing Reference: 'RFC-4282' is mentioned on line 309, but not defined ** Obsolete undefined reference: RFC 4282 (Obsoleted by RFC 7542) == Missing Reference: 'RFC-4283' is mentioned on line 1017, but not defined == Unused Reference: 'RFC4293' is defined on line 2457, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) Summary: 4 errors (**), 0 flaws (~~), 9 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETLMM Working Group Glenn M. Keeni 3 INTERNET-DRAFT Cyber Solutions Inc. 4 Intended Status: Proposed Standard Koide Kazuhide 5 Expires: January 11, 2010 KDDI Corporation 6 S. Gundavelli 7 Cisco 8 R. Wakikawa 9 Keio University 10 July 12, 2009 12 Proxy Mobile IPv6 Management Information Base 13 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This document is a product of the NETLMM Working Group. Comments 37 should be addressed to the authors or the mailing list at 38 netlmm@ietf.org 40 This Internet-Draft will expire on January 11, 2010. 42 Copyright Notice 44 Copyright (c) 2009 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents in effect on the date of 49 publication of this document (http://trustee.ietf.org/license-info). 50 Please review these documents carefully, as they describe your rights 51 and restrictions with respect to this document. 53 Abstract 55 This memo defines a portion of the Management Information Base (MIB), 56 the Proxy Mobile-IPv6 MIB, for use with network management protocols 57 in the Internet community. In particular, the Proxy Mobile-IPv6 MIB 58 will be used to monitor and control the mobile access gateway (MAG) 59 node and the local mobility anchor (LMA) functions of a Proxy Mobile 60 IPv6 (PMIPv6) entity. 62 Table of Contents 64 1. The Internet-Standard Management Framework ................... 3 65 2. Overview ..................................................... 3 66 2.1. The Proxy Mobile IPv6 Protocol Entities ................. 3 67 2.2. Terminology ............................................. 4 68 3. Proxy Mobile IPv6 Monitoring and Control Requirements ........ 4 69 4. MIB Design ................................................... 4 70 5. The Proxy Mobile-IPv6 MIB .................................... 6 71 6. Security Considerations ...................................... 57 72 7. IANA Considerations .......................................... 58 73 8. References ................................................... 59 74 8.1. Normative References .................................... 59 75 8.2. Informative References .................................. 59 76 9. Acknowledgments .............................................. 60 77 10. Author's Addresses ........................................... 60 79 1. The Internet-Standard Management Framework 81 For a detailed overview of the documents that describe the current 82 Internet-Standard Management Framework, please refer to section 7 of 83 RFC 3410 [RFC3410]. 85 Managed objects are accessed via a virtual information store, termed 86 the Management Information Base or MIB. MIB objects are generally 87 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 2. Overview 97 2.1. The Proxy Mobile IPv6 Protocol and entities 98 Proxy Mobile IPv6 (PMIPv6) [PMIPv6] is an extension to the Mobile 99 IPv6 (MIPv6) protocol which facilitates network-based localized 100 mobility management (NETLMM) for IPv6 nodes in a PMIPv6 domain. 101 There are three types of entities envisaged by the PMIPv6 protocol. 103 mobile node (MN): In the PMIPv6 context the term mobile node 104 is used to refer to an IP host or router whose mobility is 105 managed by the network. 107 local mobility anchor (LMA): Local Mobility Anchor is the 108 home agent for the mobile node in a Proxy Mobile IPv6 domain. 109 It is the topological anchor point for the mobile node's home 110 network prefix(es) and is the entity that manages the mobile 111 node's binding state. The local mobility anchor has the 112 functional capabilities of a home agent as defined in Mobile 113 IPv6 base specification [RFC3775] with the additional 114 capabilities required for supporting Proxy Mobile IPv6 115 protocol as defined in the PMIPv6 specification [RFC5213]. 117 mobile access gateway (MAG): Mobile Access Gateway is the 118 entity on an access router that manages the mobility-related 119 signaling for a mobile node that is attached to its access 120 link. It is responsible for tracking the mobile node's 121 movements to and from the access link and for signaling the 122 mobile node's local mobility anchor. 124 This document defines a set of managed objects (MOs) that can be used 125 to monitor and control PMIPv6 entities. 127 2.2. Terminology 128 The terminology used in this document is consistent with the 129 definitions used in the Mobile IPv6 protocol specification[RFC3775] 130 and in NETLMM Goals document [RFC4831]. 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 134 "OPTIONAL" in this document are to be interpreted as described in BCP 135 14, RFC 2119 [RFC2119]. 137 3. Proxy Mobile IPv6 Monitoring and Control Requirements 139 For managing a PMIPv6 entity it is necessary to monitor 140 the following: 141 o capabilities of PMIPv6 entities 142 o traffic due to PMIPv6 signalling 143 o binding related details (at LMA and MAG) 144 o binding related statistics (at LMA and MAG) 146 4. MIB Design. 148 The basic principle has been to keep the MIB as simple as possible 149 and at the same time to make it effective enough so that the 150 essential needs of monitoring and control are met. 152 It is assumed that the Proxy Mobile IPv6 Management Information Base 153 (PMIPV6-MIB) will always be implemented in conjunction with the 154 MOBILEIPV6-MIB [RFC4295] and the ifTable from the IF-MIB [RFC2863]. 155 The PMIP6-MIB uses the textual conventions defined in the INET- 156 ADDRESS-MIB [RFC4001]. 158 The PMIPV6-MIB is composed of the following groups of definitions: 160 - pmip6Core: a generic group containing objects that are 161 common to all the Proxy Mobile IPv6 entities. 162 - pmip6Mag: this group models the mobile access gateway 163 service. 164 - pmip6Lma: this group models the local mobility anchor 165 service. 166 - pmip6Notifications: defines the set of notifications that 167 will be used to asynchronously monitor the Proxy Mobile 168 IPv6 entities. 170 The tables contained in the above groups are as follows: 171 - pmip6BindingCacheTable : models the Binding Cache 172 on the local mobility 173 anchor. 174 - pmip6MagProxyCOATable : models the Proxy Care-of 175 Addresses configured on the 176 egress interfaces of the 177 mobile access gateway. 178 - pmip6MagHomeNetworkPrefixTable : contains the Home Network 179 Prefixes assigned to the 180 mobile node's connected 181 interfaces. 182 - pmip6MagBLTable : models the Binding Update List 183 (BL) that includes Proxy MIPv6 184 related information and is 185 maintained by the mobile 186 access gateway. 187 - pmip6MagMnProfileTable : contains the mobile node's 188 policy profile that includes 189 the essential operational 190 parameters that are required 191 by the network entities for 192 managing the mobile node's 193 mobility service. 194 - pmip6LmaLMAATable : contains the LMA Addresses 195 that are configured on the 196 local mobility anchor. Each 197 LMA Address acts as a 198 transport endpoint of the 199 tunnel between the local 200 mobility anchor and the mobile 201 access gateway. 202 - pmip6LmaHomeNetworkPrefixTable : contains the list of Home 203 Network Prefixes assigned to 204 the mobile node's connected 205 interfaces. 207 5. The Proxy Mobile-IPv6 MIB. 209 PMIPV6-MIB DEFINITIONS ::= BEGIN 210 IMPORTS 211 MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32, 212 OBJECT-TYPE, NOTIFICATION-TYPE 213 FROM SNMPv2-SMI 214 PhysAddress 215 FROM RFC1213-MIB 216 TEXTUAL-CONVENTION, TimeStamp, 217 TruthValue, DateAndTime 218 FROM SNMPv2-TC 219 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 220 FROM SNMPv2-CONF 221 InetAddressType, InetAddress, InetAddressPrefixLength 222 FROM INET-ADDRESS-MIB 223 Ipv6AddressIfIdentifierTC 224 FROM IP-MIB 225 mip6MnBLEntry, mip6BindingCacheEntry 226 FROM MOBILEIPV6-MIB 227 ; 229 pmip6MIB MODULE-IDENTITY 230 LAST-UPDATED "200907070000Z" -- 7th July, 2009 231 ORGANIZATION "IETF NETLMM Working Group" 232 CONTACT-INFO 233 " Glenn Mansfield Keeni 234 Postal: Cyber Solutions Inc. 235 6-6-3, Minami Yoshinari 236 Aoba-ku, Sendai, Japan 989-3204. 237 Tel: +81-22-303-4012 238 Fax: +81-22-303-4015 239 E-mail: glenn@cysols.com 241 Kazuhide Koide 242 Postal: KDDI Corporation 243 GARDEN AIR TOWER 3-10-10, Iidabashi 244 Chiyoda-ku, Tokyo, 102-8460 Japan 245 Tel: +81-3-6678-3378 246 E-mail: ka-koide@kddi.com 248 Sri Gundavelli 250 Postal: Cisco 251 170 W.Tasman Drive, 252 San Jose, CA 95134 253 USA 254 Tel: +1-408-527-6109 255 E-mail: sgundave@cisco.com 257 Ryuji Wakikawa 258 Postal: Keio University 259 Department of Environmental 260 Information, 261 Keio University. 262 5322 Endo 263 Fujisawa, Kanagawa 252-8520 264 Japan 265 E-mail: ryuji@sfc.wide.ad.jp 267 Support Group E-mail: netlmm@ietf.org" 269 DESCRIPTION 270 "The MIB module for monitoring and controlling PMIPv6 entities. 271 " 272 -- Authors' note: 273 -- It is not clear if the Copyright notice should be a part of 274 -- above description. It was a requirement sometime ago but the 275 -- submission tool at ietf.org complained so it is removed 276 -- for now. 278 -- RFC Ed.: replace XXXX with actual RFC number and remove this 279 -- note 281 REVISION "200907070000Z" -- 7th July 2009 282 DESCRIPTION "Initial version, published as RFC XXXX." 284 -- RFC Ed.: replace XXXX with actual RFC number and remove this 285 -- note 287 ::= { mib-2 YYY } -- will be assigned by IANA 289 -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' 290 -- subtree and record the assignment in the SMI Numbers 291 -- registry. 292 -- 293 -- RFC Ed.: When the above assignment has been made, please 294 -- remove the above note 295 -- replace "YYY" here with the assigned value and 296 -- remove this note. 298 -- ------------------------------------------------------------- 299 -- Textual Conventions 300 -- ------------------------------------------------------------- 301 Pmip6MNIdentifier ::= TEXTUAL-CONVENTION 302 STATUS current 303 DESCRIPTION 304 "The identity of a mobile node in the Proxy Mobile IPv6 305 domain. This is the stable identifier of a mobile node 306 that the mobility entities in a Proxy Mobile IPv6 domain 307 can always acquire and use it for predictably identifying 308 a mobile node. This is typically an identifier such as 309 Network Access Identifier (NAI) [RFC-4282] or other 310 identifier such as a Media Access Control (MAC) address. 311 " 312 REFERENCE 313 "RFC 5213: Section 2.2" 314 SYNTAX OCTET STRING (SIZE (0..255)) 316 Pmip6MNLlIdentifier ::= TEXTUAL-CONVENTION 317 STATUS current 318 DESCRIPTION 319 "An identifier that identifies the attached interface of a 320 mobile node. For those interfaces that have a link-layer 321 identifier, this identifier can be based on that. The 322 link-layer identifier in some cases is generated by the 323 mobile node and conveyed to the mobile access gateway. This 324 identifier of the attached interface must be stable as seen 325 by any of the mobile access gateways in a given Proxy Mobile 326 IPv6 domain. In some other cases, there might not be any 327 link-layer identifier associated with the mobile node's 328 interface. An identifier value of ALL_ZERO is not considered 329 a valid identifier and cannot be used as an interface 330 identifier. 331 " 332 REFERENCE 333 "RFC 5213: Section 2.2" 334 SYNTAX OCTET STRING (SIZE (0..255)) 336 Pmip6MNIndex ::= TEXTUAL-CONVENTION 337 DISPLAY-HINT "d" 338 STATUS current 339 DESCRIPTION 340 "A unique integer value, greater than zero, assigned to each 341 mobile node in a PMIPv6-Domain by the management system. 342 It is recommended that values are assigned contiguously 343 starting from 1. The value for each mobile node must remain 344 constant at least from one re-initialization of the entity's 345 network management system to the next re-initialization. 347 " 348 SYNTAX Integer32 (1..2147483647) 350 Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION 351 STATUS current 352 DESCRIPTION 353 "This specifies the access technology which connects the 354 mobile node to the access link on the mobile access gateway. 355 " 356 REFERENCE 357 "RFC 5213: Section 8.5" 358 SYNTAX INTEGER 359 { 360 reserved (0), 361 logicalNetworkInterface(1), 362 pointToPointInterface (2), 363 ethernet (3), 364 wirelessLan (4), 365 wimax (5) 366 } 368 -- The PMIPv6 MIB has the following 5 primary groups 370 pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 } 371 pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 } 372 pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 } 373 pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 } 374 pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 } 375 pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 } 377 -- The sub groups 379 pmip6System OBJECT IDENTIFIER ::= { pmip6Core 1 } 380 pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 } 381 pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 } 382 pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 } 384 pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 } 385 pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 } 386 pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 } 388 pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 } 389 pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 } 390 -- The pmip6Configuration group has the following sub groups 392 -- The pmip6Stats group has the following sub groups 394 pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 } 396 -- 397 -- 398 -- pmip6System group 399 -- 400 -- 401 pmip6Capabilities OBJECT-TYPE 402 SYNTAX BITS { 403 mobilityAccessGateway (0), 404 localMobilityAnchor (1) 405 } 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "This object indicates the PMIPv6 functions that 410 are supported by this managed entity. Multiple 411 Proxy Mobile IPv6 functions may be supported by 412 a single entity. 413 " 414 REFERENCE 415 "RFC 3775 : Section 3.2, 4.1" 416 ::= { pmip6System 1 } 418 pmip6Status OBJECT-TYPE 419 SYNTAX INTEGER { enabled(1), disabled(2) } 420 MAX-ACCESS read-write 421 STATUS current 422 DESCRIPTION 423 "This object indicates whether the Proxy Mobile 424 IPv6 function is enabled for the managed entity. 426 The value of this object SHOULD remain unchanged 427 across reboots of the managed entity. 428 " 429 ::= { pmip6System 2 } 431 pmip6MobileNodeGeneratedTimestampInUse OBJECT-TYPE 432 SYNTAX TruthValue 433 MAX-ACCESS read-write 434 STATUS current 435 DESCRIPTION 436 "This flag indicates whether or not the mobile node 437 generated timestamp mechanism is in use in that 438 Proxy Mobile IPv6 domain. 439 true(1) if the local mobility anchors and mobile 440 access gateways in that Proxy Mobile IPv6 domain 441 apply the mobile node generated timestamp 442 considerations. 443 false(0) indicates that the mobile node generated 444 timestamp mechanism is not in use in that Proxy 445 Mobile IPv6 domain. 446 The default value for this flag is set to value of 0. 447 " 448 REFERENCE 449 "RFC 5213: Section 5.5, 9.3" 450 ::= { pmip6Conf 1 } 452 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType OBJECT-TYPE 453 SYNTAX InetAddressType 454 MAX-ACCESS read-write 455 STATUS current 456 DESCRIPTION 457 "The InetAddressType of the 458 pmip6FixedMagLinkLocalAddressOnAllAccessLinks 459 that follows. 460 " 461 ::= { pmip6Conf 2 } 462 pmip6FixedMagLinkLocalAddressOnAllAccessLinks OBJECT-TYPE 463 SYNTAX InetAddress 464 MAX-ACCESS read-write 465 STATUS current 466 DESCRIPTION 467 "This variable indicates the link-local address value 468 that all the mobile access gateways should use on 469 any of the access links shared with any of the 470 mobile nodes in that Proxy Mobile IPv6 domain. If 471 this variable is initialized to ALL_ZERO value, it 472 implies the use of fixed link-local address mode is 473 not enabled for that Proxy Mobile IPv6 domain." 474 REFERENCE 475 "RFC 5213: Section 2.2, 6.8, 6.9.1.1, 6.9.3, 9.3" 476 ::= { pmip6Conf 3 } 478 pmip6FixedMagLinkLayerAddressOnAllAccessLinks OBJECT-TYPE 479 SYNTAX PhysAddress 480 MAX-ACCESS read-write 481 STATUS current 482 DESCRIPTION 483 "This variable indicates the link-layer address value 484 that all the mobile access gateways should use on 485 any of the access links shared with any of the mobile 486 nodes in that Proxy Mobile IPv6 domain. For access 487 technologies where there is no link-layer address, 488 this variable MUST be initialized to ALL_ZERO value. 489 " 490 REFERENCE 491 "RFC 5213: Section 6.9.3, 9.3" 492 ::= { pmip6Conf 4 } 494 pmip6MagProxyCOATable OBJECT-TYPE 495 SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry 496 MAX-ACCESS not-accessible 497 STATUS current 498 DESCRIPTION 499 "This table models the Proxy Care-of Addresses configured 500 on the egress interfaces of the mobile access gateway 501 and is the transport endpoint of the tunnel between the 502 local mobility anchor and the mobile access gateway. 504 Entries in this table are not required to survive 505 a reboot of the managed entity. 506 " 507 REFERENCE 508 "RFC 5213: Section 2.2, 6.10" 509 ::= { pmip6MagSystem 1 } 511 pmip6MagProxyCOAEntry OBJECT-TYPE 512 SYNTAX Pmip6MagProxyCOAEntry 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "This entry represents a conceptual row in the 517 Proxy-CoA table. It represents each Proxy-CoA 518 on the mobile access gateway. 520 Implementers need to be aware that if the total 521 number of octets in mip6BindingHomeAddress 522 exceeds 113 then OIDs of column 523 instances in this row will have more than 128 524 sub-identifiers and cannot be accessed using 525 SNMPv1, SNMPv2c, or SNMPv3. 526 " 527 INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA } 528 ::= { pmip6MagProxyCOATable 1 } 530 Pmip6MagProxyCOAEntry ::= 531 SEQUENCE { 532 pmip6MagProxyCOAType InetAddressType, 533 pmip6MagProxyCOA InetAddress, 534 pmip6MagProxyCOAState INTEGER 535 } 537 pmip6MagProxyCOAType OBJECT-TYPE 538 SYNTAX InetAddressType 539 MAX-ACCESS not-accessible 540 STATUS current 541 DESCRIPTION 542 "The InetAddressType of the pmip6MagProxyCOA 543 that follows. 544 " 545 ::= { pmip6MagProxyCOAEntry 1 } 547 pmip6MagProxyCOA OBJECT-TYPE 548 SYNTAX InetAddress 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "The Proxy-CoA configured on the egress interface of the 553 mobile access gateway. 555 The type of the address represented by this object 556 is specified by the corresponding 557 pmip6MagProxyCOAType object. 558 " 559 REFERENCE 560 "RFC 5213: Section 2.2, 6.10" 561 ::= { pmip6MagProxyCOAEntry 2 } 563 pmip6MagProxyCOAState OBJECT-TYPE 564 SYNTAX INTEGER { 565 unknown(1), 566 activated(2), 567 tunneled(3) 568 } 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "This object indicates the state of the Proxy-CoA: 573 unknown -- The state of the Proxy-CoA 574 cannot be determined. 576 activated -- The Proxy-CoA is ready to establish 577 tunnel 578 tunneled -- The Proxy-CoA is used to set up the 579 bi-directional tunnel. 580 " 581 ::= { pmip6MagProxyCOAEntry 3 } 583 pmip6MagEnableMagLocalRouting OBJECT-TYPE 584 SYNTAX TruthValue 585 MAX-ACCESS read-write 586 STATUS current 587 DESCRIPTION 588 "This flag indicates whether or not the mobile access 589 gateway is allowed to enable local routing of the 590 traffic exchanged between a visiting mobile node and 591 a correspondent node that is locally connected to one 592 of the interfaces of the mobile access gateway. 593 The correspondent node can be another visiting mobile 594 node as well, or a local fixed node. 595 true(1) indicates the mobile access gateway routes the 596 traffic locally. 597 false(0) indicates that the mobile access gateway 598 reverse tunnels all the traffic to the mobile node's 599 local mobility anchor. 601 The default value for this flag is set to false." 602 REFERENCE 603 "RFC 5213: Section 9.2" 604 ::= { pmip6MagConf 1 } 606 pmip6MagHomeNetworkPrefixTable OBJECT-TYPE 607 SYNTAX SEQUENCE OF PMip6MagHomeNetworkPrefixEntry 608 MAX-ACCESS not-accessible 609 STATUS current 610 DESCRIPTION 611 "A table representing the Home Network Prefixes 612 assigned to the mobile node's connected interfaces. 613 This table shows the prefixes registered in the 614 binding update list entry. 615 " 616 REFERENCE 617 "RFC 5213: Section 2, 6.1, 6.2" 618 ::= { pmip6MagConf 2 } 620 pmip6MagHomeNetworkPrefixEntry OBJECT-TYPE 621 SYNTAX PMip6MagHomeNetworkPrefixEntry 622 MAX-ACCESS not-accessible 623 STATUS current 624 DESCRIPTION 625 "An entry in the Home Network Prefixes table. 627 Implementers need to be aware that if the total 628 number of octets in pmip6MagHomeNetworkPrefix 629 exceeds 114 then OIDs of column 630 instances in this row will have more than 128 631 sub-identifiers and cannot be accessed using 632 SNMPv1, SNMPv2c, or SNMPv3. 633 " 634 INDEX { pmip6MagBLMnIdentifier, pmip6MagBLlMnIdentifier, 635 pmip6MagHomeNetworkPrefixType, 636 pmip6MagHomeNetworkPrefix } 637 ::= { pmip6MagHomeNetworkPrefixTable 1 } 639 PMip6MagHomeNetworkPrefixEntry ::= 640 SEQUENCE { 641 pmip6MagHomeNetworkPrefixType InetAddressType, 642 pmip6MagHomeNetworkPrefix InetAddress, 643 pmip6MagHomeNetworkPrefixLength InetAddressPrefixLength, 644 pmip6MagHomeNetworkPrefixLifeTime Gauge32 645 } 647 pmip6MagHomeNetworkPrefixType OBJECT-TYPE 648 SYNTAX InetAddressType 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "The InetAddressType of the pmip6MagHomeNetworkPrefix 653 that follows. 654 " 655 ::= { pmip6MagHomeNetworkPrefixEntry 1 } 657 pmip6MagHomeNetworkPrefix OBJECT-TYPE 658 SYNTAX InetAddress 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "The mobile network prefix that is delegated to the 663 mobile node. The type of the address represented by 664 this object is specified by the corresponding 665 pmip6MagHomeNetworkPrefixType object. 666 " 667 REFERENCE 668 "RFC 5213: Section 2" 670 ::= { pmip6MagHomeNetworkPrefixEntry 2 } 672 pmip6MagHomeNetworkPrefixLength OBJECT-TYPE 673 SYNTAX InetAddressPrefixLength 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "The prefix length of the Home Network Prefix. 678 " 679 ::= { pmip6MagHomeNetworkPrefixEntry 3 } 681 pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE 682 SYNTAX Gauge32 683 UNITS "seconds" 684 MAX-ACCESS read-write 685 STATUS current 686 DESCRIPTION 687 "The lifetime (in seconds) granted to the mobile 688 node for this registration. 689 " 690 REFERENCE 691 "RFC 5213: Section 6.2, 6.7" 692 ::= { pmip6MagHomeNetworkPrefixEntry 4 } 694 pmip6MagBLTable OBJECT-TYPE 695 SYNTAX SEQUENCE OF Pmip6MagBLEntry 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "This table corresponds to the Binding Update List(BL) 700 that includes Proxy MIPv6 related information and 701 is maintained by the mobile access gateway. 703 Entries from the table are deleted as 704 the lifetime of the binding expires. 705 " 706 REFERENCE 707 "RFC 3775: Section 4.5, 11.1, 708 RFC 5213: Section 6.1" 709 ::= { pmip6MagRegistration 1 } 711 pmip6MagBLEntry OBJECT-TYPE 712 SYNTAX Pmip6MagBLEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "An entry containing additional information contained 717 in a Binding Update sent by the mobile access gateway 718 to the local mobility anchor. 719 " 720 AUGMENTS {mip6MnBLEntry} 721 ::= { pmip6MagBLTable 1 } 723 Pmip6MagBLEntry ::= SEQUENCE { 724 pmip6MagBLFlag TruthValue, 725 pmip6MagBLMnIdentifier Pmip6MNIdentifier, 726 pmip6MagBLlMnIdentifier Pmip6MNLlIdentifier, 727 pmip6MagBLMagLinkLocalAddressType InetAddressType, 728 pmip6MagBLMagLinkLocalAddress InetAddress, 729 pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC, 730 pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC, 731 pmip6MagBLAccessTechnologyType Pmip6PBUAccessTechnologyType, 732 pmip6MagBLTimeRecentlyAccepted DateAndTime 733 } 735 pmip6MagBLFlag OBJECT-TYPE 736 SYNTAX TruthValue 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "true(1) if the mobile access gateway sent the proxy 741 binding update with Proxy Registration Flag that 742 indicates to the local mobility anchor that the 743 registration is the proxy binding update and is from 744 a mobile access gateway. 745 false(0) implies that the mobile access gateway is 746 behaving as a simple mobile node. 747 " 748 REFERENCE 749 "RFC 5213: Section 8.1" 750 ::= { pmip6MagBLEntry 1 } 752 pmip6MagBLMnIdentifier OBJECT-TYPE 753 SYNTAX Pmip6MNIdentifier 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The Identifier of the attached mobile node. This 758 identifier is acquired during the mobile node's 759 attachment to the access link. 760 " 761 REFERENCE 762 "RFC 5213: Section 2.2, 6.1, 8.1" 763 ::= { pmip6MagBLEntry 2 } 765 pmip6MagBLlMnIdentifier OBJECT-TYPE 766 SYNTAX Pmip6MNLlIdentifier 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "The link-layer identifier of the mobile node's 771 connected interface. This can be acquired from the 772 received Router Solicitation messages from the mobile 773 node or during the mobile node's attachment to the 774 access network. If this identifier is not available, 775 this variable length field MUST be set to two (octets) 776 and MUST be initialized to a value of ALL_ZERO. 777 " 778 REFERENCE 779 "RFC 5213: Section 2.2, 6.1, 8.1" 780 ::= { pmip6MagBLEntry 3 } 782 pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE 783 SYNTAX InetAddressType 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The InetAddressType of the pmip6MagBLMagLinkLocalAddress 788 that follows. 789 " 790 ::= { pmip6MagBLEntry 4 } 792 pmip6MagBLMagLinkLocalAddress OBJECT-TYPE 793 SYNTAX InetAddress 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "The Link-local address of the mobile access gateway on 798 the access link shared with the mobile node. 799 This is the address that is present in the Link-local 800 Address option of the corresponding Proxy Binding Update 801 message. 802 " 803 REFERENCE 804 "RFC 3963 : Section 4.1, 5.1" 805 ::= { pmip6MagBLEntry 5 } 807 pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE 808 SYNTAX Ipv6AddressIfIdentifierTC 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "The interface identifier (if-id) of the point-to-point 813 link between the mobile node and the mobile access 814 gateway. This is internal to the mobile access gateway 815 and is used to associate the Proxy Mobile IPv6 tunnel 816 to the access link where the mobile node is attached. 817 " 818 REFERENCE 819 "RFC 5213: Section 6.1, 8.1" 820 ::= { pmip6MagBLEntry 6 } 822 pmip6MagBLTunnelIfIdentifier OBJECT-TYPE 823 SYNTAX Ipv6AddressIfIdentifierTC 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The tunnel interface identifier (tunnel-if-id) of the 828 bi-directional tunnel between the mobile node's local 829 mobility anchor and the mobile access gateway. This 830 is internal to the mobile access gateway. The tunnel 831 interface identifier is acquired during the tunnel 832 creation. 833 " 834 REFERENCE 835 "RFC 5213: Section 6.1, 8.1" 836 ::= { pmip6MagBLEntry 7 } 838 pmip6MagBLAccessTechnologyType OBJECT-TYPE 839 SYNTAX Pmip6PBUAccessTechnologyType 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "The type of the access 844 technology by which the mobile node is currently 845 attached to the mobile access gateway. 846 " 847 REFERENCE 848 "RFC 5213: Section 6.9.1.1, 6.9.1.5, 8.1" 849 ::= { pmip6MagBLEntry 8 } 851 pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE 852 SYNTAX DateAndTime 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The 64-bit timestamp value of the most recently 857 accepted Proxy Binding Update message sent for this 858 mobile node. This is the time-of-day on the mobile 859 access gateway, when the proxy binding acknowledgement 860 message with the Status field set to 0 861 was received. If the Timestamp option is not present 862 in the Proxy Binding Update message (i.e., when the 863 sequence number based scheme is in use), the value MUST 864 be set to ALL_ZERO. 865 " 866 REFERENCE 867 "RFC 5213: Section 5.1, 8.1" 868 ::= { pmip6MagBLEntry 9 } 870 pmip6MagMnProfileTable OBJECT-TYPE 871 SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "This table corresponds to the mobile node's policy 876 profile that includes the essential operational 877 parameters that are required by the network entities 878 for managing the mobile node's mobility service. 879 It contains policy profiles of mobile nodes that are 880 connected to the mobile access gateway. 881 " 882 REFERENCE 883 "RFC 5213: Section 6.2" 884 ::= { pmip6MagRegistration 2 } 886 pmip6MagMnProfileEntry OBJECT-TYPE 887 SYNTAX Pmip6MagMnProfileEntry 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "An entry containing information about the 892 mobile node's policy profile. 893 " 894 INDEX { pmip6MagMnIndex } 895 ::= { pmip6MagMnProfileTable 1 } 897 Pmip6MagMnProfileEntry ::= 898 SEQUENCE { 899 pmip6MagMnIndex Pmip6MNIndex, 900 pmip6MagMnIdentifier Pmip6MNIdentifier, 901 pmip6MagMnLocalMobilityAnchorAddressType InetAddressType, 902 pmip6MagMnLocalMobilityAnchorAddress InetAddress 903 } 905 pmip6MagMnIndex OBJECT-TYPE 906 SYNTAX Pmip6MNIndex 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "The index for a mobile node in the Proxy Mobile IPv6 911 domain. 912 " 913 ::= { pmip6MagMnProfileEntry 1 } 915 pmip6MagMnIdentifier OBJECT-TYPE 916 SYNTAX Pmip6MNIdentifier 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The identity of a mobile node in the Proxy Mobile IPv6 921 domain. 922 " 923 REFERENCE 924 "RFC 5213: Section 2.2" 925 ::= { pmip6MagMnProfileEntry 2 } 927 pmip6MagMnLocalMobilityAnchorAddressType OBJECT-TYPE 928 SYNTAX InetAddressType 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The InetAddressType of the 933 pmip6MagMnLocalMobilityAnchorAddress that follows. 934 " 935 ::= { pmip6MagMnProfileEntry 3 } 937 pmip6MagMnLocalMobilityAnchorAddress OBJECT-TYPE 938 SYNTAX InetAddress 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The global address that is configured on the interface 943 of the local mobility anchor and is the transport 944 endpoint of the bi-directional tunnel established 945 between the local mobility anchor and the mobile access 946 gateway. This is the address to which the mobile 947 access gateway sends the Proxy Binding Update messages. 948 " 949 REFERENCE 950 "RFC 5213: Section 2.2" 951 ::= { pmip6MagMnProfileEntry 4 } 953 pmip6BindingCacheTable OBJECT-TYPE 954 SYNTAX SEQUENCE OF Pmip6BindingCacheEntry 955 MAX-ACCESS not-accessible 956 STATUS current 957 DESCRIPTION 958 "This table models the Binding Cache on the local 959 mobility anchor. 960 Entries from the table are deleted as 961 the lifetime of the binding expires. 963 Entries in this table are not required to survive 964 a reboot of the managed entity. 965 " 966 REFERENCE 967 "RFC 3775: Section 4.5, 9.1, 10.1, 968 RFC 5213: Section 5.1" 969 ::= { pmip6Bindings 1 } 971 pmip6BindingCacheEntry OBJECT-TYPE 972 SYNTAX Pmip6BindingCacheEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "An entry containing additional information contained 977 in the binding cache table 978 of the local mobility anchor. 979 " 980 AUGMENTS {mip6BindingCacheEntry} 981 ::= { pmip6BindingCacheTable 1 } 983 Pmip6BindingCacheEntry ::= SEQUENCE { 984 pmip6BindingPBUFlag TruthValue, 985 pmip6BindingMnIdentifier Pmip6MNIdentifier, 986 pmip6BindingMnLlIdentifier Pmip6MNLlIdentifier, 987 pmip6BindingMagLinkLocalAddressType InetAddressType, 988 pmip6BindingMagLinkLocalAddress InetAddress, 989 pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC, 990 pmip6BindingAccessTechnologyType 991 Pmip6PBUAccessTechnologyType, 992 pmip6BindingTimeRecentlyAccepted DateAndTime 993 } 995 pmip6BindingPBUFlag OBJECT-TYPE 996 SYNTAX TruthValue 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "true(1) if the local mobility anchor accepted the 1001 binding update with Proxy Registration Flag from a 1002 mobile access gateway. 1003 false(0) implies that the binding cache is from a 1004 mobile node. 1005 " 1006 REFERENCE 1007 "RFC 5213: Section 5.1, 8.1" 1008 ::= { pmip6BindingCacheEntry 1 } 1010 pmip6BindingMnIdentifier OBJECT-TYPE 1011 SYNTAX Pmip6MNIdentifier 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The identifier of the registered mobile node, 1016 MN-Identifier. This identifier is obtained from the 1017 Mobile Node Identifier Option [RFC-4283] present in 1018 the received Proxy Binding Update message. 1019 " 1020 REFERENCE 1021 "RFC 5213: Section 2.2, 5.1, 8.1" 1022 ::= { pmip6BindingCacheEntry 2 } 1024 pmip6BindingMnLlIdentifier OBJECT-TYPE 1025 SYNTAX Pmip6MNLlIdentifier 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "The link-layer identifier of the mobile node's 1030 connected interface on the access link. This 1031 identifier can be acquired from the Mobile Node 1032 Link-layer Identifier option, present in the received 1033 Proxy Binding Update message. If the option was not 1034 present in the request, this variable length field 1035 MUST be set to two (octets) and MUST be initialized to 1036 a value of ALL_ZERO. 1037 " 1038 REFERENCE 1039 "RFC 5213: Section 2.2, 5.1, 8.1" 1040 ::= { pmip6BindingCacheEntry 3 } 1042 pmip6BindingMagLinkLocalAddressType OBJECT-TYPE 1043 SYNTAX InetAddressType 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The InetAddressType of the 1048 pmip6BindingMagLinkLocalAddress that follows. 1049 " 1050 ::= { pmip6BindingCacheEntry 4 } 1052 pmip6BindingMagLinkLocalAddress OBJECT-TYPE 1053 SYNTAX InetAddress 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The link-local address of the mobile access gateway on 1058 the point-to-point link shared with the mobile node. 1059 This is generated by the local mobility anchor after 1060 accepting the initial Proxy Binding Update message. 1061 This is the address that is present in the Link-local 1062 Address option of the corresponding Proxy Binding 1063 Acknowledgement message. 1064 " 1065 REFERENCE 1066 "RFC 5213: Section 5.1, 6.9.1.2, 8.2" 1067 ::= { pmip6BindingCacheEntry 5 } 1069 pmip6BindingTunnelIfIdentifier OBJECT-TYPE 1070 SYNTAX Ipv6AddressIfIdentifierTC 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "The tunnel interface identifier (tunnel-if-id) of the 1075 bi-directional tunnel between the local mobility anchor 1076 and the mobile access gateway where the mobile node is 1077 currently anchored. This is internal to the local 1078 mobility anchor. The tunnel interface identifier is 1079 acquired during the tunnel creation. 1080 " 1081 REFERENCE 1082 "RFC 5213: Section 5.1, 8.1" 1083 ::= { pmip6BindingCacheEntry 6 } 1085 pmip6BindingAccessTechnologyType OBJECT-TYPE 1086 SYNTAX Pmip6PBUAccessTechnologyType 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The access technology type, by which the mobile node 1091 is currently attached. This is obtained from the 1092 Access Technology Type option, present in the Proxy 1093 Binding Update message. 1094 " 1095 REFERENCE 1096 "RFC 5213: Section 5.1, 8.1" 1097 ::= { pmip6BindingCacheEntry 7 } 1099 pmip6BindingTimeRecentlyAccepted OBJECT-TYPE 1100 SYNTAX DateAndTime 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "The 64-bit timestamp value of the most recently 1105 accepted Proxy Binding Update message sent for this 1106 mobile node. This is the time-of-day on the local 1107 mobility anchor, when the message was received. If 1108 the Timestamp option is not present in the Proxy 1109 Binding Update message (i.e., when the sequence number 1110 based scheme is in use), the value MUST be set to 1111 ALL_ZERO. 1112 " 1113 REFERENCE 1114 "RFC 5213: Section 5.1, 8.1" 1115 ::= { pmip6BindingCacheEntry 8 } 1117 --- 1118 --- 1119 --- pmip6Stats group 1120 --- 1121 --- 1123 -- 1124 -- pmip6Stats:pmip6BindingRegcounters 1125 -- 1127 pmip6MissingMnIdentifierOption OBJECT-TYPE 1128 SYNTAX Counter32 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "Total number of Proxy Binding Update message 1133 rejected by the local mobility anchor with status 1134 code in the Binding Acknowledgment message indicating 1135 'Missing mobile node identifier option' (Code 160). 1137 Discontinuities in the value of this counter can 1138 occur at re-initialization of the mobile router. 1139 and at other times as indicated by the value of 1140 pmip6CounterDiscontinuityTime. 1141 " 1142 REFERENCE 1143 "RFC 5213: Section 5.3.1, 8.9" 1144 ::= { pmip6BindingRegCounters 1 } 1146 pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE 1147 SYNTAX Counter32 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "Total number of Proxy Binding Update message 1152 rejected by the local mobility anchor with status 1153 code in the Binding Acknowledgment message indicating 1154 'Not authorized to send proxy binding updates' 1155 (Code 154). 1157 Discontinuities in the value of this counter can 1158 occur at re-initialization of the mobile router, 1159 and at other times as indicated by the value of 1160 pmip6CounterDiscontinuityTime. 1161 " 1162 REFERENCE 1163 "RFC 5213: Section 5.3.1, 8.9" 1164 ::= { pmip6BindingRegCounters 2 } 1166 pmip6NotLMAForThisMobileNode OBJECT-TYPE 1167 SYNTAX Counter32 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "Total number of Proxy Binding Update message rejected 1172 by the local mobility anchor with status code in the 1173 Binding Acknowledgment message indicating 1174 'Not local mobility anchor for this mobile node' 1175 (Code 153). 1177 Discontinuities in the value of this counter can 1178 occur at re-initialization of the management system, 1179 and at other times as indicated by the value of 1180 pmip6CounterDiscontinuityTime. 1181 " 1182 REFERENCE 1183 "RFC 5213: Section 5.3.1, 8.9" 1184 ::= { pmip6BindingRegCounters 3 } 1186 pmip6ProxyRegNotEnabled OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "Total number of Proxy Binding Update message rejected 1192 by the local mobility anchor with status code in the 1193 Binding Acknowledgment message indicating 1194 'Proxy Registration not enabled' (Code 152). 1195 Discontinuities in the value of this counter can 1196 occur at re-initialization of the management system, 1197 and at other times as indicated by the value of 1198 pmip6CounterDiscontinuityTime. 1199 " 1200 REFERENCE 1201 "RFC 5213: Section 5.3.1, 6.9.1.2, 8.9" 1202 ::= { pmip6BindingRegCounters 4 } 1204 pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE 1205 SYNTAX Counter32 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "Total number of Proxy Binding Update message rejected 1210 by the local mobility anchor with status code in the 1211 Binding Acknowledgment message indicating 1212 'Missing home network prefix option' (Code 158). 1213 Discontinuities in the value of this counter can 1214 occur at re-initialization of the management system, 1215 and at other times as indicated by the value of 1216 pmip6CounterDiscontinuityTime. 1217 " 1218 REFERENCE 1219 "RFC 5213: Section 5.3.1, 8.9" 1220 ::= { pmip6BindingRegCounters 5 } 1222 pmip6MissingHandOffIndicatorOption OBJECT-TYPE 1223 SYNTAX Counter32 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "Total number of Proxy Binding Update message rejected 1228 by the local mobility anchor with status code in the 1229 Binding Acknowledgment message indicating 1230 'Missing handoff indicator option' (Code 161). 1231 Discontinuities in the value of this counter can 1232 occur at re-initialization of the management system, 1233 and at other times as indicated by the value of 1234 pmip6CounterDiscontinuityTime. 1235 " 1236 REFERENCE 1237 "RFC 5213: Section 5.3.1, 8.9" 1238 ::= { pmip6BindingRegCounters 6 } 1240 pmip6MissingAccessTechTypeOption OBJECT-TYPE 1241 SYNTAX Counter32 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "Total number of Proxy Binding Update message rejected 1246 by the local mobility anchor with status code in the 1247 Binding Acknowledgment message indicating 1248 'Missing access technology type option' (Code 162). 1249 Discontinuities in the value of this counter can 1250 occur at re-initialization of the management system, 1251 and at other times as indicated by the value of 1252 pmip6CounterDiscontinuityTime. 1253 " 1254 REFERENCE 1255 "RFC 5213: Section 5.3.1, 8.9" 1256 ::= { pmip6BindingRegCounters 7 } 1258 pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE 1259 SYNTAX Counter32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "Total number of Proxy Binding Update message rejected 1264 by the local mobility anchor with status code in the 1265 Binding Acknowledgment message indicating 1266 'Mobile node not authorized for one or more of the 1267 requesting home network prefixes' (Code 155). 1269 Discontinuities in the value of this counter can 1270 occur at re-initialization of the management system, 1271 and at other times as indicated by the value of 1272 pmip6CounterDiscontinuityTime. 1273 " 1274 REFERENCE 1275 "RFC 5213: Section 5.3.2, 6.9.1.2, 8.9" 1276 ::= { pmip6BindingRegCounters 8 } 1278 pmip6TimestampMismatch OBJECT-TYPE 1279 SYNTAX Counter32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "Total number of Proxy Binding Update message rejected 1284 by the local mobility anchor with status code in the 1285 Binding Acknowledgment message indicating 1286 'Invalid timestamp value (the clocks are out of sync)' 1287 (Code 156) 1288 Discontinuities in the value of this counter can 1289 occur at re-initialization of the management system, 1290 and at other times as indicated by the value of 1291 pmip6CounterDiscontinuityTime. 1292 " 1293 REFERENCE 1294 "RFC 5213: Section 5.5, 6.9.1.2, 8.9" 1295 ::= { pmip6BindingRegCounters 9 } 1297 pmip6TimestampLowerThanPrevAccepted OBJECT-TYPE 1298 SYNTAX Counter32 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "Total number of Proxy Binding Update message rejected 1303 by the local mobility anchor with status code in the 1304 Binding Acknowledgment message indicating 1305 'The timestamp value is lower than the previously 1306 accepted value' (Code 157). 1307 Discontinuities in the value of this counter can 1308 occur at re-initialization of the management system, 1309 and at other times as indicated by the value of 1310 pmip6CounterDiscontinuityTime. 1311 " 1312 REFERENCE 1313 "RFC 5213: Section 5.5, 6.9.1.2, 8.9" 1314 ::= { pmip6BindingRegCounters 10 } 1316 pmip6BcePbuPrefixSetDoNotMatch OBJECT-TYPE 1317 SYNTAX Counter32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "Total number of Proxy Binding Update message rejected 1322 by the local mobility anchor with status code in the 1323 Binding Acknowledgment message indicating 1324 'All the home network prefixes listed in the Binding 1325 Cache Entry do not match all the prefixes in the 1326 received Proxy Binding Update' (Code 159). 1327 Discontinuities in the value of this counter can 1328 occur at re-initialization of the management system, 1329 and at other times as indicated by the value of 1330 pmip6CounterDiscontinuityTime. 1331 " 1332 REFERENCE 1333 "RFC 5213: Section 5.4.1.1, 8.9" 1334 ::= { pmip6BindingRegCounters 11 } 1336 pmip6InitialBindingRegistrations OBJECT-TYPE 1337 SYNTAX Counter32 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "Total number of Proxy Binding Update messages that 1342 newly creates the Binding Cache entry. 1343 Discontinuities in the value of this counter can 1344 occur at re-initialization of the management system, 1345 and at other times as indicated by the value of 1346 pmip6CounterDiscontinuityTime. 1347 " 1348 REFERENCE 1349 "RFC 5213: Section 5.3.2" 1350 ::= { pmip6BindingRegCounters 12 } 1352 pmip6BindingLifeTimeExtensionNoHandOff OBJECT-TYPE 1353 SYNTAX Counter32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "Total number of Proxy Binding Update message for 1358 extending the binding lifetime, received from the 1359 same mobile access gateway that last updated the 1360 binding. 1361 Discontinuities in the value of this counter can 1362 occur at re-initialization of the management system, 1363 and at other times as indicated by the value of 1364 pmip6CounterDiscontinuityTime. 1365 " 1366 REFERENCE 1367 "RFC 5213: Section 5.3.3" 1368 ::= { pmip6BindingRegCounters 13 } 1370 pmip6BindingLifeTimeExtensionAfterHandOff OBJECT-TYPE 1371 SYNTAX Counter32 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "Total number of Proxy Binding Update message for 1376 extending the binding lifetime, received from a new 1377 mobile access gateway where the mobile node's 1378 mobility session is handed off. 1379 Discontinuities in the value of this counter can 1380 occur at re-initialization of the management system, 1381 and at other times as indicated by the value of 1382 pmip6CounterDiscontinuityTime. 1383 " 1384 REFERENCE 1385 "RFC 5213: Section 5.3.4" 1386 ::= { pmip6BindingRegCounters 14 } 1388 pmip6BindingDeRegistrations OBJECT-TYPE 1389 SYNTAX Counter32 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "Total number of Proxy Binding Update message with the 1394 lifetime value of zero. 1395 Discontinuities in the value of this counter can 1396 occur at re-initialization of the management system, 1397 and at other times as indicated by the value of 1398 pmip6CounterDiscontinuityTime. 1399 " 1400 REFERENCE 1401 "RFC 5213: Section 5.3.5" 1402 ::= { pmip6BindingRegCounters 15 } 1404 pmip6BindingBindingAcks OBJECT-TYPE 1405 SYNTAX Counter32 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "Total number of Proxy Binding Acknowledgement 1410 messages. 1411 Discontinuities in the value of this counter can 1412 occur at re-initialization of the management system, 1413 and at other times as indicated by the value of 1414 pmip6CounterDiscontinuityTime. 1415 " 1416 REFERENCE 1417 "RFC 5213: Section 5.3.5" 1418 ::= { pmip6BindingRegCounters 16 } 1420 pmip6CounterDiscontinuityTime OBJECT-TYPE 1421 SYNTAX TimeStamp 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "The value of sysUpTime on the most recent occasion 1426 at which any one or more of this PMIPv6 entities 1427 global counters, viz., counters with OID prefix 1428 'pmip6BindingRegCounters' suffered a discontinuity. 1429 If no such discontinuities have occurred since the 1430 last re-initialization of the local management 1431 subsystem, then this object will have a zero value. 1432 " 1433 ::= { pmip6BindingRegCounters 17 } 1435 pmip6LmaLMAATable OBJECT-TYPE 1436 SYNTAX SEQUENCE OF Pmip6LmaLMAAEntry 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "This table models the LMA Addresses configured 1441 on the local mobility anchor. Each LMA Address acts as 1442 a transport endpoint of the tunnel between the local 1443 mobility anchor and the mobile access gateway and is 1444 the transport endpoint of the tunnel between the local 1445 mobility anchor and the mobile access gateway. 1447 Entries in this table are not required to survive 1448 a reboot of the managed entity. 1449 " 1450 REFERENCE 1451 "RFC 5213: Section 2.2, 5.6" 1452 ::= { pmip6LmaSystem 1 } 1454 pmip6LmaLMAAEntry OBJECT-TYPE 1455 SYNTAX Pmip6LmaLMAAEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "This entry represents a conceptual row in the 1460 LMAA table. It represents each LMAA 1461 on the local mobility anchor. 1463 Implementers need to be aware that if the total 1464 number of octets in mip6BindingHomeAddress 1465 exceeds 113 then OIDs of column 1466 instances in this row will have more than 128 1467 sub-identifiers and cannot be accessed using 1468 SNMPv1, SNMPv2c, or SNMPv3. 1469 " 1470 INDEX { pmip6LmaLMAAType, pmip6LmaLMAA } 1471 ::= { pmip6LmaLMAATable 1 } 1473 Pmip6LmaLMAAEntry ::= 1474 SEQUENCE { 1475 pmip6LmaLMAAType InetAddressType, 1476 pmip6LmaLMAA InetAddress, 1477 pmip6LmaLMAAState INTEGER 1478 } 1480 pmip6LmaLMAAType OBJECT-TYPE 1481 SYNTAX InetAddressType 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "The InetAddressType of the pmip6LmaLMAA 1486 that follows. 1487 " 1488 ::= { pmip6LmaLMAAEntry 1 } 1490 pmip6LmaLMAA OBJECT-TYPE 1491 SYNTAX InetAddress 1492 MAX-ACCESS not-accessible 1493 STATUS current 1494 DESCRIPTION 1495 "The LMAA configured on the local mobility anchor. 1497 The type of the address represented by this object 1498 is specified by the corresponding 1499 pmip6LmaLMAAType object. 1501 " 1502 REFERENCE 1503 "RFC 5213: Section 2.2, 5.6" 1504 ::= { pmip6LmaLMAAEntry 2 } 1506 pmip6LmaLMAAState OBJECT-TYPE 1507 SYNTAX INTEGER { 1508 unknown(1), 1509 activated(2), 1510 tunneled(3) 1511 } 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "This object indicates the state of the LMAA: 1516 unknown -- The state of the LMAA 1517 cannot be determined. 1518 activated -- The LMAA is ready to establish 1519 tunnel 1520 tunneled -- The LMAA is used to set up the 1521 bi-directional tunnel. 1522 " 1523 ::= { pmip6LmaLMAAEntry 3 } 1525 pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE 1526 SYNTAX Integer32 (1..65535) 1527 MAX-ACCESS read-write 1528 STATUS current 1529 DESCRIPTION 1530 "This variable specifies the amount of time in 1531 milliseconds the local mobility anchor MUST wait before 1532 it deletes a Binding Cache entry of a mobile node, upon 1533 receiving a Proxy Binding Update message from a mobile 1534 access gateway with a lifetime value of 0. 1535 During this wait time, if the local mobility anchor 1536 receives a Proxy Binding Update for the same mobility 1537 binding, with lifetime value greater than 0, then it 1538 must update the binding cache entry with the accepted 1539 binding values. By the end of this wait-time, if the 1540 local mobility anchor did not receive any valid Proxy 1541 Binding Update message for that mobility binding, it 1542 MUST delete the Binding Cache entry. This delay 1543 essentially ensures a mobile node's Binding Cache entry 1544 is not deleted too quickly and allows some time for the 1545 new mobile access gateway to complete the signaling for 1546 the mobile node. 1547 The default value for this variable is 10000 1548 milliseconds. 1549 " 1550 REFERENCE 1551 "RFC 5213: Section 5.3.5, 9.1" 1552 ::= { pmip6LmaConf 1 } 1554 pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE 1555 SYNTAX Integer32 (1..65535) 1556 MAX-ACCESS read-write 1557 STATUS current 1558 DESCRIPTION 1559 "This variable specifies the amount of time in 1560 milliseconds the local mobility anchor MUST wait for 1561 the de-registration message for an existing mobility 1562 session before it decides to create a new mobility 1563 session. 1564 The default value for this variable is 1500 1565 milliseconds. Note that there is a dependency between 1566 this value and the values used in the retransmission 1567 algorithm for Proxy Binding Updates. The retransmissions 1568 need to happen before MaxDelayBeforeNewBCEAssign runs 1569 out, as otherwise there are situations where a 1570 de-registration from a previous mobile access gateway 1571 may be lost, and the local mobility anchor creates 1572 needlessly a new mobility session and new prefixes for 1573 the mobile node. This affects situations where there 1574 is no information from the lower layers about the type 1575 of a handoff or other parameters that can be used for 1576 identifying the mobility session, however. 1577 " 1578 REFERENCE 1579 "RFC 5213: Section 5.4.1.2, 5.4.1.3, 9.1" 1580 ::= { pmip6LmaConf 2 } 1582 pmip6LmaTimestampValidityWindow OBJECT-TYPE 1583 SYNTAX Integer32 (1..65535) 1584 MAX-ACCESS read-write 1585 STATUS current 1586 DESCRIPTION 1587 "This variable specifies the maximum amount of time 1588 difference in milliseconds between the timestamp in the 1589 received Proxy Binding Update message and the current 1590 time-of-day on the local mobility anchor, that is 1591 allowed by the local mobility anchor for the received 1592 message to be considered valid. 1593 The default value for this variable is 300 milliseconds. 1594 This variable must be adjusted to suit the deployments. 1595 " 1596 REFERENCE 1597 "RFC 5213: Section 5.5, 9.1" 1598 ::= { pmip6LmaConf 3 } 1600 pmip6LmaHomeNetworkPrefixTable OBJECT-TYPE 1601 SYNTAX SEQUENCE OF PMip6LmaHomeNetworkPrefixEntry 1602 MAX-ACCESS not-accessible 1603 STATUS current 1604 DESCRIPTION 1605 "A table representing the Home Network Prefixes 1606 assigned to the mobile node's connected interfaces. 1607 This table shows the prefixes registered in the 1608 binding cache entry. 1609 " 1610 REFERENCE 1611 "RFC 5213: Section 2, 5.1, 5.2" 1612 ::= { pmip6LmaConf 4 } 1614 pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE 1615 SYNTAX PMip6LmaHomeNetworkPrefixEntry 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "An entry in the Home Network Prefixes table. 1621 Implementers need to be aware that if the total 1622 number of octets in pmip6LmaHomeNetworkPrefix 1623 exceeds 114 then OIDs of column 1624 instances in this row will have more than 128 1625 sub-identifiers and cannot be accessed using 1626 SNMPv1, SNMPv2c, or SNMPv3. 1627 " 1628 INDEX { pmip6BindingMnIdentifier, 1629 pmip6BindingMnLlIdentifier, 1630 pmip6LmaHomeNetworkPrefixType, 1631 pmip6LmaHomeNetworkPrefix } 1632 ::= { pmip6LmaHomeNetworkPrefixTable 1 } 1634 PMip6LmaHomeNetworkPrefixEntry ::= 1635 SEQUENCE { 1636 pmip6LmaHomeNetworkPrefixType InetAddressType, 1637 pmip6LmaHomeNetworkPrefix InetAddress, 1638 pmip6LmaHomeNetworkPrefixLength InetAddressPrefixLength, 1639 pmip6LmaHomeNetworkPrefixLifeTime Gauge32 1640 } 1642 pmip6LmaHomeNetworkPrefixType OBJECT-TYPE 1643 SYNTAX InetAddressType 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "The InetAddressType of the pmip6LmaHomeNetworkPrefix 1648 that follows. 1649 " 1650 ::= { pmip6LmaHomeNetworkPrefixEntry 1 } 1652 pmip6LmaHomeNetworkPrefix OBJECT-TYPE 1653 SYNTAX InetAddress 1654 MAX-ACCESS not-accessible 1655 STATUS current 1656 DESCRIPTION 1657 "The mobile network prefix that is delegated to the 1658 mobile node. The type of the address represented by 1659 this object is specified by the corresponding 1660 pmip6LmaHomeNetworkPrefixType object. 1661 " 1662 REFERENCE 1663 "RFC 5213: Section 2" 1665 ::= { pmip6LmaHomeNetworkPrefixEntry 2 } 1667 pmip6LmaHomeNetworkPrefixLength OBJECT-TYPE 1668 SYNTAX InetAddressPrefixLength 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The prefix length of the Home Network Prefix. 1673 " 1674 ::= { pmip6LmaHomeNetworkPrefixEntry 3 } 1676 pmip6LmaHomeNetworkPrefixLifeTime OBJECT-TYPE 1677 SYNTAX Gauge32 1678 UNITS "seconds" 1679 MAX-ACCESS read-write 1680 STATUS current 1681 DESCRIPTION 1682 "The lifetime (in seconds) granted to the mobile 1683 node for this registration. 1684 " 1685 REFERENCE 1686 "RFC 5213: Section 5.3" 1687 ::= { pmip6LmaHomeNetworkPrefixEntry 4 } 1689 -- 1690 -- pmip6Notifications 1691 -- 1692 -- 1694 pmip6MagHomeTunnelEstablished NOTIFICATION-TYPE 1695 OBJECTS { 1696 pmip6MagBLTunnelIfIdentifier, 1697 -- pmip6MagProxyCOAType, 1698 -- pmip6MagProxyCOA 1699 pmip6MagProxyCOAState 1700 } 1701 STATUS current 1702 DESCRIPTION 1703 "This notification is sent by the Proxy MobileIPv6 1704 entities every time the tunnel is established between 1705 the local mobility anchor and mobile access gateway. 1706 " 1707 REFERENCE 1708 "RFC 5213: Section 5.6.1" 1709 ::= { pmip6Notifications 1 } 1711 pmip6MagHomeTunnelReleased NOTIFICATION-TYPE 1712 OBJECTS { 1713 pmip6MagBLTunnelIfIdentifier, 1714 -- pmip6MagProxyCOAType, 1715 -- pmip6MagProxyCOA 1716 pmip6MagProxyCOAState 1717 } 1718 STATUS current 1719 DESCRIPTION 1720 "This notification is sent by the Proxy MobileIPv6 1721 entities every time the tunnel between the local 1722 mobility anchor and mobile access gateway is released. 1723 " 1724 REFERENCE 1725 "RFC 5213: Section 5.6.1" 1726 ::= { pmip6Notifications 2} 1728 pmip6LmaHomeTunnelEstablished NOTIFICATION-TYPE 1729 OBJECTS { 1730 pmip6BindingTunnelIfIdentifier, 1731 -- pmip6LmaLMAAType, 1732 -- pmip6LmaLMAA, 1733 pmip6LmaLMAAState 1734 } 1735 STATUS current 1736 DESCRIPTION 1737 "This notification is sent by the Proxy MobileIPv6 1738 entities every time the tunnel is established between 1739 the local mobility anchor and mobile access gateway. 1740 " 1741 REFERENCE 1742 "RFC 5213: Section 5.6.1" 1743 ::= { pmip6Notifications 3 } 1745 pmip6LmaHomeTunnelReleased NOTIFICATION-TYPE 1746 OBJECTS { 1747 pmip6BindingTunnelIfIdentifier, 1748 -- pmip6LmaLMAAType, 1749 -- pmip6LmaLMAA, 1750 pmip6LmaLMAAState 1751 } 1752 STATUS current 1753 DESCRIPTION 1754 "This notification is sent by the Proxy MobileIPv6 1755 entities every time the tunnel between the local 1756 mobility anchor and mobile access gateway is released. 1757 " 1758 REFERENCE 1759 "RFC 5213: Section 5.6.1" 1760 ::= { pmip6Notifications 4} 1762 -- Conformance information 1764 pmip6Groups OBJECT IDENTIFIER ::= { pmip6Conformance 1 } 1765 pmip6Compliances OBJECT IDENTIFIER ::= { pmip6Conformance 2 } 1767 -- Units of conformance 1768 pmip6SystemGroup OBJECT-GROUP 1769 OBJECTS { 1770 pmip6Capabilities, 1771 pmip6Status, 1772 pmip6MobileNodeGeneratedTimestampInUse, 1773 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType, 1774 pmip6FixedMagLinkLocalAddressOnAllAccessLinks, 1775 pmip6FixedMagLinkLayerAddressOnAllAccessLinks 1777 } 1778 STATUS current 1779 DESCRIPTION 1780 " A collection of objects for basic PMIPv6 1781 monitoring." 1782 ::= { pmip6Groups 1 } 1784 pmip6BindingCacheGroup OBJECT-GROUP 1785 OBJECTS { 1786 pmip6BindingPBUFlag, 1787 pmip6BindingMnIdentifier, 1788 pmip6BindingMnLlIdentifier, 1789 pmip6BindingMagLinkLocalAddressType, 1790 pmip6BindingMagLinkLocalAddress, 1791 pmip6BindingTunnelIfIdentifier, 1792 pmip6BindingAccessTechnologyType, 1793 pmip6BindingTimeRecentlyAccepted 1794 } 1795 STATUS current 1796 DESCRIPTION 1797 " A collection of objects for monitoring the 1798 PMIPv6 extensions of the Binding Cache." 1799 ::= { pmip6Groups 2 } 1801 pmip6StatsGroup OBJECT-GROUP 1802 OBJECTS { 1803 pmip6MissingMnIdentifierOption, 1804 pmip6MagNotAuthorizedForProxyReg, 1805 pmip6NotLMAForThisMobileNode, 1806 pmip6ProxyRegNotEnabled, 1807 pmip6MissingHomeNetworkPrefixOption, 1808 pmip6MissingHandOffIndicatorOption, 1809 pmip6MissingAccessTechTypeOption, 1810 pmip6NotAuthorizedForHomeNetworkPrefix, 1811 pmip6TimestampMismatch, 1812 pmip6TimestampLowerThanPrevAccepted, 1813 pmip6BcePbuPrefixSetDoNotMatch, 1814 pmip6InitialBindingRegistrations, 1815 pmip6BindingLifeTimeExtensionNoHandOff, 1816 pmip6BindingLifeTimeExtensionAfterHandOff, 1817 pmip6BindingDeRegistrations, 1818 pmip6BindingBindingAcks, 1819 pmip6CounterDiscontinuityTime 1820 } 1821 STATUS current 1822 DESCRIPTION 1823 " A collection of objects for basic PMIPv6 1824 statistics monitoring. 1825 " 1826 ::= { pmip6Groups 3 } 1828 pmip6MagSystemGroup OBJECT-GROUP 1829 OBJECTS { 1830 -- pmip6MagProxyCOAType, 1831 -- pmip6MagProxyCOA 1832 pmip6MagProxyCOAState 1833 } 1834 STATUS current 1835 DESCRIPTION 1836 " A collection of objects for monitoring the 1837 PMIPv6 system related objects on a mobile router." 1838 ::= { pmip6Groups 4 } 1840 pmip6MagConfigurationGroup OBJECT-GROUP 1841 OBJECTS { 1842 -- pmip6MagHomeNetworkPrefixType, 1843 -- pmip6MagHomeNetworkPrefix, 1844 pmip6MagHomeNetworkPrefixLength, 1845 pmip6MagHomeNetworkPrefixLifeTime, 1846 pmip6MagEnableMagLocalRouting 1847 } 1848 STATUS current 1849 DESCRIPTION 1850 " A collection of objects for monitoring the 1851 configuration related objects on a mobile access 1852 gateway. 1854 " 1855 ::= { pmip6Groups 5 } 1857 pmip6MagRegistrationGroup OBJECT-GROUP 1858 OBJECTS { 1859 pmip6MagBLFlag, 1860 pmip6MagBLMnIdentifier, 1861 pmip6MagBLlMnIdentifier, 1862 pmip6MagBLMagLinkLocalAddressType, 1863 pmip6MagBLMagLinkLocalAddress, 1864 pmip6MagBLMagIfIdentifierToMn, 1865 pmip6MagBLTunnelIfIdentifier, 1866 pmip6MagBLAccessTechnologyType, 1867 pmip6MagBLTimeRecentlyAccepted, 1868 -- pmip6MagMnIndex, 1869 pmip6MagMnIdentifier, 1870 pmip6MagMnLocalMobilityAnchorAddressType, 1871 pmip6MagMnLocalMobilityAnchorAddress 1872 } 1873 STATUS current 1874 DESCRIPTION 1875 " A collection of objects for monitoring the 1876 registration related objects on a mobile access 1877 gateway. 1878 " 1879 ::= { pmip6Groups 6 } 1881 pmip6LmaSystemGroup OBJECT-GROUP 1882 OBJECTS { 1883 pmip6LmaLMAAState 1884 } 1885 STATUS current 1886 DESCRIPTION 1887 " A collection of objects for monitoring the 1888 system related objects on a LMA." 1889 ::= { pmip6Groups 7 } 1891 pmip6LmaConfigurationGroup OBJECT-GROUP 1892 OBJECTS { 1893 pmip6LmaMinDelayBeforeBCEDelete, 1894 pmip6LmaMaxDelayBeforeNewBCEAssign, 1895 pmip6LmaTimestampValidityWindow, 1896 pmip6LmaHomeNetworkPrefixLength, 1897 pmip6LmaHomeNetworkPrefixLifeTime 1898 } 1899 STATUS current 1900 DESCRIPTION 1901 " A collection of objects for Monitoring the 1902 configuration related objects on a LMA." -- Check 1903 ::= { pmip6Groups 8 } 1905 pmip6MagNotificationGroup NOTIFICATION-GROUP 1906 NOTIFICATIONS { 1907 pmip6MagHomeTunnelEstablished, 1908 pmip6MagHomeTunnelReleased 1909 } 1910 STATUS current 1911 DESCRIPTION 1912 "A collection of notifications from a home agent 1913 or correspondent node to the Manager about the 1914 tunnel status of the mobile router. 1915 " 1916 ::= { pmip6Groups 9 } 1918 pmip6LmaNotificationGroup NOTIFICATION-GROUP 1919 NOTIFICATIONS { 1920 pmip6LmaHomeTunnelEstablished, 1921 pmip6LmaHomeTunnelReleased 1922 } 1923 STATUS current 1924 DESCRIPTION 1925 "A collection of notifications from a home agent 1926 or correspondent node to the Manager about the 1927 tunnel status of the mobile router. 1928 " 1929 ::= { pmip6Groups 10 } 1931 -- Compliance statements 1932 pmip6CoreCompliance MODULE-COMPLIANCE 1933 STATUS current 1934 DESCRIPTION 1935 "The compliance statement for SNMP entities 1936 which implement the MOBILEIPV6-MIB. 1937 There are a number of INDEX objects that cannot be 1938 represented in the form of OBJECT clauses in 1939 SMIv2, but for which there are compliance 1940 requirements, expressed in OBJECT clause form in 1941 this 1942 description: 1943 -- OBJECT pmip6BindingHomeAddressType 1944 -- SYNTAX InetAddressType { ipv6(2) } 1945 -- DESCRIPTION 1946 -- This MIB module requires support for global 1947 -- ipv6 addresses for the pmip6BindingHomeAddress 1948 -- object. 1949 -- 1950 " 1951 MODULE -- this module 1952 MANDATORY-GROUPS { pmip6SystemGroup 1953 } 1954 ::= { pmip6Compliances 1 } 1956 pmip6Compliance2 MODULE-COMPLIANCE 1957 STATUS current 1958 DESCRIPTION 1959 "The compliance statement for SNMP entities 1960 which implement the MOBILEIPV6-MIB. 1961 There are a number of INDEX objects that cannot be 1962 represented in the form of OBJECT clauses in 1963 SMIv2, but for which there are compliance 1964 requirements, expressed in OBJECT clause form in 1965 this description: 1967 -- OBJECT mip6BindingHomeAddressType 1968 -- SYNTAX InetAddressType { ipv6(2) } 1969 -- DESCRIPTION 1970 -- This MIB module requires support for global 1971 -- IPv6 addresses for the mip6BindingHomeAddress 1972 -- object. 1973 -- 1974 -- OBJECT mip6BindingHomeAddress 1975 -- SYNTAX InetAddress (SIZE(16)) 1976 -- DESCRIPTION 1977 -- This MIB module requires support for global 1978 -- IPv6 addresses for the mip6BindingHomeAddress 1979 -- object. 1980 -- 1981 " 1982 MODULE -- this module 1983 MANDATORY-GROUPS { pmip6SystemGroup, 1984 pmip6BindingCacheGroup, 1985 pmip6StatsGroup 1986 } 1988 ::= { pmip6Compliances 2 } 1990 pmip6CoreReadOnlyCompliance MODULE-COMPLIANCE 1991 STATUS current 1992 DESCRIPTION 1993 "The compliance statement for SNMP entities 1994 that implement the PMIPV6-MIB without support. 1995 for read-write (i.e., in read-only mode). 1996 " 1997 MODULE -- this module 1998 MANDATORY-GROUPS { pmip6SystemGroup 1999 } 2000 ::= { pmip6Compliances 3 } 2002 pmip6ReadOnlyCompliance2 MODULE-COMPLIANCE 2003 STATUS current 2004 DESCRIPTION 2005 "The compliance statement for SNMP entities 2006 that implement the PMIPV6-MIB without support. 2007 for read-write (i.e., in read-only mode). 2009 There are a number of INDEX objects that cannot be 2010 represented in the form of OBJECT clauses in 2011 SMIv2, but for which there are compliance 2012 requirements, expressed in OBJECT clause form in 2013 this description: 2015 -- OBJECT mip6BindingHomeAddressType 2016 -- SYNTAX InetAddressType { ipv6(2) } 2017 -- DESCRIPTION 2018 -- This MIB module requires support for global 2019 -- IPv6 addresses for the mip6BindingHomeAddress 2020 -- object. 2021 -- 2022 -- OBJECT mip6BindingHomeAddress 2023 -- SYNTAX InetAddress (SIZE(16)) 2024 -- DESCRIPTION 2025 -- This MIB module requires support for global 2026 -- IPv6 addresses for the mip6BindingHomeAddress 2027 -- object. 2028 -- 2029 " 2030 MODULE -- this module 2031 MANDATORY-GROUPS { pmip6SystemGroup, 2032 pmip6BindingCacheGroup 2034 } 2035 ::= { pmip6Compliances 4 } 2037 pmip6MagCoreCompliance MODULE-COMPLIANCE 2038 STATUS current 2039 DESCRIPTION 2040 "The compliance statement for SNMP entities 2041 which implement the PMIPV6-MIB. 2042 There are a number of INDEX objects that cannot be 2043 represented in the form of OBJECT clauses in 2044 SMIv2, but for which there are compliance 2045 requirements, expressed in OBJECT clause form in 2046 this description: 2047 -- OBJECT pmip6MagProxyCOAType 2048 -- SYNTAX InetAddressType { ipv6(2) } 2049 -- DESCRIPTION 2050 -- This MIB module requires support for global 2051 -- IPv6 addresses for the pmip6MagProxyCOA 2052 -- object. 2053 -- 2054 -- OBJECT pmip6MagProxyCOA 2055 -- SYNTAX InetAddress (SIZE(16)) 2056 -- DESCRIPTION 2057 -- This MIB module requires support for global 2058 -- IPv6 addresses for the pmip6MagProxyCOAType 2059 -- object. 2060 -- 2061 -- OBJECT pmip6MagHomeNetworkPrefixType 2062 -- SYNTAX InetAddressType { ipv6(2) } 2063 -- DESCRIPTION 2064 -- This MIB module requires support for global 2065 -- IPv6 addresses for the pmip6MagHomeNetworkPrefix 2066 -- object. 2067 -- 2068 " 2069 MODULE -- this module 2070 MANDATORY-GROUPS { pmip6MagSystemGroup 2071 } 2072 ::= { pmip6Compliances 5 } 2074 pmip6MagCompliance2 MODULE-COMPLIANCE 2075 STATUS current 2076 DESCRIPTION 2077 "The compliance statement for SNMP entities that 2078 implement the PMIPV6-MIB for monitoring configuration 2079 related information, registration details, and 2080 statistics on a mobile access gateway. 2082 There are a number of INDEX objects that cannot be 2083 represented in the form of OBJECT clauses in 2084 SMIv2, but for which there are compliance 2085 requirements, expressed in OBJECT clause form in 2086 this description: 2088 -- OBJECT pmip6MagProxyCOAType 2089 -- SYNTAX InetAddressType { ipv6(2) } 2090 -- DESCRIPTION 2091 -- This MIB module requires support for global 2092 -- IPv6 addresses for the pmip6MagProxyCOA 2093 -- object. 2094 -- 2095 -- OBJECT pmip6MagProxyCOA 2096 -- SYNTAX InetAddress (SIZE(16)) 2097 -- DESCRIPTION 2098 -- This MIB module requires support for global 2099 -- IPv6 addresses for the pmip6MagProxyCOAType 2100 -- object. 2101 -- 2102 -- OBJECT pmip6MagHomeNetworkPrefixType 2103 -- SYNTAX InetAddressType { ipv6(2) } 2104 -- DESCRIPTION 2105 -- This MIB module requires support for global 2106 -- IPv6 addresses for the pmip6MagHomeNetworkPrefix 2107 -- object. 2108 -- 2109 -- OBJECT pmip6MagHomeNetworkPrefix 2110 -- SYNTAX InetAddress (SIZE(16)) 2111 -- DESCRIPTION 2112 -- This MIB module requires support for global 2113 -- IPv6 addresses for the pmip6MagHomeNetworkPrefix 2114 -- object. 2115 -- 2117 -- OBJECT mip6MnHomeAddressType 2118 -- SYNTAX InetAddressType { ipv6(2) } 2119 -- DESCRIPTION 2120 -- This MIB module requires support for global 2121 -- IPv6 addresses for the mip6MnHomeAddress 2122 -- object. 2123 -- 2124 -- OBJECT mip6MnHomeAddress 2125 -- SYNTAX InetAddress (SIZE(16)) 2126 -- DESCRIPTION 2127 -- This MIB module requires support for global 2128 -- IPv6 addresses for the mip6MnHomeAddress 2129 -- object. 2130 -- 2131 -- OBJECT mip6MnBLNodeAddressType 2132 -- SYNTAX InetAddressType { ipv6(2) } 2133 -- DESCRIPTION 2134 -- This MIB module requires support for global 2135 -- IPv6 addresses for the mip6MnBLNodeAddress 2136 -- object. 2137 -- 2138 -- OBJECT mip6MnBLNodeAddress 2139 -- SYNTAX InetAddress (SIZE(16)) 2140 -- DESCRIPTION 2141 -- This MIB module requires support for global 2142 -- IPv6 addresses for the mip6MnBLNodeAddress 2143 -- object. 2144 " 2145 MODULE -- this module 2146 MANDATORY-GROUPS { pmip6MagSystemGroup, 2147 pmip6MagConfigurationGroup, 2148 pmip6MagRegistrationGroup 2149 } 2150 ::= { pmip6Compliances 6 } 2152 pmip6MagReadOnlyCompliance MODULE-COMPLIANCE 2153 STATUS current 2154 DESCRIPTION 2155 "The compliance statement for SNMP entities that 2156 implement the PMIPV6-MIB without support for read- 2157 write (i.e., in read-only mode) and with support 2158 for monitoring configuration related information, 2159 registration details, and statistics on a mobile 2160 access gateway. 2162 There are a number of INDEX objects that cannot be 2163 represented in the form of OBJECT clauses in 2164 SMIv2, but for which there are compliance 2165 requirements, expressed in OBJECT clause form in 2166 this description: 2168 -- OBJECT pmip6MagProxyCOAType 2169 -- SYNTAX InetAddressType { ipv6(2) } 2170 -- DESCRIPTION 2171 -- This MIB module requires support for global 2172 -- IPv6 addresses for the pmip6MagProxyCOA 2173 -- object. 2174 -- 2175 -- OBJECT pmip6MagProxyCOA 2176 -- SYNTAX InetAddress (SIZE(16)) 2177 -- DESCRIPTION 2178 -- This MIB module requires support for global 2179 -- IPv6 addresses for the pmip6MagProxyCOAType 2180 -- object. 2181 -- 2182 -- OBJECT pmip6MagHomeNetworkPrefixType 2183 -- SYNTAX InetAddressType { ipv6(2) } 2184 -- DESCRIPTION 2185 -- This MIB module requires support for global 2186 -- IPv6 addresses for the pmip6MagHomeNetworkPrefix 2187 -- object. 2188 -- 2189 -- OBJECT pmip6MagHomeNetworkPrefix 2190 -- SYNTAX InetAddress (SIZE(16)) 2191 -- DESCRIPTION 2192 -- This MIB module requires support for global 2193 -- IPv6 addresses for the pmip6MagHomeNetworkPrefix 2194 -- object. 2195 -- 2197 -- OBJECT mip6MnHomeAddressType 2198 -- SYNTAX InetAddressType { ipv6(2) } 2199 -- DESCRIPTION 2200 -- This MIB module requires support for global 2201 -- IPv6 addresses for the mip6MnHomeAddress 2202 -- object. 2203 -- 2204 -- OBJECT mip6MnHomeAddress 2205 -- SYNTAX InetAddress (SIZE(16)) 2206 -- DESCRIPTION 2207 -- This MIB module requires support for global 2208 -- IPv6 addresses for the mip6MnHomeAddress 2209 -- object. 2210 -- 2211 -- OBJECT mip6MnBLNodeAddressType 2212 -- SYNTAX InetAddressType { ipv6(2) } 2213 -- DESCRIPTION 2214 -- This MIB module requires support for global 2215 -- IPv6 addresses for the mip6MnBLNodeAddress 2216 -- object. 2217 -- 2218 -- OBJECT mip6MnBLNodeAddress 2219 -- SYNTAX InetAddress (SIZE(16)) 2220 -- DESCRIPTION 2221 -- This MIB module requires support for global 2222 -- IPv6 addresses for the mip6MnBLNodeAddress 2223 -- object. 2224 " 2225 MODULE -- this module 2226 MANDATORY-GROUPS { pmip6MagSystemGroup, 2227 pmip6MagConfigurationGroup, 2228 pmip6MagRegistrationGroup 2229 } 2230 ::= { pmip6Compliances 7 } 2232 pmip6LmaCoreCompliance MODULE-COMPLIANCE 2233 STATUS current 2234 DESCRIPTION 2235 "The compliance statement for SNMP entities 2236 which implement the PMIPV6-MIB. 2237 There are a number of INDEX objects that cannot be 2238 represented in the form of OBJECT clauses in 2239 SMIv2, but for which there are compliance 2240 requirements, expressed in OBJECT clause form in 2241 this description: 2242 -- OBJECT pmip6LmaLMAAType 2243 -- SYNTAX InetAddressType { ipv6(2) } 2244 -- DESCRIPTION 2245 -- This MIB module requires support for global 2246 -- IPv6 addresses for the pmip6LmaLMAA 2247 -- object. 2248 -- 2249 -- OBJECT pmip6LmaLMAA 2250 -- SYNTAX InetAddress (SIZE(16)) 2251 -- DESCRIPTION 2252 -- This MIB module requires support for global 2253 -- IPv6 addresses for the pmip6LmaLMAA 2254 -- object. 2255 -- 2256 " 2257 MODULE -- this module 2258 MANDATORY-GROUPS { pmip6LmaSystemGroup 2259 } 2260 ::= { pmip6Compliances 8 } 2262 pmip6LmaCompliance2 MODULE-COMPLIANCE 2263 STATUS current 2264 DESCRIPTION 2265 "The compliance statement for SNMP entities that 2266 implement the PMIPV6-MIB for monitoring configuration 2267 related information, registration details, and statistics 2268 on a mobile access gateway. 2270 There are a number of INDEX objects that cannot be 2271 represented in the form of OBJECT clauses in 2272 SMIv2, but for which there are compliance 2273 requirements, expressed in OBJECT clause form in 2274 this description: 2276 -- OBJECT pmip6LmaLMAAType 2277 -- SYNTAX InetAddressType { ipv6(2) } 2278 -- DESCRIPTION 2279 -- This MIB module requires support for global 2280 -- IPv6 addresses for the pmip6LmaLMAA 2281 -- object. 2282 -- 2283 -- OBJECT pmip6LmaLMAA 2284 -- SYNTAX InetAddress (SIZE(16)) 2285 -- DESCRIPTION 2286 -- This MIB module requires support for global 2287 -- IPv6 addresses for the pmip6LmaLMAA 2288 -- object. 2289 -- 2290 -- OBJECT pmip6LmaHomeNetworkPrefixType 2291 -- SYNTAX InetAddressType { ipv6(2) } 2292 -- DESCRIPTION 2293 -- This MIB module requires support for global 2294 -- IPv6 addresses for the pmip6LmaHomeNetworkPrefix 2295 -- object. 2296 -- 2297 -- OBJECT pmip6LmaHomeNetworkPrefix 2298 -- SYNTAX InetAddress (SIZE(16)) 2299 -- DESCRIPTION 2300 -- This MIB module requires support for global 2301 -- IPv6 addresses for the pmip6LmaHomeNetworkPrefix 2302 -- object. 2304 -- 2306 -- OBJECT mip6MnHomeAddressType 2307 -- SYNTAX InetAddressType { ipv6(2) } 2308 -- DESCRIPTION 2309 -- This MIB module requires support for global 2310 -- IPv6 addresses for the mip6MnHomeAddress 2311 -- object. 2312 -- 2313 -- OBJECT mip6MnHomeAddress 2314 -- SYNTAX InetAddress (SIZE(16)) 2315 -- DESCRIPTION 2316 -- This MIB module requires support for global 2317 -- IPv6 addresses for the mip6MnHomeAddress 2318 -- object. 2319 -- 2320 -- OBJECT mip6MnBLNodeAddressType 2321 -- SYNTAX InetAddressType { ipv6(2) } 2322 -- DESCRIPTION 2323 -- This MIB module requires support for global 2324 -- IPv6 addresses for the mip6MnBLNodeAddress 2325 -- object. 2326 -- 2327 -- OBJECT mip6MnBLNodeAddress 2328 -- SYNTAX InetAddress (SIZE(16)) 2329 -- DESCRIPTION 2330 -- This MIB module requires support for global 2331 -- IPv6 addresses for the mip6MnBLNodeAddress 2332 -- object. 2333 " 2334 MODULE -- this module 2335 MANDATORY-GROUPS { pmip6LmaSystemGroup, 2336 pmip6LmaConfigurationGroup 2337 } 2338 ::= { pmip6Compliances 9 } 2340 pmip6MagNotificationCompliance MODULE-COMPLIANCE 2341 STATUS current 2342 DESCRIPTION 2343 "The compliance statement for SNMP entities that 2344 implement the PMIPv6-MIB and support Notification 2345 from the mobile access gateway. 2346 " 2347 MODULE -- this module 2348 MANDATORY-GROUPS { pmip6MagNotificationGroup 2349 } 2350 ::= { pmip6Compliances 10 } 2352 pmip6LmaNotificationCompliance MODULE-COMPLIANCE 2353 STATUS current 2354 DESCRIPTION 2355 "The compliance statement for SNMP entities that 2356 implement the PMIPv6-MIB and support Notification 2357 from the LMA. 2358 " 2359 MODULE -- this module 2360 MANDATORY-GROUPS { pmip6LmaNotificationGroup 2361 } 2362 ::= { pmip6Compliances 11 } 2364 END 2366 6. Security Considerations 2368 There are a number of management objects defined in this MIB module 2369 with a MAX-ACCESS clause of read-write. Such objects may be 2370 considered sensitive or vulnerable in some network environments. The 2371 support for SET operations in a non-secure environment without proper 2372 protection can have a negative effect on network operations. These 2373 are the tables and objects and the corresponding 2374 sensitivity/vulnerability: 2375 nemoStatus: The value of this object is used to enable or disable 2376 the PMIPv6 functionality on a PMIPv6 entity. Access to this MO 2377 may be abused to disrupt the communication that depends on 2378 PMIPv6. 2379 pmip6MobileNodeGeneratedTimestampInUse : 2380 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType: 2381 pmip6FixedMagLinkLocalAddressOnAllAccessLinks: 2382 pmip6FixedMagLinkLayerAddressOnAllAccessLinks: 2383 pmip6MagEnableMagLocalRouting: 2384 pmip6MagHomeNetworkPrefixLifeTime: 2385 pmip6LmaMinDelayBeforeBCEDelete: 2386 pmip6LmaMaxDelayBeforeNewBCEAssign: 2387 pmip6LmaTimestampValidityWindow: 2388 pmip6LmaHomeNetworkPrefixLifeTime: 2389 Access to the above MOs may be abused to misconfigure PMIPv6 2390 entities and disrupt communications. 2392 Some of the readable objects in this MIB module (i.e., objects with a 2393 MAX-ACCESS other than not-accessible) may be considered sensitive or 2394 vulnerable in some network environments. It is thus important to 2395 control even GET and/or NOTIFY access to these objects and possibly 2396 to even encrypt the values of these objects when sending them over 2397 the network via SNMP. These are the tables and objects and their 2398 sensitivity/vulnerability: 2400 pmip6LmaHomeNetworkPrefixType: 2401 pmip6LmaHomeNetworkPrefix: 2402 pmip6LmaHomeNetworkPrefixLength: 2403 The above address-related objects may be considered to be 2404 particularly sensitive and/or private. 2406 SNMP versions prior to SNMPv3 did not include adequate security. 2407 Even if the network itself is secure (for example by using IPSec), 2408 even then, there is no control as to who on the secure network is 2409 allowed to access and GET/SET (read/change/create/delete) the objects 2410 in this MIB module. 2412 It is RECOMMENDED that implementers consider the security features as 2413 provided by the SNMPv3 framework (see [RFC3410], section 8), 2414 including full support for the SNMPv3 cryptographic mechanisms (for 2415 authentication and privacy). 2417 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2418 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2419 enable cryptographic security. It is then a customer/operator 2420 responsibility to ensure that the SNMP entity giving access to an 2421 instance of this MIB module is properly configured to give access to 2422 the objects only to those principals (users) that have legitimate 2423 rights to indeed GET or SET (change/create/delete) them. 2425 7. IANA Considerations 2427 IANA should assign a base arc in the 'mib-2' (standards track) OID 2428 tree for the 'pmip6MIB' MODULE-IDENTITY defined in the PMIPv6 MIB. 2430 8. References 2432 8.1 Normative References 2434 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 2435 Requirements Levels, BCP 14, RFC 2119, March 1997. 2437 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2438 J., Rose, M. and S. Waldbusser, Structure of 2439 Management Information Version 2 (SMIv2), STD 58, 2440 RFC 2578, April 1999. 2442 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2443 J., Rose, M. and S. Waldbusser, Textual Conventions 2444 for SMIv2, STD 58, RFC 2579, April 1999. 2446 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2447 J., Rose, M. and S. Waldbusser, Conformance 2448 Statements for SMIv2, STD 58, RFC 2580, April 1999. 2450 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility 2451 Support in IPv6 RFC 3775, June 2004. 2453 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, 2454 K., and Patil, B. Proxy Mobile IPv6), RFC 5213, 2455 August 2008. 2457 [RFC4293] Routhier, S., Management Information Base for the 2458 Internet Protocol (IP), RFC 4293, April 2006. 2460 [RFC4001] Daniele, M., Haberman, B., Routhier, S. and 2461 Schoenwaelder, J., Textual Conventions for Internet 2462 Network Addresses, RFC4001, February 2005. 2464 8.2 Informative References 2466 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2467 Introduction and Applicability Statements for 2468 Internet-Standard Management Framework, RFC 3410, 2469 December 2002. 2471 9. Acknowledgments 2473 The following groups and individuals have contributed to this draft 2474 with discussions and comments: 2475 WIDE-netman group 2477 10. Authors' Addresses 2479 Glenn Mansfield Keeni 2480 Cyber Solutions Inc. 2481 6-6-3 Minami Yoshinari 2482 Aoba-ku, Sendai 989-3204 2483 Japan 2485 Phone: +81-22-303-4012 2486 E-mail: glenn@cysols.com 2488 Kazuhide Koide 2489 KDDI CORPORATION 2490 GARDEN AIR TOWER 3-10-10, Iidabashi 2491 Chiyoda-ku, Tokyo, 102-8460 Japan 2493 Phone: +81-3-6678-3378 2494 E-mail: ka-koide@kddi.com 2496 Sri Gundavelli 2497 Cisco Systems 2498 170 W.Tasman Drive, 2499 San Jose, CA 95134 2500 USA 2502 Phone: +1-408-527-6109 2503 E-mail: sgundave@cisco.com 2505 Ryuji Wakikawa 2506 Keio University 2507 Department of Environmental Information, Keio University. 2508 5322 Endo 2509 Fujisawa, Kanagawa 252-8520 2510 Japan 2512 E-mail: ryuji@sfc.wide.ad.jp