idnits 2.17.1 draft-ietf-netlmm-pmipv6-mib-08.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 (October 25, 2011) is 4529 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: 'RFC2863' is defined on line 2883, but no explicit reference was found in the text == Unused Reference: 'RFC4282' is defined on line 2889, but no explicit reference was found in the text == Unused Reference: 'RFC4283' is defined on line 2892, 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 (~~), 5 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: March 24, 2012 KDDI Corporation 6 S. Gundavelli 7 Cisco 8 R. Wakikawa 9 Toyota ITC 10 October 25, 2011 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 March 24, 2012. 42 Copyright Notice 44 Copyright (c) 2011 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 can 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 4.1 Textual Conventions ...................................... 4 75 5. MIB Definitions .............................................. 7 76 5.1 Proxy Mobile IPv6 Textual Conventions MIB ................ 7 77 5.2 Proxy Mobile IPv6 MIB .................................... 12 78 6. Security Considerations ...................................... 66 79 7. IANA Considerations .......................................... 67 80 8. References ................................................... 68 81 8.1. Normative References .................................... 68 82 8.2. Informative References .................................. 69 83 9. Acknowledgements ............................................. 70 84 10. Authors' Addresses ........................................... 70 86 1. The Internet-Standard Management Framework 88 For a detailed overview of the documents that describe the current 89 Internet-Standard Management Framework, please refer to section 7 of 90 RFC 3410 [RFC3410]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. MIB objects are generally 94 accessed through the Simple Network Management Protocol (SNMP). 96 Objects in the MIB are defined using the mechanisms defined in the 97 Structure of Management Information (SMI). This memo specifies a MIB 98 module that is compliant to the SMIv2, which is described in STD 58, 99 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 100 [RFC2580]. 102 2. Overview 104 2.1. The Proxy Mobile IPv6 Protocol Entities 105 Proxy Mobile IPv6 (PMIPv6) [RFC5213] is an extension to the Mobile 106 IPv6 (MIPv6) protocol which facilitates network-based localized 107 mobility management (NETLMM) for IPv6 nodes in a PMIPv6 domain. 108 There are three types of entities envisaged by the PMIPv6 protocol. 110 mobile node (MN): In the PMIPv6 context the term mobile node 111 is used to refer to an IP host or router whose mobility is 112 managed by the network. 114 local mobility anchor (LMA): Local Mobility Anchor is the 115 home agent for the mobile node in a Proxy Mobile IPv6 domain. 116 It is the topological anchor point for the mobile node's home 117 network prefix(es) and is the entity that manages the mobile 118 node's binding state. The local mobility anchor has the 119 functional capabilities of a home agent as defined in Mobile 120 IPv6 base specification [RFC3775] with the additional 121 capabilities required for supporting Proxy Mobile IPv6 122 protocol as defined in the PMIPv6 specification [RFC5213]. 124 mobile access gateway (MAG): Mobile Access Gateway is the 125 entity on an access router that manages the mobility-related 126 signaling for a mobile node that is attached to its access 127 link. It is responsible for tracking the mobile node's 128 movements to and from the access link and for signaling the 129 mobile node's local mobility anchor. 131 This document defines a set of managed objects (MOs) that can be used 132 to monitor and control PMIPv6 entities. 134 2.2. Terminology 135 The terminology used in this document is consistent with the 136 definitions used in the Mobile IPv6 protocol specification [RFC3775] 137 and in NETLMM Goals document [RFC4831]. 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 141 "OPTIONAL" in this document are to be interpreted as described in BCP 142 14, RFC 2119 [RFC2119]. 144 3. Proxy Mobile IPv6 Monitoring and Control Requirements 146 For managing a PMIPv6 entity it is necessary to monitor 147 the following: 148 o capabilities of PMIPv6 entities 149 o signaling traffic due to PMIPv6 signaling 150 o binding related details (at LMA and MAG) 151 o binding related statistics (at LMA and MAG) 153 4. MIB Design 155 The basic principle has been to keep the MIB as simple as possible 156 and at the same time to make it effective enough so that the 157 essential needs of monitoring and control are met. 159 The Proxy Mobile IPv6 Management Information Base(PMIPV6-MIB) extends 160 the Mobile IPv6 Management Information Base(MIPV6-MIB). [RFC4295]. 161 It is assumed that PMIPV6-MIB will always be implemented in 162 conjunction with the MOBILEIPV6-MIB [RFC4295]. The PMIPV6-MIB uses 163 the textual conventions defined in the INET-ADDRESS-MIB [RFC4001] and 164 IP-MIB [RFC4293]. 166 The PMIPV6-MIB is composed of the following groups of definitions: 168 - pmip6Core: a generic group containing objects that are 169 common to all the Proxy Mobile IPv6 entities. Objects 170 belonging to this group will be implemented on the 171 corresponding Proxy Mobile IPv6 entity. pmip6BindingCacheTable 172 belongs to this group. 173 - pmip6Mag: this group models the mobile access gateway 174 service. Objects belonging to this group have the "pmip6Mag" 175 prefix and will be implemented on the corresponding MAG. 176 - pmip6Lma: this group models the local mobility anchor 177 service. Objects belonging to this group have the "pmip6Lma" 178 prefix and will be implemented on the corresponding LMA. 179 - pmip6Notifications: defines the set of notifications that 180 will be used to asynchronously monitor the Proxy Mobile 181 IPv6 entities. 183 The tables contained in the above groups are as follows: 184 - pmip6BindingCacheTable: models the Binding Cache on the local 185 mobility anchor. 186 - pmip6MagProxyCOATable: models the Proxy Care-of Addresses 187 configured on the egress interfaces of the mobile access 188 gateway. 189 - pmip6MagMnIdentifierTable: provides a mapping from the 190 MAG-internal pmip6MagMnIndex to the mobile node identifier. 191 - pmip6MagMnLLIdentifierTable: provides a mapping from the 192 MAG-internal pmip6MagMnLLIndex to the corresponding interface 193 of the mobile node link layer identifier. 194 - pmip6MagHomeNetworkPrefixTable : contains the Home Network 195 Prefixes assigned to interfaces of all mobile nodes attached 196 to the MAG. Each interface is distinguished by the attached 197 mobile node's identifier (MN-Identifier) and the link layer 198 identifier (MN-LL-Identifier). 199 - pmip6MagBLTable: models the Binding Update List (BL) that 200 includes Proxy MIPv6 related information and is maintained by 201 the mobile access gateway. 202 - pmip6MagMnProfileTable: contains the mobile node's policy 203 profile that includes the essential operational parameters that 204 are required by the network entities for managing the mobile 205 node's mobility service. 206 - pmip6LmaLMAATable: contains the LMA Addresses that are 207 configured on the local mobility anchor. Each LMA Address acts 208 as a transport endpoint of the tunnel between the local 209 mobility anchor and the mobile access gateway. 210 - pmip6LmaMnIdentifierTable: provides a mapping from the 211 LMA-internal pmip6BindingMnIndex to the mobile node identifier. 212 - pmip6LmaMnLLIdentifierTable: provides a mapping from the 213 LMA-internal pmip6BindingMnLLIndex to the corresponding 214 interface of the mobile node link layer identifier. 215 - pmip6LmaHomeNetworkPrefixTable : contains the list of Home 216 Network Prefixes assigned to the connected interfaces of the 217 mobile nodes anchored on an LMA. 219 4.1 Textual Conventions 221 A Proxy Mobile IPv6 Textual Conventions MIB module containing 222 Textual Conventions to represent commonly used Proxy 223 Mobile-IPv6 management information is defined. The intent 224 is that these TEXTUAL CONVENTIONS (TCs) will be imported and used 225 in PMIPv6 related MIB modules that would otherwise define their own 226 representation(s). 228 5. MIB Definitions 230 5.1 Proxy Mobile IPv6 Textual Conventions MIB 232 PMIPV6-TC-MIB DEFINITIONS ::= BEGIN 233 IMPORTS 234 MODULE-IDENTITY, mib-2, Unsigned32 235 FROM SNMPv2-SMI -- [RFC2578] 236 TEXTUAL-CONVENTION 237 FROM SNMPv2-TC; -- [RFC2579] 239 pmip6TCMIB MODULE-IDENTITY 240 LAST-UPDATED "201109250000Z" -- 25th September, 2011 241 ORGANIZATION "IETF NETLMM Working Group" 242 CONTACT-INFO 243 " Glenn Mansfield Keeni 244 Postal: Cyber Solutions Inc. 245 6-6-3, Minami Yoshinari 246 Aoba-ku, Sendai, Japan 989-3204. 247 Tel: +81-22-303-4012 248 Fax: +81-22-303-4015 249 E-mail: glenn@cysols.com 251 Sri Gundavelli 252 Postal: Cisco Systems 253 170 W.Tasman Drive, 254 San Jose, CA 95134 255 USA 256 Tel: +1-408-527-6109 257 E-mail: sgundave@cisco.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 Ryuji Wakikawa 267 Postal: TOYOTA InfoTechnology Center, U.S.A., Inc. 268 465 Bernardo Avenue 269 Mountain View, CA 270 94043 271 USA 272 E-mail: ryuji@us.toyota-itc.com 274 Support Group E-mail: netlmm@ietf.org 275 " 277 DESCRIPTION 278 "This MIB module provides textual conventions for 279 Proxy Mobile IPv6 Management information. 281 Copyright (C) The IETF Trust (2011). This version of 282 this MIB module is part of RFC XXXX; see the RFC itself for 283 full legal notices. 284 " 285 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 286 -- note 288 REVISION "201109250000Z" -- 25th September, 2011 289 DESCRIPTION 290 "The initial version, published as RFC XXXX." 292 -- RFC Ed.: replace XXXX with the actual RFC number & remove this 293 -- note 295 ::= { mib-2 YYY1 } -- Will be assigned by IANA 297 -- IANA Reg.: Please assign a value for "YYY1" under the 298 -- 'mib-2' subtree and record the assignment in the SMI 299 -- Numbers registry. 301 -- RFC Ed.: When the above assignment has been made, please 302 -- remove the above note 303 -- replace "YYY1" here with the assigned value and 304 -- remove this note. 306 -- ------------------------------------------------------------- 307 -- Textual Conventions 308 -- ------------------------------------------------------------- 309 Pmip6TimeStamp64 ::= TEXTUAL-CONVENTION 310 DISPLAY-HINT "6d:2d" 311 STATUS current 312 DESCRIPTION 313 "A 64-bit unsigned integer field containing a timestamp. 314 The value indicates the elapsed time since January 1, 315 1970, 00:00 UTC, by using a fixed point format. In this 316 format, the integer number of seconds is contained in 317 the first 48 bits of the field, and the remaining 16 318 bits indicate the number of 1/65536 fractions of a 319 second. 320 " 321 REFERENCE 322 "RFC 5213: Section 8.8" 323 SYNTAX OCTET STRING (SIZE (8)) 325 Pmip6MnIdentifier ::= TEXTUAL-CONVENTION 326 DISPLAY-HINT "255a" 327 STATUS current 328 DESCRIPTION 329 "The identity of a mobile node in the Proxy Mobile IPv6 330 domain. This is the stable identifier of a mobile node 331 that the mobility entities in a Proxy Mobile IPv6 domain 332 can always acquire and use for predictably identifying 333 a mobile node. Various forms of identifiers can be used 334 to identify a mobile node (MN). Two examples are a 335 Network Access Identifier (NAI) and an opaque 336 identifier applicable to a particular application. 337 " 338 REFERENCE 339 "RFC 4283: Section 3" 340 SYNTAX OCTET STRING (SIZE (0..255)) 342 Pmip6MnLLIdentifier ::= TEXTUAL-CONVENTION 343 DISPLAY-HINT "255a" 344 STATUS current 345 DESCRIPTION 346 "An identifier that identifies the attached interface of 347 a mobile node. 348 " 349 REFERENCE 350 "RFC 5213: Section 8.6" 351 SYNTAX OCTET STRING (SIZE (0..255)) 353 Pmip6MnIndex ::= TEXTUAL-CONVENTION 354 DISPLAY-HINT "d" 355 STATUS current 356 DESCRIPTION 357 "A unique integer value, greater than zero, assigned to 358 each mobile node that is currently attached to the 359 Proxy Mobile IPv6 domain by the management system. 360 It is recommended that the values are assigned in a 361 monotonically increasing order starting from 1. It may 362 wrap after reaching its maximum value. The value for 363 each mobile node must remain constant at least from one 364 re-initialization of the entity's network management 365 system to the next re-initialization. 366 " 367 SYNTAX Unsigned32 (1..4294967295) 368 Pmip6MnLLIndex ::= TEXTUAL-CONVENTION 369 DISPLAY-HINT "d" 370 STATUS current 371 DESCRIPTION 372 "A unique integer value, greater than zero, assigned to 373 each interface of a mobile node that is currently 374 attached to the Proxy Mobile IPv6 domain by the 375 management system. 376 It is recommended that the values are assigned in a 377 monotonically increasing order starting from 1. It may 378 wrap after reaching its maximum value. The value for 379 each interface of a mobile node must remain constant at 380 least from one re-initialization of the entity's network 381 management system to the next re-initialization. 382 " 383 SYNTAX Unsigned32 (1..4294967295) 385 Pmip6MnInterfaceATT ::= TEXTUAL-CONVENTION 386 STATUS current 387 DESCRIPTION 388 "The object specifies the access technology which 389 connects the mobile node to the access link on the 390 mobile access gateway. 391 The enumerated values and the corresponding access 392 technology are as follows: 393 reserved (0): Reserved (Not used) 394 logicalNetworkInterface (1): Logical network interface 395 pointToPointInterface (2): Point to point interface 396 ethernet (3): Ethernet interface 397 wirelessLan (4): Wireless LAN interface 398 wimax (5): Wimax interface 399 threeGPPGERAN (6): 3GPP GERAN 400 threeGPPUTRAN (7): 3GPP UTRAN 401 threeGPPETRAN (8): 3GPP ETRAN 402 threeGPP2eHRPD (9): 3GPP2 eHRPD 403 threeGPP2HRPD (10): 3GPP2 HRPD 404 threeGPP21xRTT (11): 3GPP2 1xRTT 405 threeGPP2UMB (12): 3GPP2 UMB 406 " 407 REFERENCE 408 "RFC 5213: Section 8.5, 409 http://www.iana.org/assignments/mobility-parameters/ 410 mobility-parameters.txt" 412 SYNTAX INTEGER 413 { 414 reserved (0), 415 logicalNetworkInterface(1), 416 pointToPointInterface (2), 417 ethernet (3), 418 wirelessLan (4), 419 wimax (5), 420 threeGPPGERAN (6), 421 threeGPPUTRAN (7), 422 threeGPPETRAN (8), 423 threeGPP2eHRPD (9), 424 threeGPP2HRPD (10), 425 threeGPP21xRTT (11), 426 threeGPP2UMB (12) 427 } 428 END 430 5.2 The Proxy Mobile-IPv6 MIB 432 PMIPV6-MIB DEFINITIONS ::= BEGIN 433 IMPORTS 434 MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32, 435 Unsigned32, OBJECT-TYPE, NOTIFICATION-TYPE 436 FROM SNMPv2-SMI -- RFC 2578 437 PhysAddress, TimeStamp, 438 TruthValue 439 FROM SNMPv2-TC -- RFC 2579 440 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 441 FROM SNMPv2-CONF -- RFC 2580 442 InetAddressType, InetAddress, InetAddressPrefixLength 443 FROM INET-ADDRESS-MIB -- RFC 4001 444 Ipv6AddressIfIdentifierTC 445 FROM IP-MIB -- RFC 4293 446 mip6MnBLEntry, mip6BindingCacheEntry 447 FROM MOBILEIPV6-MIB -- RFC 4295 448 Pmip6TimeStamp64, Pmip6MnIdentifier, 449 Pmip6MnLLIdentifier, Pmip6MnIndex, Pmip6MnLLIndex, 450 Pmip6MnInterfaceATT 451 FROM PMIPV6-TC-MIB -- RFC XXXX 452 ; 454 pmip6MIB MODULE-IDENTITY 455 LAST-UPDATED "201109250000Z" -- 25th September, 2011 456 ORGANIZATION "IETF NETLMM Working Group" 457 CONTACT-INFO 458 " Glenn Mansfield Keeni 459 Postal: Cyber Solutions Inc. 460 6-6-3, Minami Yoshinari 461 Aoba-ku, Sendai 989-3204, Japan. 462 Tel: +81-22-303-4012 463 Fax: +81-22-303-4015 464 E-mail: glenn@cysols.com 466 Kazuhide Koide 467 Postal: KDDI Corporation 468 GARDEN AIR TOWER 3-10-10, Iidabashi 469 Chiyoda-ku, Tokyo 102-8460, Japan. 470 Tel: +81-3-6678-3378 471 E-mail: ka-koide@kddi.com 472 Sri Gundavelli 473 Postal: Cisco 474 170 W.Tasman Drive, 475 San Jose, CA 95134 476 USA 477 Tel: +1-408-527-6109 478 E-mail: sgundave@cisco.com 480 Ryuji Wakikawa 481 Postal: TOYOTA InfoTechnology Center, U.S.A., Inc. 482 465 Bernardo Avenue 483 Mountain View, CA 484 94043 485 USA 486 E-mail: ryuji@us.toyota-itc.com 488 Support Group E-mail: netlmm@ietf.org" 490 DESCRIPTION 491 "The MIB module for monitoring and controlling PMIPv6 492 entities. 493 " 495 -- RFC Ed.: replace XXXX with actual RFC number and remove this 496 -- note 498 REVISION "201109250000Z" -- 25th September 2011 499 DESCRIPTION "Initial version, published as RFC XXXX." 501 -- RFC Ed.: replace XXXX with actual RFC number and remove this 502 -- note 504 ::= { mib-2 YYY2 } -- will be assigned by IANA 506 -- IANA Reg.: Please assign a value for "YYY2" under the 'mib-2' 507 -- subtree and record the assignment in the SMI Numbers 508 -- registry. 509 -- 510 -- RFC Ed.: When the above assignment has been made, please 511 -- remove the above note 512 -- replace "YYY" here with the assigned value and 513 -- remove this note. 515 -- The PMIPv6 MIB has the following 5 primary groups 517 pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 } 518 pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 } 519 pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 } 520 pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 } 521 pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 } 522 pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 } 524 -- The sub groups 526 pmip6System OBJECT IDENTIFIER ::= { pmip6Core 1 } 527 pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 } 528 pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 } 529 pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 } 531 pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 } 532 pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 } 533 pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 } 535 pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 } 536 pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 } 538 -- The pmip6Stats group has the following sub groups 540 pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 } 542 -- 543 -- 544 -- pmip6System group 545 -- 546 -- 547 pmip6Capabilities OBJECT-TYPE 548 SYNTAX BITS { 549 mobilityAccessGateway (0), 550 localMobilityAnchor (1) 551 } 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "This object indicates the PMIPv6 functions that 556 are supported by this managed entity. Multiple 557 Proxy Mobile IPv6 functions may be supported by 558 a single entity. 559 mobilityAccessGateway(0) indicates the availability 560 of the mobility access gateway function. 561 localMobilityAnchor(1) indicates the availability 562 of the local mobility anchor function. 563 " 564 REFERENCE 565 "RFC 3775 : Section 3.2, 4.1" 566 ::= { pmip6System 1 } 568 pmip6MobileNodeGeneratedTimestampInUse OBJECT-TYPE 569 SYNTAX TruthValue 570 MAX-ACCESS read-write 571 STATUS current 572 DESCRIPTION 573 "This flag indicates whether or not the mobile node 574 generated timestamp mechanism is in use in that 575 Proxy Mobile IPv6 domain. 576 true(1) if the local mobility anchors and mobile 577 access gateways in that Proxy Mobile IPv6 domain 578 apply the mobile node generated timestamp 579 considerations. 580 false(0) indicates that the mobile node generated 581 timestamp mechanism is not in use in that Proxy 582 Mobile IPv6 domain. 583 The default value for this flag is set to 'false'. 584 " 585 REFERENCE 586 "RFC 5213: Section 5.5, 9.3" 587 DEFVAL { false } 588 ::= { pmip6Conf 1 } 590 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType OBJECT-TYPE 591 SYNTAX InetAddressType 592 MAX-ACCESS read-write 593 STATUS current 594 DESCRIPTION 595 "The InetAddressType of the 596 pmip6FixedMagLinkLocalAddressOnAllAccessLinks 597 that follows. 598 " 599 ::= { pmip6Conf 2 } 601 pmip6FixedMagLinkLocalAddressOnAllAccessLinks OBJECT-TYPE 602 SYNTAX InetAddress 603 MAX-ACCESS read-write 604 STATUS current 605 DESCRIPTION 606 "This variable indicates the link-local address value 607 that all the mobile access gateways should use on 608 any of the access links shared with any of the 609 mobile nodes in that Proxy Mobile IPv6 domain. If 610 this variable is initialized with all zeroes, it 611 implies that the use of fixed link-local address mode 612 is not enabled for that Proxy Mobile IPv6 domain." 613 REFERENCE 614 "RFC 5213: Section 2.2, 6.8, 6.9.1.1, 6.9.3, 9.3" 615 ::= { pmip6Conf 3 } 617 pmip6FixedMagLinkLayerAddressOnAllAccessLinks OBJECT-TYPE 618 SYNTAX PhysAddress 619 MAX-ACCESS read-write 620 STATUS current 621 DESCRIPTION 622 "This variable indicates the link-layer address value 623 that all the mobile access gateways should use on 624 any of the access links shared with any of the mobile 625 nodes in that Proxy Mobile IPv6 domain. For access 626 technologies where there is no link-layer address, 627 this variable MUST be initialized with all zeroes. 628 " 629 REFERENCE 630 "RFC 5213: Section 6.9.3, 9.3" 631 ::= { pmip6Conf 4 } 633 pmip6MagStatus OBJECT-TYPE 634 SYNTAX INTEGER { enabled(1), disabled(2) } 635 MAX-ACCESS read-write 636 STATUS current 637 DESCRIPTION 638 "This object indicates whether the PMIPv6 mobile 639 access gateway function is enabled for the managed 640 entity. 642 Changing the status from enabled(1) to disabled(2) 643 will terminate the PMIPv6 mobile access gateway 644 function. On the other hand, changing the status 645 from disabled(2) to enabled(1) will start the PMIPv6 646 mobile access gateway function. 648 The value of this object MUST remain unchanged 649 across reboots of the managed entity. 650 " 651 DEFVAL { disabled } 652 ::= { pmip6MagSystem 1 } 654 pmip6MagProxyCOATable OBJECT-TYPE 655 SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "This table models the Proxy Care-of Addresses 660 configured on the egress interfaces of the mobile access 661 gateway. This address is the transport endpoint of the 662 tunnel between the local mobility anchor and the mobile 663 access gateway. 665 Entries in this table are not required to survive 666 a reboot of the managed entity. 667 " 668 REFERENCE 669 "RFC 5213: Section 2.2, 6.10" 670 ::= { pmip6MagSystem 2 } 672 pmip6MagProxyCOAEntry OBJECT-TYPE 673 SYNTAX Pmip6MagProxyCOAEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "This entry represents a conceptual row in the 678 Proxy-CoA table. It represents a Proxy Care-of 679 address on the mobile access gateway. 681 Implementers need to be aware that if the total 682 number of octets in pmip6MagProxyCOA 683 exceeds 113 then OIDs of column 684 instances in this row will have more than 128 685 sub-identifiers and cannot be accessed using 686 SNMPv1, SNMPv2c, or SNMPv3. 687 " 688 INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA } 689 ::= { pmip6MagProxyCOATable 1 } 691 Pmip6MagProxyCOAEntry ::= 692 SEQUENCE { 693 pmip6MagProxyCOAType InetAddressType, 694 pmip6MagProxyCOA InetAddress, 695 pmip6MagProxyCOAState INTEGER 696 } 698 pmip6MagProxyCOAType OBJECT-TYPE 699 SYNTAX InetAddressType 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "The InetAddressType of the pmip6MagProxyCOA 704 that follows. 705 " 706 ::= { pmip6MagProxyCOAEntry 1 } 708 pmip6MagProxyCOA OBJECT-TYPE 709 SYNTAX InetAddress 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "The Proxy-CoA configured on the egress interface of the 714 mobile access gateway. 716 The type of the address represented by this object 717 is specified by the corresponding 718 pmip6MagProxyCOAType object. 719 " 720 REFERENCE 721 "RFC 5213: Section 2.2, 6.10" 722 ::= { pmip6MagProxyCOAEntry 2 } 724 pmip6MagProxyCOAState OBJECT-TYPE 725 SYNTAX INTEGER { 726 unknown(1), 727 activated(2), 728 tunneled(3) 729 } 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "This object indicates the state of the Proxy-CoA: 734 unknown -- The state of the Proxy-CoA 735 cannot be determined. 736 activated -- The Proxy-CoA is ready to establish 737 a tunnel. This state SHOULD be 738 indicated when the MAG is up but has 739 no mobile node. 740 tunneled -- Bi-directional tunnel is established 741 using the Proxy-CoA. 742 " 743 ::= { pmip6MagProxyCOAEntry 3 } 745 pmip6MagEnableMagLocalRouting OBJECT-TYPE 746 SYNTAX TruthValue 747 MAX-ACCESS read-write 748 STATUS current 749 DESCRIPTION 750 "This flag indicates whether or not the mobile access 751 gateway is allowed to enable local routing of the 752 traffic exchanged between a visiting mobile node and 753 a correspondent node that is locally connected to one 754 of the interfaces of the mobile access gateway. 755 The correspondent node can be another visiting mobile 756 node as well, or a local fixed node. 757 true(1) indicates the mobile access gateway routes the 758 traffic locally. 759 false(0) indicates that the mobile access gateway 760 reverse tunnels all the traffic to the mobile node's 761 local mobility anchor. 763 The default value for this flag is set to false." 764 REFERENCE 765 "RFC 5213: Section 9.2" DEFVAL { false } 766 ::= { pmip6MagConf 1 } 768 pmip6MagMnIdentifierTable OBJECT-TYPE 769 SYNTAX SEQUENCE OF Pmip6MagMnIdentifierEntry 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "A table containing the indentifiers of mobile nodes 774 attached to the MAG. 775 Entries in this table are not required to survive 776 a reboot of the managed entity. 777 " 778 REFERENCE 779 "RFC 5213: Section 2.2, 6.1" 780 ::= { pmip6MagConf 2 } 782 pmip6MagMnIdentifierEntry OBJECT-TYPE 783 SYNTAX Pmip6MagMnIdentifierEntry 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "An entry in the mobile node identifier table. 789 " 790 INDEX { pmip6MagBLMnIndex 791 } 792 ::= { pmip6MagMnIdentifierTable 1 } 794 Pmip6MagMnIdentifierEntry ::= 795 SEQUENCE { 796 pmip6MagMnIdentifier Pmip6MnIdentifier 797 } 799 pmip6MagMnIdentifier OBJECT-TYPE 800 SYNTAX Pmip6MnIdentifier 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION 804 "The identity of a mobile node in the Proxy Mobile IPv6 805 domain. 806 " 807 REFERENCE 808 "RFC 5213: Section 2.2, 6.1" 809 ::= { pmip6MagMnIdentifierEntry 1 } 811 pmip6MagMnLLIdentifierTable OBJECT-TYPE 812 SYNTAX SEQUENCE OF Pmip6MagMnLLIdentifierEntry 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "A table containing the link layer indentifiers 817 of the interfaces of the mobile nodes attached 818 to the MAG. 819 Entries in this table are not required to survive 820 a reboot of the managed entity. 821 " 822 REFERENCE 823 "RFC 5213: Section 2.2, 6.1" 824 ::= { pmip6MagConf 3 } 826 pmip6MagMnLLIdentifierEntry OBJECT-TYPE 827 SYNTAX Pmip6MagMnLLIdentifierEntry 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION 831 "An entry in the mobile node link layer identifier 832 table. 833 " 834 INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex 835 } 836 ::= { pmip6MagMnLLIdentifierTable 1 } 838 Pmip6MagMnLLIdentifierEntry ::= 839 SEQUENCE { 840 pmip6MagMnLLIdentifier Pmip6MnLLIdentifier 841 } 843 pmip6MagMnLLIdentifier OBJECT-TYPE 844 SYNTAX Pmip6MnLLIdentifier 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "The link-layer identifier of the mobile node's 849 connected interface on the access link. 850 " 851 REFERENCE 852 "RFC 5213: Section 2.2, 6.1" 853 ::= { pmip6MagMnLLIdentifierEntry 1 } 855 pmip6MagHomeNetworkPrefixTable OBJECT-TYPE 856 SYNTAX SEQUENCE OF PMip6MagHomeNetworkPrefixEntry 857 MAX-ACCESS not-accessible 858 STATUS current 859 DESCRIPTION 860 "A table representing the Home Network Prefixes 861 assigned to the connected interfaces of mobile nodes 862 attached to the MAG. 863 " 864 REFERENCE 865 "RFC 5213: Section 2, 6.1, 6.2" 866 ::= { pmip6MagConf 4 } 868 pmip6MagHomeNetworkPrefixEntry OBJECT-TYPE 869 SYNTAX PMip6MagHomeNetworkPrefixEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "An entry in the Home Network Prefixes table. 875 Implementers need to be aware that if the total 876 number of octets in pmip6MagHomeNetworkPrefix 877 exceeds 111 then OIDs of column instances in 878 this row will have more than 128 sub-identifiers 879 and cannot be accessed using SNMPv1, SNMPv2c, or 880 SNMPv3. 881 " 882 INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex, 883 pmip6MagHomeNetworkPrefixType, 884 pmip6MagHomeNetworkPrefix } 885 ::= { pmip6MagHomeNetworkPrefixTable 1 } 887 PMip6MagHomeNetworkPrefixEntry ::= 888 SEQUENCE { 889 pmip6MagHomeNetworkPrefixType InetAddressType, 890 pmip6MagHomeNetworkPrefix InetAddress, 891 pmip6MagHomeNetworkPrefixLength InetAddressPrefixLength, 892 pmip6MagHomeNetworkPrefixLifeTime Unsigned32 893 } 895 pmip6MagHomeNetworkPrefixType OBJECT-TYPE 896 SYNTAX InetAddressType 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "The InetAddressType of the pmip6MagHomeNetworkPrefix 901 that follows. 902 " 903 ::= { pmip6MagHomeNetworkPrefixEntry 1 } 905 pmip6MagHomeNetworkPrefix OBJECT-TYPE 906 SYNTAX InetAddress 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "The mobile network prefix that is delegated to the 911 mobile node. The type of the address represented by 912 this object is specified by the corresponding 913 pmip6MagHomeNetworkPrefixType object. 914 " 915 REFERENCE 916 "RFC 5213: Section 2" 918 ::= { pmip6MagHomeNetworkPrefixEntry 2 } 920 pmip6MagHomeNetworkPrefixLength OBJECT-TYPE 921 SYNTAX InetAddressPrefixLength 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "The prefix length of the Home Network Prefix. 926 " 927 ::= { pmip6MagHomeNetworkPrefixEntry 3 } 929 pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE 930 SYNTAX Unsigned32 931 UNITS "seconds" 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "The lifetime parameter (in seconds) that will be 936 advertised in Router Advertisements by the MAG for 937 this Home Network Prefix. 938 " 939 REFERENCE 940 "RFC 5213: Section 6.2, 6.7" 941 ::= { pmip6MagHomeNetworkPrefixEntry 4 } 943 pmip6MagBLTable OBJECT-TYPE 944 SYNTAX SEQUENCE OF Pmip6MagBLEntry 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "This table corresponds to the Binding Update List(BL) 949 that includes Proxy MIPv6 related information and 950 is maintained by the mobile access gateway. 951 Entries from the table are deleted as 952 the lifetime of the binding expires. 953 " 954 REFERENCE 955 "RFC 3775: Section 4.5, 11.1, 956 RFC 5213: Section 6.1" 957 ::= { pmip6MagRegistration 1 } 959 pmip6MagBLEntry OBJECT-TYPE 960 SYNTAX Pmip6MagBLEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "An entry containing additional information contained 965 in a Binding Update sent by the mobile access gateway 966 to the local mobility anchor. 967 " 968 AUGMENTS {mip6MnBLEntry} 969 ::= { pmip6MagBLTable 1 } 971 Pmip6MagBLEntry ::= SEQUENCE { 972 pmip6MagBLFlag TruthValue, 973 pmip6MagBLMnIndex Pmip6MnIndex, 974 pmip6MagBLMnLLIndex Pmip6MnLLIndex, 975 pmip6MagBLMagLinkLocalAddressType InetAddressType, 976 pmip6MagBLMagLinkLocalAddress InetAddress, 977 pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC, 978 pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC, 979 pmip6MagBLMnInterfaceATT Pmip6MnInterfaceATT, 980 pmip6MagBLTimeRecentlyAccepted Pmip6TimeStamp64 981 } 983 pmip6MagBLFlag OBJECT-TYPE 984 SYNTAX TruthValue 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "true(1) if the mobile access gateway sent the proxy 989 binding update with Proxy Registration Flag that 990 indicates to the local mobility anchor that the 991 registration is the proxy binding update and is from 992 a mobile access gateway. 993 false(0) implies that the mobile access gateway is 994 behaving as a simple mobile node. 995 " 996 REFERENCE 997 "RFC 5213: Section 8.1" 998 ::= { pmip6MagBLEntry 1 } 1000 pmip6MagBLMnIndex OBJECT-TYPE 1001 SYNTAX Pmip6MnIndex 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "The index to the Identifier of the attached mobile 1006 node in the pmip6MagMnIdentifierTable. 1007 " 1008 REFERENCE 1009 "RFC 5213: Section 2.2, 6.1, 8.1" 1010 ::= { pmip6MagBLEntry 2 } 1012 pmip6MagBLMnLLIndex OBJECT-TYPE 1013 SYNTAX Pmip6MnLLIndex 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "The index to the link-layer identifier of the mobile 1018 node's connected interface in the 1019 pmip6MagMnLLIdentifierTable. 1020 " 1021 REFERENCE 1022 "RFC 5213: Section 2.2, 6.1, 8.1" 1023 ::= { pmip6MagBLEntry 3 } 1025 pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE 1026 SYNTAX InetAddressType 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The InetAddressType of the pmip6MagBLMagLinkLocalAddress 1031 that follows. 1032 " 1033 ::= { pmip6MagBLEntry 4 } 1035 pmip6MagBLMagLinkLocalAddress OBJECT-TYPE 1036 SYNTAX InetAddress 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION 1040 "The Link-local address of the mobile access gateway on 1041 the access link shared with the mobile node. 1042 This is the address that is present in the Link-local 1043 Address option of the corresponding Proxy Binding Update 1044 message. 1045 " 1046 REFERENCE 1047 "RFC 3963 : Section 4.1, 5.1" 1049 ::= { pmip6MagBLEntry 5 } 1051 pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE 1052 SYNTAX Ipv6AddressIfIdentifierTC 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "The interface identifier (if-id) of the point-to-point 1057 link between the mobile node and the mobile access 1058 gateway. This is internal to the mobile access gateway 1059 and is used to associate the Proxy Mobile IPv6 tunnel 1060 to the access link where the mobile node is attached. 1061 " 1062 REFERENCE 1063 "RFC 5213: Section 6.1, 8.1" 1064 ::= { pmip6MagBLEntry 6 } 1066 pmip6MagBLTunnelIfIdentifier OBJECT-TYPE 1067 SYNTAX Ipv6AddressIfIdentifierTC 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The tunnel interface identifier (tunnel-if-id) of the 1072 bi-directional tunnel between the mobile node's local 1073 mobility anchor and the mobile access gateway. This 1074 is internal to the mobile access gateway. The tunnel 1075 interface identifier is acquired during the tunnel 1076 creation. 1077 " 1078 REFERENCE 1079 "RFC 5213: Section 6.1, 8.1" 1080 ::= { pmip6MagBLEntry 7 } 1082 pmip6MagBLMnInterfaceATT OBJECT-TYPE 1083 SYNTAX Pmip6MnInterfaceATT 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "The type of the access technology by which the mobile 1088 node is currently attached to the mobile access gateway. 1089 " 1090 REFERENCE 1091 "RFC 5213: Section 6.9.1.1, 6.9.1.5, 8.1" 1092 ::= { pmip6MagBLEntry 8 } 1094 pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE 1095 SYNTAX Pmip6TimeStamp64 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "The 64-bit timestamp value of the most recently 1100 accepted Proxy Binding Update message sent for this 1101 mobile node. This is the time-of-day on the mobile 1102 access gateway, when the proxy binding acknowledgement 1103 message with the Status field set to 0 1104 was received. If the Timestamp option is not present 1105 in the Proxy Binding Update message (i.e., when the 1106 sequence number based scheme is in use), the value MUST 1107 be initialized with all zeroes. 1108 " 1109 REFERENCE 1110 "RFC 5213: Section 5.1, 8.1" 1111 ::= { pmip6MagBLEntry 9 } 1113 pmip6MagMnProfileTable OBJECT-TYPE 1114 SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "This table corresponds to the mobile node's policy 1119 profile that includes the essential operational 1120 parameters that are required by the network entities 1121 for managing the mobile node's mobility service. 1122 It contains policy profiles of mobile nodes that are 1123 connected to the mobile access gateway. 1124 Entries in this table are not required to survive 1125 a reboot of the managed entity. 1126 " 1127 REFERENCE 1128 "RFC 5213: Section 6.2" 1129 ::= { pmip6MagRegistration 2 } 1131 pmip6MagMnProfileEntry OBJECT-TYPE 1132 SYNTAX Pmip6MagMnProfileEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "An entry containing information about the 1137 mobile node's policy profile. 1139 " 1140 INDEX { pmip6MagProfMnIndex } 1141 ::= { pmip6MagMnProfileTable 1 } 1143 Pmip6MagMnProfileEntry ::= 1144 SEQUENCE { 1145 pmip6MagProfMnIndex Pmip6MnIndex, 1146 pmip6MagProfMnIdentifier Pmip6MnIdentifier, 1147 pmip6MagProfMnLocalMobilityAnchorAddressType 1148 InetAddressType, 1149 pmip6MagProfMnLocalMobilityAnchorAddress InetAddress 1150 } 1152 pmip6MagProfMnIndex OBJECT-TYPE 1153 SYNTAX Pmip6MnIndex 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "The index for a mobile node in the Proxy Mobile IPv6 1158 domain. 1159 " 1160 ::= { pmip6MagMnProfileEntry 1 } 1162 pmip6MagProfMnIdentifier OBJECT-TYPE 1163 SYNTAX Pmip6MnIdentifier 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "The identity of a mobile node in the Proxy Mobile IPv6 1168 domain. 1169 " 1170 REFERENCE 1171 "RFC 5213: Section 2.2" 1172 ::= { pmip6MagMnProfileEntry 2 } 1174 pmip6MagProfMnLocalMobilityAnchorAddressType OBJECT-TYPE 1175 SYNTAX InetAddressType 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "The InetAddressType of the 1180 pmip6MagMnLocalMobilityAnchorAddress that follows. 1181 " 1182 ::= { pmip6MagMnProfileEntry 3 } 1184 pmip6MagProfMnLocalMobilityAnchorAddress OBJECT-TYPE 1185 SYNTAX InetAddress 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "The global address that is configured on the interface 1190 of the local mobility anchor and is the transport 1191 endpoint of the bi-directional tunnel established 1192 between the local mobility anchor and the mobile access 1193 gateway. This is the address to which the mobile 1194 access gateway sends the Proxy Binding Update messages. 1195 " 1196 REFERENCE 1197 "RFC 5213: Section 2.2" 1198 ::= { pmip6MagMnProfileEntry 4 } 1200 pmip6BindingCacheTable OBJECT-TYPE 1201 SYNTAX SEQUENCE OF Pmip6BindingCacheEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "This table models the Binding Cache on the local 1206 mobility anchor. 1207 Entries from the table are deleted as 1208 the lifetime of the binding expires. 1210 Entries in this table are not required to survive 1211 a reboot of the managed entity. 1212 " 1213 REFERENCE 1214 "RFC 3775: Section 4.5, 9.1, 10.1, 1215 RFC 5213: Section 5.1" 1216 ::= { pmip6Bindings 1 } 1218 pmip6BindingCacheEntry OBJECT-TYPE 1219 SYNTAX Pmip6BindingCacheEntry 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "An entry containing additional information contained 1224 in the binding cache table 1225 of the local mobility anchor. 1227 " 1228 AUGMENTS {mip6BindingCacheEntry} 1229 ::= { pmip6BindingCacheTable 1 } 1231 Pmip6BindingCacheEntry ::= SEQUENCE { 1232 pmip6BindingPBUFlag TruthValue, 1233 pmip6BindingMnIndex Pmip6MnIndex, 1234 pmip6BindingMnLLIndex Pmip6MnLLIndex, 1235 pmip6BindingMagLinkLocalAddressType InetAddressType, 1236 pmip6BindingMagLinkLocalAddress InetAddress, 1237 pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC, 1238 pmip6BindingMnInterfaceATT 1239 Pmip6MnInterfaceATT, 1240 pmip6BindingTimeRecentlyAccepted Pmip6TimeStamp64 1241 } 1243 pmip6BindingPBUFlag OBJECT-TYPE 1244 SYNTAX TruthValue 1245 MAX-ACCESS read-only 1246 STATUS current 1247 DESCRIPTION 1248 "true(1) if the local mobility anchor accepted the 1249 binding update with Proxy Registration Flag from a 1250 mobile access gateway. 1251 false(0) implies that the binding cache is from a 1252 mobile node. In this case the remaining objects will 1253 not be accessible. 1254 " 1255 REFERENCE 1256 "RFC 5213: Section 5.1, 8.1" 1257 ::= { pmip6BindingCacheEntry 1 } 1259 pmip6BindingMnIndex OBJECT-TYPE 1260 SYNTAX Pmip6MnIndex 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "An index to the identifier of the registered mobile 1265 node. 1266 " 1267 REFERENCE 1268 "RFC 5213: Section 2.2, 5.1, 8.1 1269 RFC 4283: Section 3" 1270 ::= { pmip6BindingCacheEntry 2 } 1272 pmip6BindingMnLLIndex OBJECT-TYPE 1273 SYNTAX Pmip6MnLLIndex 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "The index to the link-layer identifier of the mobile 1278 node's connected interface on the access link. 1279 " 1280 REFERENCE 1281 "RFC 5213: Section 2.2, 5.1, 8.1" 1282 ::= { pmip6BindingCacheEntry 3 } 1284 pmip6BindingMagLinkLocalAddressType OBJECT-TYPE 1285 SYNTAX InetAddressType 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "The InetAddressType of the 1290 pmip6BindingMagLinkLocalAddress that follows. 1291 " 1292 ::= { pmip6BindingCacheEntry 4 } 1294 pmip6BindingMagLinkLocalAddress OBJECT-TYPE 1295 SYNTAX InetAddress 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The link-local address of the mobile access gateway on 1300 the point-to-point link shared with the mobile node. 1301 This is generated by the local mobility anchor after 1302 accepting the initial Proxy Binding Update message. 1303 This is the address that is present in the Link-local 1304 Address option of the corresponding Proxy Binding 1305 Acknowledgement message. 1306 " 1307 REFERENCE 1308 "RFC 5213: Section 5.1, 6.9.1.2, 8.2" 1309 ::= { pmip6BindingCacheEntry 5 } 1311 pmip6BindingTunnelIfIdentifier OBJECT-TYPE 1312 SYNTAX Ipv6AddressIfIdentifierTC 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "The tunnel interface identifier (tunnel-if-id) of the 1317 bi-directional tunnel between the local mobility anchor 1318 and the mobile access gateway where the mobile node is 1319 currently anchored. This is internal to the local 1320 mobility anchor. The tunnel interface identifier is 1321 acquired during the tunnel creation. 1322 " 1323 REFERENCE 1324 "RFC 5213: Section 5.1, 8.1" 1325 ::= { pmip6BindingCacheEntry 6 } 1327 pmip6BindingMnInterfaceATT OBJECT-TYPE 1328 SYNTAX Pmip6MnInterfaceATT 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "The access technology type, by which the mobile node 1333 is currently attached. This is obtained from the 1334 Access Technology Type option, present in the Proxy 1335 Binding Update message. 1336 " 1337 REFERENCE 1338 "RFC 5213: Section 5.1, 8.1" 1339 ::= { pmip6BindingCacheEntry 7 } 1341 pmip6BindingTimeRecentlyAccepted OBJECT-TYPE 1342 SYNTAX Pmip6TimeStamp64 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The 64-bit timestamp value of the most recently 1347 accepted Proxy Binding Update message sent for this 1348 mobile node. This is the time-of-day on the local 1349 mobility anchor, when the message was received. If 1350 the Timestamp option is not present in the Proxy 1351 Binding Update message (i.e., when the sequence number 1352 based scheme is in use), the value MUST be initialized 1353 with all zeroes. 1354 " 1355 REFERENCE 1356 "RFC 5213: Section 5.1, 8.1" 1357 ::= { pmip6BindingCacheEntry 8 } 1359 --- 1360 --- 1361 --- pmip6Stats group 1362 --- 1363 --- 1365 -- 1366 -- pmip6Stats:pmip6BindingRegCounters 1367 -- 1369 pmip6MissingMnIdentifierOption OBJECT-TYPE 1370 SYNTAX Counter32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "Total number of Proxy Binding Update messages 1375 rejected by the local mobility anchor with status 1376 code in the Binding Acknowledgement message indicating 1377 'Missing mobile node identifier option' (Code 160). 1379 Discontinuities in the value of this counter can 1380 occur at re-initialization of the mobile router, 1381 and at other times as indicated by the value of 1382 pmip6CounterDiscontinuityTime. 1383 " 1384 REFERENCE 1385 "RFC 5213: Section 5.3.1, 8.9" 1386 ::= { pmip6BindingRegCounters 1 } 1388 pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE 1389 SYNTAX Counter32 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "Total number of Proxy Binding Update messages 1394 rejected by the local mobility anchor with status 1395 code in the Binding Acknowledgement message indicating 1396 'Not authorized to send proxy binding updates' 1397 (Code 154). 1399 Discontinuities in the value of this counter can 1400 occur at re-initialization of the mobile router, 1401 and at other times as indicated by the value of 1402 pmip6CounterDiscontinuityTime. 1404 " 1405 REFERENCE 1406 "RFC 5213: Section 5.3.1, 8.9" 1407 ::= { pmip6BindingRegCounters 2 } 1409 pmip6NotLMAForThisMobileNode OBJECT-TYPE 1410 SYNTAX Counter32 1411 MAX-ACCESS read-only 1412 STATUS current 1413 DESCRIPTION 1414 "Total number of Proxy Binding Update messages rejected 1415 by the local mobility anchor with status code in the 1416 Binding Acknowledgement message indicating 1417 'Not local mobility anchor for this mobile node' 1418 (Code 153). 1420 Discontinuities in the value of this counter can 1421 occur at re-initialization of the management system, 1422 and at other times as indicated by the value of 1423 pmip6CounterDiscontinuityTime. 1424 " 1425 REFERENCE 1426 "RFC 5213: Section 5.3.1, 8.9" 1427 ::= { pmip6BindingRegCounters 3 } 1429 pmip6ProxyRegNotEnabled OBJECT-TYPE 1430 SYNTAX Counter32 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "Total number of Proxy Binding Update messages rejected 1435 by the local mobility anchor with status code in the 1436 Binding Acknowledgement message indicating 1437 'Proxy Registration not enabled' (Code 152). 1438 Discontinuities in the value of this counter can 1439 occur at re-initialization of the management system, 1440 and at other times as indicated by the value of 1441 pmip6CounterDiscontinuityTime. 1442 " 1443 REFERENCE 1444 "RFC 5213: Section 5.3.1, 6.9.1.2, 8.9" 1445 ::= { pmip6BindingRegCounters 4 } 1447 pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE 1448 SYNTAX Counter32 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "Total number of Proxy Binding Update messages rejected 1453 by the local mobility anchor with status code in the 1454 Binding Acknowledgement message indicating 1455 'Missing home network prefix option' (Code 158). 1456 Discontinuities in the value of this counter can 1457 occur at re-initialization of the management system, 1458 and at other times as indicated by the value of 1459 pmip6CounterDiscontinuityTime. 1460 " 1461 REFERENCE 1462 "RFC 5213: Section 5.3.1, 8.9" 1463 ::= { pmip6BindingRegCounters 5 } 1465 pmip6MissingHandOffIndicatorOption OBJECT-TYPE 1466 SYNTAX Counter32 1467 MAX-ACCESS read-only 1468 STATUS current 1469 DESCRIPTION 1470 "Total number of Proxy Binding Update messages rejected 1471 by the local mobility anchor with status code in the 1472 Binding Acknowledgement message indicating 1473 'Missing handoff indicator option' (Code 161). 1474 Discontinuities in the value of this counter can 1475 occur at re-initialization of the management system, 1476 and at other times as indicated by the value of 1477 pmip6CounterDiscontinuityTime. 1478 " 1479 REFERENCE 1480 "RFC 5213: Section 5.3.1, 8.9" 1481 ::= { pmip6BindingRegCounters 6 } 1483 pmip6MissingAccessTechTypeOption OBJECT-TYPE 1484 SYNTAX Counter32 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "Total number of Proxy Binding Update messages rejected 1489 by the local mobility anchor with status code in the 1490 Binding Acknowledgement message indicating 1491 'Missing access technology type option' (Code 162). 1493 Discontinuities in the value of this counter can 1494 occur at re-initialization of the management system, 1495 and at other times as indicated by the value of 1496 pmip6CounterDiscontinuityTime. 1497 " 1498 REFERENCE 1499 "RFC 5213: Section 5.3.1, 8.9" 1500 ::= { pmip6BindingRegCounters 7 } 1502 pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "Total number of Proxy Binding Update messages rejected 1508 by the local mobility anchor with status code in the 1509 Binding Acknowledgement message indicating 1510 'Mobile node not authorized for one or more of the 1511 requesting home network prefixes' (Code 155). 1513 Discontinuities in the value of this counter can 1514 occur at re-initialization of the management system, 1515 and at other times as indicated by the value of 1516 pmip6CounterDiscontinuityTime. 1517 " 1518 REFERENCE 1519 "RFC 5213: Section 5.3.2, 6.9.1.2, 8.9" 1520 ::= { pmip6BindingRegCounters 8 } 1522 pmip6TimestampMismatch OBJECT-TYPE 1523 SYNTAX Counter32 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "Total number of Proxy Binding Update messages rejected 1528 by the local mobility anchor with status code in the 1529 Binding Acknowledgement message indicating 1530 'Invalid timestamp value (the clocks are out of sync)' 1531 (Code 156) 1532 Discontinuities in the value of this counter can 1533 occur at re-initialization of the management system, 1534 and at other times as indicated by the value of 1535 pmip6CounterDiscontinuityTime. 1536 " 1537 REFERENCE 1538 "RFC 5213: Section 5.5, 6.9.1.2, 8.9" 1539 ::= { pmip6BindingRegCounters 9 } 1541 pmip6TimestampLowerThanPrevAccepted OBJECT-TYPE 1542 SYNTAX Counter32 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "Total number of Proxy Binding Update messages rejected 1547 by the local mobility anchor with status code in the 1548 Binding Acknowledgement message indicating 1549 'The timestamp value is lower than the previously 1550 accepted value' (Code 157). 1551 Discontinuities in the value of this counter can 1552 occur at re-initialization of the management system, 1553 and at other times as indicated by the value of 1554 pmip6CounterDiscontinuityTime. 1555 " 1556 REFERENCE 1557 "RFC 5213: Section 5.5, 6.9.1.2, 8.9" 1558 ::= { pmip6BindingRegCounters 10 } 1560 pmip6BcePbuPrefixSetDoNotMatch OBJECT-TYPE 1561 SYNTAX Counter32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "Total number of Proxy Binding Update messages rejected 1566 by the local mobility anchor with status code in the 1567 Binding Acknowledgement message indicating 1568 'All the home network prefixes listed in the Binding 1569 Cache Entry do not match all the prefixes in the 1570 received Proxy Binding Update' (Code 159). 1571 Discontinuities in the value of this counter can 1572 occur at re-initialization of the management system, 1573 and at other times as indicated by the value of 1574 pmip6CounterDiscontinuityTime. 1575 " 1576 REFERENCE 1577 "RFC 5213: Section 5.4.1.1, 8.9" 1578 ::= { pmip6BindingRegCounters 11 } 1580 pmip6InitialBindingRegistrations OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "Total number of Proxy Binding Update messages that 1586 newly creates the Binding Cache entry. 1587 Discontinuities in the value of this counter can 1588 occur at re-initialization of the management system, 1589 and at other times as indicated by the value of 1590 pmip6CounterDiscontinuityTime. 1591 " 1592 REFERENCE 1593 "RFC 5213: Section 5.3.2" 1594 ::= { pmip6BindingRegCounters 12 } 1596 pmip6BindingLifeTimeExtensionNoHandOff OBJECT-TYPE 1597 SYNTAX Counter32 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "Total number of Proxy Binding Update messages for 1602 extending the binding lifetime, received from the 1603 same mobile access gateway that last updated the 1604 binding. 1605 Discontinuities in the value of this counter can 1606 occur at re-initialization of the management system, 1607 and at other times as indicated by the value of 1608 pmip6CounterDiscontinuityTime. 1609 " 1610 REFERENCE 1611 "RFC 5213: Section 5.3.3" 1612 ::= { pmip6BindingRegCounters 13 } 1614 pmip6BindingLifeTimeExtensionAfterHandOff OBJECT-TYPE 1615 SYNTAX Counter32 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "Total number of Proxy Binding Update messages for 1620 extending the binding lifetime, received from a new 1621 mobile access gateway where the mobile node's 1622 mobility session is handed off. 1623 Discontinuities in the value of this counter can 1624 occur at re-initialization of the management system, 1625 and at other times as indicated by the value of 1626 pmip6CounterDiscontinuityTime. 1628 " 1629 REFERENCE 1630 "RFC 5213: Section 5.3.4" 1631 ::= { pmip6BindingRegCounters 14 } 1633 pmip6BindingDeRegistrations OBJECT-TYPE 1634 SYNTAX Counter32 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "Total number of Proxy Binding Update messages with 1639 the lifetime value of zero. 1640 Discontinuities in the value of this counter can 1641 occur at re-initialization of the management system, 1642 and at other times as indicated by the value of 1643 pmip6CounterDiscontinuityTime. 1644 " 1645 REFERENCE 1646 "RFC 5213: Section 5.3.5" 1647 ::= { pmip6BindingRegCounters 15 } 1649 pmip6BindingBindingAcks OBJECT-TYPE 1650 SYNTAX Counter32 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "Total number of Proxy Binding Acknowledgement 1655 messages. 1656 Discontinuities in the value of this counter can 1657 occur at re-initialization of the management system, 1658 and at other times as indicated by the value of 1659 pmip6CounterDiscontinuityTime. 1660 " 1661 REFERENCE 1662 "RFC 5213: Section 5.3.5" 1663 ::= { pmip6BindingRegCounters 16 } 1665 pmip6CounterDiscontinuityTime OBJECT-TYPE 1666 SYNTAX TimeStamp 1667 MAX-ACCESS read-only 1668 STATUS current 1669 DESCRIPTION 1670 "The value of sysUpTime on the most recent occasion 1671 at which any one or more of this PMIPv6 entities 1672 global counters, viz., counters with OID prefix 1673 'pmip6BindingRegCounters' suffered a discontinuity. 1674 If no such discontinuities have occurred since the 1675 last re-initialization of the local management 1676 subsystem, then this object will have a zero value. 1677 " 1678 ::= { pmip6BindingRegCounters 17 } 1680 pmip6LmaStatus OBJECT-TYPE 1681 SYNTAX INTEGER { enabled(1), disabled(2) } 1682 MAX-ACCESS read-write 1683 STATUS current 1684 DESCRIPTION 1685 "This object indicates whether the PMIPv6 local 1686 mobility anchor function is enabled for the managed 1687 entity. 1689 Changing the status from enabled(1) to disabled(2) 1690 will terminate the PMIPv6 local mobility anchor 1691 function. On the other hand, changing the status 1692 from disabled(2) to enabled(1) will start the PMIPv6 1693 local mobility anchor function. 1695 The value of this object MUST remain unchanged 1696 across reboots of the managed entity. 1697 " 1698 DEFVAL { disabled } 1699 ::= { pmip6LmaSystem 1 } 1701 pmip6LmaLMAATable OBJECT-TYPE 1702 SYNTAX SEQUENCE OF Pmip6LmaLMAAEntry 1703 MAX-ACCESS not-accessible 1704 STATUS current 1705 DESCRIPTION 1706 "This table models the LMA Addresses configured 1707 on the local mobility anchor. Each LMA Address acts as 1708 a transport endpoint of the tunnel between the local 1709 mobility anchor and the mobile access gateway and is 1710 the transport endpoint of the tunnel between the local 1711 mobility anchor and the mobile access gateway. 1713 Entries in this table are not required to survive 1714 a reboot of the managed entity. 1715 " 1717 REFERENCE 1718 "RFC 5213: Section 2.2, 5.6" 1719 ::= { pmip6LmaSystem 2 } 1721 pmip6LmaLMAAEntry OBJECT-TYPE 1722 SYNTAX Pmip6LmaLMAAEntry 1723 MAX-ACCESS not-accessible 1724 STATUS current 1725 DESCRIPTION 1726 "This entry represents a conceptual row in the 1727 LMAA table. It represents each LMAA 1728 on the local mobility anchor. 1730 Implementers need to be aware that if the total 1731 number of octets in pmip6LmaLMAA exceeds 113 1732 then OIDs of column instances in this row will 1733 have more than 128 sub-identifiers and cannot 1734 be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1735 " 1736 INDEX { pmip6LmaLMAAType, pmip6LmaLMAA } 1737 ::= { pmip6LmaLMAATable 1 } 1739 Pmip6LmaLMAAEntry ::= 1740 SEQUENCE { 1741 pmip6LmaLMAAType InetAddressType, 1742 pmip6LmaLMAA InetAddress, 1743 pmip6LmaLMAAState INTEGER 1744 } 1746 pmip6LmaLMAAType OBJECT-TYPE 1747 SYNTAX InetAddressType 1748 MAX-ACCESS not-accessible 1749 STATUS current 1750 DESCRIPTION 1751 "The InetAddressType of the pmip6LmaLMAA 1752 that follows. 1753 " 1754 ::= { pmip6LmaLMAAEntry 1 } 1756 pmip6LmaLMAA OBJECT-TYPE 1757 SYNTAX InetAddress 1758 MAX-ACCESS not-accessible 1759 STATUS current 1760 DESCRIPTION 1761 "The LMAA configured on the local mobility anchor. 1763 The type of the address represented by this object 1764 is specified by the corresponding 1765 pmip6LmaLMAAType object. 1766 " 1767 REFERENCE 1768 "RFC 5213: Section 2.2, 5.6" 1769 ::= { pmip6LmaLMAAEntry 2 } 1771 pmip6LmaLMAAState OBJECT-TYPE 1772 SYNTAX INTEGER { 1773 unknown(1), 1774 activated(2), 1775 tunneled(3) 1776 } 1777 MAX-ACCESS read-only 1778 STATUS current 1779 DESCRIPTION 1780 "This object indicates the state of the LMAA: 1781 unknown -- The state of the LMAA 1782 cannot be determined. 1783 activated -- The LMAA is ready to establish 1784 tunnel 1785 tunneled -- The LMAA is used to set up the 1786 bi-directional tunnel. 1787 " 1788 ::= { pmip6LmaLMAAEntry 3 } 1790 pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE 1791 SYNTAX Integer32 (1..65535) 1792 UNITS "milliseconds" 1793 MAX-ACCESS read-write 1794 STATUS current 1795 DESCRIPTION 1796 "This variable specifies the length of time in 1797 milliseconds the local mobility anchor MUST wait before 1798 it deletes a Binding Cache entry of a mobile node, upon 1799 receiving a Proxy Binding Update message from a mobile 1800 access gateway with a lifetime value of 0. 1801 During this wait time, if the local mobility anchor 1802 receives a Proxy Binding Update for the same mobility 1803 binding, with a lifetime value greater than 0, then it 1804 must update the binding cache entry with the accepted 1805 binding values. By the end of this wait-time, if the 1806 local mobility anchor did not receive any valid Proxy 1807 Binding Update message for that mobility binding, it 1808 MUST delete the Binding Cache entry. This delay 1809 essentially ensures that a mobile node's Binding Cache 1810 entry is not deleted too quickly and allows some time 1811 for the new mobile access gateway to complete the 1812 signaling for the mobile node. 1813 The default value for this variable is 10000 1814 milliseconds. 1815 " 1816 REFERENCE 1817 "RFC 5213: Section 5.3.5, 9.1" 1818 DEFVAL { 10000 } 1819 ::= { pmip6LmaConf 1 } 1821 pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE 1822 SYNTAX Integer32 (1..65535) 1823 UNITS "milliseconds" 1824 MAX-ACCESS read-write 1825 STATUS current 1826 DESCRIPTION 1827 "This variable specifies the length of time in 1828 milliseconds the local mobility anchor MUST wait for 1829 the de-registration message for an existing mobility 1830 session before it decides to create a new mobility 1831 session. 1832 The default value for this variable is 1500 1833 milliseconds. Note that there is a dependency between 1834 this value and the values used in the retransmission 1835 algorithm for Proxy Binding Updates. The retransmissions 1836 need to happen before MaxDelayBeforeNewBCEAssign runs 1837 out, as otherwise there are situations where a 1838 de-registration from a previous mobile access gateway 1839 may be lost, and the local mobility anchor creates, 1840 needlessly, a new mobility session and new prefixes for 1841 the mobile node. However, this affects situations where 1842 there is no information from the lower layers about the 1843 type of a handoff or other parameters that can be used 1844 for identifying the mobility session. 1845 " 1846 REFERENCE 1847 "RFC 5213: Section 5.4.1.2, 5.4.1.3, 9.1" 1848 DEFVAL { 1500 } 1849 ::= { pmip6LmaConf 2 } 1851 pmip6LmaTimestampValidityWindow OBJECT-TYPE 1852 SYNTAX Integer32 (1..65535) 1853 UNITS "milliseconds" 1854 MAX-ACCESS read-write 1855 STATUS current 1856 DESCRIPTION 1857 "This variable specifies the maximum length of time 1858 difference in milliseconds between the timestamp in the 1859 received Proxy Binding Update message and the current 1860 time-of-day on the local mobility anchor, that is 1861 allowed by the local mobility anchor for the received 1862 message to be considered valid. 1863 The default value for this variable is 300 milliseconds. 1864 This variable must be adjusted to suit the deployments. 1865 " 1866 REFERENCE 1867 "RFC 5213: Section 5.5, 9.1" 1868 DEFVAL { 300 } 1869 ::= { pmip6LmaConf 3 } 1871 pmip6LmaMnIdentifierTable OBJECT-TYPE 1872 SYNTAX SEQUENCE OF Pmip6LmaMnIdentifierEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "A table containing the indentifiers of mobile nodes 1877 served by the LMA. 1878 Entries in this table are not required to survive 1879 a reboot of the managed entity. 1880 " 1881 REFERENCE 1882 "RFC 5213: Section 2, 6.1" 1883 ::= { pmip6LmaConf 4 } 1885 pmip6LmaMnIdentifierEntry OBJECT-TYPE 1886 SYNTAX Pmip6LmaMnIdentifierEntry 1887 MAX-ACCESS not-accessible 1888 STATUS current 1889 DESCRIPTION 1890 "An entry in the mobile node identifier table. 1891 " 1892 INDEX { pmip6BindingMnIndex 1893 } 1895 ::= { pmip6LmaMnIdentifierTable 1 } 1897 Pmip6LmaMnIdentifierEntry ::= 1898 SEQUENCE { 1899 pmip6LmaMnIdentifier Pmip6MnIdentifier 1900 } 1902 pmip6LmaMnIdentifier OBJECT-TYPE 1903 SYNTAX Pmip6MnIdentifier 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The identity of a mobile node in the Proxy Mobile IPv6 1908 domain. 1909 " 1910 REFERENCE 1911 "RFC 5213: Section 2.2" 1912 ::= { pmip6LmaMnIdentifierEntry 1 } 1914 pmip6LmaMnLLIdentifierTable OBJECT-TYPE 1915 SYNTAX SEQUENCE OF Pmip6LmaMnLLIdentifierEntry 1916 MAX-ACCESS not-accessible 1917 STATUS current 1918 DESCRIPTION 1919 "A table containing the link layer indentifiers 1920 of the interfaces of the mobile nodes served 1921 by the LMA. 1922 Entries in this table are not required to survive 1923 a reboot of the managed entity. 1924 " 1925 REFERENCE 1926 "RFC 5213: Section 2, 6.1" 1927 ::= { pmip6LmaConf 5 } 1929 pmip6LmaMnLLIdentifierEntry OBJECT-TYPE 1930 SYNTAX Pmip6LmaMnLLIdentifierEntry 1931 MAX-ACCESS not-accessible 1932 STATUS current 1933 DESCRIPTION 1934 "An entry in the mobile node link layer identifier 1935 table. 1936 " 1938 INDEX { pmip6BindingMnIndex, pmip6BindingMnLLIndex 1939 } 1940 ::= { pmip6LmaMnLLIdentifierTable 1 } 1942 Pmip6LmaMnLLIdentifierEntry ::= 1943 SEQUENCE { 1944 pmip6LmaMnLLIdentifier Pmip6MnLLIdentifier 1945 } 1947 pmip6LmaMnLLIdentifier OBJECT-TYPE 1948 SYNTAX Pmip6MnLLIdentifier 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "The link-layer identifier of the mobile node's 1953 connected interface on the access link. 1954 " 1955 ::= { pmip6LmaMnLLIdentifierEntry 1 } 1957 pmip6LmaHomeNetworkPrefixTable OBJECT-TYPE 1958 SYNTAX SEQUENCE OF PMip6LmaHomeNetworkPrefixEntry 1959 MAX-ACCESS not-accessible 1960 STATUS current 1961 DESCRIPTION 1962 "A table representing the Home Network Prefixes 1963 assigned to the connected interfaces of all the 1964 mobile nodes anchored at the LMA. 1965 " 1966 REFERENCE 1967 "RFC 5213: Section 2, 5.1, 5.2" 1968 ::= { pmip6LmaConf 6 } 1970 pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE 1971 SYNTAX PMip6LmaHomeNetworkPrefixEntry 1972 MAX-ACCESS not-accessible 1973 STATUS current 1974 DESCRIPTION 1975 "An entry in the Home Network Prefixes table. 1977 Implementers need to be aware that if the total 1978 number of octets in pmip6LmaHomeNetworkPrefix 1979 exceeds 111 then OIDs of column instances in this 1980 row will have more than 128 sub-identifiers and 1981 cannot be accessed using SNMPv1, SNMPv2c, or 1982 SNMPv3. 1984 " 1985 INDEX { pmip6BindingMnIndex, pmip6BindingMnLLIndex, 1986 pmip6LmaHomeNetworkPrefixType, 1987 pmip6LmaHomeNetworkPrefix } 1988 ::= { pmip6LmaHomeNetworkPrefixTable 1 } 1990 PMip6LmaHomeNetworkPrefixEntry ::= 1991 SEQUENCE { 1992 pmip6LmaHomeNetworkPrefixType InetAddressType, 1993 pmip6LmaHomeNetworkPrefix InetAddress, 1994 pmip6LmaHomeNetworkPrefixLength InetAddressPrefixLength, 1995 pmip6LmaHomeNetworkPrefixLifeTime Gauge32 1996 } 1998 pmip6LmaHomeNetworkPrefixType OBJECT-TYPE 1999 SYNTAX InetAddressType 2000 MAX-ACCESS not-accessible 2001 STATUS current 2002 DESCRIPTION 2003 "The InetAddressType of the pmip6LmaHomeNetworkPrefix 2004 that follows. 2005 " 2006 ::= { pmip6LmaHomeNetworkPrefixEntry 1 } 2008 pmip6LmaHomeNetworkPrefix OBJECT-TYPE 2009 SYNTAX InetAddress 2010 MAX-ACCESS not-accessible 2011 STATUS current 2012 DESCRIPTION 2013 "The mobile network prefix that is delegated to the 2014 mobile node. The type of the address represented by 2015 this object is specified by the corresponding 2016 pmip6LmaHomeNetworkPrefixType object. 2017 " 2018 REFERENCE 2019 "RFC 5213: Section 2" 2021 ::= { pmip6LmaHomeNetworkPrefixEntry 2 } 2023 pmip6LmaHomeNetworkPrefixLength OBJECT-TYPE 2024 SYNTAX InetAddressPrefixLength 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "The prefix length of the Home Network Prefix. 2029 " 2030 ::= { pmip6LmaHomeNetworkPrefixEntry 3 } 2032 pmip6LmaHomeNetworkPrefixLifeTime OBJECT-TYPE 2033 SYNTAX Gauge32 2034 UNITS "seconds" 2035 MAX-ACCESS read-write 2036 STATUS current 2037 DESCRIPTION 2038 "The lifetime (in seconds) granted to the mobile 2039 node for this registration. 2040 " 2041 REFERENCE 2042 "RFC 5213: Section 5.3" 2043 ::= { pmip6LmaHomeNetworkPrefixEntry 4 } 2045 -- 2046 -- pmip6Notifications 2047 -- 2048 -- 2050 pmip6MagHomeTunnelEstablished NOTIFICATION-TYPE 2051 OBJECTS { 2052 pmip6MagBLTunnelIfIdentifier, 2053 pmip6MagProxyCOAState 2054 } 2055 STATUS current 2056 DESCRIPTION 2057 "This notification is sent by the Proxy MobileIPv6 2058 entities every time the tunnel is established between 2059 the local mobility anchor and mobile access gateway. 2060 " 2061 REFERENCE 2062 "RFC 5213: Section 5.6.1" 2063 ::= { pmip6Notifications 1 } 2065 pmip6MagHomeTunnelReleased NOTIFICATION-TYPE 2066 OBJECTS { 2067 pmip6MagBLTunnelIfIdentifier, 2068 pmip6MagProxyCOAState 2069 } 2070 STATUS current 2071 DESCRIPTION 2072 "This notification is sent by the Proxy MobileIPv6 2073 entities every time the tunnel between the local 2074 mobility anchor and mobile access gateway is released. 2075 " 2076 REFERENCE 2077 "RFC 5213: Section 5.6.1" 2078 ::= { pmip6Notifications 2} 2080 pmip6LmaHomeTunnelEstablished NOTIFICATION-TYPE 2081 OBJECTS { 2082 pmip6BindingTunnelIfIdentifier, 2083 pmip6LmaLMAAState 2084 } 2085 STATUS current 2086 DESCRIPTION 2087 "This notification is sent by the Proxy MobileIPv6 2088 entities every time the tunnel is established between 2089 the local mobility anchor and mobile access gateway. 2090 " 2091 REFERENCE 2092 "RFC 5213: Section 5.6.1" 2093 ::= { pmip6Notifications 3 } 2095 pmip6LmaHomeTunnelReleased NOTIFICATION-TYPE 2096 OBJECTS { 2097 pmip6BindingTunnelIfIdentifier, 2098 pmip6LmaLMAAState 2099 } 2100 STATUS current 2101 DESCRIPTION 2102 "This notification is sent by the Proxy MobileIPv6 2103 entities every time the tunnel between the local 2104 mobility anchor and mobile access gateway is released. 2105 " 2106 REFERENCE 2107 "RFC 5213: Section 5.6.1" 2108 ::= { pmip6Notifications 4} 2110 -- Conformance information 2111 pmip6Groups OBJECT IDENTIFIER ::= { pmip6Conformance 1 } 2112 pmip6Compliances OBJECT IDENTIFIER ::= { pmip6Conformance 2 } 2114 -- Units of conformance 2115 pmip6SystemGroup OBJECT-GROUP 2116 OBJECTS { 2117 pmip6Capabilities, 2118 pmip6MobileNodeGeneratedTimestampInUse, 2119 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType, 2120 pmip6FixedMagLinkLocalAddressOnAllAccessLinks, 2121 pmip6FixedMagLinkLayerAddressOnAllAccessLinks 2123 } 2124 STATUS current 2125 DESCRIPTION 2126 " A collection of objects for basic PMIPv6 2127 monitoring." 2128 ::= { pmip6Groups 1 } 2130 pmip6BindingCacheGroup OBJECT-GROUP 2131 OBJECTS { 2132 pmip6BindingPBUFlag, 2133 pmip6BindingMnIndex, 2134 pmip6BindingMnLLIndex, 2135 pmip6BindingMagLinkLocalAddressType, 2136 pmip6BindingMagLinkLocalAddress, 2137 pmip6BindingTunnelIfIdentifier, 2138 pmip6BindingMnInterfaceATT, 2139 pmip6BindingTimeRecentlyAccepted, 2140 pmip6LmaMnIdentifier, 2141 pmip6LmaMnLLIdentifier 2142 } 2143 STATUS current 2144 DESCRIPTION 2145 " A collection of objects for monitoring the 2146 PMIPv6 extensions of the Binding Cache." 2147 ::= { pmip6Groups 2 } 2149 pmip6StatsGroup OBJECT-GROUP 2150 OBJECTS { 2151 pmip6MissingMnIdentifierOption, 2152 pmip6MagNotAuthorizedForProxyReg, 2153 pmip6NotLMAForThisMobileNode, 2154 pmip6ProxyRegNotEnabled, 2155 pmip6MissingHomeNetworkPrefixOption, 2156 pmip6MissingHandOffIndicatorOption, 2157 pmip6MissingAccessTechTypeOption, 2158 pmip6NotAuthorizedForHomeNetworkPrefix, 2159 pmip6TimestampMismatch, 2160 pmip6TimestampLowerThanPrevAccepted, 2161 pmip6BcePbuPrefixSetDoNotMatch, 2162 pmip6InitialBindingRegistrations, 2163 pmip6BindingLifeTimeExtensionNoHandOff, 2164 pmip6BindingLifeTimeExtensionAfterHandOff, 2165 pmip6BindingDeRegistrations, 2166 pmip6BindingBindingAcks, 2167 pmip6CounterDiscontinuityTime 2168 } 2169 STATUS current 2170 DESCRIPTION 2171 " A collection of objects for basic PMIPv6 2172 statistics monitoring. 2173 " 2174 ::= { pmip6Groups 3 } 2176 pmip6MagSystemGroup OBJECT-GROUP 2177 OBJECTS { 2178 pmip6MagStatus, 2179 pmip6MagProxyCOAState 2180 } 2181 STATUS current 2182 DESCRIPTION 2183 " A collection of objects for monitoring the 2184 PMIPv6 system related objects on a mobile router." 2185 ::= { pmip6Groups 4 } 2187 pmip6MagConfigurationGroup OBJECT-GROUP 2188 OBJECTS { 2189 pmip6MagHomeNetworkPrefixLength, 2190 pmip6MagHomeNetworkPrefixLifeTime, 2191 pmip6MagEnableMagLocalRouting 2192 } 2193 STATUS current 2194 DESCRIPTION 2195 " A collection of objects for monitoring the 2196 configuration related objects on a mobile access 2197 gateway. 2198 " 2199 ::= { pmip6Groups 5 } 2201 pmip6MagRegistrationGroup OBJECT-GROUP 2202 OBJECTS { 2203 pmip6MagBLFlag, 2204 pmip6MagBLMnIndex, 2205 pmip6MagBLMnLLIndex, 2206 pmip6MagBLMagLinkLocalAddressType, 2207 pmip6MagBLMagLinkLocalAddress, 2208 pmip6MagBLMagIfIdentifierToMn, 2209 pmip6MagBLTunnelIfIdentifier, 2210 pmip6MagBLMnInterfaceATT, 2211 pmip6MagBLTimeRecentlyAccepted, 2212 pmip6MagMnIdentifier, 2213 pmip6MagMnLLIdentifier, 2214 pmip6MagProfMnIdentifier, 2215 pmip6MagProfMnLocalMobilityAnchorAddressType, 2216 pmip6MagProfMnLocalMobilityAnchorAddress 2217 } 2218 STATUS current 2219 DESCRIPTION 2220 " A collection of objects for monitoring the 2221 registration related objects on a mobile access 2222 gateway. 2223 " 2224 ::= { pmip6Groups 6 } 2226 pmip6LmaSystemGroup OBJECT-GROUP 2227 OBJECTS { 2228 pmip6LmaStatus, 2229 pmip6LmaLMAAState 2230 } 2231 STATUS current 2232 DESCRIPTION 2233 " A collection of objects for monitoring the 2234 system related objects on an LMA." 2235 ::= { pmip6Groups 7 } 2237 pmip6LmaConfigurationGroup OBJECT-GROUP 2238 OBJECTS { 2239 pmip6LmaMinDelayBeforeBCEDelete, 2240 pmip6LmaMaxDelayBeforeNewBCEAssign, 2241 pmip6LmaTimestampValidityWindow, 2242 pmip6LmaHomeNetworkPrefixLength, 2243 pmip6LmaHomeNetworkPrefixLifeTime 2244 } 2245 STATUS current 2246 DESCRIPTION 2247 " A collection of objects for Monitoring the 2248 configuration related objects on an LMA." 2249 ::= { pmip6Groups 8 } 2251 pmip6MagNotificationGroup NOTIFICATION-GROUP 2252 NOTIFICATIONS { 2253 pmip6MagHomeTunnelEstablished, 2254 pmip6MagHomeTunnelReleased 2255 } 2256 STATUS current 2257 DESCRIPTION 2258 "A collection of notifications from a home agent 2259 or correspondent node to the Manager about the 2260 tunnel status of the mobile router. 2261 " 2262 ::= { pmip6Groups 9 } 2264 pmip6LmaNotificationGroup NOTIFICATION-GROUP 2265 NOTIFICATIONS { 2266 pmip6LmaHomeTunnelEstablished, 2267 pmip6LmaHomeTunnelReleased 2268 } 2269 STATUS current 2270 DESCRIPTION 2271 "A collection of notifications from a home agent 2272 or correspondent node to the Manager about the 2273 tunnel status of the mobile router. 2274 " 2275 ::= { pmip6Groups 10 } 2277 -- Compliance statements 2278 pmip6CoreCompliance MODULE-COMPLIANCE 2279 STATUS current 2280 DESCRIPTION 2281 "The compliance statement for SNMP entities 2282 which implement the PMIPV6-MIB. 2283 There are a number of INDEX objects that cannot be 2284 represented in the form of OBJECT clauses in 2285 SMIv2, but for which there are compliance 2286 requirements, expressed in OBJECT clause form in 2287 this description: 2288 -- OBJECT pmip6BindingHomeAddressType 2289 -- SYNTAX InetAddressType { ipv6(2) } 2290 -- DESCRIPTION 2291 -- This MIB module requires support for global 2292 -- ipv6 addresses for the pmip6BindingHomeAddress 2293 -- object. 2294 -- 2295 " 2296 MODULE -- this module 2297 MANDATORY-GROUPS { pmip6SystemGroup 2298 } 2299 ::= { pmip6Compliances 1 } 2301 pmip6Compliance2 MODULE-COMPLIANCE 2302 STATUS current 2303 DESCRIPTION 2304 "The compliance statement for SNMP entities 2305 which implement the PMIPV6-MIB. 2306 " 2307 MODULE -- this module 2308 MANDATORY-GROUPS { pmip6SystemGroup, 2309 pmip6BindingCacheGroup, 2310 pmip6StatsGroup 2311 } 2312 ::= { pmip6Compliances 2 } 2314 pmip6CoreReadOnlyCompliance MODULE-COMPLIANCE 2315 STATUS current 2316 DESCRIPTION 2317 "The compliance statement for SNMP entities 2318 that implement the PMIPV6-MIB without support 2319 for read-write (i.e., in read-only mode). 2320 " 2321 MODULE -- this module 2322 MANDATORY-GROUPS { pmip6SystemGroup 2323 } 2324 OBJECT pmip6MobileNodeGeneratedTimestampInUse 2325 MIN-ACCESS read-only 2326 DESCRIPTION 2327 "Write access is not required." 2328 OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinksType 2329 MIN-ACCESS read-only 2330 DESCRIPTION 2331 "Write access is not required." 2332 OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinks 2333 MIN-ACCESS read-only 2334 DESCRIPTION 2335 "Write access is not required." 2336 OBJECT pmip6FixedMagLinkLayerAddressOnAllAccessLinks 2337 MIN-ACCESS read-only 2338 DESCRIPTION 2339 "Write access is not required." 2341 ::= { pmip6Compliances 3 } 2343 pmip6ReadOnlyCompliance2 MODULE-COMPLIANCE 2344 STATUS current 2345 DESCRIPTION 2346 "The compliance statement for SNMP entities 2347 that implement the PMIPV6-MIB without support 2348 for read-write (i.e., in read-only mode). 2349 " 2350 MODULE -- this module 2351 MANDATORY-GROUPS { pmip6SystemGroup, 2352 pmip6BindingCacheGroup, 2353 pmip6StatsGroup 2354 } 2355 OBJECT pmip6MobileNodeGeneratedTimestampInUse 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "Write access is not required." 2359 OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinksType 2360 MIN-ACCESS read-only 2361 DESCRIPTION 2362 "Write access is not required." 2363 OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinks 2364 MIN-ACCESS read-only 2365 DESCRIPTION 2366 "Write access is not required." 2367 OBJECT pmip6FixedMagLinkLayerAddressOnAllAccessLinks 2368 MIN-ACCESS read-only 2369 DESCRIPTION 2370 "Write access is not required." 2372 ::= { pmip6Compliances 4 } 2374 pmip6MagCoreCompliance MODULE-COMPLIANCE 2375 STATUS current 2376 DESCRIPTION 2377 "The compliance statement for SNMP entities 2378 which implement the PMIPV6-MIB. 2380 There are a number of INDEX objects that cannot be 2381 represented in the form of OBJECT clauses in 2382 SMIv2, but for which there are compliance 2383 requirements, expressed in OBJECT clause form in 2384 this description: 2385 -- OBJECT pmip6MagProxyCOAType 2386 -- SYNTAX InetAddressType { ipv6(2) } 2387 -- DESCRIPTION 2388 -- This MIB module requires support for global 2389 -- IPv6 addresses for the pmip6MagProxyCOAType 2390 -- object. 2391 -- 2392 -- OBJECT pmip6MagProxyCOA 2393 -- SYNTAX InetAddress (SIZE(16)) 2394 -- DESCRIPTION 2395 -- This MIB module requires support for global 2396 -- IPv6 addresses for the pmip6MagProxyCOA 2397 -- object. 2398 -- 2399 " 2400 MODULE -- this module 2401 MANDATORY-GROUPS { pmip6MagSystemGroup 2402 } 2403 ::= { pmip6Compliances 5 } 2405 pmip6MagCompliance2 MODULE-COMPLIANCE 2406 STATUS current 2407 DESCRIPTION 2408 "The compliance statement for SNMP entities that 2409 implement the PMIPV6-MIB for monitoring configuration 2410 related information, registration details, and 2411 statistics on a mobile access gateway. 2413 There are a number of INDEX objects that cannot be 2414 represented in the form of OBJECT clauses in 2415 SMIv2, but for which there are compliance 2416 requirements, expressed in OBJECT clause form in 2417 this description: 2419 -- OBJECT pmip6MagProxyCOAType 2420 -- SYNTAX InetAddressType { ipv6(2) } 2421 -- DESCRIPTION 2422 -- This MIB module requires support for global 2423 -- IPv6 addresses for the pmip6MagProxyCOA 2424 -- object. 2425 -- 2426 -- OBJECT pmip6MagProxyCOA 2427 -- SYNTAX InetAddress (SIZE(16)) 2428 -- DESCRIPTION 2429 -- This MIB module requires support for global 2430 -- IPv6 addresses for the pmip6MagProxyCOAType 2431 -- object. 2432 -- 2433 -- OBJECT pmip6MagHomeNetworkPrefixType 2434 -- SYNTAX InetAddressType { ipv6(2) } 2435 -- DESCRIPTION 2436 -- This MIB module requires support for global 2437 -- IPv6 addresses for the 2438 -- pmip6MagHomeNetworkPrefix object. 2439 -- 2440 -- OBJECT pmip6MagHomeNetworkPrefix 2441 -- SYNTAX InetAddress (SIZE(16)) 2442 -- DESCRIPTION 2443 -- This MIB module requires support for global 2444 -- IPv6 addresses for the 2445 -- pmip6MagHomeNetworkPrefix object. 2446 -- 2447 " 2448 MODULE -- this module 2449 MANDATORY-GROUPS { pmip6MagSystemGroup, 2450 pmip6MagConfigurationGroup, 2451 pmip6MagRegistrationGroup 2452 } 2453 ::= { pmip6Compliances 6 } 2455 pmip6MagCoreReadOnlyCompliance MODULE-COMPLIANCE 2456 STATUS current 2457 DESCRIPTION 2458 "The compliance statement for SNMP entities 2459 which implement the PMIPV6-MIB without support 2460 for read-write (i.e., in read-only mode). 2461 There are a number of INDEX objects that cannot be 2462 represented in the form of OBJECT clauses in 2463 SMIv2, but for which there are compliance 2464 requirements, expressed in OBJECT clause form in 2465 this description: 2466 -- OBJECT pmip6MagProxyCOAType 2467 -- SYNTAX InetAddressType { ipv6(2) } 2468 -- DESCRIPTION 2469 -- This MIB module requires support for global 2470 -- IPv6 addresses for the pmip6MagProxyCOA 2471 -- object. 2472 -- 2473 -- OBJECT pmip6MagProxyCOA 2474 -- SYNTAX InetAddress (SIZE(16)) 2475 -- DESCRIPTION 2476 -- This MIB module requires support for global 2477 -- IPv6 addresses for the pmip6MagProxyCOAType 2478 -- object. 2479 -- 2480 -- OBJECT pmip6MagHomeNetworkPrefixType 2481 -- SYNTAX InetAddressType { ipv6(2) } 2482 -- DESCRIPTION 2483 -- This MIB module requires support for global 2484 -- IPv6 addresses for the 2485 -- pmip6MagHomeNetworkPrefix object. 2486 -- 2487 " 2488 MODULE -- this module 2489 MANDATORY-GROUPS { pmip6MagSystemGroup 2490 } 2491 OBJECT pmip6MagStatus 2492 MIN-ACCESS read-only 2493 DESCRIPTION 2494 "Write access is not required." 2495 ::= { pmip6Compliances 7 } 2497 pmip6MagReadOnlyCompliance2 MODULE-COMPLIANCE 2498 STATUS current 2499 DESCRIPTION 2500 "The compliance statement for SNMP entities that 2501 implement the PMIPV6-MIB without support for read- 2502 write (i.e., in read-only mode) and with support 2503 for monitoring configuration related information, 2504 registration details, and statistics on a mobile 2505 access gateway. 2507 There are a number of INDEX objects that cannot be 2508 represented in the form of OBJECT clauses in 2509 SMIv2, but for which there are compliance 2510 requirements, expressed in OBJECT clause form in 2511 this description: 2513 -- OBJECT pmip6MagProxyCOAType 2514 -- SYNTAX InetAddressType { ipv6(2) } 2515 -- DESCRIPTION 2516 -- This MIB module requires support for global 2517 -- IPv6 addresses for the pmip6MagProxyCOA 2518 -- object. 2519 -- 2520 -- OBJECT pmip6MagProxyCOA 2521 -- SYNTAX InetAddress (SIZE(16)) 2522 -- DESCRIPTION 2523 -- This MIB module requires support for global 2524 -- IPv6 addresses for the pmip6MagProxyCOAType 2525 -- object. 2526 -- 2527 -- OBJECT pmip6MagHomeNetworkPrefixType 2528 -- SYNTAX InetAddressType { ipv6(2) } 2529 -- DESCRIPTION 2530 -- This MIB module requires support for global 2531 -- IPv6 addresses for the 2532 -- pmip6MagHomeNetworkPrefix object. 2533 -- 2534 -- OBJECT pmip6MagHomeNetworkPrefix 2535 -- SYNTAX InetAddress (SIZE(16)) 2536 -- DESCRIPTION 2537 -- This MIB module requires support for global 2538 -- IPv6 addresses for the 2539 -- pmip6MagHomeNetworkPrefix object. 2540 -- 2541 " 2542 MODULE -- this module 2543 MANDATORY-GROUPS { pmip6MagSystemGroup, 2544 pmip6MagConfigurationGroup, 2545 pmip6MagRegistrationGroup 2546 } 2547 OBJECT pmip6MagStatus 2548 MIN-ACCESS read-only 2549 DESCRIPTION 2550 "Write access is not required." 2551 OBJECT pmip6MagEnableMagLocalRouting 2552 MIN-ACCESS read-only 2553 DESCRIPTION 2554 "Write access is not required." 2556 ::= { pmip6Compliances 8 } 2558 pmip6LmaCoreCompliance MODULE-COMPLIANCE 2559 STATUS current 2560 DESCRIPTION 2561 "The compliance statement for SNMP entities 2562 which implement the PMIPV6-MIB. 2563 There are a number of INDEX objects that cannot be 2564 represented in the form of OBJECT clauses in 2565 SMIv2, but for which there are compliance 2566 requirements, expressed in OBJECT clause form in 2567 this description: 2568 -- OBJECT pmip6LmaLMAAType 2569 -- SYNTAX InetAddressType { ipv6(2) } 2570 -- DESCRIPTION 2571 -- This MIB module requires support for global 2572 -- IPv6 addresses for the pmip6LmaLMAA 2573 -- object. 2574 -- 2575 -- OBJECT pmip6LmaLMAA 2576 -- SYNTAX InetAddress (SIZE(16)) 2577 -- DESCRIPTION 2578 -- This MIB module requires support for global 2579 -- IPv6 addresses for the pmip6LmaLMAA 2580 -- object. 2581 -- 2582 " 2583 MODULE -- this module 2584 MANDATORY-GROUPS { pmip6LmaSystemGroup 2585 } 2586 ::= { pmip6Compliances 9 } 2588 pmip6LmaCompliance2 MODULE-COMPLIANCE 2589 STATUS current 2590 DESCRIPTION 2591 "The compliance statement for SNMP entities that 2592 implement the PMIPV6-MIB for monitoring configuration 2593 related information, registration details, and 2594 statistics on a mobile access gateway. 2596 There are a number of INDEX objects that cannot be 2597 represented in the form of OBJECT clauses in 2598 SMIv2, but for which there are compliance 2599 requirements, expressed in OBJECT clause form in 2600 this description: 2602 -- OBJECT pmip6LmaLMAAType 2603 -- SYNTAX InetAddressType { ipv6(2) } 2604 -- DESCRIPTION 2605 -- This MIB module requires support for global 2606 -- IPv6 addresses for the pmip6LmaLMAA 2607 -- object. 2608 -- 2609 -- OBJECT pmip6LmaLMAA 2610 -- SYNTAX InetAddress (SIZE(16)) 2611 -- DESCRIPTION 2612 -- This MIB module requires support for global 2613 -- IPv6 addresses for the pmip6LmaLMAA 2614 -- object. 2615 -- 2616 -- OBJECT pmip6LmaHomeNetworkPrefixType 2617 -- SYNTAX InetAddressType { ipv6(2) } 2618 -- DESCRIPTION 2619 -- This MIB module requires support for global 2620 -- IPv6 addresses for the 2621 -- pmip6LmaHomeNetworkPrefix object. 2622 -- 2623 -- OBJECT pmip6LmaHomeNetworkPrefix 2624 -- SYNTAX InetAddress (SIZE(16)) 2625 -- DESCRIPTION 2626 -- This MIB module requires support for global 2627 -- IPv6 addresses for the 2628 -- pmip6LmaHomeNetworkPrefix object. 2629 -- 2630 " 2631 MODULE -- this module 2632 MANDATORY-GROUPS { pmip6LmaSystemGroup, 2633 pmip6LmaConfigurationGroup 2634 } 2635 ::= { pmip6Compliances 10 } 2637 pmip6LmaReadOnlyCompliance MODULE-COMPLIANCE 2638 STATUS current 2639 DESCRIPTION 2640 "The compliance statement for SNMP entities 2641 which implement the PMIPV6-MIB. 2642 There are a number of INDEX objects that cannot be 2643 represented in the form of OBJECT clauses in 2644 SMIv2, but for which there are compliance 2645 requirements, expressed in OBJECT clause form in 2646 this description: 2647 -- OBJECT pmip6LmaLMAAType 2648 -- SYNTAX InetAddressType { ipv6(2) } 2649 -- DESCRIPTION 2650 -- This MIB module requires support for global 2651 -- IPv6 addresses for the pmip6LmaLMAA 2652 -- object. 2653 -- 2654 -- OBJECT pmip6LmaLMAA 2655 -- SYNTAX InetAddress (SIZE(16)) 2656 -- DESCRIPTION 2657 -- This MIB module requires support for global 2658 -- IPv6 addresses for the pmip6LmaLMAA 2659 -- object. 2660 -- 2661 " 2662 MODULE -- this module 2663 MANDATORY-GROUPS { pmip6LmaSystemGroup 2664 } 2665 OBJECT pmip6LmaStatus 2666 MIN-ACCESS read-only 2667 DESCRIPTION 2668 "Write access is not required." 2669 ::= { pmip6Compliances 11 } 2671 pmip6LmaReadOnlyCompliance2 MODULE-COMPLIANCE 2672 STATUS current 2673 DESCRIPTION 2674 "The compliance statement for SNMP entities that 2675 implement the PMIPV6-MIB without support 2676 for read-write (i.e., in read-only mode) and for 2677 monitoring configuration related information, 2678 registration details, and statistics on a mobile 2679 access gateway. 2681 There are a number of INDEX objects that cannot be 2682 represented in the form of OBJECT clauses in 2683 SMIv2, but for which there are compliance 2684 requirements, expressed in OBJECT clause form in 2685 this description: 2687 -- OBJECT pmip6LmaLMAAType 2688 -- SYNTAX InetAddressType { ipv6(2) } 2689 -- DESCRIPTION 2690 -- This MIB module requires support for global 2691 -- IPv6 addresses for the pmip6LmaLMAA 2692 -- object. 2694 -- 2695 -- OBJECT pmip6LmaLMAA 2696 -- SYNTAX InetAddress (SIZE(16)) 2697 -- DESCRIPTION 2698 -- This MIB module requires support for global 2699 -- IPv6 addresses for the pmip6LmaLMAA 2700 -- object. 2701 -- 2702 -- OBJECT pmip6LmaHomeNetworkPrefixType 2703 -- SYNTAX InetAddressType { ipv6(2) } 2704 -- DESCRIPTION 2705 -- This MIB module requires support for global 2706 -- IPv6 addresses for the 2707 -- pmip6LmaHomeNetworkPrefix object. 2708 -- 2709 -- OBJECT pmip6LmaHomeNetworkPrefix 2710 -- SYNTAX InetAddress (SIZE(16)) 2711 -- DESCRIPTION 2712 -- This MIB module requires support for global 2713 -- IPv6 addresses for the 2714 -- pmip6LmaHomeNetworkPrefix object. 2715 -- 2716 " 2717 MODULE -- this module 2718 MANDATORY-GROUPS { pmip6LmaSystemGroup, 2719 pmip6LmaConfigurationGroup 2720 } 2721 OBJECT pmip6LmaStatus 2722 MIN-ACCESS read-only 2723 DESCRIPTION 2724 "Write access is not required." 2725 OBJECT pmip6LmaMinDelayBeforeBCEDelete 2726 MIN-ACCESS read-only 2727 DESCRIPTION 2728 "Write access is not required." 2729 OBJECT pmip6LmaMaxDelayBeforeNewBCEAssign 2730 MIN-ACCESS read-only 2731 DESCRIPTION 2732 "Write access is not required." 2733 OBJECT pmip6LmaTimestampValidityWindow 2734 MIN-ACCESS read-only 2735 DESCRIPTION 2736 "Write access is not required." 2737 OBJECT pmip6LmaHomeNetworkPrefixLifeTime 2738 MIN-ACCESS read-only 2739 DESCRIPTION 2740 "Write access is not required." 2742 ::= { pmip6Compliances 12 } 2744 pmip6MagNotificationCompliance MODULE-COMPLIANCE 2745 STATUS current 2746 DESCRIPTION 2747 "The compliance statement for SNMP entities that 2748 implement the PMIPV6-MIB and support Notification 2749 from the mobile access gateway. 2750 " 2751 MODULE -- this module 2752 MANDATORY-GROUPS { pmip6MagNotificationGroup 2753 } 2754 ::= { pmip6Compliances 13 } 2756 pmip6LmaNotificationCompliance MODULE-COMPLIANCE 2757 STATUS current 2758 DESCRIPTION 2759 "The compliance statement for SNMP entities that 2760 implement the PMIPV6-MIB and support Notification 2761 from the LMA. 2762 " 2763 MODULE -- this module 2764 MANDATORY-GROUPS { pmip6LmaNotificationGroup 2765 } 2766 ::= { pmip6Compliances 14 } 2768 END 2770 6. Security Considerations 2772 There are a number of management objects defined in this MIB module 2773 with a MAX-ACCESS clause of read-write. Such objects may be 2774 considered sensitive or vulnerable in some network environments. The 2775 support for SET operations in a non-secure environment without proper 2776 protection can have a negative effect on network operations. These 2777 are the tables and objects and the corresponding 2778 sensitivity/vulnerability: 2779 pmip6MagStatus: 2780 pmip6LmaStatus: 2781 The value of these objects is used to enable or disable 2782 the PMIPv6 functionality on the corresponding PMIPv6 entity. 2783 Access to these MOs may be abused to disrupt the communication 2784 that depends on the PMIPv6 functionality. 2785 pmip6MobileNodeGeneratedTimestampInUse: 2786 pmip6FixedMagLinkLocalAddressOnAllAccessLinksType: 2787 pmip6FixedMagLinkLocalAddressOnAllAccessLinks: 2788 pmip6FixedMagLinkLayerAddressOnAllAccessLinks: 2789 pmip6MagEnableMagLocalRouting: 2790 pmip6MagHomeNetworkPrefixLifeTime: 2791 pmip6LmaMinDelayBeforeBCEDelete: 2792 pmip6LmaMaxDelayBeforeNewBCEAssign: 2793 pmip6LmaTimestampValidityWindow: 2794 pmip6LmaHomeNetworkPrefixLifeTime: 2795 Access to the above MOs may be abused to misconfigure PMIPv6 2796 entities and disrupt communications. 2798 Some of the readable objects in this MIB module (i.e., objects with a 2799 MAX-ACCESS other than not-accessible) may be considered sensitive or 2800 vulnerable in some network environments. It is thus important to 2801 control even GET and/or NOTIFY access to these objects and possibly 2802 to even encrypt the values of these objects when sending them over 2803 the network via SNMP. These are the tables and objects and their 2804 sensitivity/vulnerability: 2806 pmip6LmaHomeNetworkPrefixType: 2807 pmip6LmaHomeNetworkPrefix: 2808 pmip6LmaHomeNetworkPrefixLength: 2809 The above address-related objects may be considered to be 2810 particularly sensitive and/or private. 2811 pmip6MagMnIdentifier: 2812 pmip6MagMnLLIdentifier: 2813 pmip6LmaMnIdentifier: 2814 pmip6LmaMnLLIdentifier: 2816 pmip6MagProfMnIdentifier: 2817 The above MN Identifier-related MOs may be used to identify 2818 users. These may be considered to be sensitive and/or private. 2820 SNMP versions prior to SNMPv3 did not include adequate security. 2821 Even if the network itself is secure (for example by using IPsec), 2822 even then, there is no control as to who on the secure network is 2823 allowed to access and GET/SET (read/change/create/delete) the objects 2824 in this MIB module. 2826 It is RECOMMENDED that implementers consider the security features as 2827 provided by the SNMPv3 framework (see [RFC3410], section 8), 2828 including full support for the SNMPv3 cryptographic mechanisms (for 2829 authentication and privacy). 2831 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2832 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2833 enable cryptographic security. It is then a customer/operator 2834 responsibility to ensure that the SNMP entity giving access to an 2835 instance of this MIB module is properly configured to give access to 2836 the objects only to those principals (users) that have legitimate 2837 rights to indeed GET or SET (change/create/delete) them. 2839 7. IANA Considerations 2841 IANA should assign 2842 1. a base arc in the 'mib-2' (standards track) OID 2843 tree for the 'pmip6TCMIB' MODULE-IDENTITY defined in the 2844 PMIPV6-TC-MIB. 2845 2. a base arc in the 'mib-2' (standards track) OID 2846 tree for the 'pmip6MIB' MODULE-IDENTITY defined in the 2847 PMIPV6-MIB. 2849 8. References 2851 8.1 Normative References 2853 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 2854 Requirements Levels, BCP 14, RFC 2119, March 1997. 2856 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2857 J., Rose, M. and S. Waldbusser, Structure of 2858 Management Information Version 2 (SMIv2), STD 58, 2859 RFC 2578, April 1999. 2861 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2862 J., Rose, M. and S. Waldbusser, Textual Conventions 2863 for SMIv2, STD 58, RFC 2579, April 1999. 2865 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2866 J., Rose, M. and S. Waldbusser, Conformance 2867 Statements for SMIv2, STD 58, RFC 2580, April 1999. 2869 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility 2870 Support in IPv6 RFC 3775, June 2004. 2872 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, 2873 K., and Patil, B., Proxy Mobile IPv6, RFC 5213, 2874 August 2008. 2876 [RFC4293] Routhier, S., Management Information Base for the 2877 Internet Protocol (IP), RFC 4293, April 2006. 2879 [RFC4001] Daniele, M., Haberman, B., Routhier, S. and 2880 Schoenwaelder, J., Textual Conventions for Internet 2881 Network Addresses, RFC 4001, February 2005. 2883 [RFC2863] McCloghrie, K., and Kastenholz., F., The Interfaces 2884 Group MIB, RFC 2863, June 2000. 2886 [RFC4295] Keeni, G., Koide, K., Nagami, K. and Gundavelli, S., The 2887 Mobile IPv6 MIB, RFC 4295, April 2006. 2889 [RFC4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, The 2890 Network Access Identifier, RFC 4282, December 2005. 2892 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 2893 Chowdhury, Mobile Node Identifier Option for Mobile 2894 IPv6 (MIPv6), RFC 4283, November 2005. 2896 8.2 Informative References 2898 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2899 Introduction and Applicability Statements for 2900 Internet-Standard Management Framework, RFC 3410, 2901 December 2002. 2903 [RFC4831] Kempf, J., Goals for Network-Based Localized Mobility 2904 Management (NETLMM), RFC 4831, April 2007. 2906 9. Acknowledgements 2908 The following individuals and groups have contributed to this draft 2909 with discussions and comments: 2910 Adrian Farrel 2911 Dan Romascanu 2912 David Harrington 2913 Dirk von-Hugo 2914 Francis Dupont 2915 Harrie Hazewinkel 2916 Jari Arkko 2917 Sean Turner 2918 Stephen Farrell 2919 Vincent Roca 2920 WIDE Project netman-WG 2922 10. Authors' Addresses 2924 Glenn Mansfield Keeni 2925 Cyber Solutions Inc. 2926 6-6-3 Minami Yoshinari 2927 Aoba-ku, Sendai 989-3204 2928 Japan 2930 Phone: +81-22-303-4012 2931 E-mail: glenn@cysols.com 2933 Kazuhide Koide 2934 KDDI Corporation 2935 GARDEN AIR TOWER 3-10-10, Iidabashi 2936 Chiyoda-ku, Tokyo, 102-8460 2937 Japan 2939 Phone: +81-3-6678-3378 2940 E-mail: ka-koide@kddi.com 2942 Sri Gundavelli 2943 Cisco Systems 2944 170 W.Tasman Drive, 2945 San Jose, CA 95134 2946 USA 2948 Phone: +1-408-527-6109 2949 E-mail: sgundave@cisco.com 2950 Ryuji Wakikawa 2951 TOYOTA InfoTechnology Center, U.S.A., Inc. 2952 465 Bernardo Avenue 2953 Mountain View, CA 94043 2954 USA 2955 E-mail: ryuji@us.toyota-itc.com