Internet DRAFT - draft-chen-l3vpn-mt-extensions-to-mpls-l3vpn-mib
draft-chen-l3vpn-mt-extensions-to-mpls-l3vpn-mib
L3VPN Working Group Emily Chen
Internet-Draft Huawei Technology
Intended status: Standards Track Chen Li
Expires: January 10, 2013 Lianyuan Li
Peng Fan
China Mobile
July 9, 2012
Multi Topology Extensions To MPLS/BGP Layer 3 Virtual Private Network
Management Information Base
draft-chen-l3vpn-mt-extensions-to-mpls-l3vpn-mib-00.txt
Abstract
This document defines extensions to Multiprotocol Label Switching
(MPLS) Layer-3 Virtual Private Networks (L3VPN) Management
Information Base (MIB), to support Multi Topology routing. It
describes managed objects to configure and/or monitor Multi Topology
based Multiprotocol Label Switching Layer-3 Virtual Private Networks
on a Multiprotocol Label Switching (MPLS) Label Switched Router (LSR)
supporting this feature.
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 10, 2013.
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
Chen, et al. Expires January 10, 2013 [Page 1]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
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.
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.
Chen, et al. Expires January 10, 2013 [Page 2]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Extensions To MPLS-L3VPN-STD-MIB . . . . . . . . . . . . . . . 5
4.1. Example Of Setting UP MT Based MPLS L3VPN . . . . . . . . 5
4.2. New Definition of VRF Configuration Table . . . . . . . . 6
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Chen, et al. Expires January 10, 2013 [Page 3]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
1. Introduction
Multi Topology (MT) solution makes it possible to establish
Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) across
a specific, or set of, multiple topologies. By using these MT LSPs,
Layer-3 Virtual Private Networks (L3VPN) can benefit from the
advantages of Multi Topology, such as service separation, end-to-end
protection, simplified inter-AS deployment, etc.
The motivation of this document is to facilitate the configuration
and management of such MT based MPLS/BGP L3VPN. It defines
extensions to MPLS-L3VPN-STD-MIB to support MT features.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Terminology
This document uses terminologies from the document describing the
MPLS architecture [RFC3031] and from the document describing MPLS
Layer-3 VPNs (L3VPN) [RFC4364], as well as the MPLS LDP Multi
Topology [I-D.ietf-mpls-ldp-multi-topology].
Throughout this document, the use of the terms "Provider Edge (PE)
and Customer Edge (CE)" or "PE/CE" will be replaced by "PE" in all
cases except when a network device is a CE when used in the carrier's
carrier model.
3. Requirements
Within a Service Provider's MPLS backbone, besides default topology,
there might be some more topolgies with MT LSPs on them. Provider
Edge (PE) routers should associate the VPN service(s) to a specific
topology. Multiple VPN application can share a same topology, or use
their respective ones.
Chen, et al. Expires January 10, 2013 [Page 4]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
+-------+ +------+ +-------+
| App 1 | * * * * * * | P1 | * * * * * * | App 1 |
+-------+ * +------+ * +-------+
\ * * /
\ * * /
\ * * /
+-------+ +-------+ +-------+ +-------+
| App 2 |------| PE 1 |----------------------| PE 2 |------| App 2 |
+-------+ +-------+ +-------+ +-------+
/ ' ' \
/ ' ' \
/ ' ' \
+-------+ ' +------+ ' +-------+
| App 3 | ' ' ' ' ' ' | P2 | ' ' ' ' ' ' | App 3 |
+-------+ +------+ +-------+
MT Based MPLS/BGP L3VPN Example
Figure 1
In the figure above, the paths between PE1 and PE2 can be separated
into several topologies. In this example, PE1--PE2 belongs to
default topology, while PE1--P1--PE2 belongs to RED topology, and
PE1--P2--PE2 belongs to BLUE topology. And the applications over
this MT based MPLS backbone can be associated to diferrent VPNs, or
diferrent services (such as IPv4 and IPv6 services) in a same VPN.
Users are allowed to map each application to a specific topology by
configuration, for instance, App1 maps to the LSPs in the RED
topology, App2 maps to the LSPs in the default topology, App3 maps to
the LSPs in the BLUE topology. Then the VPN performance can be
monitored per topology.
4. Extensions To MPLS-L3VPN-STD-MIB
4.1. Example Of Setting UP MT Based MPLS L3VPN
[RFC4364] demonstrates MPLS-L3VPN-STD-MIB to setup MPLS L3VPN. In
order to setup MT based MPLS L3VPN, this document adds one object to
mplsL3VpnVrfTable to specify the topology used in MPLS backbone.
Chen, et al. Expires January 10, 2013 [Page 5]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
In mplsL3VpnVrfTable:
{
mplsL3VpnVrfName = "RED",
mplsL3VpnVrfDescription = "Intranet of Company ABC",
mplsL3VpnVrfMplsMtId = "50", -- Unsigned32
mplsL3VpnVrfRD = "100:1", -- octet string
mplsL3VpnVrfRowStatus = createAndGo(4)
}
4.2. New Definition of VRF Configuration Table
mplsL3VpnVrfTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsL3VpnVrfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface MPLS L3VPN
VRF Table capability and associated information.
Entries in this table define VRF routing instances
associated with MPLS/VPN interfaces. Note that
multiple interfaces can belong to the same VRF
instance. The collection of all VRF instances
comprises an actual VPN."
::= { mplsL3VpnConf 2 }
mplsL3VpnVrfEntry OBJECT-TYPE
SYNTAX MplsL3VpnVrfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by an LSR for
every VRF capable of supporting MPLS L3VPN. The
indexing provides an ordering of VRFs per-VPN
interface."
INDEX { mplsL3VpnVrfName }
::= { mplsL3VpnVrfTable 1 }
MplsL3VpnVrfEntry ::= SEQUENCE {
mplsL3VpnVrfName MplsL3VpnName,
mplsL3VpnVrfVpnId VPNIdOrZero,
mplsL3VpnVrfDescription SnmpAdminString,
mplsL3VpnVrfMplsMtId Unsigned32,
mplsL3VpnVrfRD MplsL3VpnRouteDistinguisher,
mplsL3VpnVrfCreationTime TimeStamp,
mplsL3VpnVrfOperStatus INTEGER,
mplsL3VpnVrfActiveInterfaces Gauge32,
mplsL3VpnVrfAssociatedInterfaces Unsigned32,
mplsL3VpnVrfConfMidRteThresh Unsigned32,
mplsL3VpnVrfConfHighRteThresh Unsigned32,
Chen, et al. Expires January 10, 2013 [Page 6]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
mplsL3VpnVrfConfMaxRoutes Unsigned32,
mplsL3VpnVrfConfLastChanged TimeStamp,
mplsL3VpnVrfConfRowStatus RowStatus,
mplsL3VpnVrfConfAdminStatus INTEGER,
mplsL3VpnVrfConfStorageType StorageType
}
mplsL3VpnVrfName OBJECT-TYPE
SYNTAX MplsL3VpnName
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The human-readable name of this VPN. This MAY
be equivalent to the [RFC2685] VPN-ID, but may
also vary. If it is set to the VPN ID, it MUST
be equivalent to the value of mplsL3VpnVrfVpnId.
It is strongly recommended that all sites supporting
VRFs that are part of the same VPN use the same
naming convention for VRFs as well as the same VPN
ID."
REFERENCE
"[RFC2685]"
::= { mplsL3VpnVrfEntry 1 }
mplsL3VpnVrfVpnId OBJECT-TYPE
SYNTAX VPNIdOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VPN ID as specified in [RFC2685]. If a VPN ID
has not been specified for this VRF, then this
variable SHOULD be set to a zero-length OCTET
STRING."
::= { mplsL3VpnVrfEntry 2 }
mplsL3VpnVrfDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The human-readable description of this VRF."
DEFVAL { "" }
::= { mplsL3VpnVrfEntry 3 }
mplsL3VpnVrfMplsMtId OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-create
STATUS current
Chen, et al. Expires January 10, 2013 [Page 7]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
DESCRIPTION
"The Multi Topology Identifier used by the MPLS
backbone of this VRF."
DEFVAL { "0" }
REFERENCE
"draft-ietf-mpls-ldp-multi-topology, LDP Extensions
for Multi Topology Routing, Section on
Multi-Topology ID."
::= { mplsL3VpnVrfEntry 4 }
mplsL3VpnVrfRD OBJECT-TYPE
SYNTAX MplsL3VpnRouteDistinguisher
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The route distinguisher for this VRF."
DEFVAL { "" }
::= { mplsL3VpnVrfEntry 5 }
mplsL3VpnVrfCreationTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which this VRF entry was created."
::= { mplsL3VpnVrfEntry 6 }
mplsL3VpnVrfOperStatus OBJECT-TYPE
SYNTAX INTEGER { up (1),
down (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Denotes whether or not a VRF is operational. A VRF is
up(1) when there is at least one interface associated
with the VRF whose ifOperStatus is up(1). A VRF is
down(2) when:
a. There does not exist at least one interface whose
ifOperStatus is up(1).
b. There are no interfaces associated with the VRF."
::= { mplsL3VpnVrfEntry 7 }
mplsL3VpnVrfActiveInterfaces OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Chen, et al. Expires January 10, 2013 [Page 8]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
"Total number of interfaces connected to this VRF with
ifOperStatus = up(1).
This value should increase when an interface is associated
with the corresponding VRF and its corresponding ifOperStatus
is equal to up(1). If an interface is associated whose
ifOperStatus is not up(1), then the value is not incremented
until such time as it transitions to this state.
This value should be decremented when an interface is
disassociated with a VRF or the corresponding ifOperStatus
transitions out of the up(1) state to any other state.
"
::= { mplsL3VpnVrfEntry 8 }
mplsL3VpnVrfAssociatedInterfaces OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of interfaces connected to this VRF
(independent of ifOperStatus type)."
::= { mplsL3VpnVrfEntry 9 }
mplsL3VpnVrfConfMidRteThresh OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes mid-level water marker for the number
of routes that this VRF may hold."
DEFVAL { 0 }
::= { mplsL3VpnVrfEntry 10 }
mplsL3VpnVrfConfHighRteThresh OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Denotes high-level water marker for the number of
routes that this VRF may hold."
DEFVAL { 0 }
::= { mplsL3VpnVrfEntry 11 }
mplsL3VpnVrfConfMaxRoutes OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
Chen, et al. Expires January 10, 2013 [Page 9]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
DESCRIPTION
"Denotes maximum number of routes that this VRF is
configured to hold. This value MUST be less than or
equal to mplsL3VpnVrfConfMaxPossRts unless it is set
to 0."
DEFVAL { 0 }
::= { mplsL3VpnVrfEntry 12 }
mplsL3VpnVrfConfLastChanged OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
change of this table entry, which includes changes of
VRF parameters defined in this table or addition or
deletion of interfaces associated with this VRF."
::= { mplsL3VpnVrfEntry 13 }
mplsL3VpnVrfConfRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table.
When a row in this table is in active(1) state, no
objects in that row can be modified except
mplsL3VpnVrfConfAdminStatus, mplsL3VpnVrfConfRowStatus,
and mplsL3VpnVrfConfStorageType."
::= { mplsL3VpnVrfEntry 14 }
mplsL3VpnVrfConfAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2), -- can't pass packets
testing(3) -- in some test mode
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the desired operational status of this
VRF."
::= { mplsL3VpnVrfEntry 15 }
mplsL3VpnVrfConfStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
Chen, et al. Expires January 10, 2013 [Page 10]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
STATUS current
DESCRIPTION
"The storage type for this VPN VRF entry.
Conceptual rows having the value 'permanent'
need not allow write access to any columnar
objects in the row."
REFERENCE
"See RFC2579."
DEFVAL { volatile }
::= { mplsL3VpnVrfEntry 16 }
5. Acknowledgements
We would like to thank authors of [RFC4362] and the authors of
draft-ietf-mpls-ldp-multi-topology from which some text of this
document has been inspired.
6. IANA Considerations
The IANA has assigned { mplsStdMIB 11 } to the MPLS-L3VPN-STD-MIB
module specified in [RFC 4362]. This document only makes extensions
to the MPLS-L3VPN-STD-MIB module, there is no further IANA
requirement.
7. Security Considerations
No specific security issues with the proposed solutions are known.
The proposed extension in this document does not introduce any new
security considerations beyond that already apply to the base MPLS/
BGP L3VPN specification as [RFC 3031] and [RFC 4364].
8. References
8.1. Normative References
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, January 2001.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006.
[RFC4382] Nadeau, T. and H. van der Linde, "MPLS/BGP Layer 3 Virtual
Private Network (VPN) Management Information Base",
Chen, et al. Expires January 10, 2013 [Page 11]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
RFC 4382, February 2006.
8.2. Informative References
[I-D.ietf-mpls-ldp-multi-topology]
Zhao, Q., Fang, L., Zhou, C., Li, L., and N. So, "LDP
Extensions for Multi Topology Routing",
draft-ietf-mpls-ldp-multi-topology-03 (work in progress),
March 2012.
[I-D.li-mpls-ldp-mt-mib]
Li, C., Li, L., Huang, L., Chen, E., and Q. Zhao,
"Management Information Base for MPLS LDP Multi Topology",
draft-li-mpls-ldp-mt-mib-03 (work in progress), June 2012.
Authors' Addresses
Emily Chen
Huawei Technology
2330 Central Expressway
Santa Clara, CA 95050
US
Email: emily.chenying@huawei.com
Chen Li
China Mobile
32 Xuanwumen West Street, Xicheng District
Beijing 100053
P.R. China
Email: lichenyj@chinamobile.com
Lianyuan Li
China Mobile
32 Xuanwumen West Street, Xicheng District
Beijing 100053
P.R. China
Email: lichenyj@chinamobile.com
Chen, et al. Expires January 10, 2013 [Page 12]
Internet-Draft MT Extensions To MPLS/BGP L3VPN MIB July 2012
Peng Fan
China Mobile
32 Xuanwumen West Street, Xicheng District
Beijing 100053
P.R. China
Email: lichenyj@chinamobile.com
Chen, et al. Expires January 10, 2013 [Page 13]
