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