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