RFC 6475
Proxy Mobile IPv6 Management Information Base
Internet Engineering Task Force (IETF) G. Keeni Request for Comments: 6475 Cyber Solutions, Inc. Category: Standards Track K. Koide ISSN: 2070-1721 KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012 Proxy Mobile IPv6 Management Information BaseAbstract
This memo defines a portion of the Proxy Mobile IPv6 Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, the Proxy Mobile IPv6 MIB can 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has 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. 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 (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.Table of Contents
1. The Internet-Standard Management Framework ......................3 2. Overview ........................................................3 2.1. The Proxy Mobile IPv6 Protocol Entities ....................3 2.2. Terminology ................................................4 3. Proxy Mobile IPv6 Monitoring and Control Requirements ...........4 4. MIB Design ......................................................4 4.1. Textual Conventions ........................................6 5. MIB Definitions .................................................6 5.1. Proxy Mobile IPv6 Textual Conventions MIB ..................6 5.2. The Proxy Mobile IPv6 MIB .................................10 6. Security Considerations ........................................58 7. IANA Considerations ............................................60 8. References .....................................................60 8.1. Normative References ......................................60 8.2. Informative References ....................................61 9. Acknowledgements ...............................................62
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].2. Overview
2.1. The Proxy Mobile IPv6 Protocol Entities
Proxy Mobile IPv6 (PMIPv6) [RFC5213] is an extension to the Mobile IPv6 (MIPv6) protocol that facilitates network-based localized mobility management (NETLMM) for IPv6 nodes in a PMIPv6 domain. There are three types of entities envisaged by the PMIPv6 protocol. mobile node (MN): In the PMIPv6 context, this term is used to refer to an IP host or router whose mobility is managed by the network. local mobility anchor (LMA): Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile IPv6 domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. The local mobility anchor has the functional capabilities of a home agent as defined in the Mobile IPv6 base specification [RFC6275] with the additional capabilities required for supporting the Proxy Mobile IPv6 protocol as defined in the PMIPv6 specification [RFC5213]. mobile access gateway (MAG): Mobile Access Gateway is the entity on an access router that manages the mobility-related signaling for a mobile node that is attached to its access link. It is responsible for tracking the mobile node's movements to and from the access link and for signaling the mobile node's local mobility anchor. This document defines a set of managed objects (MOs) that can be used to monitor and control PMIPv6 entities.
2.2. Terminology
The terminology used in this document is consistent with the definitions used in the Mobile IPv6 protocol specification [RFC6275] and in the NETLMM goals document [RFC4831]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].3. Proxy Mobile IPv6 Monitoring and Control Requirements
For managing a PMIPv6 entity, it is necessary to monitor the following: o capabilities of PMIPv6 entities o signaling traffic due to PMIPv6 signaling o binding-related details (at LMA and MAG) o binding-related statistics (at LMA and MAG)4. MIB Design
The basic principle has been to keep the MIB as simple as possible and, at the same time, to make it effective enough so that the essential needs of monitoring and control are met. The Proxy Mobile IPv6 Management Information Base (PMIPV6-MIB) extends the Mobile IPv6 Management Information Base (MIPV6-MIB) [RFC4295]. It is assumed that PMIPV6-MIB will always be implemented in conjunction with the MOBILEIPV6-MIB [RFC4295]. The PMIPV6-MIB 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: - pmip6Core: a generic group containing objects that are 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 service. Objects belonging to this group have the "pmip6Mag" prefix and will be implemented on the corresponding MAG. - 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.
- 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:
- pmip6BindingCacheTable: models the Binding Cache on the local
mobility anchor.
- pmip6MagProxyCOATable: models the Proxy Care-of Addresses
configured on the egress interfaces of the mobile access
gateway.
- pmip6MagMnIdentifierTable: provides a mapping from the MAG-
internal pmip6MagMnIndex to the mobile node identifier.
- pmip6MagMnLLIdentifierTable: provides a mapping from the MAG-
internal pmip6MagMnLLIndex to the corresponding interface of the
mobile node link-layer identifier.
- 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).
- pmip6MagBLTable: models the Binding Update List (BL) that
includes PMIPv6-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 (LMAAs) 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.
- pmip6LmaMnIdentifierTable: provides a mapping from the LMA-
internal pmip6BindingMnIndex to the mobile node identifier.
- pmip6LmaMnLLIdentifierTable: provides a mapping from the LMA-
internal pmip6BindingMnLLIndex to the corresponding interface of
the mobile node link-layer identifier.
- pmip6LmaHomeNetworkPrefixTable: contains the list of home
network prefixes assigned to the connected interfaces of the
mobile nodes anchored on an LMA.
4.1. Textual Conventions
A Proxy Mobile IPv6 Textual Conventions MIB module containing
Textual Conventions to represent commonly used Proxy Mobile IPv6
management information is defined. The intent is that these
TEXTUAL CONVENTIONS (TCs) will be imported and used in
PMIPv6-related MIB modules that would otherwise define their own
representation(s). This MIB module includes references to RFC
4283 [RFC4283] and RFC 5213 [RFC5213].
5. MIB Definitions
5.1. Proxy Mobile IPv6 Textual Conventions MIB
PMIPV6-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32
FROM SNMPv2-SMI -- [RFC2578]
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
"
DESCRIPTION
"This MIB module provides textual conventions for
Proxy Mobile IPv6 Management information.
Copyright (c) 2012 IETF Trust and the persons
identified as authors of the code. All rights
reserved.
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
"The initial version, published as RFC 6475."
::= { mib-2 205 }
-- -------------------------------------------------------------
-- Textual Conventions
-- -------------------------------------------------------------
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))
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) 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))
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"
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
(page 10 continued on part 2)
