Internet Engineering Task Force G. Chen
Internet-Draft L. Li
Intended status: Informational China Mobile
Expires: January 7, 2012 July 6, 2011
IPv6 Provider Edge Routers (6PE) Information Base (MIB)
draft-chen-mpls-6pe-mib-02
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a MIB module for IPv6 Provider Edge
Routers (6PE)over Multiprotocol Label Switching (MPLS) Label
Switching Routers (LSRs).
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2012.
Copyright Notice
Copyright (c) 2011 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.
Chen & Li Expires January 7, 2012 [Page 1]
Internet-Draft 6PE MIB July 2011
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview of MIB objects . . . . . . . . . . . . . . . . . . . . 3
3.1. 6PETunnelIfTable . . . . . . . . . . . . . . . . . . . . . 4
3.2. 6PEMplsIfTable . . . . . . . . . . . . . . . . . . . . . . 4
4. 6PE-MPLS-STD-MIB Module Definitions . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
7. Normative References . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
Chen & Li Expires January 7, 2012 [Page 2]
Internet-Draft 6PE MIB July 2011
1. Introduction
IPv6 Provider Edge Routers (6PE) is a IPv6 transition technology,
which could shift network to provide IPv6 access depending on
existing Multiprotocol Label Switching (MPLS) core network.
Operators could deploy IPv6 network without modifying IPv4 enable
MPLS cloud. Therefore, 6PE is treated as a IPv6 transition solution
on the early stage. 6PE will be adopted in more and more operational
IP networks on account of IPv4 depletion and incremental advantages.
RFC 4789[RFC4789] has elaborated 6PE technology. When tunneling IPv6
packets over the IPv4 MPLS backbone, rather than successively prepend
an IPv4 header and then perform label imposition based on the IPv4
header, the ingress 6PE Router MUST directly perform label imposition
of the IPv6 header without prepending any IPv4 header. In respect of
managing IPv6 tunnel, RFC 4087[RFC4087] has specified managed objects
used for managing tunnels of any type over IPv4 and IPv6 networks.
However, This MIB module does not support tunnels over non-IP
networks. RFC 4382[RFC4382] has defined managed objects to configure
and monitor MPLS layer 3 Virtual Private Networks. Nevertheless, 6PE
is neither Layer 3 IP tunnel nor MPLS layer 3 VPN. This document is
aimed at discribing managed objects for 6PE.
2. 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]
3. Overview of MIB objects
The following subsections describe the purpose of each of the objects
contained in the 6PE-MPLS-STD-MIB.
Chen & Li Expires January 7, 2012 [Page 3]
Internet-Draft 6PE MIB July 2011
3.1. 6PETunnelIfTable
6PETunnelIfTable are defined in the MIBs defining the encapsulation.
An entry in the 6PE Tunnel MIB will exist for every interface entry
with this interface type. An implementation of the 6PE Tunnel MIB
may allow 6PETunnelIfTable to be created. Creating a tunnel will
also add an entry in the 6PETunnelIfTable, and deleting a tunnel will
likewise delete the entry in the 6PETunnelIfTable.
3.2. 6PEMplsIfTable
This table controls MPLS-specific parameters when 6PE is going to be
carried over MPLS cloud.
4. 6PE-MPLS-STD-MIB Module Definitions
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, transmission,
Integer32, IpAddress FROM SNMPv2-SMI -- [RFC2578]
RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
InetAddressType,
InetAddress FROM INET-ADDRESS-MIB -- [RFC4001]
ifIndex,
InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsLdpIdentifier, MplsLsrIdentifier
FROM MPLS-TC-STD-MIB -- [RFC3811]
MplsIndexType
FROM MPLS-LSR-STD-MIB -- [RFC3813]
Chen & Li Expires January 7, 2012 [Page 4]
Internet-Draft 6PE MIB July 2011
6peMplsStdMIB MODULE-IDENTITY
LAST-UPDATED "201107060000Z" -- 06 July 2011 00:00:00 GMT
ORGANIZATION "IPv6 Provider Edge Routers (6PE) Working Group."
CONTACT-INFO
"
Chen Gang, Editor
Email: chengang@chinamobile.com
Li Lianyuan, Editor
Email: lilianyuan@chinamobile.com
"
DESCRIPTION
"This MIB module complements the 6PE-MPLS-STD-MIB for 6PE.
Copyright (c) 2010 IETF Trust and the persons identified as
authors of the code. All rights reserved.
-- Revision history.
REVISION "201107060000Z" -- 06 July 2011 00:00:00 GMT
DESCRIPTION
"Third published"
::= { 6peMplsStdMIB 1 }
-- 6PETunnelIfTable.
6PETunnelIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF TunnelIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing information on
6PE tunnels."
::= { 6peMplsStdMIB 1 }
6PETunnelIfEntry OBJECT-TYPE
SYNTAX TunnelIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) containing the information
on a particular configured 6PE tunnel."
INDEX { ifIndex }
::= { 6PETunnelIfTable 1 }
6PETunnelIfEntry ::= SEQUENCE {
6PETunnelIfHopLimit Integer32,
Chen & Li Expires January 7, 2012 [Page 5]
Internet-Draft 6PE MIB July 2011
6PETunnelIfSecurity INTEGER,
6PETunnelIfTOS Integer32,
6PETunnelIfFlowLabel IPv6FlowLabelOrAny,
6PETunnelIfLocalAddress InetAddress,
6PETunnelIfRemoteAddress InetAddress
}
6PETunnelIfLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The address of the local endpoint of the tunnel"
::= { 6PETunnelIfEntry 1 }
6PETunnelIfRemoteAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The address of the remote endpoint of the tunnel"
::= { 6PETunnelIfEntry 2 }
6PETunnelIfHopLimit OBJECT-TYPE
SYNTAX Integer32 (0 | 1..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IPv6 Hop Limit to use in IPv6 header."
::= { 6PETunnelIfEntry 3 }
6PETunnelIfTOS OBJECT-TYPE
SYNTAX Integer32 (-2..63)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The method used to set IPv6 Traffic Class in IP header."
::= { 6PETunnelIfEntry 4 }
6PETunnelIfFlowLabel OBJECT-TYPE
SYNTAX IPv6FlowLabelOrAny
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The method used to set the IPv6 Flow Label value."
::= { 6PETunnelIfEntry 5}
Chen & Li Expires January 7, 2012 [Page 6]
Internet-Draft 6PE MIB July 2011
-- 6PEMplsIfTable.
6PEMplsIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table controls MPLS-specific parameters when the 6PE is
going to be carried over MPLS cloud."
::= { 6peMplsStdMIB 2 }
6PEMplsEntry OBJECT-TYPE
SYNTAX 6PEMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents parameters specific to MPLS
cloud for 6PE."
INDEX { 6PEIndex }
::= { 6PEMplsIfTable 1 }
Figure 1
5. Security Considerations
It needs to be further identified.
6. IANA Considerations
This memo includes no request to IANA.
7. Normative References
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Chen & Li Expires January 7, 2012 [Page 7]
Internet-Draft 6PE MIB July 2011
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual
Conventions (TCs) for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB)", RFC 3813,
June 2004.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005.
[RFC4382] Nadeau, T. and H. van der Linde, "MPLS/BGP Layer 3 Virtual
Private Network (VPN) Management Information Base",
RFC 4382, February 2006.
[RFC4789] Schoenwaelder, J. and T. Jeffree, "Simple Network
Management Protocol (SNMP) over IEEE 802 Networks",
RFC 4789, November 2006.
Authors' Addresses
Gang Chen
China Mobile
53A,Xibianmennei Ave.,
Xuanwu District,
Beijing 100053
China
Email: chengang@chinamobile.com
Chen & Li Expires January 7, 2012 [Page 8]
Internet-Draft 6PE MIB July 2011
Lianyuan Li
China Mobile
53A,Xibianmennei Ave.
Beijing 100053
P.R.China
Phone: +86-13910750201
Email: lilianyuan@chinamobile.com
Chen & Li Expires January 7, 2012 [Page 9]