draft-ietf-netlmm-pmipv6-mib-02.txt   draft-ietf-netlmm-pmipv6-mib-03.txt 
NETLMM Working Group Glenn M. Keeni NETLMM Working Group Glenn M. Keeni
INTERNET-DRAFT Cyber Solutions Inc. INTERNET-DRAFT Cyber Solutions Inc.
Intended Status: Proposed Standard Koide Kazuhide Intended Status: Proposed Standard K. Koide
Expires: July 7, 2010 KDDI Corporation Expires: February 19, 2011 KDDI Corporation
S. Gundavelli S. Gundavelli
Cisco Cisco
R. Wakikawa R. Wakikawa
Toyota ITC Toyota ITC
January 22, 2010 August 20, 2010
Proxy Mobile IPv6 Management Information Base Proxy Mobile IPv6 Management Information Base
<draft-ietf-netlmm-pmipv6-mib-02.txt> <draft-ietf-netlmm-pmipv6-mib-03.txt>
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 9 skipping to change at page 1, line 41
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document is a product of the NETLMM Working Group. Comments This document is a product of the NETLMM Working Group. Comments
should be addressed to the authors or the mailing list at should be addressed to the authors or the mailing list at
netlmm@ietf.org netlmm@ietf.org
This Internet-Draft will expire on July 21, 2010. This Internet-Draft will expire on February 19, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 32 skipping to change at page 2, line 26
document must include Simplified BSD License text as described document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB), This memo defines a portion of the Management Information Base (MIB),
the Proxy Mobile-IPv6 MIB, for use with network management protocols the Proxy Mobile-IPv6 MIB, for use with network management protocols
in the Internet community. In particular, the Proxy Mobile-IPv6 MIB in the Internet community. In particular, the Proxy Mobile-IPv6 MIB
will be used to monitor and control the mobile access gateway (MAG) will be used to monitor and control the mobile access gateway (MAG)
node and the local mobility anchor (LMA) functions of a Proxy Mobile and the local mobility anchor (LMA) functions of a Proxy Mobile
IPv6 (PMIPv6) entity. 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 .................................... 6 5. The Proxy Mobile-IPv6 MIB .................................... 7
6. Security Considerations ...................................... 57 6. Security Considerations ...................................... 58
7. IANA Considerations .......................................... 58 7. IANA Considerations .......................................... 59
8. References ................................................... 59 8. References ................................................... 60
8.1. Normative References .................................... 59 8.1. Normative References .................................... 60
8.2. Informative References .................................. 59 8.2. Informative References .................................. 61
9. Acknowledgements ............................................. 62
9. Acknowledgements ............................................. 60 10. Author's Addresses ........................................... 62
10. Author's Addresses ........................................... 60
Appendix: History of Changes Appendix: History of Changes
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
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 and 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 which 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 the term mobile node
is used to refer to an IP host or router whose mobility is is used to refer 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
skipping to change at page 5, line 23 skipping to change at page 4, line 23
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 following: the following:
o capabilities of PMIPv6 entities o capabilities of PMIPv6 entities
o traffic due to PMIPv6 signalling o traffic due to PMIPv6 signaling
o binding related details (at LMA and MAG) o binding related details (at LMA and MAG)
o binding related statistics (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 It is assumed that the Proxy Mobile IPv6 Management Information Base
(PMIPV6-MIB) will always be implemented in conjunction with the (PMIPV6-MIB) will always be implemented in conjunction with the
MOBILEIPV6-MIB [RFC4295] and the ifTable from the IF-MIB [RFC2863]. MOBILEIPV6-MIB [RFC4295] and the ifTable from the IF-MIB [RFC2863].
The PMIP6-MIB uses the textual conventions defined in the INET- The PMIPV6-MIB uses the textual conventions defined in the INET-
ADDRESS-MIB [RFC4001]. ADDRESS-MIB [RFC4001].
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 all the Proxy Mobile IPv6 entities. common to all the Proxy Mobile IPv6 entities. Objects
belonging to this group will be implemented on the
corresponding Proxy Mobile IPv6 entity. pmip6BindingCacheTable
belongs to this group.
- pmip6Mag: this group models the mobile access gateway - pmip6Mag: this group models the mobile access gateway
service. 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 - pmip6Lma: this group models the local mobility anchor
service. 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 - pmip6Notifications: defines the set of notifications that
will be used to asynchronously monitor the Proxy Mobile will be used to asynchronously monitor the Proxy Mobile
IPv6 entities. IPv6 entities.
The tables contained in the above groups are as follows: The tables contained in the above groups are as follows:
- pmip6BindingCacheTable : models the Binding Cache - pmip6BindingCacheTable : models the Binding Cache
on the local mobility on the local mobility
anchor. anchor.
- pmip6MagProxyCOATable : models the Proxy Care-of - pmip6MagProxyCOATable : models the Proxy Care-of
Addresses configured on the Addresses configured on the
egress interfaces of the egress interfaces of the
mobile access gateway. mobile access gateway.
- pmip6MagHomeNetworkPrefixTable : contains the Home Network - pmip6MagHomeNetworkPrefixTable : contains the Home Network
Prefixes assigned to the Prefixes assigned to
mobile node's connected interfaces of all mobile
interfaces. 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 - pmip6MagBLTable : models the Binding Update List
(BL) that includes Proxy MIPv6 (BL) that includes Proxy MIPv6
related information and is related information and is
maintained by the mobile maintained by the mobile
access gateway. access gateway.
- pmip6MagMnProfileTable : contains the mobile node's - pmip6MagMnProfileTable : contains the mobile node's
policy profile that includes policy profile that includes
the essential operational the essential operational
parameters that are required parameters that are required
by the network entities for by the network entities for
skipping to change at page 6, line 40 skipping to change at page 6, line 7
- pmip6LmaLMAATable : contains the LMA Addresses - pmip6LmaLMAATable : contains the LMA Addresses
that are configured on the that are configured on the
local mobility anchor. Each local mobility anchor. Each
LMA Address acts as a LMA Address acts as a
transport endpoint of the transport endpoint of the
tunnel between the local tunnel between the local
mobility anchor and the mobile mobility anchor and the mobile
access gateway. access gateway.
- pmip6LmaHomeNetworkPrefixTable : contains the list of Home - pmip6LmaHomeNetworkPrefixTable : contains the list of Home
Network Prefixes assigned to Network Prefixes assigned to
the mobile node's connected the connected interfaces of
interfaces. the mobiles nodes anchored on
an LMA.
5. The Proxy Mobile-IPv6 MIB. 5. The Proxy Mobile-IPv6 MIB
PMIPV6-MIB DEFINITIONS ::= BEGIN PMIPV6-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32, MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32,
OBJECT-TYPE, NOTIFICATION-TYPE OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
PhysAddress PhysAddress
FROM RFC1213-MIB FROM RFC1213-MIB
TEXTUAL-CONVENTION, TimeStamp, TEXTUAL-CONVENTION, TimeStamp,
TruthValue, DateAndTime TruthValue, DateAndTime
skipping to change at page 7, line 28 skipping to change at page 7, line 28
FROM SNMPv2-CONF FROM SNMPv2-CONF
InetAddressType, InetAddress, InetAddressPrefixLength InetAddressType, InetAddress, InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
Ipv6AddressIfIdentifierTC Ipv6AddressIfIdentifierTC
FROM IP-MIB FROM IP-MIB
mip6MnBLEntry, mip6BindingCacheEntry mip6MnBLEntry, mip6BindingCacheEntry
FROM MOBILEIPV6-MIB FROM MOBILEIPV6-MIB
; ;
pmip6MIB MODULE-IDENTITY pmip6MIB MODULE-IDENTITY
LAST-UPDATED "200907070000Z" -- 7th July, 2009 LAST-UPDATED "201008160000Z" -- 16th August, 2010
ORGANIZATION "IETF NETLMM Working Group" ORGANIZATION "IETF NETLMM Working Group"
CONTACT-INFO CONTACT-INFO
" Glenn Mansfield Keeni " Glenn Mansfield Keeni
Postal: Cyber Solutions Inc. Postal: Cyber Solutions Inc.
6-6-3, Minami Yoshinari 6-6-3, Minami Yoshinari
Aoba-ku, Sendai, Japan 989-3204. Aoba-ku, Sendai, Japan 989-3204.
Tel: +81-22-303-4012 Tel: +81-22-303-4012
Fax: +81-22-303-4015 Fax: +81-22-303-4015
E-mail: glenn@cysols.com E-mail: glenn@cysols.com
skipping to change at page 8, line 35 skipping to change at page 8, line 35
" "
-- Authors' note: -- Authors' note:
-- It is not clear if the Copyright notice should be a part -- It is not clear if the Copyright notice should be a part
-- of above description. It was a requirement sometime ago -- of above description. It was a requirement sometime ago
-- but the submission tool at ietf.org complained so it is -- but the submission tool at ietf.org complained so it is
-- removed for now. -- removed for now.
-- RFC Ed.: replace XXXX with actual RFC number and remove this -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note -- note
REVISION "200907070000Z" -- 7th July 2009 REVISION "201008160000Z" -- 16th August 2010
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this -- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note -- note
::= { mib-2 YYY } -- will be assigned by IANA ::= { mib-2 YYY } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers -- subtree and record the assignment in the SMI Numbers
-- registry. -- registry.
-- --
-- RFC Ed.: When the above assignment has been made, please -- RFC Ed.: When the above assignment has been made, please
-- remove the above note -- remove the above note
-- replace "YYY" here with the assigned value and -- replace "YYY" here with the assigned value and
-- remove this note. -- remove this note.
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
Pmip6MNIdentifier ::= TEXTUAL-CONVENTION Pmip6MNIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
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. This is the stable identifier of a mobile node domain. This is the stable identifier of a mobile node
that the mobility entities in a Proxy Mobile IPv6 domain that the mobility entities in a Proxy Mobile IPv6 domain
can always acquire and use it for predictably identifying can always acquire and use for predictably identifying
a mobile node. This is typically an identifier such as a mobile node. Various forms of identifiers can be used to
Network Access Identifier (NAI) [RFC4282] or other identify a mobile node (MN). Two examples are a Network
identifier such as a Media Access Control (MAC) address. Access Identifier (NAI) [RFC4282] and an opaque identifier
applicable to a particular application.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2" "RFC 4283: Section 3"
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
Pmip6MNLlIdentifier ::= TEXTUAL-CONVENTION Pmip6MNLlIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier that identifies the attached interface of a "An identifier that identifies the attached interface of a
mobile node. For those interfaces that have a link-layer mobile node. For those interfaces that have a link-layer
identifier, this identifier can be based on that. The identifier, this identifier can be based on that. The
link-layer identifier in some cases is generated by the link-layer identifier, in some cases, is generated by the
mobile node and conveyed to the mobile access gateway. This mobile node and conveyed to the mobile access gateway. This
identifier of the attached interface must be stable as seen identifier of the attached interface must be stable as seen
by any of the mobile access gateways in a given Proxy Mobile by any of the mobile access gateways in a given Proxy Mobile
IPv6 domain. In some other cases, there might not be any IPv6 domain. In some other cases, there might not be any
link-layer identifier associated with the mobile node's link-layer identifier associated with the mobile node's
interface. An identifier value of ALL_ZERO is not considered interface. An identifier value of ALL_ZERO is not considered
a valid identifier and cannot be used as an interface a valid identifier and cannot be used as an interface
identifier. identifier.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2.2" "RFC 5213: Section 8.6"
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
Pmip6MNIndex ::= TEXTUAL-CONVENTION Pmip6MNIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique integer value, greater than zero, assigned to each "A unique integer value, greater than zero, assigned to each
mobile node in a PMIPv6-Domain by the management system. mobile node that is currently attached to the PMIPv6-Domain
It is recommended that values are assigned contiguously by the management system.
It is recommended that the values are assigned contiguously
starting from 1. The value for each mobile node must remain starting from 1. The value for each mobile node must remain
constant at least from one re-initialization of the entity's constant at least from one re-initialization of the entity's
network management system to the next re-initialization. network management system to the next re-initialization.
" "
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This specifies the access technology which connects the "This specifies the access technology which connects the
mobile node to the access link on the mobile access gateway. mobile node to the access link on the mobile access gateway.
" "
REFERENCE REFERENCE
skipping to change at page 11, line 15 skipping to change at page 11, line 19
" "
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION Pmip6PBUAccessTechnologyType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This specifies the access technology which connects the "This specifies the access technology which connects the
mobile node to the access link on the mobile access gateway. mobile node to the access link on the mobile access gateway.
" "
REFERENCE REFERENCE
"RFC 5213: Section 8.5" "RFC 5213: Section 8.5,
http://www.iana.org/assignments/mobility-parameters/
mobility-parameters.txt"
SYNTAX INTEGER SYNTAX INTEGER
{ {
reserved (0), reserved (0),
logicalNetworkInterface(1), logicalNetworkInterface(1),
pointToPointInterface (2), pointToPointInterface (2),
ethernet (3), ethernet (3),
wirelessLan (4), wirelessLan (4),
wimax (5) 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 -- The PMIPv6 MIB has the following 5 primary groups
pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 } pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 }
pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 } pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 }
pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 } pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 }
pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 } pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 }
pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 } pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 }
pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 } pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 }
skipping to change at page 12, line 4 skipping to change at page 12, line 16
pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 } pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 }
pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 } pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 }
pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 } pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 }
pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 } pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 }
pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 } pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 }
pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 } pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 }
pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 } pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 }
pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 } pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 }
-- The pmip6Configuration group has the following sub groups
-- The pmip6Stats group has the following sub groups -- The pmip6Stats group has the following sub groups
pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 } pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 }
-- --
-- --
-- pmip6System group -- pmip6System group
-- --
-- --
skipping to change at page 14, line 25 skipping to change at page 14, line 26
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 to ALL_ZERO value, it
implies the use of fixed link-local address mode is implies that the use of fixed link-local address mode
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: Section 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
skipping to change at page 17, line 6 skipping to change at page 17, line 6
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
tunnel a tunnel. This state SHOULD be
indicated when the MAG is up but has
no mobile node.
tunneled -- The Proxy-CoA is used to set up the tunneled -- The Proxy-CoA is used to set up the
bi-directional tunnel. bi-directional tunnel.
" "
::= { 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
skipping to change at page 17, line 41 skipping to change at page 17, line 43
REFERENCE REFERENCE
"RFC 5213: Section 9.2" "RFC 5213: Section 9.2"
::= { pmip6MagConf 1 } ::= { pmip6MagConf 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 mobile node's connected interfaces. assigned to the connected interfaces of mobile nodes
This table shows the prefixes registered in the attached to the MAG.
binding update list entry.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2, 6.1, 6.2" "RFC 5213: Section 2, 6.1, 6.2"
::= { pmip6MagConf 2 } ::= { 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
skipping to change at page 19, line 29 skipping to change at page 19, line 32
"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 Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lifetime (in seconds) granted to the mobile "The lifetime parameter (in seconds) that will be
node for this registration. advertised in Router Advertisements by the MAG for
this Home Network Prefix.
" "
REFERENCE REFERENCE
"RFC 5213: Section 6.2, 6.7" "RFC 5213: Section 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
skipping to change at page 26, line 38 skipping to change at page 26, line 44
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) if the local mobility anchor accepted the
binding update with Proxy Registration Flag from a binding update with Proxy Registration Flag from a
mobile access gateway. 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. mobile node. In this case the remaining objects will
not be accessible.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.1, 8.1" "RFC 5213: Section 5.1, 8.1"
::= { pmip6BindingCacheEntry 1 } ::= { pmip6BindingCacheEntry 1 }
pmip6BindingMnIdentifier OBJECT-TYPE pmip6BindingMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MNIdentifier SYNTAX Pmip6MNIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 29, line 31 skipping to change at page 29, line 40
-- --
-- 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 message "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 and at other times as indicated by the value of
pmip6CounterDiscontinuityTime. pmip6CounterDiscontinuityTime.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.3.1, 8.9" "RFC 5213: Section 5.3.1, 8.9"
::= { pmip6BindingRegCounters 1 } ::= { pmip6BindingRegCounters 1 }
pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 38, line 34 skipping to change at page 38, line 40
tunneled -- The LMAA is used to set up the tunneled -- The LMAA is used to set up the
bi-directional tunnel. bi-directional tunnel.
" "
::= { pmip6LmaLMAAEntry 3 } ::= { pmip6LmaLMAAEntry 3 }
pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE pmip6LmaMinDelayBeforeBCEDelete OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the amount 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 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 a mobile node's Binding Cache entry essentially ensures that a mobile node's Binding Cache
is not deleted too quickly and allows some time for the entry is not deleted too quickly and allows some time
new mobile access gateway to complete the signaling for for the new mobile access gateway to complete the
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: Section 5.3.5, 9.1"
::= { pmip6LmaConf 1 } ::= { pmip6LmaConf 1 }
pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE pmip6LmaMaxDelayBeforeNewBCEAssign OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the amount 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 retransmissions
need to happen before MaxDelayBeforeNewBCEAssign runs need to happen before MaxDelayBeforeNewBCEAssign runs
out, as otherwise there are situations where a out, as otherwise there are situations where a
de-registration from a previous mobile access gateway de-registration from a previous mobile access gateway
may be lost, and the local mobility anchor creates may be lost, and the local mobility anchor creates,
needlessly a new mobility session and new prefixes for needlessly, a new mobility session and new prefixes for
the mobile node. This affects situations where there the mobile node. However, this affects situations where
is no information from the lower layers about the type there is no information from the lower layers about the
of a handoff or other parameters that can be used for type of a handoff or other parameters that can be used
identifying the mobility session, however. for identifying the mobility session.
" "
REFERENCE REFERENCE
"RFC 5213: Section 5.4.1.2, 5.4.1.3, 9.1" "RFC 5213: Section 5.4.1.2, 5.4.1.3, 9.1"
::= { pmip6LmaConf 2 } ::= { pmip6LmaConf 2 }
pmip6LmaTimestampValidityWindow OBJECT-TYPE pmip6LmaTimestampValidityWindow OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable specifies the maximum amount 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: Section 5.5, 9.1"
::= { pmip6LmaConf 3 } ::= { pmip6LmaConf 3 }
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 mobile node's connected interfaces. assigned to the connected interfaces of all the
This table shows the prefixes registered in the mobile nodes anchored at the LMA.
binding cache entry.
" "
REFERENCE REFERENCE
"RFC 5213: Section 2, 5.1, 5.2" "RFC 5213: Section 2, 5.1, 5.2"
::= { pmip6LmaConf 4 } ::= { pmip6LmaConf 4 }
pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE pmip6LmaHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX PMip6LmaHomeNetworkPrefixEntry SYNTAX PMip6LmaHomeNetworkPrefixEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 46, line 39 skipping to change at page 46, line 45
" "
::= { pmip6Groups 6 } ::= { pmip6Groups 6 }
pmip6LmaSystemGroup OBJECT-GROUP pmip6LmaSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pmip6LmaLMAAState pmip6LmaLMAAState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A collection of objects for monitoring the " A collection of objects for monitoring the
system related objects on a LMA." system related objects on an LMA."
::= { pmip6Groups 7 } ::= { 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 a 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
skipping to change at page 47, line 41 skipping to change at page 48, line 5
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 10 } ::= { pmip6Groups 10 }
-- Compliance statements -- Compliance statements
pmip6CoreCompliance MODULE-COMPLIANCE pmip6CoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities "The compliance statement for SNMP entities
which implement the MOBILEIPV6-MIB. which implement the PMIPV6-MIB.
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 this description:
description:
-- OBJECT pmip6BindingHomeAddressType -- OBJECT pmip6BindingHomeAddressType
-- 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 pmip6BindingHomeAddress -- ipv6 addresses for the pmip6BindingHomeAddress
-- object. -- object.
-- --
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pmip6SystemGroup MANDATORY-GROUPS { pmip6SystemGroup
skipping to change at page 56, line 45 skipping to change at page 57, line 4
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pmip6LmaSystemGroup, MANDATORY-GROUPS { pmip6LmaSystemGroup,
pmip6LmaConfigurationGroup pmip6LmaConfigurationGroup
} }
::= { pmip6Compliances 9 } ::= { pmip6Compliances 9 }
pmip6MagNotificationCompliance MODULE-COMPLIANCE pmip6MagNotificationCompliance 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 and support Notification
from the mobile access gateway. from the mobile access gateway.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pmip6MagNotificationGroup MANDATORY-GROUPS { pmip6MagNotificationGroup
} }
::= { pmip6Compliances 10 } ::= { pmip6Compliances 10 }
pmip6LmaNotificationCompliance MODULE-COMPLIANCE pmip6LmaNotificationCompliance 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 and support Notification
from the LMA. from the LMA.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pmip6LmaNotificationGroup MANDATORY-GROUPS { pmip6LmaNotificationGroup
} }
::= { pmip6Compliances 11 } ::= { pmip6Compliances 11 }
END 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:
nemoStatus: The value of this object is used to enable or disable pmip6Status: The value of this object is used to enable or disable
the PMIPv6 functionality on a PMIPv6 entity. Access to this MO the PMIPv6 functionality on a PMIPv6 entity. Access to this MO
may be abused to disrupt the communication that depends on may be abused to disrupt the communication that depends on
PMIPv6. PMIPv6.
pmip6MobileNodeGeneratedTimestampInUse : pmip6MobileNodeGeneratedTimestampInUse :
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType: pmip6FixedMagLinkLocalAddressOnAllAccessLinksType:
pmip6FixedMagLinkLocalAddressOnAllAccessLinks: pmip6FixedMagLinkLocalAddressOnAllAccessLinks:
pmip6FixedMagLinkLayerAddressOnAllAccessLinks: pmip6FixedMagLinkLayerAddressOnAllAccessLinks:
pmip6MagEnableMagLocalRouting: pmip6MagEnableMagLocalRouting:
pmip6MagHomeNetworkPrefixLifeTime: pmip6MagHomeNetworkPrefixLifeTime:
pmip6LmaMinDelayBeforeBCEDelete: pmip6LmaMinDelayBeforeBCEDelete:
pmip6LmaMaxDelayBeforeNewBCEAssign: pmip6LmaMaxDelayBeforeNewBCEAssign:
pmip6LmaTimestampValidityWindow: pmip6LmaTimestampValidityWindow:
pmip6LmaHomeNetworkPrefixLifeTime: pmip6LmaHomeNetworkPrefixLifeTime:
skipping to change at page 59, line 21 skipping to change at page 59, line 21
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 should assign a base arc in the 'mib-2' (standards track) OID
tree for the 'pmip6MIB' MODULE-IDENTITY defined in the PMIPv6 MIB. 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. Requirements Levels, BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, Structure of J., Rose, M. and S. Waldbusser, Structure of
skipping to change at page 62, line 9 skipping to change at page 62, line 9
Internet-Standard Management Framework, RFC 3410, Internet-Standard Management Framework, RFC 3410,
December 2002. December 2002.
[RFC4831] Kempf, J., Goals for Network-Based Localized Mobility [RFC4831] Kempf, J., Goals for Network-Based Localized Mobility
Management (NETLMM), RFC 4831, April 2007. Management (NETLMM), RFC 4831, April 2007.
9. Acknowledgements 9. Acknowledgements
The following groups and individuals have contributed to this draft The following groups and individuals have contributed to this draft
with discussions and comments: with discussions and comments:
WIDE-netman group WIDE Project netman-WG
Dirk von-Hugo Dirk von-Hugo
10. Authors' Addresses 10. 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 E-mail: 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 E-mail: 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
skipping to change at page 63, line 4 skipping to change at page 63, line 4
Phone: +1-408-527-6109 Phone: +1-408-527-6109
E-mail: sgundave@cisco.com E-mail: 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 E-mail: ryuji@us.toyota-itc.com
Appendix. History of Changes
Changes since draft-ietf-netlmm-pmipv6-mib-00.txt Changes since draft-ietf-netlmm-pmipv6-mib-00.txt
a. Fixed editorial nits, missing references a. Fixed editorial nits, missing references
Changes since draft-ietf-netlmm-pmipv6-mib-00.txt Changes since draft-ietf-netlmm-pmipv6-mib-00.txt
a. Addded appendix for change history a. Added appendix for change history
b. Changed MAX-ACCESS of pmip6MagHomeNetworkPrefixLifeTime b. Changed MAX-ACCESS of pmip6MagHomeNetworkPrefixLifeTime
read-write -> read-only 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. 59 change blocks. 
83 lines changed or deleted 113 lines changed or added

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