draft-ietf-netlmm-pmipv6-mib-03.txt   rfc6475.txt 
NETLMM Working Group Glenn M. Keeni Internet Engineering Task Force (IETF) G. Keeni
INTERNET-DRAFT Cyber Solutions Inc. Request for Comments: 6475 Cyber Solutions, Inc.
Intended Status: Proposed Standard K. Koide Category: Standards Track K. Koide
Expires: February 19, 2011 KDDI Corporation ISSN: 2070-1721 KDDI Corporation
S. Gundavelli S. Gundavelli
Cisco Cisco
R. Wakikawa R. Wakikawa
Toyota ITC Toyota ITC
August 20, 2010 May 2012
Proxy Mobile IPv6 Management Information Base Proxy Mobile IPv6 Management Information Base
<draft-ietf-netlmm-pmipv6-mib-03.txt>
Status of this Memo Abstract
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and 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 This memo defines a portion of the Proxy Mobile IPv6 Management
and may be updated, replaced, or obsoleted by other documents at any Information Base (MIB) for use with network management protocols in
time. It is inappropriate to use Internet-Drafts as reference the Internet community. In particular, the Proxy Mobile IPv6 MIB can
material or to cite them other than as "work in progress." be used to monitor and control the mobile access gateway (MAG) and
the local mobility anchor (LMA) functions of a Proxy Mobile IPv6
(PMIPv6) entity.
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/shadow.html.
This document is a product of the NETLMM Working Group. Comments This document is a product of the Internet Engineering Task Force
should be addressed to the authors or the mailing list at (IETF). It represents the consensus of the IETF community. It has
netlmm@ietf.org received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on February 19, 2011. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6475.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described include Simplified BSD License text as described in Section 4.e of
in Section 4.e of the Trust Legal Provisions and are provided the Trust Legal Provisions and are provided without warranty as
without warranty as described in the Simplified BSD License. described in the Simplified BSD License.
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 (MAG)
and the local mobility anchor (LMA) functions of a Proxy Mobile
IPv6 (PMIPv6) entity.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework ................... 3 1. The Internet-Standard Management Framework ......................3
2. Overview ..................................................... 3 2. Overview ........................................................3
2.1. The Proxy Mobile IPv6 Protocol Entities ................. 3 2.1. The Proxy Mobile IPv6 Protocol Entities ....................3
2.2. Terminology ............................................. 4 2.2. Terminology ................................................4
3. Proxy Mobile IPv6 Monitoring and Control Requirements ........ 4 3. Proxy Mobile IPv6 Monitoring and Control Requirements ...........4
4. MIB Design ................................................... 4 4. MIB Design ......................................................4
5. The Proxy Mobile-IPv6 MIB .................................... 7 4.1. Textual Conventions ........................................6
6. Security Considerations ...................................... 58 5. MIB Definitions .................................................6
7. IANA Considerations .......................................... 59 5.1. Proxy Mobile IPv6 Textual Conventions MIB ..................6
8. References ................................................... 60 5.2. The Proxy Mobile IPv6 MIB .................................10
8.1. Normative References .................................... 60 6. Security Considerations ........................................58
8.2. Informative References .................................. 61 7. IANA Considerations ............................................60
9. Acknowledgements ............................................. 62 8. References .....................................................60
10. Author's Addresses ........................................... 62 8.1. Normative References ......................................60
Appendix: History of Changes 8.2. Informative References ....................................61
9. Acknowledgements ...............................................62
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 3, line 24 skipping to change at page 3, line 24
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Overview 2. Overview
2.1. The Proxy Mobile IPv6 Protocol Entities 2.1. The Proxy Mobile IPv6 Protocol Entities
Proxy Mobile IPv6 (PMIPv6) [RFC5213] is an extension to the Mobile Proxy Mobile IPv6 (PMIPv6) [RFC5213] is an extension to the Mobile
IPv6 (MIPv6) protocol which facilitates network-based localized IPv6 (MIPv6) protocol that facilitates network-based localized
mobility management (NETLMM) for IPv6 nodes in a PMIPv6 domain. mobility management (NETLMM) for IPv6 nodes in a PMIPv6 domain.
There are three types of entities envisaged by the PMIPv6 protocol. There are three types of entities envisaged by the PMIPv6 protocol.
mobile node (MN): In the PMIPv6 context the term mobile node mobile node (MN): In the PMIPv6 context, this term is used to refer
is used to refer to an IP host or router whose mobility is to an IP host or router whose mobility is managed by the network.
managed by the network.
local mobility anchor (LMA): Local Mobility Anchor is the local mobility anchor (LMA): Local Mobility Anchor is the home agent
home agent for the mobile node in a Proxy Mobile IPv6 domain. for the mobile node in a Proxy Mobile IPv6 domain. It is the
It is the topological anchor point for the mobile node's home topological anchor point for the mobile node's home network
network prefix(es) and is the entity that manages the mobile prefix(es) and is the entity that manages the mobile node's binding
node's binding state. The local mobility anchor has the state. The local mobility anchor has the functional capabilities of
functional capabilities of a home agent as defined in Mobile a home agent as defined in the Mobile IPv6 base specification
IPv6 base specification [RFC3775] with the additional [RFC6275] with the additional capabilities required for supporting
capabilities required for supporting Proxy Mobile IPv6 the Proxy Mobile IPv6 protocol as defined in the PMIPv6 specification
protocol as defined in the PMIPv6 specification [RFC5213]. [RFC5213].
mobile access gateway (MAG): Mobile Access Gateway is the mobile access gateway (MAG): Mobile Access Gateway is the entity on
entity on an access router that manages the mobility-related an access router that manages the mobility-related signaling for a
signaling for a mobile node that is attached to its access mobile node that is attached to its access link. It is responsible
link. It is responsible for tracking the mobile node's for tracking the mobile node's movements to and from the access link
movements to and from the access link and for signaling the and for signaling the mobile node's local mobility anchor.
mobile node's local mobility anchor.
This document defines a set of managed objects (MOs) that can be used This document defines a set of managed objects (MOs) that can be used
to monitor and control PMIPv6 entities. to monitor and control PMIPv6 entities.
2.2. Terminology 2.2. Terminology
The terminology used in this document is consistent with the The terminology used in this document is consistent with the
definitions used in the Mobile IPv6 protocol specification [RFC3775] definitions used in the Mobile IPv6 protocol specification [RFC6275]
and in NETLMM Goals document [RFC4831]. and in the NETLMM goals document [RFC4831].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, RFC 2119 [RFC2119]. 14, RFC 2119 [RFC2119].
3. Proxy Mobile IPv6 Monitoring and Control Requirements 3. Proxy Mobile IPv6 Monitoring and Control Requirements
For managing a PMIPv6 entity it is necessary to monitor For managing a PMIPv6 entity, it is necessary to monitor the
the following: following:
o capabilities of PMIPv6 entities
o traffic due to PMIPv6 signaling o capabilities of PMIPv6 entities
o binding related details (at LMA and MAG) o signaling traffic due to PMIPv6 signaling
o binding related statistics (at LMA and MAG) o binding-related details (at LMA and MAG)
o binding-related statistics (at LMA and MAG)
4. MIB Design 4. MIB Design
The basic principle has been to keep the MIB as simple as possible 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 and, at the same time, to make it effective enough so that the
essential needs of monitoring and control are met. essential needs of monitoring and control are met.
It is assumed that the Proxy Mobile IPv6 Management Information Base The Proxy Mobile IPv6 Management Information Base (PMIPV6-MIB)
(PMIPV6-MIB) will always be implemented in conjunction with the extends the Mobile IPv6 Management Information Base (MIPV6-MIB)
MOBILEIPV6-MIB [RFC4295] and the ifTable from the IF-MIB [RFC2863]. [RFC4295]. It is assumed that PMIPV6-MIB will always be implemented
The PMIPV6-MIB uses the textual conventions defined in the INET- in conjunction with the MOBILEIPV6-MIB [RFC4295]. The PMIPV6-MIB
ADDRESS-MIB [RFC4001]. uses the textual conventions defined in the INET-ADDRESS-MIB
[RFC4001] and IP-MIB [RFC4293].
The PMIPV6-MIB is composed of the following groups of definitions: The PMIPV6-MIB is composed of the following groups of definitions:
- pmip6Core: a generic group containing objects that are - pmip6Core: a generic group containing objects that are common to
common to all the Proxy Mobile IPv6 entities. Objects all the Proxy Mobile IPv6 entities. Objects belonging to this
belonging to this group will be implemented on the group will be implemented on the corresponding Proxy Mobile IPv6
corresponding Proxy Mobile IPv6 entity. pmip6BindingCacheTable entity. pmip6BindingCacheTable belongs to this group.
belongs to this group.
- pmip6Mag: this group models the mobile access gateway
service. Objects belonging to this group will be
implemented on the corresponding MAG. The tables belonging
to this group have the "pmip6Mag" prefix.
- pmip6Lma: this group models the local mobility anchor
service. Objects belonging to this group will be
implemented on the corresponding LMA. The tables belonging
to this group have the "pmip6Lma" prefix.
- pmip6Notifications: defines the set of notifications that
will be used to asynchronously monitor the Proxy Mobile
IPv6 entities.
The tables contained in the above groups are as follows: - pmip6Mag: this group models the mobile access gateway service.
- pmip6BindingCacheTable : models the Binding Cache Objects belonging to this group have the "pmip6Mag" prefix and
on the local mobility will be implemented on the corresponding MAG.
anchor.
- pmip6MagProxyCOATable : models the Proxy Care-of
Addresses configured on the
egress interfaces of the
mobile access gateway.
- pmip6MagHomeNetworkPrefixTable : contains the Home Network
Prefixes assigned to
interfaces of all mobile
nodes attached to the MAG.
Each interface is
distinguished by the attached
mobile node's identifier (MN-
Identifier) and the link layer
identifier (MN-LL-Identifier).
- pmip6MagBLTable : models the Binding Update List
(BL) that includes Proxy MIPv6
related information and is
maintained by the mobile
access gateway.
- pmip6MagMnProfileTable : contains 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.
- pmip6LmaLMAATable : contains the LMA Addresses
that are configured on the
local mobility anchor. Each
LMA Address acts as a
transport endpoint of the
tunnel between the local
mobility anchor and the mobile
access gateway.
- pmip6LmaHomeNetworkPrefixTable : contains the list of Home
Network Prefixes assigned to
the connected interfaces of
the mobiles nodes anchored on
an LMA.
5. The Proxy Mobile-IPv6 MIB - pmip6Lma: this group models the local mobility anchor service.
Objects belonging to this group have the "pmip6Lma" prefix and
will be implemented on the corresponding LMA.
PMIPV6-MIB DEFINITIONS ::= BEGIN - pmip6Notifications: defines the set of notifications that will
IMPORTS be used to asynchronously monitor the Proxy Mobile IPv6
MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32, entities.
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
PhysAddress
FROM RFC1213-MIB
TEXTUAL-CONVENTION, TimeStamp,
TruthValue, DateAndTime
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddressType, InetAddress, InetAddressPrefixLength
FROM INET-ADDRESS-MIB
Ipv6AddressIfIdentifierTC
FROM IP-MIB
mip6MnBLEntry, mip6BindingCacheEntry
FROM MOBILEIPV6-MIB
;
pmip6MIB MODULE-IDENTITY The tables contained in the above groups are as follows:
LAST-UPDATED "201008160000Z" -- 16th August, 2010
ORGANIZATION "IETF NETLMM 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 - pmip6BindingCacheTable: models the Binding Cache on the local
Postal: KDDI Corporation mobility anchor.
GARDEN AIR TOWER 3-10-10, Iidabashi
Chiyoda-ku, Tokyo, 102-8460 Japan
Tel: +81-3-6678-3378
E-mail: ka-koide@kddi.com
Sri Gundavelli - pmip6MagProxyCOATable: models the Proxy Care-of Addresses
configured on the egress interfaces of the mobile access
gateway.
Postal: Cisco - pmip6MagMnIdentifierTable: provides a mapping from the MAG-
170 W.Tasman Drive, internal pmip6MagMnIndex to the mobile node identifier.
San Jose, CA 95134
USA
Tel: +1-408-527-6109
E-mail: sgundave@cisco.com
Ryuji Wakikawa - pmip6MagMnLLIdentifierTable: provides a mapping from the MAG-
Postal: TOYOTA InfoTechnology Center, U.S.A., Inc. internal pmip6MagMnLLIndex to the corresponding interface of the
465 Bernardo Avenue mobile node link-layer identifier.
Mountain View, CA
94043
USA
E-mail: ryuji@us.toyota-itc.com
Support Group E-mail: netlmm@ietf.org" - pmip6MagHomeNetworkPrefixTable: contains the home network
prefixes assigned to interfaces of all mobile nodes attached to
the MAG. Each interface is distinguished by the attached mobile
node identifier (MN-Identifier) and the link-layer identifier
(MN-LL-Identifier).
DESCRIPTION - pmip6MagBLTable: models the Binding Update List (BL) that
"The MIB module for monitoring and controlling PMIPv6 includes PMIPv6-related information and is maintained by the
entities. mobile access gateway.
"
-- Authors' note:
-- It is not clear if the Copyright notice should be a part
-- of above description. It was a requirement sometime ago
-- but the submission tool at ietf.org complained so it is
-- removed for now.
-- RFC Ed.: replace XXXX with actual RFC number and remove this - pmip6MagMnProfileTable: contains the mobile node's policy
-- note profile that includes the essential operational parameters that
are required by the network entities for managing the mobile
node's mobility service.
REVISION "201008160000Z" -- 16th August 2010 - pmip6LmaLMAATable: contains the LMA Addresses (LMAAs) that are
DESCRIPTION "Initial version, published as RFC XXXX." configured on the local mobility anchor. Each LMA Address acts
as a transport endpoint of the tunnel between the local mobility
anchor and the mobile access gateway.
-- RFC Ed.: replace XXXX with actual RFC number and remove this - pmip6LmaMnIdentifierTable: provides a mapping from the LMA-
-- note internal pmip6BindingMnIndex to the mobile node identifier.
::= { mib-2 YYY } -- will be assigned by IANA - pmip6LmaMnLLIdentifierTable: provides a mapping from the LMA-
internal pmip6BindingMnLLIndex to the corresponding interface of
the mobile node link-layer identifier.
-- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' - pmip6LmaHomeNetworkPrefixTable: contains the list of home
-- subtree and record the assignment in the SMI Numbers network prefixes assigned to the connected interfaces of the
-- registry. mobile nodes anchored on an LMA.
--
-- 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.
-- ------------------------------------------------------------- 4.1. Textual Conventions
-- Textual Conventions
-- -------------------------------------------------------------
Pmip6MNIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
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 for predictably identifying
a mobile node. Various forms of identifiers can be used to
identify a mobile node (MN). Two examples are a Network
Access Identifier (NAI) [RFC4282] and an opaque identifier
applicable to a particular application.
"
REFERENCE
"RFC 4283: Section 3"
SYNTAX OCTET STRING (SIZE (0..255))
Pmip6MNLlIdentifier ::= TEXTUAL-CONVENTION A Proxy Mobile IPv6 Textual Conventions MIB module containing
DISPLAY-HINT "255a" Textual Conventions to represent commonly used Proxy Mobile IPv6
STATUS current management information is defined. The intent is that these
DESCRIPTION TEXTUAL CONVENTIONS (TCs) will be imported and used in
"An identifier that identifies the attached interface of a PMIPv6-related MIB modules that would otherwise define their own
mobile node. For those interfaces that have a link-layer representation(s). This MIB module includes references to RFC
identifier, this identifier can be based on that. The 4283 [RFC4283] and RFC 5213 [RFC5213].
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
"RFC 5213: Section 8.6"
SYNTAX OCTET STRING (SIZE (0..255))
Pmip6MNIndex ::= TEXTUAL-CONVENTION 5. MIB Definitions
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique integer value, greater than zero, assigned to each
mobile node that is currently attached to the PMIPv6-Domain
by the management system.
It is recommended that the values are assigned contiguously 5.1. Proxy Mobile IPv6 Textual Conventions MIB
starting from 1. The value for each mobile node must remain
constant at least from one re-initialization of the entity's
network management system to the next re-initialization.
"
SYNTAX Integer32 (1..2147483647)
Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION PMIPV6-TC-MIB DEFINITIONS ::= BEGIN
STATUS current IMPORTS
DESCRIPTION MODULE-IDENTITY, mib-2, Unsigned32
"This specifies the access technology which connects the FROM SNMPv2-SMI -- [RFC2578]
mobile node to the access link on the mobile access gateway. TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579]
pmip6TCMIB MODULE-IDENTITY
LAST-UPDATED "201205070000Z" -- 7th May, 2012
ORGANIZATION "IETF NETLMM 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
EMail: glenn@cysols.com
Sri Gundavelli
Postal: Cisco Systems
170 W.Tasman Drive,
San Jose, CA 95134
USA
Tel: +1-408-527-6109
EMail: sgundave@cisco.com
Kazuhide Koide
Postal: KDDI Corporation
GARDEN AIR TOWER 3-10-10, Iidabashi
Chiyoda-ku, Tokyo 102-8460, Japan.
Tel: +81-3-6678-3378
EMail: ka-koide@kddi.com
Ryuji Wakikawa
Postal: TOYOTA InfoTechnology Center, U.S.A., Inc.
465 Bernardo Avenue
Mountain View, CA
94043
USA
EMail: ryuji@us.toyota-itc.com
Support Group EMail: netlmm@ietf.org
" "
REFERENCE
"RFC 5213: Section 8.5,
http://www.iana.org/assignments/mobility-parameters/
mobility-parameters.txt"
SYNTAX INTEGER
{
reserved (0),
logicalNetworkInterface(1),
pointToPointInterface (2),
ethernet (3),
wirelessLan (4),
wimax (5),
threeGPPGERAN (6),
threeGPPUTRAN (7),
threeGPPETRAN (8),
threeGPP2eHRPD (9),
threeGPP2HRPD (10),
threeGPP21xRTT (11),
threeGPP2UMB (12)
}
-- The PMIPv6 MIB has the following 5 primary groups DESCRIPTION
"This MIB module provides textual conventions for
Proxy Mobile IPv6 Management information.
pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 } Copyright (c) 2012 IETF Trust and the persons
pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 } identified as authors of the code. All rights
pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 } reserved.
pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 }
pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 }
pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 }
-- The sub groups Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant
to, and subject to the license terms contained in,
the Simplified BSD License set forth in Section 4.c
of the IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info).
"
pmip6System OBJECT IDENTIFIER ::= { pmip6Core 1 } REVISION "201205070000Z" -- 7th May, 2012
pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 } DESCRIPTION
pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 } "The initial version, published as RFC 6475."
pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 } ::= { mib-2 205 }
pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 } -- -------------------------------------------------------------
pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 } -- Textual Conventions
pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 } -- -------------------------------------------------------------
Pmip6TimeStamp64 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "6d:2d"
STATUS current
DESCRIPTION
"A 64-bit unsigned integer field containing a timestamp.
The value indicates the elapsed time since January 1,
1970, 00:00 UTC, by using a fixed-point format. In this
format, the integer number of seconds is contained in
the first 48 bits of the field, and the remaining 16
bits indicate the number of 1/65536 fractions of a
second.
"
REFERENCE
"RFC 5213: Section 8.8"
SYNTAX OCTET STRING (SIZE (8))
pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 } Pmip6MnIdentifier ::= TEXTUAL-CONVENTION
pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 } DISPLAY-HINT "255a"
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 for predictably identifying
a mobile node. Various forms of identifiers can be used
to identify a mobile node (MN). Two examples are a
Network Access Identifier (NAI) and an opaque
identifier applicable to a particular application.
"
REFERENCE
"RFC 4283: Section 3"
SYNTAX OCTET STRING (SIZE (0..255))
Pmip6MnLLIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"An identifier that identifies the attached interface of
a mobile node.
"
REFERENCE
"RFC 5213: Section 8.6"
SYNTAX OCTET STRING (SIZE (0..255))
-- The pmip6Stats group has the following sub groups Pmip6MnIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique integer value, greater than zero, assigned to
each mobile node that is currently attached to the
Proxy Mobile IPv6 domain by the management system.
It is recommended that the values are assigned in a
monotonically increasing order starting from 1. It may
wrap after reaching its maximum value. The value for
each mobile node must remain constant at least from one
re-initialization of the entity's network management
system to the next re-initialization.
"
SYNTAX Unsigned32 (1..4294967295)
Pmip6MnLLIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique integer value, greater than zero, assigned to
each interface of a mobile node that is currently
attached to the Proxy Mobile IPv6 domain by the
management system.
It is recommended that the values are assigned in a
monotonically increasing order starting from 1. It may
wrap after reaching its maximum value. The value for
each interface of a mobile node must remain constant at
least from one re-initialization of the entity's network
management system to the next re-initialization.
"
SYNTAX Unsigned32 (1..4294967295)
Pmip6MnInterfaceATT ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The object specifies the access technology that
connects the mobile node to the access link on the
mobile access gateway.
The enumerated values and the corresponding access
technology are as follows:
reserved (0): Reserved (Not used)
logicalNetworkInterface (1): Logical network interface
pointToPointInterface (2): Point-to-point interface
ethernet (3): Ethernet interface
wirelessLan (4): Wireless LAN interface
wimax (5): Wimax interface
threeGPPGERAN (6): 3GPP GERAN
threeGPPUTRAN (7): 3GPP UTRAN
threeGPPEUTRAN (8): 3GPP E-UTRAN
threeGPP2eHRPD (9): 3GPP2 eHRPD
threeGPP2HRPD (10): 3GPP2 HRPD
threeGPP21xRTT (11): 3GPP2 1xRTT
threeGPP2UMB (12): 3GPP2 UMB
"
REFERENCE
"RFC 5213: Section 8.5,
Mobile IPv6 parameters registry on
http://www.iana.org/mobility-parameters"
pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 } SYNTAX INTEGER
{
reserved (0),
logicalNetworkInterface(1),
pointToPointInterface (2),
ethernet (3),
wirelessLan (4),
wimax (5),
threeGPPGERAN (6),
threeGPPUTRAN (7),
threeGPPEUTRAN (8),
threeGPP2eHRPD (9),
threeGPP2HRPD (10),
threeGPP21xRTT (11),
threeGPP2UMB (12)
}
END
-- 5.2. The Proxy Mobile IPv6 MIB
--
-- pmip6System group PMIPV6-MIB DEFINITIONS ::= BEGIN
-- IMPORTS
-- MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32,
pmip6Capabilities OBJECT-TYPE Unsigned32, OBJECT-TYPE, NOTIFICATION-TYPE
SYNTAX BITS { FROM SNMPv2-SMI -- RFC 2578
mobilityAccessGateway (0), PhysAddress, TimeStamp,
localMobilityAnchor (1) TruthValue
} FROM SNMPv2-TC -- RFC 2579
MAX-ACCESS read-only MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
STATUS current FROM SNMPv2-CONF -- RFC 2580
DESCRIPTION InetAddressType, InetAddress, InetAddressPrefixLength
"This object indicates the PMIPv6 functions that FROM INET-ADDRESS-MIB -- RFC 4001
are supported by this managed entity. Multiple Ipv6AddressIfIdentifierTC
Proxy Mobile IPv6 functions may be supported by FROM IP-MIB -- RFC 4293
a single entity. mip6MnBLEntry, mip6BindingCacheEntry
" FROM MOBILEIPV6-MIB -- RFC 4295
REFERENCE Pmip6TimeStamp64, Pmip6MnIdentifier,
"RFC 3775 : Section 3.2, 4.1" Pmip6MnLLIdentifier, Pmip6MnIndex, Pmip6MnLLIndex,
::= { pmip6System 1 } Pmip6MnInterfaceATT
FROM PMIPV6-TC-MIB -- RFC 6475
;
pmip6MIB MODULE-IDENTITY
LAST-UPDATED "201205070000Z" -- 7th May, 2012
ORGANIZATION "IETF NETLMM Working Group"
CONTACT-INFO
" Glenn Mansfield Keeni
Postal: Cyber Solutions, Inc.
6-6-3, Minami Yoshinari
Aoba-ku, Sendai 989-3204, Japan.
Tel: +81-22-303-4012
Fax: +81-22-303-4015
EMail: glenn@cysols.com
Kazuhide Koide
Postal: KDDI Corporation
GARDEN AIR TOWER 3-10-10, Iidabashi
Chiyoda-ku, Tokyo 102-8460, Japan.
Tel: +81-3-6678-3378
EMail: ka-koide@kddi.com
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: TOYOTA InfoTechnology Center, U.S.A., Inc.
465 Bernardo Avenue
Mountain View, CA
94043
USA
EMail: ryuji@us.toyota-itc.com
Support Group EMail: netlmm@ietf.org"
pmip6Status OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the Proxy Mobile "The MIB module for monitoring and controlling PMIPv6
IPv6 function is enabled for the managed entity. entities.
The value of this object SHOULD remain unchanged Copyright (c) 2012 IETF Trust and the persons
across reboots of the managed entity. identified as authors of the code. All rights
" reserved.
::= { pmip6System 2 }
Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant
to, and subject to the license terms contained in,
the Simplified BSD License set forth in Section 4.c
of the IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info).
"
REVISION "201205070000Z" -- 7th May 2012
DESCRIPTION "Initial version, published as RFC 6475."
::= { mib-2 206 }
-- The PMIPv6 MIB has the following 5 primary groups
pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 }
pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 }
pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 }
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 }
pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 }
pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 }
pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 }
pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 }
pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 }
pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 }
pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 }
-- The pmip6Stats group has the following sub groups
pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 }
--
--
-- pmip6System group
--
--
pmip6Capabilities OBJECT-TYPE
SYNTAX BITS {
mobilityAccessGateway (0),
localMobilityAnchor (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the PMIPv6 functions that
are supported by this managed entity. Multiple
Proxy Mobile IPv6 functions may be supported by
a single entity.
mobilityAccessGateway(0) indicates the availability
of the mobility access gateway function.
localMobilityAnchor(1) indicates the availability
of the local mobility anchor function.
"
REFERENCE
"RFC 6275: Sections 3.2, 4.1"
::= { pmip6System 1 }
pmip6MobileNodeGeneratedTimestampInUse OBJECT-TYPE pmip6MobileNodeGeneratedTimestampInUse OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This flag indicates whether or not the mobile node "This flag indicates whether or not the
generated timestamp mechanism is in use in that MN-generated timestamp mechanism is in use in that
Proxy Mobile IPv6 domain. Proxy Mobile IPv6 domain.
true(1) if the local mobility anchors and mobile true(1) indicates that the local mobility anchors and
access gateways in that Proxy Mobile IPv6 domain mobile access gateways in that Proxy Mobile IPv6
apply the mobile node generated timestamp domain apply the MN-generated timestamp considerations.
considerations. false(0) indicates that the MN-generated timestamp
false(0) indicates that the mobile node generated mechanism is not in use in that Proxy Mobile IPv6
timestamp mechanism is not in use in that Proxy domain.
Mobile IPv6 domain. The default value for this flag is 'false'.
The default value for this flag is set to value of 0.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.5, 9.3" "RFC 5213: Sections 5.5, 9.3"
::= { pmip6Conf 1 } DEFVAL { false }
::= { pmip6Conf 1 }
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType OBJECT-TYPE pmip6FixedMagLinkLocalAddressOnAllAccessLinksType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the "The InetAddressType of the
pmip6FixedMagLinkLocalAddressOnAllAccessLinks pmip6FixedMagLinkLocalAddressOnAllAccessLinks
that follows. that follows.
" "
::= { pmip6Conf 2 } ::= { pmip6Conf 2 }
pmip6FixedMagLinkLocalAddressOnAllAccessLinks OBJECT-TYPE pmip6FixedMagLinkLocalAddressOnAllAccessLinks OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the link-local address value "This variable indicates the link-local address value
that all the mobile access gateways should use on that all the mobile access gateways should use on
any of the access links shared with any of the any of the access links shared with any of the
mobile nodes in that Proxy Mobile IPv6 domain. If mobile nodes in that Proxy Mobile IPv6 domain. If
this variable is initialized to ALL_ZERO value, it this variable is initialized with all zeroes, it
implies that the use of fixed link-local address mode implies that the use of fixed link-local address mode
is not enabled for that Proxy Mobile IPv6 domain." is not enabled for that Proxy Mobile IPv6 domain."
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 6.8, 6.9.1.1, 6.9.3, 9.3" "RFC 5213: Sections 2.2, 6.8, 6.9.1.1, 6.9.3, 9.3"
::= { pmip6Conf 3 } ::= { pmip6Conf 3 }
pmip6FixedMagLinkLayerAddressOnAllAccessLinks OBJECT-TYPE pmip6FixedMagLinkLayerAddressOnAllAccessLinks OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the link-layer address value "This variable indicates the link-layer address value
that all the mobile access gateways should use on that all the mobile access gateways should use on
any of the access links shared with any of the mobile any of the access links shared with any of the mobile
nodes in that Proxy Mobile IPv6 domain. For access nodes in that Proxy Mobile IPv6 domain. For access
technologies where there is no link-layer address, technologies where there is no link-layer address,
this variable MUST be initialized to ALL_ZERO value. this variable MUST be initialized with all zeroes.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.9.3, 9.3" "RFC 5213: Sections 6.9.3, 9.3"
::= { pmip6Conf 4 } ::= { pmip6Conf 4 }
pmip6MagStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates whether the PMIPv6 mobile
access gateway function is enabled for the managed
entity.
pmip6MagProxyCOATable OBJECT-TYPE Changing the status from enabled(1) to disabled(2)
will terminate the PMIPv6 mobile access gateway
function. On the other hand, changing the status
from disabled(2) to enabled(1) will start the PMIPv6
mobile access gateway function.
The value of this object MUST remain unchanged
across reboots of the managed entity.
"
DEFVAL { disabled }
::= { pmip6MagSystem 1 }
pmip6MagProxyCOATable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table models the Proxy Care-of Addresses configured "This table models the Proxy Care-of Addresses
on the egress interfaces of the mobile access gateway configured on the egress interfaces of the mobile access
and is the transport endpoint of the tunnel between the gateway. This address is the transport endpoint of the
local mobility anchor and the mobile access gateway. tunnel between the local mobility anchor and the mobile
access gateway.
Entries in this table are not required to survive Entries in this table are not required to survive
a reboot of the managed entity. a reboot of the managed entity.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 6.10" "RFC 5213: Sections 2.2, 6.10"
::= { pmip6MagSystem 1 } ::= { pmip6MagSystem 2 }
pmip6MagProxyCOAEntry OBJECT-TYPE
pmip6MagProxyCOAEntry OBJECT-TYPE
SYNTAX Pmip6MagProxyCOAEntry SYNTAX Pmip6MagProxyCOAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry represents a conceptual row in the "This entry represents a conceptual row in the
Proxy-CoA table. It represents each Proxy-CoA Proxy-CoA table. It represents a Proxy Care-of
on the mobile access gateway. Address on the mobile access gateway.
Implementers need to be aware that if the total Implementers need to be aware that if the total
number of octets in mip6BindingHomeAddress number of octets in pmip6MagProxyCOA
exceeds 113 then OIDs of column exceeds 113, then OIDs of column
instances in this row will have more than 128 instances in this row will have more than 128
sub-identifiers and cannot be accessed using sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3. SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA } INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA }
::= { pmip6MagProxyCOATable 1 } ::= { pmip6MagProxyCOATable 1 }
Pmip6MagProxyCOAEntry ::= Pmip6MagProxyCOAEntry ::=
SEQUENCE { SEQUENCE {
pmip6MagProxyCOAType InetAddressType, pmip6MagProxyCOAType InetAddressType,
pmip6MagProxyCOA InetAddress, pmip6MagProxyCOA InetAddress,
pmip6MagProxyCOAState INTEGER pmip6MagProxyCOAState INTEGER
} }
pmip6MagProxyCOAType OBJECT-TYPE pmip6MagProxyCOAType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 16, line 35 skipping to change at page 16, line 13
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Proxy-CoA configured on the egress interface of the "The Proxy-CoA configured on the egress interface of the
mobile access gateway. mobile access gateway.
The type of the address represented by this object The type of the address represented by this object
is specified by the corresponding is specified by the corresponding
pmip6MagProxyCOAType object. pmip6MagProxyCOAType object.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 6.10" "RFC 5213: Sections 2.2, 6.10"
::= { pmip6MagProxyCOAEntry 2 } ::= { pmip6MagProxyCOAEntry 2 }
pmip6MagProxyCOAState OBJECT-TYPE pmip6MagProxyCOAState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
activated(2), activated(2),
tunneled(3) tunneled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 17, line 4 skipping to change at page 16, line 28
unknown(1), unknown(1),
activated(2), activated(2),
tunneled(3) tunneled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the state of the Proxy-CoA: "This object indicates the state of the Proxy-CoA:
unknown -- The state of the Proxy-CoA unknown -- The state of the Proxy-CoA
cannot be determined. cannot be determined.
activated -- The Proxy-CoA is ready to establish activated -- The Proxy-CoA is ready to establish
a tunnel. This state SHOULD be a tunnel. This state SHOULD be
indicated when the MAG is up but has indicated when the MAG is up but has
no mobile node. no mobile node.
tunneled -- The Proxy-CoA is used to set up the tunneled -- Bidirectional tunnel is established
bi-directional tunnel. using the Proxy-CoA.
" "
::= { pmip6MagProxyCOAEntry 3 } ::= { pmip6MagProxyCOAEntry 3 }
pmip6MagEnableMagLocalRouting OBJECT-TYPE pmip6MagEnableMagLocalRouting OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This flag indicates whether or not the mobile access "This flag indicates whether or not the mobile access
gateway is allowed to enable local routing of the gateway is allowed to enable local routing of the
traffic exchanged between a visiting mobile node and traffic exchanged between a visiting mobile node and
a correspondent node that is locally connected to one a correspondent node that is locally connected to one
of the interfaces of the mobile access gateway. of the interfaces of the mobile access gateway.
skipping to change at page 17, line 26 skipping to change at page 16, line 48
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This flag indicates whether or not the mobile access "This flag indicates whether or not the mobile access
gateway is allowed to enable local routing of the gateway is allowed to enable local routing of the
traffic exchanged between a visiting mobile node and traffic exchanged between a visiting mobile node and
a correspondent node that is locally connected to one a correspondent node that is locally connected to one
of the interfaces of the mobile access gateway. of the interfaces of the mobile access gateway.
The correspondent node can be another visiting mobile The correspondent node can be another visiting mobile
node as well, or a local fixed node. node as well, or a local fixed node.
true(1) indicates the mobile access gateway routes the true(1) indicates that the mobile access gateway routes
traffic locally. the traffic locally.
false(0) indicates that the mobile access gateway false(0) indicates that the mobile access gateway
reverse tunnels all the traffic to the mobile node's reverse tunnels all the traffic to the mobile node's
local mobility anchor. local mobility anchor.
The default value for this flag is set to false." The default value for this flag is 'false'.
"
REFERENCE REFERENCE
"RFC 5213: Section 9.2" "RFC 5213: Section 9.2" DEFVAL { false }
::= { pmip6MagConf 1 } ::= { pmip6MagConf 1 }
pmip6MagMnIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing the identifiers of mobile nodes
attached to the MAG.
Entries in this table are not required to survive
a reboot of the managed entity.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagConf 2 }
pmip6MagMnIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6MagMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node identifier table.
"
INDEX { pmip6MagBLMnIndex
}
::= { pmip6MagMnIdentifierTable 1 }
Pmip6MagMnIdentifierEntry ::=
SEQUENCE {
pmip6MagMnIdentifier Pmip6MnIdentifier
}
pmip6MagMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MnIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identity of a mobile node in the Proxy Mobile IPv6
domain.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagMnIdentifierEntry 1 }
pmip6MagMnLLIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing the link-layer identifiers
of the interfaces of the mobile nodes attached
to the MAG.
Entries in this table are not required to survive
a reboot of the managed entity.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagConf 3 }
pmip6MagMnLLIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6MagMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node link-layer identifier
table.
"
INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex
}
::= { pmip6MagMnLLIdentifierTable 1 }
Pmip6MagMnLLIdentifierEntry ::=
SEQUENCE {
pmip6MagMnLLIdentifier Pmip6MnLLIdentifier
}
pmip6MagMnLLIdentifier OBJECT-TYPE
SYNTAX Pmip6MnLLIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The link-layer identifier of the mobile node's
connected interface on the access link.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagMnLLIdentifierEntry 1 }
pmip6MagHomeNetworkPrefixTable OBJECT-TYPE pmip6MagHomeNetworkPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF PMip6MagHomeNetworkPrefixEntry SYNTAX SEQUENCE OF Pmip6MagHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table representing the Home Network Prefixes "A table representing the home network prefixes
assigned to the connected interfaces of mobile nodes assigned to the connected interfaces of mobile nodes
attached to the MAG. attached to the MAG.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2, 6.1, 6.2" "RFC 5213: Sections 2, 6.1, 6.2"
::= { pmip6MagConf 4 }
::= { pmip6MagConf 2 }
pmip6MagHomeNetworkPrefixEntry OBJECT-TYPE pmip6MagHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX PMip6MagHomeNetworkPrefixEntry SYNTAX Pmip6MagHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Home Network Prefixes table. "An entry in the home network prefixes table.
Implementers need to be aware that if the total Implementers need to be aware that if the total
number of octets in pmip6MagHomeNetworkPrefix number of octets in pmip6MagHomeNetworkPrefix
exceeds 114 then OIDs of column exceeds 111, then OIDs of column instances in
instances in this row will have more than 128 this row will have more than 128 sub-identifiers
sub-identifiers and cannot be accessed using and cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv1, SNMPv2c, or SNMPv3. SNMPv3.
" "
INDEX { pmip6MagBLMnIdentifier, pmip6MagBLlMnIdentifier, INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex,
pmip6MagHomeNetworkPrefixType, pmip6MagHomeNetworkPrefixType,
pmip6MagHomeNetworkPrefix } pmip6MagHomeNetworkPrefix }
::= { pmip6MagHomeNetworkPrefixTable 1 } ::= { pmip6MagHomeNetworkPrefixTable 1 }
PMip6MagHomeNetworkPrefixEntry ::= Pmip6MagHomeNetworkPrefixEntry ::=
SEQUENCE { SEQUENCE {
pmip6MagHomeNetworkPrefixType InetAddressType, pmip6MagHomeNetworkPrefixType InetAddressType,
pmip6MagHomeNetworkPrefix InetAddress, pmip6MagHomeNetworkPrefix InetAddress,
pmip6MagHomeNetworkPrefixLength InetAddressPrefixLength, pmip6MagHomeNetworkPrefixLength InetAddressPrefixLength,
pmip6MagHomeNetworkPrefixLifeTime Gauge32 pmip6MagHomeNetworkPrefixLifeTime Unsigned32
} }
pmip6MagHomeNetworkPrefixType OBJECT-TYPE pmip6MagHomeNetworkPrefixType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the pmip6MagHomeNetworkPrefix "The InetAddressType of the pmip6MagHomeNetworkPrefix
that follows. that follows.
" "
::= { pmip6MagHomeNetworkPrefixEntry 1 } ::= { pmip6MagHomeNetworkPrefixEntry 1 }
pmip6MagHomeNetworkPrefix OBJECT-TYPE pmip6MagHomeNetworkPrefix OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mobile network prefix that is delegated to the "The mobile network prefix that is delegated to the
mobile node. The type of the address represented by mobile node. The type of the address represented by
this object is specified by the corresponding this object is specified by the corresponding
pmip6MagHomeNetworkPrefixType object. pmip6MagHomeNetworkPrefixType object.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2" "RFC 5213: Section 2"
::= { pmip6MagHomeNetworkPrefixEntry 2 } ::= { pmip6MagHomeNetworkPrefixEntry 2 }
pmip6MagHomeNetworkPrefixLength OBJECT-TYPE pmip6MagHomeNetworkPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the Home Network Prefix. "The prefix length of the home network prefix.
" "
::= { pmip6MagHomeNetworkPrefixEntry 3 } ::= { pmip6MagHomeNetworkPrefixEntry 3 }
pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime parameter (in seconds) that will be "The lifetime parameter (in seconds) that will be
advertised in Router Advertisements by the MAG for advertised in Router Advertisements by the MAG for
this Home Network Prefix. this home network prefix.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.2, 6.7" "RFC 5213: Sections 6.2, 6.7"
::= { pmip6MagHomeNetworkPrefixEntry 4 } ::= { pmip6MagHomeNetworkPrefixEntry 4 }
pmip6MagBLTable OBJECT-TYPE pmip6MagBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagBLEntry SYNTAX SEQUENCE OF Pmip6MagBLEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table corresponds to the Binding Update List(BL) "This table corresponds to the Binding Update List (BL)
that includes Proxy MIPv6 related information and that includes PMIPv6-related information and is
is maintained by the mobile access gateway. maintained by the mobile access gateway.
Entries from the table are deleted as Entries from the table are deleted as the lifetime of
the lifetime of the binding expires. the binding expires.
" "
REFERENCE REFERENCE
"RFC 3775: Section 4.5, 11.1, "RFC 6275: Sections 4.5, 11.1
RFC 5213: Section 6.1" RFC 5213: Section 6.1"
::= { pmip6MagRegistration 1 } ::= { pmip6MagRegistration 1 }
pmip6MagBLEntry OBJECT-TYPE pmip6MagBLEntry OBJECT-TYPE
SYNTAX Pmip6MagBLEntry SYNTAX Pmip6MagBLEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing additional information contained "An entry containing additional information from
in a Binding Update sent by the mobile access gateway a Binding Update sent by the mobile access gateway
to the local mobility anchor. to the local mobility anchor.
" "
AUGMENTS {mip6MnBLEntry} AUGMENTS {mip6MnBLEntry}
::= { pmip6MagBLTable 1 } ::= { pmip6MagBLTable 1 }
Pmip6MagBLEntry ::= SEQUENCE { Pmip6MagBLEntry ::= SEQUENCE {
pmip6MagBLFlag TruthValue, pmip6MagBLFlag TruthValue,
pmip6MagBLMnIdentifier Pmip6MNIdentifier, pmip6MagBLMnIndex Pmip6MnIndex,
pmip6MagBLlMnIdentifier Pmip6MNLlIdentifier, pmip6MagBLMnLLIndex Pmip6MnLLIndex,
pmip6MagBLMagLinkLocalAddressType InetAddressType, pmip6MagBLMagLinkLocalAddressType InetAddressType,
pmip6MagBLMagLinkLocalAddress InetAddress, pmip6MagBLMagLinkLocalAddress InetAddress,
pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC, pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC,
pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC, pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC,
pmip6MagBLAccessTechnologyType Pmip6PBUAccessTechnologyType, pmip6MagBLMnInterfaceATT Pmip6MnInterfaceATT,
pmip6MagBLTimeRecentlyAccepted DateAndTime pmip6MagBLTimeRecentlyAccepted Pmip6TimeStamp64
} }
pmip6MagBLFlag OBJECT-TYPE pmip6MagBLFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"true(1) if the mobile access gateway sent the proxy "true(1) indicates that the mobile access gateway sent
binding update with Proxy Registration Flag that the Proxy Binding Update with Proxy Registration Flag
indicates to the local mobility anchor that the that indicates to the local mobility anchor that the
registration is the proxy binding update and is from registration is the Proxy Binding Update and is from a
a mobile access gateway. mobile access gateway.
false(0) implies that the mobile access gateway is false(0) implies that the mobile access gateway is
behaving as a simple mobile node. behaving as a simple mobile node.
" "
REFERENCE REFERENCE
"RFC 5213: Section 8.1" "RFC 5213: Section 8.1"
::= { pmip6MagBLEntry 1 } ::= { pmip6MagBLEntry 1 }
pmip6MagBLMnIdentifier OBJECT-TYPE pmip6MagBLMnIndex OBJECT-TYPE
SYNTAX Pmip6MNIdentifier SYNTAX Pmip6MnIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Identifier of the attached mobile node. This "The index to the identifier of the attached mobile
identifier is acquired during the mobile node's node in the pmip6MagMnIdentifierTable.
attachment to the access link.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 6.1, 8.1" "RFC 5213: Sections 2.2, 6.1, 8.1"
::= { pmip6MagBLEntry 2 } ::= { pmip6MagBLEntry 2 }
pmip6MagBLlMnIdentifier OBJECT-TYPE pmip6MagBLMnLLIndex OBJECT-TYPE
SYNTAX Pmip6MNLlIdentifier SYNTAX Pmip6MnLLIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The link-layer identifier of the mobile node's "The index to the link-layer identifier of the mobile
connected interface. This can be acquired from the node's connected interface in the
received Router Solicitation messages from the mobile pmip6MagMnLLIdentifierTable.
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 REFERENCE
"RFC 5213: Section 2.2, 6.1, 8.1" "RFC 5213: Sections 2.2, 6.1, 8.1"
::= { pmip6MagBLEntry 3 } ::= { pmip6MagBLEntry 3 }
pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the pmip6MagBLMagLinkLocalAddress "The InetAddressType of the pmip6MagBLMagLinkLocalAddress
that follows. that follows.
" "
::= { pmip6MagBLEntry 4 } ::= { pmip6MagBLEntry 4 }
pmip6MagBLMagLinkLocalAddress OBJECT-TYPE pmip6MagBLMagLinkLocalAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Link-local address of the mobile access gateway on "The link-local address of the mobile access gateway on
the access link shared with the mobile node. the access link shared with the mobile node.
This is the address that is present in the Link-local This is the address that is present in the Link-local
Address option of the corresponding Proxy Binding Update Address option of the corresponding Proxy Binding Update
message. message.
" "
REFERENCE REFERENCE
"RFC 3963 : Section 4.1, 5.1" "RFC 3963: Sections 4.1, 5.1"
::= { pmip6MagBLEntry 5 } ::= { pmip6MagBLEntry 5 }
pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface identifier (if-id) of the point-to-point "The interface identifier (if-id) of the point-to-point
link between the mobile node and the mobile access link between the mobile node and the mobile access
gateway. This is internal to the mobile access gateway gateway. This is internal to the mobile access gateway
and is used to associate the Proxy Mobile IPv6 tunnel and is used to associate the Proxy Mobile IPv6 tunnel
to the access link where the mobile node is attached. to the access link where the mobile node is attached.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.1, 8.1" "RFC 5213: Sections 6.1, 8.1"
::= { pmip6MagBLEntry 6 } ::= { pmip6MagBLEntry 6 }
pmip6MagBLTunnelIfIdentifier OBJECT-TYPE pmip6MagBLTunnelIfIdentifier OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tunnel interface identifier (tunnel-if-id) of the "The tunnel interface identifier (tunnel-if-id) of the
bi-directional tunnel between the mobile node's local bidirectional tunnel between the mobile node's local
mobility anchor and the mobile access gateway. This mobility anchor and the mobile access gateway. This
is internal to the mobile access gateway. The tunnel is internal to the mobile access gateway. The tunnel
interface identifier is acquired during the tunnel interface identifier is acquired during the tunnel
creation. creation.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.1, 8.1" "RFC 5213: Sections 6.1, 8.1"
::= { pmip6MagBLEntry 7 } ::= { pmip6MagBLEntry 7 }
pmip6MagBLAccessTechnologyType OBJECT-TYPE pmip6MagBLMnInterfaceATT OBJECT-TYPE
SYNTAX Pmip6PBUAccessTechnologyType SYNTAX Pmip6MnInterfaceATT
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the access "The type of the access technology by which the mobile
technology by which the mobile node is currently node is currently attached to the mobile access gateway.
attached to the mobile access gateway.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.9.1.1, 6.9.1.5, 8.1" "RFC 5213: Sections 6.9.1.1, 6.9.1.5, 8.1"
::= { pmip6MagBLEntry 8 } ::= { pmip6MagBLEntry 8 }
pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE
SYNTAX DateAndTime SYNTAX Pmip6TimeStamp64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 64-bit timestamp value of the most recently "The 64-bit timestamp value of the most recently
accepted Proxy Binding Update message sent for this accepted Proxy Binding Update message sent for this
mobile node. This is the time-of-day on the mobile mobile node. This is the time of day on the mobile
access gateway, when the proxy binding acknowledgement access gateway, when the Proxy Binding Acknowledgement
message with the Status field set to 0 message with the Status field set to 0
was received. If the Timestamp option is not present was received. If the Timestamp option is not present
in the Proxy Binding Update message (i.e., when the in the Proxy Binding Update message (i.e., when the
sequence number based scheme is in use), the value MUST sequence-number-based scheme is in use), the value MUST
be set to ALL_ZERO. be initialized with all zeroes.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Sections 5.1, 8.1"
::= { pmip6MagBLEntry 9 } ::= { pmip6MagBLEntry 9 }
pmip6MagMnProfileTable OBJECT-TYPE pmip6MagMnProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table corresponds to the mobile node's policy "This table corresponds to the mobile node's policy
profile that includes the essential operational profile that includes the essential operational
parameters that are required by the network entities parameters that are required by the network entities
for managing the mobile node's mobility service. for managing the mobile node's mobility service.
It contains policy profiles of mobile nodes that are It contains policy profiles of mobile nodes that are
connected to the mobile access gateway. connected to the mobile access gateway.
Entries in this table are not required to survive
a reboot of the managed entity.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.2" "RFC 5213: Section 6.2"
::= { pmip6MagRegistration 2 } ::= { pmip6MagRegistration 2 }
pmip6MagMnProfileEntry OBJECT-TYPE pmip6MagMnProfileEntry OBJECT-TYPE
SYNTAX Pmip6MagMnProfileEntry SYNTAX Pmip6MagMnProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing information about the "An entry containing information about the
mobile node's policy profile. mobile node's policy profile.
" "
INDEX { pmip6MagMnIndex } INDEX { pmip6MagProfMnIndex }
::= { pmip6MagMnProfileTable 1 } ::= { pmip6MagMnProfileTable 1 }
Pmip6MagMnProfileEntry ::= Pmip6MagMnProfileEntry ::=
SEQUENCE { SEQUENCE {
pmip6MagMnIndex Pmip6MNIndex, pmip6MagProfMnIndex Pmip6MnIndex,
pmip6MagMnIdentifier Pmip6MNIdentifier, pmip6MagProfMnIdentifier Pmip6MnIdentifier,
pmip6MagMnLocalMobilityAnchorAddressType InetAddressType, pmip6MagProfMnLocalMobilityAnchorAddressType
pmip6MagMnLocalMobilityAnchorAddress InetAddress InetAddressType,
pmip6MagProfMnLocalMobilityAnchorAddress InetAddress
} }
pmip6MagMnIndex OBJECT-TYPE pmip6MagProfMnIndex OBJECT-TYPE
SYNTAX Pmip6MNIndex SYNTAX Pmip6MnIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for a mobile node in the Proxy Mobile IPv6 "The index for a mobile node in the Proxy Mobile IPv6
domain. domain.
" "
::= { pmip6MagMnProfileEntry 1 } ::= { pmip6MagMnProfileEntry 1 }
pmip6MagMnIdentifier OBJECT-TYPE pmip6MagProfMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MNIdentifier SYNTAX Pmip6MnIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identity of a mobile node in the Proxy Mobile IPv6 "The identity of a mobile node in the Proxy Mobile IPv6
domain. domain.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2" "RFC 5213: Section 2.2"
::= { pmip6MagMnProfileEntry 2 } ::= { pmip6MagMnProfileEntry 2 }
pmip6MagMnLocalMobilityAnchorAddressType OBJECT-TYPE pmip6MagProfMnLocalMobilityAnchorAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the "The InetAddressType of the
pmip6MagMnLocalMobilityAnchorAddress that follows. pmip6MagMnLocalMobilityAnchorAddress that follows.
" "
::= { pmip6MagMnProfileEntry 3 } ::= { pmip6MagMnProfileEntry 3 }
pmip6MagProfMnLocalMobilityAnchorAddress OBJECT-TYPE
pmip6MagMnLocalMobilityAnchorAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The global address that is configured on the interface "The global address that is configured on the interface
of the local mobility anchor and is the transport of the local mobility anchor and is the transport
endpoint of the bi-directional tunnel established endpoint of the bidirectional tunnel established
between the local mobility anchor and the mobile access between the local mobility anchor and the mobile access
gateway. This is the address to which the mobile gateway. This is the address to which the mobile
access gateway sends the Proxy Binding Update messages. access gateway sends the Proxy Binding Update messages.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2" "RFC 5213: Section 2.2"
::= { pmip6MagMnProfileEntry 4 } ::= { pmip6MagMnProfileEntry 4 }
pmip6BindingCacheTable OBJECT-TYPE pmip6BindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6BindingCacheEntry SYNTAX SEQUENCE OF Pmip6BindingCacheEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table models the Binding Cache on the local "This table models the Binding Cache on the local
mobility anchor. mobility anchor.
Entries from the table are deleted as
the lifetime of the binding expires. Entries from the table are deleted as the lifetime
of the binding expires.
Entries in this table are not required to survive Entries in this table are not required to survive
a reboot of the managed entity. a reboot of the managed entity.
" "
REFERENCE REFERENCE
"RFC 3775: Section 4.5, 9.1, 10.1, "RFC 6275: Sections 4.5, 9.1, 10.1
RFC 5213: Section 5.1" RFC 5213: Section 5.1"
::= { pmip6Bindings 1 } ::= { pmip6Bindings 1 }
pmip6BindingCacheEntry OBJECT-TYPE pmip6BindingCacheEntry OBJECT-TYPE
SYNTAX Pmip6BindingCacheEntry SYNTAX Pmip6BindingCacheEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing additional information contained "An entry containing additional information contained
in the binding cache table in the Binding Cache table of the local mobility anchor.
of the local mobility anchor.
" "
AUGMENTS {mip6BindingCacheEntry} AUGMENTS {mip6BindingCacheEntry}
::= { pmip6BindingCacheTable 1 } ::= { pmip6BindingCacheTable 1 }
Pmip6BindingCacheEntry ::= SEQUENCE { Pmip6BindingCacheEntry ::= SEQUENCE {
pmip6BindingPBUFlag TruthValue, pmip6BindingPBUFlag TruthValue,
pmip6BindingMnIdentifier Pmip6MNIdentifier, pmip6BindingMnIndex Pmip6MnIndex,
pmip6BindingMnLlIdentifier Pmip6MNLlIdentifier, pmip6BindingMnLLIndex Pmip6MnLLIndex,
pmip6BindingMagLinkLocalAddressType InetAddressType, pmip6BindingMagLinkLocalAddressType InetAddressType,
pmip6BindingMagLinkLocalAddress InetAddress, pmip6BindingMagLinkLocalAddress InetAddress,
pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC, pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC,
pmip6BindingAccessTechnologyType pmip6BindingMnInterfaceATT
Pmip6PBUAccessTechnologyType, Pmip6MnInterfaceATT,
pmip6BindingTimeRecentlyAccepted DateAndTime pmip6BindingTimeRecentlyAccepted Pmip6TimeStamp64
} }
pmip6BindingPBUFlag OBJECT-TYPE pmip6BindingPBUFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"true(1) if the local mobility anchor accepted the "true(1) indicates that the local mobility anchor
binding update with Proxy Registration Flag from a accepted the binding update with Proxy Registration
mobile access gateway. Flag from a mobile access gateway.
false(0) implies that the binding cache is from a false(0) implies that the binding cache is from a
mobile node. In this case the remaining objects will mobile node. In this case, the remaining objects will
not be accessible. not be accessible.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 1 } ::= { pmip6BindingCacheEntry 1 }
pmip6BindingMnIdentifier OBJECT-TYPE pmip6BindingMnIndex OBJECT-TYPE
SYNTAX Pmip6MNIdentifier SYNTAX Pmip6MnIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier of the registered mobile node, "An index to the identifier of the registered mobile
MN-Identifier. This identifier is obtained from the node.
Mobile Node Identifier Option [RFC4283] present in
the received Proxy Binding Update message.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 5.1, 8.1" "RFC 5213: Sections 2.2, 5.1, 8.1
RFC 4283: Section 3"
::= { pmip6BindingCacheEntry 2 } ::= { pmip6BindingCacheEntry 2 }
pmip6BindingMnLLIndex OBJECT-TYPE
pmip6BindingMnLlIdentifier OBJECT-TYPE SYNTAX Pmip6MnLLIndex
SYNTAX Pmip6MNLlIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The link-layer identifier of the mobile node's "The index to the link-layer identifier of the mobile
connected interface on the access link. This node's connected interface on the access link.
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 REFERENCE
"RFC 5213: Section 2.2, 5.1, 8.1" "RFC 5213: Sections 2.2, 5.1, 8.1"
::= { pmip6BindingCacheEntry 3 } ::= { pmip6BindingCacheEntry 3 }
pmip6BindingMagLinkLocalAddressType OBJECT-TYPE pmip6BindingMagLinkLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The InetAddressType of the "The InetAddressType of the
pmip6BindingMagLinkLocalAddress that follows. pmip6BindingMagLinkLocalAddress that follows.
" "
skipping to change at page 28, line 19 skipping to change at page 28, line 14
DESCRIPTION DESCRIPTION
"The link-local address of the mobile access gateway on "The link-local address of the mobile access gateway on
the point-to-point link shared with the mobile node. the point-to-point link shared with the mobile node.
This is generated by the local mobility anchor after This is generated by the local mobility anchor after
accepting the initial Proxy Binding Update message. accepting the initial Proxy Binding Update message.
This is the address that is present in the Link-local This is the address that is present in the Link-local
Address option of the corresponding Proxy Binding Address option of the corresponding Proxy Binding
Acknowledgement message. Acknowledgement message.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 6.9.1.2, 8.2" "RFC 5213: Sections 5.1, 6.9.1.2, 8.2"
::= { pmip6BindingCacheEntry 5 } ::= { pmip6BindingCacheEntry 5 }
pmip6BindingTunnelIfIdentifier OBJECT-TYPE pmip6BindingTunnelIfIdentifier OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tunnel interface identifier (tunnel-if-id) of the "The tunnel interface identifier (tunnel-if-id) of the
bi-directional tunnel between the local mobility anchor bidirectional tunnel between the local mobility anchor
and the mobile access gateway where the mobile node is and the mobile access gateway where the mobile node is
currently anchored. This is internal to the local currently anchored. This is internal to the local
mobility anchor. The tunnel interface identifier is mobility anchor. The tunnel interface identifier is
acquired during the tunnel creation. acquired during the tunnel creation.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 6 } ::= { pmip6BindingCacheEntry 6 }
pmip6BindingAccessTechnologyType OBJECT-TYPE pmip6BindingMnInterfaceATT OBJECT-TYPE
SYNTAX Pmip6PBUAccessTechnologyType SYNTAX Pmip6MnInterfaceATT
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The access technology type, by which the mobile node "The access technology type by which the mobile node
is currently attached. This is obtained from the is currently attached. This is obtained from the
Access Technology Type option, present in the Proxy Access Technology Type option, present in the Proxy
Binding Update message. Binding Update message.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 7 } ::= { pmip6BindingCacheEntry 7 }
pmip6BindingTimeRecentlyAccepted OBJECT-TYPE pmip6BindingTimeRecentlyAccepted OBJECT-TYPE
SYNTAX DateAndTime SYNTAX Pmip6TimeStamp64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 64-bit timestamp value of the most recently "The 64-bit timestamp value of the most recently
accepted Proxy Binding Update message sent for this accepted Proxy Binding Update message sent for this
mobile node. This is the time-of-day on the local mobile node. This is the time of day on the local
mobility anchor, when the message was received. If mobility anchor, when the message was received. If
the Timestamp option is not present in the Proxy the Timestamp option is not present in the Proxy
Binding Update message (i.e., when the sequence number Binding Update message (i.e., when the sequence number
based scheme is in use), the value MUST be set to based scheme is in use), the value MUST be initialized
ALL_ZERO. with all zeroes.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 8 } ::= { pmip6BindingCacheEntry 8 }
--- ---
--- ---
--- pmip6Stats group --- pmip6Stats group
--- ---
--- ---
-- --
-- pmip6Stats:pmip6BindingRegcounters -- pmip6Stats:pmip6BindingRegCounters
-- --
pmip6MissingMnIdentifierOption OBJECT-TYPE pmip6MissingMnIdentifierOption OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update messages "Total number of Proxy Binding Update messages
rejected by the local mobility anchor with status rejected by the local mobility anchor with status
code in the Binding Acknowledgement message indicating code in the Binding Acknowledgement message indicating
'Missing mobile node identifier option' (Code 160). 'Missing mobile node identifier option' (Code 160).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the mobile router. occur at re-initialization of the mobile router,
and at other times as indicated by the value of
pmip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 1 }
and at other times as indicated by the value of pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE
pmip6CounterDiscontinuityTime. SYNTAX Counter32
" MAX-ACCESS read-only
REFERENCE STATUS current
"RFC 5213: Section 5.3.1, 8.9" DESCRIPTION
::= { pmip6BindingRegCounters 1 } "Total number of Proxy Binding Update messages
rejected by the local mobility anchor with status
code in the Binding Acknowledgement message indicating
'Not authorized to send Proxy Binding Updates'
(Code 154).
pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE Discontinuities in the value of this counter can
SYNTAX Counter32 occur at re-initialization of the mobile router,
MAX-ACCESS read-only and at other times as indicated by the value of
STATUS current pmip6CounterDiscontinuityTime.
DESCRIPTION "
"Total number of Proxy Binding Update message REFERENCE
rejected by the local mobility anchor with status "RFC 5213: Sections 5.3.1, 8.9"
code in the Binding Acknowledgement message indicating ::= { pmip6BindingRegCounters 2 }
'Not authorized to send proxy binding updates'
(Code 154).
Discontinuities in the value of this counter can pmip6NotLMAForThisMobileNode OBJECT-TYPE
occur at re-initialization of the mobile router, SYNTAX Counter32
and at other times as indicated by the value of MAX-ACCESS read-only
pmip6CounterDiscontinuityTime. STATUS current
" DESCRIPTION
REFERENCE "Total number of Proxy Binding Update messages rejected
"RFC 5213: Section 5.3.1, 8.9" by the local mobility anchor with status code in the
::= { pmip6BindingRegCounters 2 } Binding Acknowledgement message indicating
'Not local mobility anchor for this mobile node'
(Code 153).
pmip6NotLMAForThisMobileNode OBJECT-TYPE Discontinuities in the value of this counter can
SYNTAX Counter32 occur at re-initialization of the management system,
MAX-ACCESS read-only and at other times as indicated by the value of
STATUS current pmip6CounterDiscontinuityTime.
DESCRIPTION "
"Total number of Proxy Binding Update message rejected REFERENCE
by the local mobility anchor with status code in the "RFC 5213: Sections 5.3.1, 8.9"
Binding Acknowledgement message indicating ::= { pmip6BindingRegCounters 3 }
'Not local mobility anchor for this mobile node'
(Code 153).
Discontinuities in the value of this counter can pmip6ProxyRegNotEnabled OBJECT-TYPE
occur at re-initialization of the management system, SYNTAX Counter32
and at other times as indicated by the value of MAX-ACCESS read-only
pmip6CounterDiscontinuityTime. STATUS current
" DESCRIPTION
REFERENCE "Total number of Proxy Binding Update messages rejected
"RFC 5213: Section 5.3.1, 8.9" by the local mobility anchor with status code in the
::= { pmip6BindingRegCounters 3 } Binding Acknowledgement message indicating
'Proxy Registration not enabled' (Code 152).
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.
"
pmip6ProxyRegNotEnabled OBJECT-TYPE REFERENCE
SYNTAX Counter32 "RFC 5213: Sections 5.3.1, 6.9.1.2, 8.9"
MAX-ACCESS read-only ::= { pmip6BindingRegCounters 4 }
STATUS current pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE
DESCRIPTION SYNTAX Counter32
"Total number of Proxy Binding Update message rejected MAX-ACCESS read-only
by the local mobility anchor with status code in the STATUS current
Binding Acknowledgement message indicating DESCRIPTION
'Proxy Registration not enabled' (Code 152). "Total number of Proxy Binding Update messages rejected
Discontinuities in the value of this counter can by the local mobility anchor with status code in the
occur at re-initialization of the management system, Binding Acknowledgement message indicating
and at other times as indicated by the value of 'Missing home network prefix option' (Code 158).
pmip6CounterDiscontinuityTime. Discontinuities in the value of this counter can
" occur at re-initialization of the management system,
REFERENCE and at other times as indicated by the value of
"RFC 5213: Section 5.3.1, 6.9.1.2, 8.9" pmip6CounterDiscontinuityTime.
::= { pmip6BindingRegCounters 4 } "
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 5 }
pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE pmip6MissingHandOffIndicatorOption OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'Missing home network prefix option' (Code 158). 'Missing handoff indicator option' (Code 161).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.1, 8.9" "RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 5 } ::= { pmip6BindingRegCounters 6 }
pmip6MissingHandOffIndicatorOption OBJECT-TYPE pmip6MissingAccessTechTypeOption OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'Missing handoff indicator option' (Code 161). 'Missing access technology type option' (Code 162).
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
"RFC 5213: Section 5.3.1, 8.9"
::= { pmip6BindingRegCounters 6 }
pmip6MissingAccessTechTypeOption OBJECT-TYPE Discontinuities in the value of this counter can
SYNTAX Counter32 occur at re-initialization of the management system,
MAX-ACCESS read-only and at other times as indicated by the value of
STATUS current pmip6CounterDiscontinuityTime.
DESCRIPTION "
"Total number of Proxy Binding Update message rejected REFERENCE
by the local mobility anchor with status code in the "RFC 5213: Sections 5.3.1, 8.9"
Binding Acknowledgement message indicating ::= { pmip6BindingRegCounters 7 }
'Missing access technology type option' (Code 162).
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
"RFC 5213: Section 5.3.1, 8.9"
::= { pmip6BindingRegCounters 7 }
pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'Mobile node not authorized for one or more of the 'Mobile node not authorized for one or more of the
requesting home network prefixes' (Code 155). requesting home network prefixes' (Code 155).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.2, 6.9.1.2, 8.9" "RFC 5213: Sections 5.3.2, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 8 } ::= { pmip6BindingRegCounters 8 }
pmip6TimestampMismatch OBJECT-TYPE pmip6TimestampMismatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'Invalid timestamp value (the clocks are out of sync)' 'Invalid timestamp value (the clocks are out of sync)'
(Code 156) (Code 156).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.5, 6.9.1.2, 8.9" "RFC 5213: Sections 5.5, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 9 } ::= { pmip6BindingRegCounters 9 }
pmip6TimestampLowerThanPrevAccepted OBJECT-TYPE pmip6TimestampLowerThanPrevAccepted OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'The timestamp value is lower than the previously 'The timestamp value is lower than the previously
accepted value' (Code 157). accepted value' (Code 157).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.5, 6.9.1.2, 8.9" "RFC 5213: Sections 5.5, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 10 } ::= { pmip6BindingRegCounters 10 }
pmip6BcePbuPrefixSetDoNotMatch OBJECT-TYPE pmip6BcePbuPrefixSetDoNotMatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message rejected "Total number of Proxy Binding Update messages rejected
by the local mobility anchor with status code in the by the local mobility anchor with status code in the
Binding Acknowledgement message indicating Binding Acknowledgement message indicating
'All the home network prefixes listed in the Binding 'All the home network prefixes listed in the Binding
Cache Entry do not match all the prefixes in the Cache entry do not match all the prefixes in the
received Proxy Binding Update' (Code 159). received Proxy Binding Update' (Code 159).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.4.1.1, 8.9" "RFC 5213: Sections 5.4.1.1, 8.9"
::= { pmip6BindingRegCounters 11 } ::= { pmip6BindingRegCounters 11 }
pmip6InitialBindingRegistrations OBJECT-TYPE pmip6InitialBindingRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update messages that "Total number of Proxy Binding Update messages that
newly creates the Binding Cache entry. newly creates the Binding Cache entry.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.2" "RFC 5213: Sections 5.3.2"
::= { pmip6BindingRegCounters 12 } ::= { pmip6BindingRegCounters 12 }
pmip6BindingLifeTimeExtensionNoHandOff OBJECT-TYPE pmip6BindingLifeTimeExtensionNoHandOff OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message for "Total number of Proxy Binding Update messages for
extending the binding lifetime, received from the extending the binding lifetime, received from the
same mobile access gateway that last updated the same mobile access gateway that last updated the
binding. 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
"RFC 5213: Sections 5.3.3"
::= { pmip6BindingRegCounters 13 }
Discontinuities in the value of this counter can pmip6BindingLifeTimeExtensionAfterHandOff OBJECT-TYPE
occur at re-initialization of the management system, SYNTAX Counter32
and at other times as indicated by the value of MAX-ACCESS read-only
pmip6CounterDiscontinuityTime. STATUS current
" DESCRIPTION
REFERENCE "Total number of Proxy Binding Update messages for
"RFC 5213: Section 5.3.3" extending the binding lifetime, received from a new
::= { pmip6BindingRegCounters 13 } 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
"RFC 5213: Sections 5.3.4"
::= { pmip6BindingRegCounters 14 }
pmip6BindingLifeTimeExtensionAfterHandOff OBJECT-TYPE pmip6BindingDeRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message for "Total number of Proxy Binding Update messages with
extending the binding lifetime, received from a new the lifetime value of zero.
mobile access gateway where the mobile node's Discontinuities in the value of this counter can
mobility session is handed off. occur at re-initialization of the management system,
Discontinuities in the value of this counter can and at other times as indicated by the value of
occur at re-initialization of the management system, pmip6CounterDiscontinuityTime.
and at other times as indicated by the value of "
pmip6CounterDiscontinuityTime. REFERENCE
" "RFC 5213: Sections 5.3.5"
REFERENCE ::= { pmip6BindingRegCounters 15 }
"RFC 5213: Section 5.3.4"
::= { pmip6BindingRegCounters 14 }
pmip6BindingDeRegistrations OBJECT-TYPE pmip6BindingBindingAcks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Update message with the "Total number of Proxy Binding Acknowledgement
lifetime value of zero. messages.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management system, occur at re-initialization of the management system,
and at other times as indicated by the value of and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.5" "RFC 5213: Sections 5.3.5"
::= { pmip6BindingRegCounters 15 } ::= { pmip6BindingRegCounters 16 }
pmip6BindingBindingAcks OBJECT-TYPE pmip6CounterDiscontinuityTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Total number of Proxy Binding Acknowledgement "The value of sysUpTime on the most recent occasion
messages. at which any one or more of this PMIPv6 entity's
Discontinuities in the value of this counter can global counters, viz., counters with OID prefix
occur at re-initialization of the management system, 'pmip6BindingRegCounters' suffered a discontinuity.
and at other times as indicated by the value of If no such discontinuities have occurred since the
pmip6CounterDiscontinuityTime. last re-initialization of the local management
" subsystem, then this object will have a zero value.
REFERENCE "
"RFC 5213: Section 5.3.5" ::= { pmip6BindingRegCounters 17 }
::= { pmip6BindingRegCounters 16 }
pmip6CounterDiscontinuityTime OBJECT-TYPE pmip6LmaStatus OBJECT-TYPE
SYNTAX TimeStamp SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion "This object indicates whether the PMIPv6 local
at which any one or more of this PMIPv6 entities mobility anchor function is enabled for the managed
global counters, viz., counters with OID prefix entity.
'pmip6BindingRegCounters' suffered a discontinuity.
If no such discontinuities have occurred since the
last re-initialization of the local management
subsystem, then this object will have a zero value.
"
::= { pmip6BindingRegCounters 17 }
pmip6LmaLMAATable OBJECT-TYPE Changing the status from enabled(1) to disabled(2)
will terminate the PMIPv6 local mobility anchor
function. On the other hand, changing the status
from disabled(2) to enabled(1) will start the PMIPv6
local mobility anchor function.
The value of this object MUST remain unchanged
across reboots of the managed entity.
"
DEFVAL { disabled }
::= { pmip6LmaSystem 1 }
pmip6LmaLMAATable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6LmaLMAAEntry SYNTAX SEQUENCE OF Pmip6LmaLMAAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table models the LMA Addresses configured "This table models the LMA Addresses configured
on the local mobility anchor. Each LMA Address acts as on the local mobility anchor. Each LMA Address acts as
a transport endpoint of the tunnel between the local a transport endpoint of the tunnel between the local
mobility anchor and the mobile access gateway and is mobility anchor and the mobile access gateway and is
the transport endpoint of the tunnel between the local the transport endpoint of the tunnel between the local
mobility anchor and the mobile access gateway. mobility anchor and the mobile access gateway.
Entries in this table are not required to survive Entries in this table are not required to survive
a reboot of the managed entity. a reboot of the managed entity.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 5.6" "RFC 5213: Sections 2.2, 5.6"
::= { pmip6LmaSystem 1 } ::= { pmip6LmaSystem 2 }
pmip6LmaLMAAEntry OBJECT-TYPE pmip6LmaLMAAEntry OBJECT-TYPE
SYNTAX Pmip6LmaLMAAEntry SYNTAX Pmip6LmaLMAAEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry represents a conceptual row in the "This entry represents a conceptual row in the
LMAA table. It represents each LMAA LMAA table. It represents each LMAA on the
on the local mobility anchor. local mobility anchor.
Implementers need to be aware that if the total Implementers need to be aware that if the total
number of octets in mip6BindingHomeAddress number of octets in pmip6LmaLMAA exceeds 113,
exceeds 113 then OIDs of column then OIDs of column instances in this row will
instances in this row will have more than 128 have more than 128 sub-identifiers and cannot
sub-identifiers and cannot be accessed using be accessed using SNMPv1, SNMPv2c, or SNMPv3.
SNMPv1, SNMPv2c, or SNMPv3.
" "
INDEX { pmip6LmaLMAAType, pmip6LmaLMAA } INDEX { pmip6LmaLMAAType, pmip6LmaLMAA }
::= { pmip6LmaLMAATable 1 } ::= { pmip6LmaLMAATable 1 }
Pmip6LmaLMAAEntry ::= Pmip6LmaLMAAEntry ::=
SEQUENCE { SEQUENCE {
pmip6LmaLMAAType InetAddressType, pmip6LmaLMAAType InetAddressType,
pmip6LmaLMAA InetAddress, pmip6LmaLMAA InetAddress,
pmip6LmaLMAAState INTEGER pmip6LmaLMAAState INTEGER
} }
pmip6LmaLMAAType OBJECT-TYPE pmip6LmaLMAAType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 38, line 13 skipping to change at page 37, line 38
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LMAA configured on the local mobility anchor. "The LMAA configured on the local mobility anchor.
The type of the address represented by this object The type of the address represented by this object
is specified by the corresponding is specified by the corresponding
pmip6LmaLMAAType object. pmip6LmaLMAAType object.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2, 5.6" "RFC 5213: Sections 2.2, 5.6"
::= { pmip6LmaLMAAEntry 2 } ::= { pmip6LmaLMAAEntry 2 }
pmip6LmaLMAAState OBJECT-TYPE pmip6LmaLMAAState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
activated(2), activated(2),
tunneled(3) tunneled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 38, line 28 skipping to change at page 38, line 4
unknown(1), unknown(1),
activated(2), activated(2),
tunneled(3) tunneled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the state of the LMAA: "This object indicates the state of the LMAA:
unknown -- The state of the LMAA unknown -- The state of the LMAA
cannot be determined. cannot be determined.
activated -- The LMAA is ready to establish activated -- The LMAA is ready to establish
tunnel a tunnel.
tunneled -- The LMAA is used to set up the tunneled -- The LMAA is used to set up the
bi-directional tunnel. bidirectional tunnel.
" "
::= { pmip6LmaLMAAEntry 3 } ::= { pmip6LmaLMAAEntry 3 }
pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the length of time in "This variable specifies the length of time in
milliseconds the local mobility anchor MUST wait before milliseconds the local mobility anchor MUST wait before
it deletes a Binding Cache entry of a mobile node, upon it deletes a Binding Cache entry of a mobile node, upon
receiving a Proxy Binding Update message from a mobile receiving a Proxy Binding Update message from a mobile
access gateway with a lifetime value of 0. access gateway with a lifetime value of 0.
During this wait time, if the local mobility anchor During this wait time, if the local mobility anchor
receives a Proxy Binding Update for the same mobility receives a Proxy Binding Update for the same mobility
binding, with a lifetime value greater than 0, then it binding, with a lifetime value greater than 0, then it
must update the binding cache entry with the accepted must update the Binding Cache entry with the accepted
binding values. By the end of this wait-time, if the binding values. By the end of this wait time, if the
local mobility anchor did not receive any valid Proxy local mobility anchor did not receive any valid Proxy
Binding Update message for that mobility binding, it Binding Update message for that mobility binding, it
MUST delete the Binding Cache entry. This delay MUST delete the Binding Cache entry. This delay
essentially ensures that a mobile node's Binding Cache essentially ensures that a mobile node's Binding Cache
entry is not deleted too quickly and allows some time entry is not deleted too quickly and allows some time
for the new mobile access gateway to complete the for the new mobile access gateway to complete the
signaling for the mobile node. signaling for the mobile node.
The default value for this variable is 10000 The default value for this variable is 10000
milliseconds. milliseconds.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.5, 9.1" "RFC 5213: Sections 5.3.5, 9.1"
DEFVAL { 10000 }
::= { pmip6LmaConf 1 } ::= { pmip6LmaConf 1 }
pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the length of time in "This variable specifies the length of time in
milliseconds the local mobility anchor MUST wait for milliseconds the local mobility anchor MUST wait for
the de-registration message for an existing mobility the de-registration message for an existing mobility
session before it decides to create a new mobility session before it decides to create a new mobility
session. session.
The default value for this variable is 1500 The default value for this variable is 1500
milliseconds. Note that there is a dependency between milliseconds. Note that there is a dependency between
this value and the values used in the retransmission this value and the values used in the retransmission
algorithm for Proxy Binding Updates. The retransmissions algorithm for Proxy Binding Updates. The
need to happen before MaxDelayBeforeNewBCEAssign runs retransmissions need to happen before
out, as otherwise there are situations where a MaxDelayBeforeNewBCEAssign runs out, as otherwise there
de-registration from a previous mobile access gateway are situations where a de-registration from a previous
may be lost, and the local mobility anchor creates, mobile access gateway may be lost, and the local
needlessly, a new mobility session and new prefixes for mobility anchor creates, needlessly, a new mobility
the mobile node. However, this affects situations where session and new prefixes for the mobile node. However,
there is no information from the lower layers about the this affects situations where there is no information
type of a handoff or other parameters that can be used from the lower layers about the type of a handoff or
for identifying the mobility session. other parameters that can be used for identifying the
mobility session.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.4.1.2, 5.4.1.3, 9.1" "RFC 5213: Sections 5.4.1.2, 5.4.1.3, 9.1"
DEFVAL { 1500 }
::= { pmip6LmaConf 2 } ::= { pmip6LmaConf 2 }
pmip6LmaTimestampValidityWindow OBJECT-TYPE pmip6LmaTimestampValidityWindow OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the maximum length of time "This variable specifies the maximum length of time
difference in milliseconds between the timestamp in the difference in milliseconds between the timestamp in the
received Proxy Binding Update message and the current received Proxy Binding Update message and the current
time-of-day on the local mobility anchor, that is time of day on the local mobility anchor that is
allowed by the local mobility anchor for the received allowed by the local mobility anchor for the received
message to be considered valid. message to be considered valid.
The default value for this variable is 300 milliseconds. The default value for this variable is 300 milliseconds.
This variable must be adjusted to suit the deployments. This variable must be adjusted to suit the deployments.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.5, 9.1" "RFC 5213: Sections 5.5, 9.1"
DEFVAL { 300 }
::= { pmip6LmaConf 3 } ::= { pmip6LmaConf 3 }
pmip6LmaMnIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6LmaMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing the identifiers of mobile nodes
served by the LMA.
Entries in this table are not required to survive
a reboot of the managed entity.
"
REFERENCE
"RFC 5213: Sections 2, 6.1"
::= { pmip6LmaConf 4 }
pmip6LmaMnIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6LmaMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node identifier table.
"
INDEX { pmip6BindingMnIndex
}
::= { pmip6LmaMnIdentifierTable 1 }
Pmip6LmaMnIdentifierEntry ::=
SEQUENCE {
pmip6LmaMnIdentifier Pmip6MnIdentifier
}
pmip6LmaMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MnIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identity of a mobile node in the Proxy Mobile IPv6
domain.
"
REFERENCE
"RFC 5213: Section 2.2"
::= { pmip6LmaMnIdentifierEntry 1 }
pmip6LmaMnLLIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6LmaMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing the link-layer identifiers
of the interfaces of the mobile nodes served
by the LMA.
Entries in this table are not required to survive
a reboot of the managed entity.
"
REFERENCE
"RFC 5213: Sections 2, 6.1"
::= { pmip6LmaConf 5 }
pmip6LmaMnLLIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6LmaMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node link-layer identifier
table.
"
INDEX { pmip6BindingMnIndex, pmip6BindingMnLLIndex
}
::= { pmip6LmaMnLLIdentifierTable 1 }
Pmip6LmaMnLLIdentifierEntry ::=
SEQUENCE {
pmip6LmaMnLLIdentifier Pmip6MnLLIdentifier
}
pmip6LmaMnLLIdentifier OBJECT-TYPE
SYNTAX Pmip6MnLLIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The link-layer identifier of the mobile node's
connected interface on the access link.
"
::= { pmip6LmaMnLLIdentifierEntry 1 }
pmip6LmaHomeNetworkPrefixTable OBJECT-TYPE pmip6LmaHomeNetworkPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF PMip6LmaHomeNetworkPrefixEntry SYNTAX SEQUENCE OF Pmip6LmaHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table representing the Home Network Prefixes "A table representing the home network prefixes
assigned to the connected interfaces of all the assigned to the connected interfaces of all the
mobile nodes anchored at the LMA. mobile nodes anchored at the LMA.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2, 5.1, 5.2" "RFC 5213: Sections 2, 5.1, 5.2"
::= { pmip6LmaConf 4 } ::= { pmip6LmaConf 6 }
pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX PMip6LmaHomeNetworkPrefixEntry SYNTAX Pmip6LmaHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Home Network Prefixes table. "An entry in the home network prefixes table.
Implementers need to be aware that if the total Implementers need to be aware that if the total
number of octets in pmip6LmaHomeNetworkPrefix number of octets in pmip6LmaHomeNetworkPrefix
exceeds 114 then OIDs of column exceeds 111 then OIDs of column instances in this
instances in this row will have more than 128 row will have more than 128 sub-identifiers and
sub-identifiers and cannot be accessed using cannot be accessed using SNMPv1, SNMPv2c, or
SNMPv1, SNMPv2c, or SNMPv3. SNMPv3.
" "
INDEX { pmip6BindingMnIndex, pmip6BindingMnLLIndex,
INDEX { pmip6BindingMnIdentifier,
pmip6BindingMnLlIdentifier,
pmip6LmaHomeNetworkPrefixType, pmip6LmaHomeNetworkPrefixType,
pmip6LmaHomeNetworkPrefix } pmip6LmaHomeNetworkPrefix }
::= { pmip6LmaHomeNetworkPrefixTable 1 } ::= { pmip6LmaHomeNetworkPrefixTable 1 }
PMip6LmaHomeNetworkPrefixEntry ::= Pmip6LmaHomeNetworkPrefixEntry ::=
SEQUENCE { SEQUENCE {
pmip6LmaHomeNetworkPrefixType InetAddressType, pmip6LmaHomeNetworkPrefixType InetAddressType,
pmip6LmaHomeNetworkPrefix InetAddress, pmip6LmaHomeNetworkPrefix InetAddress,
pmip6LmaHomeNetworkPrefixLength InetAddressPrefixLength, pmip6LmaHomeNetworkPrefixLength InetAddressPrefixLength,
pmip6LmaHomeNetworkPrefixLifeTime Gauge32 pmip6LmaHomeNetworkPrefixLifeTime Gauge32
} }
pmip6LmaHomeNetworkPrefixType OBJECT-TYPE pmip6LmaHomeNetworkPrefixType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 41, line 35 skipping to change at page 42, line 41
that follows. that follows.
" "
::= { pmip6LmaHomeNetworkPrefixEntry 1 } ::= { pmip6LmaHomeNetworkPrefixEntry 1 }
pmip6LmaHomeNetworkPrefix OBJECT-TYPE pmip6LmaHomeNetworkPrefix OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mobile network prefix that is delegated to the "The mobile network prefix that is delegated to the
mobile node. The type of the address represented by mobile node. The type of the address represented by
this object is specified by the corresponding this object is specified by the corresponding
pmip6LmaHomeNetworkPrefixType object. pmip6LmaHomeNetworkPrefixType object.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2" "RFC 5213: Section 2"
::= { pmip6LmaHomeNetworkPrefixEntry 2 } ::= { pmip6LmaHomeNetworkPrefixEntry 2 }
pmip6LmaHomeNetworkPrefixLength OBJECT-TYPE pmip6LmaHomeNetworkPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The prefix length of the Home Network Prefix. "The prefix length of the home network prefix.
" "
::= { pmip6LmaHomeNetworkPrefixEntry 3 } ::= { pmip6LmaHomeNetworkPrefixEntry 3 }
pmip6LmaHomeNetworkPrefixLifeTime OBJECT-TYPE pmip6LmaHomeNetworkPrefixLifeTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime (in seconds) granted to the mobile "The lifetime (in seconds) granted to the mobile
node for this registration. node for this registration.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3" "RFC 5213: Section 5.3"
::= { pmip6LmaHomeNetworkPrefixEntry 4 } ::= { pmip6LmaHomeNetworkPrefixEntry 4 }
-- --
-- pmip6Notifications -- pmip6Notifications
-- --
-- --
pmip6MagHomeTunnelEstablished 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
the local mobility anchor and mobile access gateway.
"
REFERENCE
"RFC 5213: Section 5.6.1"
::= { pmip6Notifications 1 }
pmip6MagHomeTunnelReleased NOTIFICATION-TYPE pmip6MagHomeTunnelEstablished NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pmip6MagBLTunnelIfIdentifier, pmip6MagBLTunnelIfIdentifier,
-- pmip6MagProxyCOAType,
-- pmip6MagProxyCOA
pmip6MagProxyCOAState pmip6MagProxyCOAState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by the Proxy MobileIPv6 "This notification is sent by the Proxy Mobile IPv6
entities every time the tunnel between the local entities every time the tunnel is established between
mobility anchor and mobile access gateway is released. the local mobility anchor and mobile access gateway.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.6.1" "RFC 5213: Section 5.6.1"
::= { pmip6Notifications 2} ::= { pmip6Notifications 1 }
pmip6LmaHomeTunnelEstablished NOTIFICATION-TYPE pmip6MagHomeTunnelReleased NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pmip6BindingTunnelIfIdentifier, pmip6MagBLTunnelIfIdentifier,
-- pmip6LmaLMAAType, pmip6MagProxyCOAState
-- pmip6LmaLMAA, }
pmip6LmaLMAAState STATUS current
} DESCRIPTION
STATUS current "This notification is sent by the Proxy Mobile IPv6
DESCRIPTION entities every time the tunnel between the local
"This notification is sent by the Proxy MobileIPv6 mobility anchor and mobile access gateway is released.
entities every time the tunnel is established between "
the local mobility anchor and mobile access gateway. REFERENCE
" "RFC 5213: Section 5.6.1"
REFERENCE ::= { pmip6Notifications 2}
"RFC 5213: Section 5.6.1"
::= { pmip6Notifications 3 }
pmip6LmaHomeTunnelReleased NOTIFICATION-TYPE pmip6LmaHomeTunnelEstablished NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pmip6BindingTunnelIfIdentifier, pmip6BindingTunnelIfIdentifier,
-- pmip6LmaLMAAType,
-- pmip6LmaLMAA,
pmip6LmaLMAAState pmip6LmaLMAAState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent by the Proxy MobileIPv6 "This notification is sent by the Proxy Mobile IPv6
entities every time the tunnel between the local entities every time the tunnel is established between
mobility anchor and mobile access gateway is released. the local mobility anchor and mobile access gateway.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.6.1" "RFC 5213: Section 5.6.1"
::= { pmip6Notifications 4} ::= { pmip6Notifications 3 }
-- Conformance information pmip6LmaHomeTunnelReleased NOTIFICATION-TYPE
pmip6Groups OBJECT IDENTIFIER ::= { pmip6Conformance 1 } OBJECTS {
pmip6Compliances OBJECT IDENTIFIER ::= { pmip6Conformance 2 } pmip6BindingTunnelIfIdentifier,
pmip6LmaLMAAState
}
STATUS current
DESCRIPTION
"This notification is sent by the Proxy Mobile IPv6
entities every time the tunnel between the local
mobility anchor and mobile access gateway is released.
"
REFERENCE
"RFC 5213: Section 5.6.1"
::= { pmip6Notifications 4}
-- Units of conformance -- Conformance information
pmip6SystemGroup OBJECT-GROUP pmip6Groups OBJECT IDENTIFIER ::= { pmip6Conformance 1 }
OBJECTS { pmip6Compliances OBJECT IDENTIFIER ::= { pmip6Conformance 2 }
pmip6Capabilities,
pmip6Status,
pmip6MobileNodeGeneratedTimestampInUse,
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType,
pmip6FixedMagLinkLocalAddressOnAllAccessLinks,
pmip6FixedMagLinkLayerAddressOnAllAccessLinks
} -- Units of conformance
STATUS current pmip6SystemGroup OBJECT-GROUP
DESCRIPTION OBJECTS {
" A collection of objects for basic PMIPv6 pmip6Capabilities,
monitoring." pmip6MobileNodeGeneratedTimestampInUse,
::= { pmip6Groups 1 } pmip6FixedMagLinkLocalAddressOnAllAccessLinksType,
pmip6FixedMagLinkLocalAddressOnAllAccessLinks,
pmip6FixedMagLinkLayerAddressOnAllAccessLinks
pmip6BindingCacheGroup OBJECT-GROUP }
OBJECTS { STATUS current
pmip6BindingPBUFlag, DESCRIPTION
pmip6BindingMnIdentifier, " A collection of objects for basic PMIPv6
pmip6BindingMnLlIdentifier, monitoring."
pmip6BindingMagLinkLocalAddressType, ::= { pmip6Groups 1 }
pmip6BindingMagLinkLocalAddress,
pmip6BindingTunnelIfIdentifier,
pmip6BindingAccessTechnologyType,
pmip6BindingTimeRecentlyAccepted
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
PMIPv6 extensions of the Binding Cache."
::= { pmip6Groups 2 }
pmip6StatsGroup OBJECT-GROUP pmip6BindingCacheGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmip6MissingMnIdentifierOption, pmip6BindingPBUFlag,
pmip6MagNotAuthorizedForProxyReg, pmip6BindingMnIndex,
pmip6NotLMAForThisMobileNode, pmip6BindingMnLLIndex,
pmip6ProxyRegNotEnabled, pmip6BindingMagLinkLocalAddressType,
pmip6MissingHomeNetworkPrefixOption, pmip6BindingMagLinkLocalAddress,
pmip6MissingHandOffIndicatorOption, pmip6BindingTunnelIfIdentifier,
pmip6MissingAccessTechTypeOption, pmip6BindingMnInterfaceATT,
pmip6NotAuthorizedForHomeNetworkPrefix, pmip6BindingTimeRecentlyAccepted,
pmip6TimestampMismatch, pmip6LmaMnIdentifier,
pmip6TimestampLowerThanPrevAccepted, pmip6LmaMnLLIdentifier
pmip6BcePbuPrefixSetDoNotMatch, }
pmip6InitialBindingRegistrations, STATUS current
pmip6BindingLifeTimeExtensionNoHandOff, DESCRIPTION
pmip6BindingLifeTimeExtensionAfterHandOff, " A collection of objects for monitoring the
pmip6BindingDeRegistrations, PMIPv6 extensions of the Binding Cache."
pmip6BindingBindingAcks, ::= { pmip6Groups 2 }
pmip6CounterDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for basic PMIPv6
statistics monitoring.
"
::= { pmip6Groups 3 }
pmip6MagSystemGroup OBJECT-GROUP pmip6StatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- pmip6MagProxyCOAType, pmip6MissingMnIdentifierOption,
-- pmip6MagProxyCOA pmip6MagNotAuthorizedForProxyReg,
pmip6MagProxyCOAState pmip6NotLMAForThisMobileNode,
} pmip6ProxyRegNotEnabled,
STATUS current pmip6MissingHomeNetworkPrefixOption,
DESCRIPTION pmip6MissingHandOffIndicatorOption,
" A collection of objects for monitoring the pmip6MissingAccessTechTypeOption,
PMIPv6 system related objects on a mobile router." pmip6NotAuthorizedForHomeNetworkPrefix,
::= { pmip6Groups 4 } pmip6TimestampMismatch,
pmip6TimestampLowerThanPrevAccepted,
pmip6BcePbuPrefixSetDoNotMatch,
pmip6InitialBindingRegistrations,
pmip6BindingLifeTimeExtensionNoHandOff,
pmip6BindingLifeTimeExtensionAfterHandOff,
pmip6BindingDeRegistrations,
pmip6BindingBindingAcks,
pmip6CounterDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for basic PMIPv6
statistics monitoring.
"
::= { pmip6Groups 3 }
pmip6MagConfigurationGroup OBJECT-GROUP pmip6MagSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
-- pmip6MagHomeNetworkPrefixType, pmip6MagStatus,
-- pmip6MagHomeNetworkPrefix, pmip6MagProxyCOAState
pmip6MagHomeNetworkPrefixLength, }
pmip6MagHomeNetworkPrefixLifeTime, STATUS current
pmip6MagEnableMagLocalRouting DESCRIPTION
} " A collection of objects for monitoring the
STATUS current PMIPv6-system-related objects on a mobile router."
DESCRIPTION ::= { pmip6Groups 4 }
" A collection of objects for monitoring the
configuration related objects on a mobile access
gateway.
"
::= { pmip6Groups 5 }
pmip6MagRegistrationGroup OBJECT-GROUP pmip6MagConfigurationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmip6MagBLFlag, pmip6MagHomeNetworkPrefixLength,
pmip6MagBLMnIdentifier, pmip6MagHomeNetworkPrefixLifeTime,
pmip6MagBLlMnIdentifier, pmip6MagEnableMagLocalRouting
pmip6MagBLMagLinkLocalAddressType, }
pmip6MagBLMagLinkLocalAddress, STATUS current
pmip6MagBLMagIfIdentifierToMn, DESCRIPTION
pmip6MagBLTunnelIfIdentifier, " A collection of objects for monitoring the
pmip6MagBLAccessTechnologyType, configuration-related objects on a mobile access
pmip6MagBLTimeRecentlyAccepted, gateway.
-- pmip6MagMnIndex, "
pmip6MagMnIdentifier, ::= { pmip6Groups 5 }
pmip6MagMnLocalMobilityAnchorAddressType, pmip6MagRegistrationGroup OBJECT-GROUP
pmip6MagMnLocalMobilityAnchorAddress OBJECTS {
} pmip6MagBLFlag,
STATUS current pmip6MagBLMnIndex,
DESCRIPTION pmip6MagBLMnLLIndex,
" A collection of objects for monitoring the pmip6MagBLMagLinkLocalAddressType,
registration related objects on a mobile access pmip6MagBLMagLinkLocalAddress,
gateway. pmip6MagBLMagIfIdentifierToMn,
" pmip6MagBLTunnelIfIdentifier,
::= { pmip6Groups 6 } pmip6MagBLMnInterfaceATT,
pmip6MagBLTimeRecentlyAccepted,
pmip6MagMnIdentifier,
pmip6MagMnLLIdentifier,
pmip6MagProfMnIdentifier,
pmip6MagProfMnLocalMobilityAnchorAddressType,
pmip6MagProfMnLocalMobilityAnchorAddress
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
registration-related objects on a mobile access
gateway.
"
::= { pmip6Groups 6 }
pmip6LmaSystemGroup OBJECT-GROUP pmip6LmaSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmip6LmaLMAAState pmip6LmaStatus,
} pmip6LmaLMAAState
STATUS current }
DESCRIPTION STATUS current
" A collection of objects for monitoring the DESCRIPTION
system related objects on an LMA." " A collection of objects for monitoring the
::= { pmip6Groups 7 } system-related objects on an LMA."
::= { pmip6Groups 7 }
pmip6LmaConfigurationGroup OBJECT-GROUP pmip6LmaConfigurationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmip6LmaMinDelayBeforeBCEDelete, pmip6LmaMinDelayBeforeBCEDelete,
pmip6LmaMaxDelayBeforeNewBCEAssign, pmip6LmaMaxDelayBeforeNewBCEAssign,
pmip6LmaTimestampValidityWindow, pmip6LmaTimestampValidityWindow,
pmip6LmaHomeNetworkPrefixLength, pmip6LmaHomeNetworkPrefixLength,
pmip6LmaHomeNetworkPrefixLifeTime pmip6LmaHomeNetworkPrefixLifeTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A collection of objects for Monitoring the " A collection of objects for Monitoring the
configuration related objects on an LMA." configuration-related objects on an LMA."
::= { pmip6Groups 8 } ::= { pmip6Groups 8 }
pmip6MagNotificationGroup NOTIFICATION-GROUP pmip6MagNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
pmip6MagHomeTunnelEstablished, pmip6MagHomeTunnelEstablished,
pmip6MagHomeTunnelReleased pmip6MagHomeTunnelReleased
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications from a home agent "A collection of notifications from a home agent
or correspondent node to the Manager about the or correspondent node to the Manager about the
tunnel status of the mobile router. tunnel status of the mobile router.
" "
::= { pmip6Groups 9 } ::= { pmip6Groups 9 }
pmip6LmaNotificationGroup NOTIFICATION-GROUP pmip6LmaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
pmip6LmaHomeTunnelEstablished, pmip6LmaHomeTunnelEstablished,
pmip6LmaHomeTunnelReleased pmip6LmaHomeTunnelReleased
}
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 10 }
-- Compliance statements }
pmip6CoreCompliance MODULE-COMPLIANCE STATUS current
STATUS current DESCRIPTION
DESCRIPTION "A collection of notifications from a home agent
"The compliance statement for SNMP entities or correspondent node to the Manager about the
which implement the PMIPV6-MIB. tunnel status of the mobile router.
There are a number of INDEX objects that cannot be "
represented in the form of OBJECT clauses in ::= { pmip6Groups 10 }
SMIv2, but for which there are compliance
requirements, expressed in OBJECT clause form in
this description:
-- OBJECT pmip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the pmip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup
}
::= { pmip6Compliances 1 }
pmip6Compliance2 MODULE-COMPLIANCE -- Compliance statements
STATUS current pmip6CoreCompliance MODULE-COMPLIANCE
DESCRIPTION STATUS current
"The compliance statement for SNMP entities DESCRIPTION
which implement the MOBILEIPV6-MIB. "The compliance statement for SNMP entities
There are a number of INDEX objects that cannot be that implement the PMIPV6-MIB.
represented in the form of OBJECT clauses in There are a number of INDEX objects that cannot be
SMIv2, but for which there are compliance represented in the form of OBJECT clauses in
requirements, expressed in OBJECT clause form in SMIv2, but for which there are compliance
this description: requirements, expressed in OBJECT clause form in
this description:
-- OBJECT pmip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the pmip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup
}
::= { pmip6Compliances 1 }
-- OBJECT mip6BindingHomeAddressType pmip6Compliance2 MODULE-COMPLIANCE
-- SYNTAX InetAddressType { ipv6(2) } STATUS current
-- DESCRIPTION DESCRIPTION
-- This MIB module requires support for global "The compliance statement for SNMP entities
-- IPv6 addresses for the mip6BindingHomeAddress that implement the PMIPV6-MIB.
-- object. "
-- MODULE -- this module
-- OBJECT mip6BindingHomeAddress MANDATORY-GROUPS { pmip6SystemGroup,
-- SYNTAX InetAddress (SIZE(16)) pmip6BindingCacheGroup,
-- DESCRIPTION pmip6StatsGroup
-- This MIB module requires support for global }
-- IPv6 addresses for the mip6BindingHomeAddress ::= { pmip6Compliances 2 }
-- object.
--
" pmip6CoreReadOnlyCompliance MODULE-COMPLIANCE
MODULE -- this module STATUS current
MANDATORY-GROUPS { pmip6SystemGroup, DESCRIPTION
pmip6BindingCacheGroup, "The compliance statement for SNMP entities
pmip6StatsGroup that implement the PMIPV6-MIB without support
} for read-write (i.e., in read-only mode).
::= { pmip6Compliances 2 } "
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup
}
OBJECT pmip6MobileNodeGeneratedTimestampInUse
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinksType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinks
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLayerAddressOnAllAccessLinks
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
pmip6CoreReadOnlyCompliance MODULE-COMPLIANCE ::= { pmip6Compliances 3 }
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
that implement the PMIPV6-MIB without support.
for read-write (i.e., in read-only mode).
"
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup
}
::= { pmip6Compliances 3 }
pmip6ReadOnlyCompliance2 MODULE-COMPLIANCE pmip6ReadOnlyCompliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities "The compliance statement for SNMP entities
that implement the PMIPV6-MIB without support. that implement the PMIPV6-MIB without support
for read-write (i.e., in read-only mode). for read-write (i.e., in read-only mode).
"
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup,
pmip6BindingCacheGroup,
pmip6StatsGroup
}
OBJECT pmip6MobileNodeGeneratedTimestampInUse
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinksType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLocalAddressOnAllAccessLinks
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6FixedMagLinkLayerAddressOnAllAccessLinks
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
There are a number of INDEX objects that cannot be ::= { pmip6Compliances 4 }
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 mip6BindingHomeAddressType pmip6MagCoreCompliance MODULE-COMPLIANCE
-- SYNTAX InetAddressType { ipv6(2) } STATUS current
-- DESCRIPTION DESCRIPTION
-- This MIB module requires support for global "The compliance statement for SNMP entities
-- IPv6 addresses for the mip6BindingHomeAddress that implement the PMIPV6-MIB.
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup,
pmip6BindingCacheGroup
}
::= { pmip6Compliances 4 }
pmip6MagCoreCompliance MODULE-COMPLIANCE There are a number of INDEX objects that cannot be
STATUS current represented in the form of OBJECT clauses in
DESCRIPTION SMIv2, but for which there are compliance
"The compliance statement for SNMP entities requirements, expressed in OBJECT clause form in
which implement the PMIPV6-MIB. this description:
There are a number of INDEX objects that cannot be -- OBJECT pmip6MagProxyCOAType
represented in the form of OBJECT clauses in -- SYNTAX InetAddressType { ipv6(2) }
SMIv2, but for which there are compliance -- DESCRIPTION
requirements, expressed in OBJECT clause form in -- This MIB module requires support for global
this description: -- IPv6 addresses for the pmip6MagProxyCOAType
-- OBJECT pmip6MagProxyCOAType -- object.
-- SYNTAX InetAddressType { ipv6(2) } --
-- DESCRIPTION -- OBJECT pmip6MagProxyCOA
-- This MIB module requires support for global -- SYNTAX InetAddress (SIZE(16))
-- IPv6 addresses for the pmip6MagProxyCOA -- DESCRIPTION
-- object. -- This MIB module requires support for global
-- -- IPv6 addresses for the pmip6MagProxyCOA
-- OBJECT pmip6MagProxyCOA -- object.
-- SYNTAX InetAddress (SIZE(16)) --
-- DESCRIPTION "
-- This MIB module requires support for global MODULE -- this module
-- IPv6 addresses for the pmip6MagProxyCOAType MANDATORY-GROUPS { pmip6MagSystemGroup
-- object. }
-- ::= { pmip6Compliances 5 }
-- OBJECT pmip6MagHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6MagSystemGroup
}
::= { pmip6Compliances 5 }
pmip6MagCompliance2 MODULE-COMPLIANCE pmip6MagCompliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities that "The compliance statement for SNMP entities that
implement the PMIPV6-MIB for monitoring configuration implement the PMIPV6-MIB for monitoring configuration-
related information, registration details, and related information, registration details, and
statistics on a mobile access gateway. statistics on a mobile access gateway.
There are a number of INDEX objects that cannot be There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in represented in the form of OBJECT clauses in
SMIv2, but for which there are compliance SMIv2, but for which there are compliance
requirements, expressed in OBJECT clause form in requirements, expressed in OBJECT clause form in
this description: this description:
-- OBJECT pmip6MagProxyCOAType -- OBJECT pmip6MagProxyCOAType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the pmip6MagProxyCOA -- IPv6 addresses for the pmip6MagProxyCOA
-- object. -- object.
-- --
-- OBJECT pmip6MagProxyCOA -- OBJECT pmip6MagProxyCOA
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the pmip6MagProxyCOAType -- IPv6 addresses for the pmip6MagProxyCOAType
-- object. -- object.
-- --
-- OBJECT pmip6MagHomeNetworkPrefixType -- OBJECT pmip6MagHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the -- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object. -- pmip6MagHomeNetworkPrefix object.
-- --
-- OBJECT pmip6MagHomeNetworkPrefix -- OBJECT pmip6MagHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the -- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object. -- pmip6MagHomeNetworkPrefix object.
-- --
"
MODULE -- this module
MANDATORY-GROUPS { pmip6MagSystemGroup,
pmip6MagConfigurationGroup,
pmip6MagRegistrationGroup
}
::= { pmip6Compliances 6 }
-- OBJECT mip6MnHomeAddressType pmip6MagCoreReadOnlyCompliance MODULE-COMPLIANCE
-- SYNTAX InetAddressType { ipv6(2) } STATUS current
-- DESCRIPTION DESCRIPTION
-- This MIB module requires support for global "The compliance statement for SNMP entities
-- IPv6 addresses for the mip6MnHomeAddress that implement the PMIPV6-MIB without support
-- object. for read-write (i.e., in read-only mode).
--
-- OBJECT mip6MnHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the mip6MnHomeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress
-- object.
"
MODULE -- this module
MANDATORY-GROUPS { pmip6MagSystemGroup,
pmip6MagConfigurationGroup,
pmip6MagRegistrationGroup
}
::= { pmip6Compliances 6 }
pmip6MagReadOnlyCompliance MODULE-COMPLIANCE There are a number of INDEX objects that cannot be
STATUS current represented in the form of OBJECT clauses in
DESCRIPTION SMIv2, but for which there are compliance
"The compliance statement for SNMP entities that requirements, expressed in OBJECT clause form in
implement the PMIPV6-MIB without support for read- this description:
write (i.e., in read-only mode) and with support -- OBJECT pmip6MagProxyCOAType
for monitoring configuration related information, -- SYNTAX InetAddressType { ipv6(2) }
registration details, and statistics on a mobile -- DESCRIPTION
access gateway. -- This MIB module requires support for global
-- IPv6 addresses for the pmip6MagProxyCOA
-- object.
--
-- OBJECT pmip6MagProxyCOA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6MagProxyCOAType
-- object.
--
-- OBJECT pmip6MagHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6MagSystemGroup
}
OBJECT pmip6MagStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { pmip6Compliances 7 }
There are a number of INDEX objects that cannot be pmip6MagReadOnlyCompliance2 MODULE-COMPLIANCE
represented in the form of OBJECT clauses in STATUS current
SMIv2, but for which there are compliance DESCRIPTION
requirements, expressed in OBJECT clause form in "The compliance statement for SNMP entities that
this description: implement the PMIPV6-MIB without support for read-
write (i.e., in read-only mode) and with support
for monitoring configuration-related information,
registration details, and statistics on a mobile
access gateway.
-- OBJECT pmip6MagProxyCOAType There are a number of INDEX objects that cannot be
-- SYNTAX InetAddressType { ipv6(2) } represented in the form of OBJECT clauses in
-- DESCRIPTION SMIv2, but for which there are compliance
-- This MIB module requires support for global requirements, expressed in OBJECT clause form in
-- IPv6 addresses for the pmip6MagProxyCOA this description:
-- object.
--
-- OBJECT pmip6MagProxyCOA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6MagProxyCOAType
-- object.
--
-- OBJECT pmip6MagHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object.
--
-- OBJECT pmip6MagHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6MagHomeNetworkPrefix object.
--
-- OBJECT mip6MnHomeAddressType -- OBJECT pmip6MagProxyCOAType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnHomeAddress -- IPv6 addresses for the pmip6MagProxyCOA
-- object. -- object.
-- --
-- OBJECT mip6MnHomeAddress -- OBJECT pmip6MagProxyCOA
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnHomeAddress -- IPv6 addresses for the pmip6MagProxyCOAType
-- object. -- object.
-- --
-- OBJECT mip6MnBLNodeAddressType -- OBJECT pmip6MagHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress -- IPv6 addresses for the
-- object. -- pmip6MagHomeNetworkPrefix object.
-- --
-- OBJECT mip6MnBLNodeAddress -- OBJECT pmip6MagHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress -- IPv6 addresses for the
-- object. -- pmip6MagHomeNetworkPrefix object.
" --
MODULE -- this module "
MANDATORY-GROUPS { pmip6MagSystemGroup, MODULE -- this module
pmip6MagConfigurationGroup, MANDATORY-GROUPS { pmip6MagSystemGroup,
pmip6MagRegistrationGroup pmip6MagConfigurationGroup,
} pmip6MagRegistrationGroup
::= { pmip6Compliances 7 } }
OBJECT pmip6MagStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6MagEnableMagLocalRouting
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
pmip6LmaCoreCompliance MODULE-COMPLIANCE ::= { pmip6Compliances 8 }
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the PMIPV6-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 pmip6LmaLMAAType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6LmaSystemGroup
}
::= { pmip6Compliances 8 }
pmip6LmaCompliance2 MODULE-COMPLIANCE pmip6LmaCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities that "The compliance statement for SNMP entities
implement the PMIPV6-MIB for monitoring configuration that implement the PMIPV6-MIB.
related information, registration details, and There are a number of INDEX objects that cannot be
statistics on a mobile access gateway. 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 pmip6LmaLMAAType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6LmaSystemGroup
}
::= { pmip6Compliances 9 }
There are a number of INDEX objects that cannot be pmip6LmaCompliance2 MODULE-COMPLIANCE
represented in the form of OBJECT clauses in STATUS current
SMIv2, but for which there are compliance DESCRIPTION
requirements, expressed in OBJECT clause form in "The compliance statement for SNMP entities that
this description: implement the PMIPV6-MIB for monitoring configuration-
related information, registration details, and
statistics on a mobile access gateway.
-- OBJECT pmip6LmaLMAAType There are a number of INDEX objects that cannot be
-- SYNTAX InetAddressType { ipv6(2) } represented in the form of OBJECT clauses in
-- DESCRIPTION SMIv2, but for which there are compliance
-- This MIB module requires support for global requirements, expressed in OBJECT clause form in
-- IPv6 addresses for the pmip6LmaLMAA this description:
-- object.
--
-- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6LmaHomeNetworkPrefix object.
--
-- OBJECT pmip6LmaHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6LmaHomeNetworkPrefix object.
--
-- OBJECT mip6MnHomeAddressType -- OBJECT pmip6LmaLMAAType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnHomeAddress -- IPv6 addresses for the pmip6LmaLMAA
-- object. -- object.
-- --
-- OBJECT mip6MnHomeAddress -- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnHomeAddress -- IPv6 addresses for the pmip6LmaLMAA
-- object. -- object.
-- --
-- OBJECT mip6MnBLNodeAddressType -- OBJECT pmip6LmaHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) } -- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress -- IPv6 addresses for the
-- object. -- pmip6LmaHomeNetworkPrefix object.
-- --
-- OBJECT mip6MnBLNodeAddress -- OBJECT pmip6LmaHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16)) -- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION -- DESCRIPTION
-- This MIB module requires support for global -- This MIB module requires support for global
-- IPv6 addresses for the mip6MnBLNodeAddress -- IPv6 addresses for the
-- object. -- pmip6LmaHomeNetworkPrefix object.
" --
MODULE -- this module "
MANDATORY-GROUPS { pmip6LmaSystemGroup, MODULE -- this module
pmip6LmaConfigurationGroup MANDATORY-GROUPS { pmip6LmaSystemGroup,
} pmip6LmaConfigurationGroup
::= { pmip6Compliances 9 } }
::= { pmip6Compliances 10 }
pmip6MagNotificationCompliance MODULE-COMPLIANCE pmip6LmaReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities that "The compliance statement for SNMP entities
implement the PMIPV6-MIB and support Notification that implement the PMIPV6-MIB.
from the mobile access gateway. There are a number of INDEX objects that cannot be
" represented in the form of OBJECT clauses in
MODULE -- this module SMIv2, but for which there are compliance
MANDATORY-GROUPS { pmip6MagNotificationGroup requirements, expressed in OBJECT clause form in
} this description:
::= { pmip6Compliances 10 } -- OBJECT pmip6LmaLMAAType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6LmaSystemGroup
}
OBJECT pmip6LmaStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { pmip6Compliances 11 }
pmip6LmaNotificationCompliance MODULE-COMPLIANCE pmip6LmaReadOnlyCompliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities that "The compliance statement for SNMP entities that
implement the PMIPV6-MIB and support Notification implement the PMIPV6-MIB without support
from the LMA. for read-write (i.e., in read-only mode) and for
" monitoring configuration-related information,
MODULE -- this module registration details, and statistics on a mobile
MANDATORY-GROUPS { pmip6LmaNotificationGroup access gateway.
}
::= { pmip6Compliances 11 }
END 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 pmip6LmaLMAAType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaLMAA
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the pmip6LmaLMAA
-- object.
--
-- OBJECT pmip6LmaHomeNetworkPrefixType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6LmaHomeNetworkPrefix object.
--
-- OBJECT pmip6LmaHomeNetworkPrefix
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- IPv6 addresses for the
-- pmip6LmaHomeNetworkPrefix object.
--
"
MODULE -- this module
MANDATORY-GROUPS { pmip6LmaSystemGroup,
pmip6LmaConfigurationGroup
}
OBJECT pmip6LmaStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6LmaMinDelayBeforeBCEDelete
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6LmaMaxDelayBeforeNewBCEAssign
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6LmaTimestampValidityWindow
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT pmip6LmaHomeNetworkPrefixLifeTime
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { pmip6Compliances 12 }
pmip6MagNotificationCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
implement the PMIPV6-MIB and support notification
from the mobile access gateway.
"
MODULE -- this module
MANDATORY-GROUPS { pmip6MagNotificationGroup
}
::= { pmip6Compliances 13 }
pmip6LmaNotificationCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
implement the PMIPV6-MIB and support notification
from the LMA.
"
MODULE -- this module
MANDATORY-GROUPS { pmip6LmaNotificationGroup
}
::={ pmip6Compliances 14 }
END
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. Such objects may be with a MAX-ACCESS clause of read-write. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. These protection can have a negative effect on network operations. These
are the tables and objects and the corresponding are the tables and objects and the corresponding
sensitivity/vulnerability: sensitivity/vulnerability:
pmip6Status: The value of this object is used to enable or disable
the PMIPv6 functionality on a PMIPv6 entity. Access to this MO The value of the following objects is used to enable or disable
may be abused to disrupt the communication that depends on the PMIPv6 functionality on the corresponding PMIPv6 entity.
PMIPv6. Access to these MOs may be abused to disrupt the communication
pmip6MobileNodeGeneratedTimestampInUse : that depends on the PMIPv6 functionality.
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType: pmip6MagStatus
pmip6FixedMagLinkLocalAddressOnAllAccessLinks: pmip6LmaStatus
pmip6FixedMagLinkLayerAddressOnAllAccessLinks:
pmip6MagEnableMagLocalRouting: Access to the following MOs may be abused to misconfigure PMIPv6
pmip6MagHomeNetworkPrefixLifeTime: entities and disrupt communications.
pmip6LmaMinDelayBeforeBCEDelete: pmip6MobileNodeGeneratedTimestampInUse
pmip6LmaMaxDelayBeforeNewBCEAssign: pmip6FixedMagLinkLocalAddressOnAllAccessLinksType
pmip6LmaTimestampValidityWindow: pmip6FixedMagLinkLocalAddressOnAllAccessLinks
pmip6LmaHomeNetworkPrefixLifeTime: pmip6FixedMagLinkLayerAddressOnAllAccessLinks
Access to the above MOs may be abused to misconfigure PMIPv6 pmip6MagEnableMagLocalRouting
entities and disrupt communications. pmip6MagHomeNetworkPrefixLifeTime
pmip6LmaMinDelayBeforeBCEDelete
pmip6LmaMaxDelayBeforeNewBCEAssign
pmip6LmaTimestampValidityWindow
pmip6LmaHomeNetworkPrefixLifeTime
Some of the readable objects in this MIB module (i.e., objects with a 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 MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
pmip6LmaHomeNetworkPrefixType: The following address-related objects may be considered to be
pmip6LmaHomeNetworkPrefix: particularly sensitive and/or private.
pmip6LmaHomeNetworkPrefixLength:
The above address-related objects may be considered to be pmip6LmaHomeNetworkPrefixType
particularly sensitive and/or private. pmip6LmaHomeNetworkPrefix
pmip6LmaHomeNetworkPrefixLength
The following MN Identifier-related MOs may be used to identify
users. These may be considered to be sensitive and/or private.
pmip6MagMnIdentifier
pmip6MagMnLLIdentifier
pmip6LmaMnIdentifier
pmip6LmaMnLLIdentifier
pmip6MagProfMnIdentifier
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Implementations MUST provide the security features described by the
SNMPv3 framework (see [RFC3410]), including full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
IANA should assign a base arc in the 'mib-2' (standards track) OID IANA has assigned the following:
tree for the 'pmip6MIB' MODULE-IDENTITY defined in the PMIPV6-MIB.
1. a base arc in the 'mib-2' (Standards Track) OID tree for the
'pmip6TCMIB' MODULE-IDENTITY defined in the PMIPV6-TC-MIB.
2. a base arc in the 'mib-2' (Standards Track) OID tree for the
'pmip6MIB' MODULE-IDENTITY defined in the PMIPV6-MIB.
8. References 8. References
8.1 Normative References 8.1. Normative References
[RFC2119] Bradner, S., Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels, BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, Structure of "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2), STD 58, STD 58, RFC 2578, April 1999.
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, Textual Conventions "Textual Conventions for SMIv2", STD 58, RFC 2579, April
for SMIv2, STD 58, RFC 2579, April 1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, Conformance "Conformance Statements for SMIv2", STD 58, RFC 2580,
Statements for SMIv2, STD 58, RFC 2580, April 1999. April 1999.
[RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Support in IPv6 RFC 3775, June 2004. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
K., and Patil, B., Proxy Mobile IPv6), RFC 5213, Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
August 2008. (MIPv6)", RFC 4283, November 2005.
[RFC4293] Routhier, S., Management Information Base for the [RFC4293] Routhier, S., Ed., "Management Information Base for the
Internet Protocol (IP), RFC 4293, April 2006. Internet Protocol (IP)", RFC 4293, April 2006.
[RFC4001] Daniele, M., Haberman, B., Routhier, S. and [RFC4295] Keeni, G., Koide, K., Nagami, K., and S. Gundavelli,
Schoenwaelder, J., Textual Conventions for Internet "Mobile IPv6 Management Information Base", RFC 4295, April
Network Addresses, RFC 4001, February 2005. 2006.
[RFC2863] McCloghrie, K., and Kastenholz., F., The Interfaces [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Group MIB, RFC 2863, June 2000. Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC
5213, August 2008.
[RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
Mobile IPv6 MIB, RFC 4295, April 2006. Support in IPv6", RFC 6275, July 2011.
[RFC4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, The 8.2. Informative References
Network Access Identifier, RFC 4282, December 2005.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Chowdhury, Mobile Node Identifier Option for Mobile "Introduction and Applicability Statements for Internet-
IPv6 (MIPv6), RFC 4283, November 2005. Standard Management Framework", RFC 3410, December 2002.
8.2 Informative References [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Introduction and Applicability Statements for Advanced Encryption Standard (AES) Cipher Algorithm in the
Internet-Standard Management Framework, RFC 3410, SNMP User-based Security Model", RFC 3826, June 2004.
December 2002.
[RFC4831] Kempf, J., Goals for Network-Based Localized Mobility [RFC4831] Kempf, J., Ed., "Goals for Network-Based Localized
Management (NETLMM), RFC 4831, April 2007. Mobility Management (NETLMM)", RFC 4831, April 2007.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", RFC
5591, June 2009.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
RFC 6353, July 2011.
9. Acknowledgements 9. Acknowledgements
The following groups and individuals have contributed to this draft The following individuals and groups have contributed to this
with discussions and comments: document with discussions and comments:
WIDE Project netman-WG
Dirk von-Hugo
10. Authors' Addresses Adrian Farrel
Dan Romascanu
David Harrington
Dirk von-Hugo
Francis Dupont
Harrie Hazewinkel
Jari Arkko
Sean Turner
Stephen Farrell
Vincent Roca
WIDE Project netman-WG
Authors' Addresses
Glenn Mansfield Keeni Glenn Mansfield Keeni
Cyber Solutions Inc. Cyber Solutions, Inc.
6-6-3 Minami Yoshinari 6-6-3 Minami Yoshinari
Aoba-ku, Sendai 989-3204 Aoba-ku, Sendai 989-3204
Japan Japan
Phone: +81-22-303-4012 Phone: +81-22-303-4012
E-mail: glenn@cysols.com EMail: glenn@cysols.com
Kazuhide Koide Kazuhide Koide
KDDI Corporation KDDI Corporation
GARDEN AIR TOWER 3-10-10, Iidabashi GARDEN AIR TOWER 3-10-10, Iidabashi
Chiyoda-ku, Tokyo, 102-8460 Japan Chiyoda-ku, Tokyo, 102-8460
Japan
Phone: +81-3-6678-3378 Phone: +81-3-6678-3378
E-mail: ka-koide@kddi.com EMail: ka-koide@kddi.com
Sri Gundavelli Sri Gundavelli
Cisco Systems Cisco Systems
170 W.Tasman Drive, 170 W.Tasman Drive,
San Jose, CA 95134 San Jose, CA 95134
USA USA
Phone: +1-408-527-6109 Phone: +1-408-527-6109
E-mail: sgundave@cisco.com EMail: sgundave@cisco.com
Ryuji Wakikawa Ryuji Wakikawa
TOYOTA InfoTechnology Center, U.S.A., Inc. TOYOTA InfoTechnology Center, U.S.A., Inc.
465 Bernardo Avenue 465 Bernardo Avenue
Mountain View, CA Mountain View, CA 94043
94043
USA USA
E-mail: ryuji@us.toyota-itc.com EMail: ryuji@us.toyota-itc.com
Appendix. History of Changes
Changes since draft-ietf-netlmm-pmipv6-mib-00.txt
a. Fixed editorial nits, missing references
Changes since draft-ietf-netlmm-pmipv6-mib-00.txt
a. Added appendix for change history
b. Changed MAX-ACCESS of pmip6MagHomeNetworkPrefixLifeTime
read-write -> read-only
Changes since draft-ietf-netlmm-pmipv6-mib-02.txt
a. Fixed editorial nits.
b. Added DISPLAY-HINT, fixed DESCRIPTION and REFERENCE of
Pmip6MNLlIdentifier ::= TEXTUAL-CONVENTION
c. Fixed DESCRIPTION of
Pmip6MNIndex ::= TEXTUAL-CONVENTION
d. Fixed DESCRIPTION of
Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION
e. Fixed DESCRIPTION of
pmip6MagProxyCOAState OBJECT-TYPE
pmip6MagHomeNetworkPrefixTable OBJECT-TYPE
pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE
pmip6BindingPBUFlag OBJECT-TYPE
pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE
pmip6LmaHomeNetworkPrefixTable OBJECT-TYPE
pmip6CoreCompliance MODULE-COMPLIANCE
 End of changes. 297 change blocks. 
1586 lines changed or deleted 1987 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/