NETLMM Working Group Glenn Mansfield Keeni INTERNET-DRAFT Cyber Solutions Inc. Intended Status: Proposed Standard Koide Kazuhide Expires: January 6, 2009 Tohoku University S. Gundavelli Cisco R. Wakikawa Keio University July 7, 2008 Proxy Mobile IPv6 Management Information Base Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This document is a product of the NETLMM Working Group. Comments should be addressed to the authors or the mailing list at netlmm@ietf.org This Internet-Draft will expire on January 6, 2009. Copyright Notice Copyright (C) The IETF Trust (2008). Glenn M. Keeni. Expires: January 6, 2009 [Page 1] Internet Draft pmip6MIB July 2008 Abstract This memo defines a portion of the Management Information Base (MIB), the Proxy Mobile-IPv6 MIB, for use with network management protocols in the Internet community. In particular, the Proxy Mobile-IPv6 MIB will be used to monitor and control the mobile access gateway node and the local mobility anchor functions of a Proxy Mobile IPv6 (PMIPv6) entity. Table of Contents 1. The Internet-Standard Management Framework ................... 3 2. Overview ..................................................... 2 2.1. The Proxy Mobile IPv6 Protocol Entities ................. 2 2.2. Terminology ............................................. 3 3. Proxy Mobile IPv6 Monitoring and Control Requirements ........ 3 4. MIB Design ................................................... 4 5. The Proxy Mobile-IPv6 MIB .................................... 6 6. Security Considerations ...................................... 14 7. IANA Considerations .......................................... 16 8. References ................................................... 16 8.1. Normative References .................................... 16 8.2. Informative References .................................. 17 9. Acknowledgements ............................................. 17 10. Author's Addresses ........................................... 18 11. Full Copyright Statement ..................................... 19 Appendix ..................................................... 13 Glenn M. Keeni. Expires: January 6, 2009 [Page 2] Internet Draft pmip6MIB July 2008 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 2. Overview 2.1. The Proxy Mobile IPv6 Protocol and entities Proxy Mobile IPv6 (MIPv6) [PMIPv6] is an extension to the Mobile IPv6 protocol which facilitates network-based localized mobility management (NETLMM) of IPv6 nodes in a PMIPv6 domain. to remain reachable while moving around in the IPv6 Internet. 2.2. Terminology The terminology used in this document is consistent with the definitions used in the Mobile IPv6 protocol specification[RFC3775] and in NETLMM Goals document [RFC4831]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119]. 3. Proxy Mobile IPv6 Monitoring and Control Requirements For managing a PMIPv6 entity it is necessary to monitor the following: o capabilities of PMIPv6 entities o traffic due to PMIPv6 o binding related statistics (at LMA and MAG) o binding related details (at LMA agent and MAG) o history of Binding Updates (at LMA agent and MAG) Glenn M. Keeni. Expires: January 6, 2009 [Page 3] Internet Draft pmip6MIB July 2008 4. MIB Design. The basic principle has been to keep the MIB as simple as possible and at the same time to make it effective enough so that the essential needs of monitoring and control are met. It is assumed that the Proxy Mobile IPv6 Management Information Base (PMIPV6-MIB) will always be implemented in conjunction with the MOBILEIPV6-MIB. The PMIPV6-MIB comprises of the following primary groups: o pmip6System o pmip6Configuration o pmip6Stats o pmip6Notifications o pmip6Conformance Glenn M. Keeni. Expires: January 6, 2009 [Page 4] Internet Draft pmip6MIB July 2008 5. The Proxy Mobile-IPv6 MIB. PMIPV6-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2, Counter32, Gauge32, -- Counter64, OBJECT-TYPE, NOTIFICATION-TYPE FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, DateAndTime FROM SNMPv2-TC -- SnmpAdminString -- FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF InetAddressType, InetAddress, InetAddressPrefixLength FROM INET-ADDRESS-MIB Ipv6AddressIfIdentifierTC FROM IP-MIB -- InterfaceIndex -- FROM IF-MIB mip6BindingHomeAddressType, mip6BindingHomeAddress, -- mip6HaListEntry, mip6MnBLEntry, mip6BindingCacheEntry mip6MnBLEntry, mip6BindingCacheEntry FROM MOBILEIPV6-MIB ; pmip6MIB MODULE-IDENTITY LAST-UPDATED "200807060000Z" -- 6th July, 2008 ORGANIZATION "IETF PMIPV6 Working Group" CONTACT-INFO " Glenn Mansfield Keeni Postal: Cyber Solutions Inc. 6-6-3, Minami Yoshinari Aoba-ku, Sendai, Japan 989-3204. Tel: +81-22-303-4012 Fax: +81-22-303-4015 E-mail: glenn@cysols.com Kazuhide Koide Postal: Tohoku University Research Institute of Electrical Communication, Glenn M. Keeni. Expires: January 6, 2009 [Page 5] Internet Draft pmip6MIB July 2008 Tohoku University. 2-1-1 Katahira, Aoba-ku, Sendai, Miyagi, Japan 980-8577. Tel: +81-22-217-5455 E-mail: koide@shiratori.riec.tohoku.ac.jp Sri Gundavelli Postal: Cisco 170 W.Tasman Drive, San Jose, CA 95134 USA Tel: +1-408-527-6109 Email: sgundave@cisco.com Ryuji Wakikawa Postal: Keio University Department of Environmental Information, Keio University. 5322 Endo Fujisawa, Kanagawa 252-8520 Japan Email: ryuji@sfc.wide.ad.jp Support Group E-mail: netlmm@ietf.org" DESCRIPTION "The MIB module for monitoring a PMIPV6 entity. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices. " -- RFC Ed.: replace XXXX with actual RFC number and remove this -- note REVISION "200807060000Z" -- 6th July 2008 DESCRIPTION "Initial version, published as RFC XXXX." -- RFC Ed.: replace XXXX with actual RFC number and remove this -- note Glenn M. Keeni. Expires: January 6, 2009 [Page 6] Internet Draft pmip6MIB July 2008 -- ::= { mib-2 YYY } ::= { mib-2 999 } -- will be assigned by IANA -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' -- subtree and record the assignment in the SMI Numbers -- registry. -- -- RFC Ed.: When the above assignment has been made, please -- remove the above note -- replace "YYY" here with the assigned value and -- remove this note. -- ------------------------------------------------------------- -- Textual Conventions -- ------------------------------------------------------------- Glenn M. Keeni. Expires: January 6, 2009 [Page 7] Internet Draft pmip6MIB July 2008 MNIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The identity of a mobile node in the Proxy Mobile IPv6 domain. This is the stable identifier of a mobile node that the mobility entities in a Proxy Mobile IPv6 domain can always acquire and use it for predictably identifying a mobile node. This is typically an identifier such as Network Access Identifier (NAI) [RFC-4282] or other identifier such as a Media Access Control (MAC) address. " REFERENCE " draft-ietf-netlmm-proxymip6-18.txt : Section 2.2." SYNTAX OCTET STRING (SIZE (0..255)) MNLlIdentifier ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An identifier that identifies the attached interface of a mobile node. For those interfaces that have a link-layer identifier, this identifier can be based on that. The link-layer identifier in some cases is generated by the mobile node and conveyed to the mobile access gateway. This identifier of the attached interface must be stable as seen by any of the mobile access gateways in a given Proxy Mobile IPv6 domain. In some other cases, there might not be any link-layer identifier associated with the mobile node's interface. An identifier value of ALL_ZERO is not considered a valid identifier and cannot be used as an interface identifier. " REFERENCE " draft-ietf-netlmm-proxymip6-18.txt : Section 2.2." SYNTAX OCTET STRING (SIZE (0..255)) Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This specifies the access technology through which the mobile node is connected to the access link on the mobile access gateway. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 8.5." SYNTAX INTEGER Glenn M. Keeni. Expires: January 6, 2009 [Page 8] Internet Draft pmip6MIB July 2008 { reserved (0), logicalNetworkInterface(1), pointToPointInterface (2), ethernet (3), wirelessLan (4), wimax (5) } -- The PMIPV6 MIB has the following 5 primary groups pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 } pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 } pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 3 } pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 } pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 } pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 } -- The sub groups pmip6System OBJECT IDENTIFIER ::= { pmip6Core 1 } pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 } pmip6Configuration OBJECT IDENTIFIER ::= { pmip6Core 3 } pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 } pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 } pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 } pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 } -- The pmip6Configuration group has the following sub groups -- The pmip6Stats group has the following sub groups pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 } -- -- -- pmip6System group -- Glenn M. Keeni. Expires: January 6, 2009 [Page 9] Internet Draft pmip6MIB July 2008 -- pmip6MagProxyCOATable OBJECT-TYPE SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table models the Proxy Care-of Addresses configured on the egress interfaces of the mobile access gateway and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 6.10." ::= { pmip6System 1 } pmip6MagProxyCOAEntry OBJECT-TYPE SYNTAX Pmip6MagProxyCOAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry represents a conceptual row in the Proxy-CoA table. It represents each Proxy-CoA on the mobile access gateway. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113 then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. " INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA } ::= { pmip6MagProxyCOATable 1 } Glenn M. Keeni. Expires: January 6, 2009 [Page 10] Internet Draft pmip6MIB July 2008 Pmip6MagProxyCOAEntry ::= SEQUENCE { pmip6MagProxyCOAType InetAddressType, pmip6MagProxyCOA InetAddress, pmip6MagProxyCOAState INTEGER } pmip6MagProxyCOAType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The InetAddressType of the pmip6MagProxyCOA that follows. " ::= { pmip6MagProxyCOAEntry 1 } pmip6MagProxyCOA OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Proxy-CoA configured on the egress interface of the mobile access gateway. The type of the address represented by this object is specified by the corresponding pmip6MagProxyCOAType object. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 6.10." ::= { pmip6MagProxyCOAEntry 2 } pmip6MagProxyCOAState OBJECT-TYPE SYNTAX INTEGER { unknown(1), activated(2), tunneled(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the state of the Proxy-CoA: unknown -- The state of the Proxy-CoA cannot be determined. Glenn M. Keeni. Expires: January 6, 2009 [Page 11] Internet Draft pmip6MIB July 2008 activated -- The Proxy-CoA is ready to establish tunnel tunneled -- The Proxy-CoA is used to set up the bi-directional tunnel. " ::= { pmip6MagProxyCOAEntry 3 } pmip6HomeNetworkPrefixTable OBJECT-TYPE SYNTAX SEQUENCE OF PMip6HomeNetworkPrefixEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table representing the NEMO prefixes. " REFERENCE "XXXXXXXXXXXXXXXXXXXXXXXX" ::= { pmip6Configuration 1 } pmip6HomeNetworkPrefixEntry OBJECT-TYPE SYNTAX PMip6HomeNetworkPrefixEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the HomeNetwork Prefixes table table. Implementers need to be aware that if the total number of octets in pmip6HomeNetworkPrefix exceeds 114 then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. " INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress, pmip6HomeNetworkPrefixType, pmip6HomeNetworkPrefix, pmip6HomeNetworkPrefixLength } ::= { pmip6HomeNetworkPrefixTable 1 } PMip6HomeNetworkPrefixEntry ::= SEQUENCE { pmip6HomeNetworkPrefixType InetAddressType, pmip6HomeNetworkPrefix InetAddress, pmip6HomeNetworkPrefixLength InetAddressPrefixLength, Glenn M. Keeni. Expires: January 6, 2009 [Page 12] Internet Draft pmip6MIB July 2008 pmip6HomeNetworkPrefixLifeTime Gauge32 } pmip6HomeNetworkPrefixType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The InetAddressType of the pmip6HomeNetworkPrefix that follows. " ::= { pmip6HomeNetworkPrefixEntry 1 } pmip6HomeNetworkPrefix OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The mobile network prefix that is delegated to the mobile node. The type of the address represented by this object is specified by the corresponding pmip6HomeNetworkPrefixType object. " REFERENCE "XXXXXXXXXXXXXXXXXXXXXXXX" ::= { pmip6HomeNetworkPrefixEntry 2 } pmip6HomeNetworkPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength MAX-ACCESS not-accessible STATUS current DESCRIPTION "The prefix length of the mobile network prefix. " ::= { pmip6HomeNetworkPrefixEntry 3 } pmip6HomeNetworkPrefixLifeTime OBJECT-TYPE SYNTAX Gauge32 UNITS "seconds" MAX-ACCESS read-only Glenn M. Keeni. Expires: January 6, 2009 [Page 13] Internet Draft pmip6MIB July 2008 STATUS current DESCRIPTION "The lifetime (in seconds) granted to the mobile router for this registration. " ::= { pmip6HomeNetworkPrefixEntry 4 } pmip6MagEnableMagLocalRouting OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This flag indicates whether or not the mobile access gateway is allowed to enable local routing of the traffic exchanged between a visiting mobile node and a correspondent node that is locally connected to one of the interfaces of the mobile access gateway. The correspondent node can be another visiting mobile node as well, or a local fixed node. The default value for this flag is set to disabled(2)." REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 9.2." ::= { pmip6MagConf 1 } pmip6MagBLTable OBJECT-TYPE SYNTAX SEQUENCE OF Pmip6MnBLEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table corresponds to the Binding Update List(BL) that includes Proxy MIPv6 related information and is maintained by the mobile access gateway. Entries from the table are deleted as the lifetime of the binding expires. " REFERENCE "RFC 3775 : Section 4.5, 11.1, draft-ietf-netlmm-proxymip6-18.txt : Section 6.1" ::= { pmip6MagRegistration 1 } pmip6MagBLEntry OBJECT-TYPE Glenn M. Keeni. Expires: January 6, 2009 [Page 14] Internet Draft pmip6MIB July 2008 SYNTAX Pmip6MnBLEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing additional information contained in a Binding Update sent by the mobile access gateway to the local mobility anchor. " AUGMENTS {mip6MnBLEntry} ::= { pmip6MagBLTable 1 } Pmip6MnBLEntry ::= SEQUENCE { pmip6MagBLFlag TruthValue, pmip6MagBLMnIdentifier MNIdentifier, pmip6MagBLlMnIdentifier MNLlIdentifier, pmip6MagBLMagLinkLocalAddressType InetAddressType, pmip6MagBLMagLinkLocalAddress InetAddress, pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC, pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC, pmip6MagBLAccessTechnologyType Pmip6PBUAccessTechnologyType, pmip6MagBLTimeRecentlyAccepted DateAndTime } pmip6MagBLFlag OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "true(1) if the mobile access gateway sent the proxy binding update with Proxy Registration Flag that indicates to the local mobility anchor that the registration is the proxy binding update and is from a mobile access gateway. false(0) implies that the mobile access gateway is behaving as a simple mobile node. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 8.1." ::= { pmip6MagBLEntry 1 } pmip6MagBLMnIdentifier OBJECT-TYPE SYNTAX MNIdentifier MAX-ACCESS read-write STATUS current Glenn M. Keeni. Expires: January 6, 2009 [Page 15] Internet Draft pmip6MIB July 2008 DESCRIPTION "The Identifier of the attached mobile node. This identifier is acquired during the mobile node's attachment to the access link. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 6.1, 8.1." ::= { pmip6MagBLEntry 2 } pmip6MagBLlMnIdentifier OBJECT-TYPE SYNTAX MNLlIdentifier MAX-ACCESS read-write STATUS current DESCRIPTION "The link-layer identifier of the mobile node's connected interface. This can be acquired from the received Router Solicitation messages from the mobile node or during the mobile node's attachment to the access network. If this identifier is not available, this variable length field MUST be set to two (octets) and MUST be initialized to a value of ALL_ZERO. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 6.1, 8.1." ::= { pmip6MagBLEntry 3 } pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION "The InetAddressType of the pmip6MagBLMagLinkLocalAddress that follows. " ::= { pmip6MagBLEntry 4 } pmip6MagBLMagLinkLocalAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "The Link-local address of the mobile access gateway on the access link shared with the mobile node. Glenn M. Keeni. Expires: January 6, 2009 [Page 16] Internet Draft pmip6MIB July 2008 This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Update message. " REFERENCE "RFC 3963 : Section 4.1, 5.1" ::= { pmip6MagBLEntry 5 } pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE SYNTAX Ipv6AddressIfIdentifierTC MAX-ACCESS read-write STATUS current DESCRIPTION "The interface identifier (if-id) of the point-to-point link between the mobile node and the mobile access gateway. This is internal to the mobile access gateway and is used to associate the Proxy Mobile IPv6 tunnel to the access link where the mobile node is attached. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 6.1, 8.1." ::= { pmip6MagBLEntry 6 } pmip6MagBLTunnelIfIdentifier OBJECT-TYPE SYNTAX Ipv6AddressIfIdentifierTC MAX-ACCESS read-write STATUS current DESCRIPTION "The tunnel interface identifier (tunnel-if-id) of the bi-directional tunnel between the mobile node's local mobility anchor and the mobile access gateway. This is internal to the mobile access gateway. The tunnel interface identifier is acquired during the tunnel creation. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 6.1, 8.1." ::= { pmip6MagBLEntry 7 } pmip6MagBLAccessTechnologyType OBJECT-TYPE SYNTAX Pmip6PBUAccessTechnologyType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the access Glenn M. Keeni. Expires: January 6, 2009 [Page 17] Internet Draft pmip6MIB July 2008 technology by which the mobile node is currently attached to the mobile access gateway. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 6.9.1.1, 6.9.1.5, 8.1." ::= { pmip6MagBLEntry 8 } pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time-of-day on the mobile access gateway, when the proxy binding acknowledgement message with the Status field set to 0 was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence number based scheme is in use), the value MUST be set to ALL_ZERO. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 8.1" ::= { pmip6MagBLEntry 9 } pmip6MagMnProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table corresponds to the mobile node's policy profile that includes the essential operational parameters that are required by the network entities for managing the mobile node's mobility service. This table only contains policy profiles of mobile nodes that is connected to the mobile access gateway. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 6.2" ::= { pmip6MagRegistration 2 } pmip6MagMnProfileEntry OBJECT-TYPE Glenn M. Keeni. Expires: January 6, 2009 [Page 18] Internet Draft pmip6MIB July 2008 SYNTAX Pmip6MagMnProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing information about the mobile node's policy profile. " INDEX { pmip6MagMnIdentifier } ::= { pmip6MagMnProfileTable 1 } Pmip6MagMnProfileEntry ::= SEQUENCE { pmip6MagMnIdentifier MNIdentifier, pmip6MagMnLocalMobilityAnchorAddressType InetAddressType, pmip6MagMnLocalMobilityAnchorAddress InetAddress } pmip6MagMnIdentifier OBJECT-TYPE SYNTAX MNIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The identity of a mobile node in the Proxy Mobile IPv6 domain. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2" ::= { pmip6MagMnProfileEntry 1 } pmip6MagMnLocalMobilityAnchorAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION "The InetAddressType of the pmip6MagMnLocalMobilityAnchorAddress that follows. " ::= { pmip6MagMnProfileEntry 2 } pmip6MagMnLocalMobilityAnchorAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "The global address that is configured on the interface Glenn M. Keeni. Expires: January 6, 2009 [Page 19] Internet Draft pmip6MIB July 2008 of the local mobility anchor and is the transport endpoint of the bi-directional tunnel established between the local mobility anchor and the mobile access gateway. This is the address to where the mobile access gateway sends the Proxy Binding Update messages. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2" ::= { pmip6MagMnProfileEntry 3 } pmip6BindingCacheTable OBJECT-TYPE SYNTAX SEQUENCE OF Pmip6BindingCacheEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table models the Binding Cache on the local mobility anchor. Entries from the table are deleted as the lifetime of the binding expires. Entries in this table are not required to survive a reboot of the managed entity. " REFERENCE "RFC 3775 : Section 4.5, 9.1, 10.1, draft-ietf-netlmm-proxymip6-18.txt : Section 5.1 " ::= { pmip6Bindings 1 } pmip6BindingCacheEntry OBJECT-TYPE SYNTAX Pmip6BindingCacheEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing additional information contained in the binding cache table of the local mobility anchor. " AUGMENTS {mip6BindingCacheEntry} ::= { pmip6BindingCacheTable 1 } Pmip6BindingCacheEntry ::= SEQUENCE { Glenn M. Keeni. Expires: January 6, 2009 [Page 20] Internet Draft pmip6MIB July 2008 pmip6BindingPBUFlag TruthValue, pmip6BindingMnIdentifier MNIdentifier, pmip6BindingMnLlIdentifier MNLlIdentifier, pmip6BindingMagLinkLocalAddressType InetAddressType, pmip6BindingMagLinkLocalAddress InetAddress, pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC, pmip6BindingAccessTechnologyType Pmip6PBUAccessTechnologyType, pmip6BindingTimeRecentlyAccepted DateAndTime } pmip6BindingPBUFlag OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "true(1) if the local mobility anchor accepted the binding update with Proxy Registration Flag from a mobile access gateway. false(0) implies that the binding cache is from a mobile node. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 8.1" ::= { pmip6BindingCacheEntry 1 } pmip6BindingMnIdentifier OBJECT-TYPE SYNTAX MNIdentifier MAX-ACCESS read-only STATUS current DESCRIPTION "The identifier of the registered mobile node, MN-Identifier. This identifier is obtained from the Mobile Node Identifier Option [RFC-4283] present in the received Proxy Binding Update message. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 5.1, 8.1" ::= { pmip6BindingCacheEntry 2 } pmip6BindingMnLlIdentifier OBJECT-TYPE SYNTAX MNLlIdentifier MAX-ACCESS read-only STATUS current DESCRIPTION Glenn M. Keeni. Expires: January 6, 2009 [Page 21] Internet Draft pmip6MIB July 2008 "The link-layer identifier of the mobile node's connected interface on the access link. This identifier can be acquired from the Mobile Node Link-layer Identifier option, present in the received Proxy Binding Update message. If the option was not present in the request, this variable length field MUST be set to two (octets) and MUST be initialized to a value of ALL_ZERO. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 2.2, 5.1, 8.1" ::= { pmip6BindingCacheEntry 3 } pmip6BindingMagLinkLocalAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The InetAddressType of the pmip6BindingMagLinkLocalAddress that follows. " ::= { pmip6BindingCacheEntry 4 } pmip6BindingMagLinkLocalAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The link-local address of the mobile access gateway on the point-to-point link shared with the mobile node. This is generated by the local mobility anchor after accepting the initial Proxy Binding Update message. This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Acknowledgement message. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 6.9.1.2, 8.2" ::= { pmip6BindingCacheEntry 5 } pmip6BindingTunnelIfIdentifier OBJECT-TYPE SYNTAX Ipv6AddressIfIdentifierTC Glenn M. Keeni. Expires: January 6, 2009 [Page 22] Internet Draft pmip6MIB July 2008 MAX-ACCESS read-only STATUS current DESCRIPTION "The tunnel interface identifier (tunnel-if-id) of the bi-directional tunnel between the local mobility anchor and the mobile access gateway where the mobile node is currently anchored. This is internal to the local mobility anchor. The tunnel interface identifier is acquired during the tunnel creation. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 8.1" ::= { pmip6BindingCacheEntry 6 } pmip6BindingAccessTechnologyType OBJECT-TYPE SYNTAX Pmip6PBUAccessTechnologyType MAX-ACCESS read-only STATUS current DESCRIPTION "The access technology type, by which the mobile node is currently attached. This is obtained from the Access Technology Type option, present in the Proxy Binding Update message. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 8.1" ::= { pmip6BindingCacheEntry 7 } pmip6BindingTimeRecentlyAccepted OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time-of-day on the local mobility anchor, when the message was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence number based scheme is in use), the value MUST be set to ALL_ZERO. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.1, 8.1" ::= { pmip6BindingCacheEntry 8 } Glenn M. Keeni. Expires: January 6, 2009 [Page 23] Internet Draft pmip6MIB July 2008 --- --- --- pmip6Stats group --- --- -- -- pmip6Stats:pmip6BindingRegcounters -- pmip6MissingMnIdentifierOption OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Missing mobile node identifier option' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the mobile router. and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 1 } pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Not authorized to send proxy binding updates' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the mobile router, Glenn M. Keeni. Expires: January 6, 2009 [Page 24] Internet Draft pmip6MIB July 2008 and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 2 } pmip6NotLMAForThisMobileNode OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Not local mobility anchor for this mobile node' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 3 } pmip6ProxyRegNotEnabled OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Proxy Registration not enabled' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 4 } Glenn M. Keeni. Expires: January 6, 2009 [Page 25] Internet Draft pmip6MIB July 2008 pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Missing home network prefix option' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "RFC3963 : Section 6.6." ::= { pmip6BindingRegCounters 5 } pmip6MissingHandOffIndicatorOption OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Missing handoff indicator option' (Code XXX). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 6 } pmip6MissingAccessTechTypeOption OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message rejected by the local mobility anchor with status code in the Binding Acknowledgment message indicating 'Missing access technology type option' (Code XXX). Glenn M. Keeni. Expires: January 6, 2009 [Page 26] Internet Draft pmip6MIB July 2008 Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.1" ::= { pmip6BindingRegCounters 7 } pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section X.x.x" ::= { pmip6BindingRegCounters 8 } pmip6TimestampMismatch OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section X.x.x" ::= { pmip6BindingRegCounters 9 } pmip6TimestampLowerThanPrevAccepted OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " Glenn M. Keeni. Expires: January 6, 2009 [Page 27] Internet Draft pmip6MIB July 2008 Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section X.x.x" ::= { pmip6BindingRegCounters 10 } pmip6BcePbuPrefixSetDoNotMatch OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION " Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section X.x.x" ::= { pmip6BindingRegCounters 11 } pmip6InitialBindingRegistrations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message that newly creates the Binding Cache entry. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.2" ::= { pmip6BindingRegCounters 12 } pmip6BindingLifeTimeExtensionNoHandOff OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Glenn M. Keeni. Expires: January 6, 2009 [Page 28] Internet Draft pmip6MIB July 2008 DESCRIPTION "Total number of Proxy Binding Update message for extending the binding lifetime, received from the same mobile access gateway that last updated the binding. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "Rdraft-ietf-netlmm-proxymip6-18.txt : Section 5.3.3" ::= { pmip6BindingRegCounters 13 } pmip6BindingLifeTimeExtensionAfterHandOff OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message for extending the binding lifetime, received from a new mobile access gateway where the mobile node's mobility session is handed off. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.4" ::= { pmip6BindingRegCounters 14 } pmip6BindingDeRegistrations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Update message with the lifetime value of zero. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE Glenn M. Keeni. Expires: January 6, 2009 [Page 29] Internet Draft pmip6MIB July 2008 "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.5" ::= { pmip6BindingRegCounters 15 } pmip6BindingBindingAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Proxy Binding Acknowledgement messages. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.3.5" ::= { pmip6BindingRegCounters 16 } -- -- pmip6Stats: -- -- -- -- pmip6Notifications -- -- pmip6HomeTunnelEstablished NOTIFICATION-TYPE OBJECTS { pmip6MagBLTunnelIfIdentifier, -- pmip6MagProxyCOAType, -- pmip6MagProxyCOA pmip6MagProxyCOAState } STATUS current DESCRIPTION "This notification is sent by the Proxy MobileIPv6 entities every time the tunnel is established between Glenn M. Keeni. Expires: January 6, 2009 [Page 30] Internet Draft pmip6MIB July 2008 the local mobility anchor and mobile access gateway. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.6.1" ::= { pmip6Notifications 1 } pmip6HomeTunnelReleased NOTIFICATION-TYPE OBJECTS { pmip6MagBLTunnelIfIdentifier, -- pmip6MagProxyCOAType, -- pmip6MagProxyCOA pmip6MagProxyCOAState } STATUS current DESCRIPTION "This notification is sent by the Proxy MobileIPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released. " REFERENCE "draft-ietf-netlmm-proxymip6-18.txt : Section 5.6.1" ::= { pmip6Notifications 2} -- Conformance information pmip6Groups OBJECT IDENTIFIER ::= { pmip6Conformance 1 } pmip6Compliances OBJECT IDENTIFIER ::= { pmip6Conformance 2 } -- Units of conformance pmip6SystemGroup OBJECT-GROUP OBJECTS { -- pmip6MagProxyCOAType, -- pmip6MagProxyCOA pmip6MagProxyCOAState } STATUS current DESCRIPTION " A collection of objects for basic PMIPv6 monitoring." ::= { pmip6Groups 1 } Glenn M. Keeni. Expires: January 6, 2009 [Page 31] Internet Draft pmip6MIB July 2008 pmip6ConfigurationGroup OBJECT-GROUP OBJECTS { -- pmip6HomeNetworkPrefixType, -- pmip6HomeNetworkPrefix, -- pmip6HomeNetworkPrefixLength, pmip6HomeNetworkPrefixLifeTime, pmip6MagEnableMagLocalRouting, pmip6MagBLFlag, pmip6MagBLMnIdentifier, pmip6MagBLlMnIdentifier, pmip6MagBLMagLinkLocalAddressType, pmip6MagBLMagLinkLocalAddress, pmip6MagBLMagIfIdentifierToMn, pmip6MagBLTunnelIfIdentifier, pmip6MagBLAccessTechnologyType, pmip6MagBLTimeRecentlyAccepted, pmip6BindingPBUFlag, pmip6BindingMnIdentifier, pmip6BindingMnLlIdentifier, pmip6BindingMagLinkLocalAddressType, pmip6BindingMagLinkLocalAddress, pmip6BindingTunnelIfIdentifier, pmip6BindingAccessTechnologyType, pmip6BindingTimeRecentlyAccepted, -- pmip6MagMnIdentifier, pmip6MagMnLocalMobilityAnchorAddressType, pmip6MagMnLocalMobilityAnchorAddress } STATUS current DESCRIPTION " A collection of objects for basic PMIPv6 configuration monitoring." ::= { pmip6Groups 2 } pmip6StatsGroup OBJECT-GROUP OBJECTS { pmip6MissingMnIdentifierOption, pmip6MagNotAuthorizedForProxyReg, pmip6NotLMAForThisMobileNode, pmip6ProxyRegNotEnabled, pmip6MissingHomeNetworkPrefixOption, pmip6MissingHandOffIndicatorOption, pmip6MissingAccessTechTypeOption, pmip6NotAuthorizedForHomeNetworkPrefix, Glenn M. Keeni. Expires: January 6, 2009 [Page 32] Internet Draft pmip6MIB July 2008 pmip6TimestampMismatch, pmip6TimestampLowerThanPrevAccepted, pmip6BcePbuPrefixSetDoNotMatch, pmip6InitialBindingRegistrations, pmip6BindingLifeTimeExtensionNoHandOff, pmip6BindingLifeTimeExtensionAfterHandOff, pmip6BindingDeRegistrations, pmip6BindingBindingAcks } STATUS current DESCRIPTION " A collection of objects for basic PMIPv6 monitoring. " ::= { pmip6Groups 3 } pmip6NotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { pmip6HomeTunnelEstablished, pmip6HomeTunnelReleased } STATUS current DESCRIPTION "A collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router. " ::= { pmip6Groups 4 } -- Compliance statements pmip6CoreCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which implement the MOBILEIPV6-MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6BindingHomeAddressType Glenn M. Keeni. Expires: January 6, 2009 [Page 33] Internet Draft pmip6MIB July 2008 -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the pmip6BindingHomeAddress -- object. -- " MODULE -- this module MANDATORY-GROUPS { pmip6SystemGroup, pmip6ConfigurationGroup, pmip6StatsGroup, pmip6NotificationGroup } ::= { pmip6Compliances 1 } END Glenn M. Keeni. Expires: January 6, 2009 [Page 34] Internet Draft pmip6MIB July 2008 6. Security Considerations There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and the corresponding sensitivity/vulnerability: Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 7. IANA Considerations IANA should assign a base arc in the 'mib-2' (standards track) OID tree for the 'pmip6MIB' MODULE-IDENTITY defined in the PMIPv6 MIB. Glenn M. Keeni. Expires: January 6, 2009 [Page 35] Internet Draft pmip6MIB July 2008 8. References 8.1 Normative References [RFC2119] Bradner, S., Key words for use in RFCs to Indicate Requirements Levels, BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, Structure of Management Information Version 2 (SMIv2), STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, Textual Conventions for SMIv2, STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, Conformance Statements for SMIv2, STD 58, RFC 2580, April 1999. [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in IPv6 RFC 3775, June 2004. [RFC2011bis] Routhier, S., Management Information Base for the Internet Protocol (IP), work in progress (currently ). [RFC3291bis] Daniele, M., Haberman, B., Routhier, S. and Schoenwaelder, J., Textual Conventions for Internet Network Addresses, work in progress (currently ). 8.2 Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, Introduction and Applicability Statements for Internet-Standard Management Framework, RFC 3410, December 2002. [RFC4087] Thaler, D., IP Tunnel MIB, RFC 4087, June 2005. 9. Acknowledgments The following groups and individuals have contributed to this draft with discussions and comments: Glenn M. Keeni. Expires: January 6, 2009 [Page 36] Internet Draft pmip6MIB July 2008 WIDE-netman group Glenn M. Keeni. Expires: January 6, 2009 [Page 37] Internet Draft pmip6MIB July 2008 10. Authors' Addresses Glenn Mansfield Keeni Cyber Solutions Inc. 6-6-3 Minami Yoshinari Aoba-ku, Sendai 989-3204 Japan Phone: +81-22-303-4012 EMail: glenn@cysols.com Kazuhide Koide Research Institute of Electrical Communication, Tohoku University. 2-1-1 Katahira, Aoba-ku, Sendai, Miyagi, 980-8577. Japan Phone: +81-22-217-5454 E-mail: koide@shiratori.riec.tohoku.ac.jp Sri Gundavelli Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA Phone: +1-408-527-6109 Email: sgundave@cisco.com Ryuji Wakikawa Keio University Department of Environmental Information, Keio University. 5322 Endo Fujisawa, Kanagawa 252-8520 Japan Email: ryuji@sfc.wide.ad.jp Glenn M. Keeni. Expires: January 6, 2009 [Page 38] Internet Draft pmip6MIB July 2008 11. Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Glenn M. Keeni. Expires: January 6, 2009 [Page 39] Internet Draft pmip6MIB July 2008 Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Glenn M. Keeni. Expires: January 6, 2009 [Page 40] Internet Draft pmip6MIB July 2008 Glenn M. Keeni. Expires: January 6, 2009 [Page 41]