Internet Draft David Zelig
Expires: June 2004 Corrigent Systems
A. Malis Thomas D. Nadeau
Tellabs, Inc. Cisco Systems, Inc.
Sharon Mantin Dave Danenberg
AxONLinks Litchfield Communications, Inc.
December 2003
Pseudo Wire (PW) over MPLS PSN Management Information Base
draft-ietf-pwe3-pw-mpls-mib-04.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months 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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright (C) The Internet Society (2001). All rights reserved.
1 Abstract
This memo defines an experimental 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 PW operation over Multi-Protocol Label Switching (MPLS) Label
Switch Router (LSR).
Zelig et al. Expires June 2004 [page 1]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
Table of Contents
1 Abstract.......................................................1
2 Introduction...................................................2
3 Terminology....................................................3
4 The Internet-Standard Management Framework.....................3
5 Feature Checklist..............................................4
6 MIB module usage...............................................4
6.1 PW-MPLS-MIB usage............................................4
6.2 Example of MIB module usage..................................6
7 Object definitions.............................................7
8 Security Considerations.......................................20
9 IANA considerations...........................................22
10 References..................................................22
10.1 Normative references........................................22
10.2 Informative references......................................23
11 Author's Addresses..........................................23
12 Full Copyright Statement....................................24
13 Intellectual Property Notice................................25
2 Introduction
This document describes a model for managing pseudo wire services
for transmission over different flavors of MPLS tunnels. The
general PW MIB module [PW-MIB] defines the parameters global to the
PW regardless of underlying PSN and emulated service. Indicating
PSN type of MPLS in PW-MIB references this module.
This document describes the MIB objects that define pseudo wire
association to the MPLS PSN, in a way that is not specific to the
carried service.
Together, [TEMIB and LSRMIB], describe the modeling of an MPLS
Tunnel, and a Tunnel's underlying cross-connects. The defined MIB
support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by
LDP or manually), and MPLS PW label only (no outer tunnel).
Some flavors of MPLS, such as carrying PW in MPLS in IP and MPLS in
GRE are not defined here, waiting to the WG documents that will
describe the exact MPLS functionality. It still for further study
whether this functionality will be treated in this MIB module or in
another one specific to IP PSN.
Zelig et al Expires June 2004 [page 2]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
Conventions used in this document
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 RFC-2119
[BCP14].
3 Terminology
This document uses terminology from the document describing the PW
architecture [PWARCH], [PWREQ] and [PWCNTRL].
The terms "Outbound" and "Inbound" in this MIB module are based on
the common practice in the MPLS standards, i.e. "outbound" are
toward the PSN. However, where these terms are used in an object
name, the object description clarifies the exact packet direction
to prevent confusion with these terms in other documents.
"PSN Tunnel" is a general term indicating a virtual connection
between the two PWE3 edge devices. Each tunnel may potentially
carry multiple PWs inside. In the scope of this document, it is
MPLS tunnel.
This document uses terminology from the document describing the
MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path
(LSP) is modeled as described in [LSRMIB and TEMIB] via a series of
cross-connects through 1 or more Label switch routers (LSR).
In MPLS PSN, a PW connection typically uses a PW Label within a
Tunnel Label [TRANS]. Multiple pseudo wires each with a unique PW
Label can share the same Tunnel. For PW transport over MPLS, the
Tunnel Label is known as the "outer" Label, while the PW Label is
known as the "inner" Label. An exception to this is with adjacent
LSRs or the use of PHP. In this case, there is an option for PWs to
connect directly without an outer Label.
4 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
Zelig et al Expires June 2004 [page 3]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579]
and STD 58, RFC 2580 [RFC2580].
5 Feature Checklist
The PW MPLS MIB module is designed to satisfy the following
requirements and constraints:
- The MIB module supports both manually configured and signaled
PWs.
- The MIB module supports point-to-point PW connections.
- The MIB module enables the use of any emulated service.
- The MIB supports MPLS-TE outer tunnel, Non TE MPLS outer tunnel
(an outer tunnel signaled by LDP or set-up manually), and no
outer tunnel (where the PW label is the only label in the
incoming MPLS stack). The later case is applicable for manual
configuration of PW over a single hop (in multiple hops case, it
is required to have an outer MPLS tunnel).
6 MIB module usage
The MIB module structure for defining a PW service is composed from
three types of modules.
The first type is the PW-MIB module [PW-MIB], which configures
general parameters of the PW that are common to all types of
emulated services and PSN.
The second type of modules is per PSN module. There is a different
module for each type of PSN. This document defines the MIB module
for MPLS (PW-MPLS-MIB).
The third type of modules is service-specific module, which is
emulated signal type dependent. These modules are defined in other
documents; see for example [CEPMIB].
[PWTC] defines some of the object types used in this module.
6.1 PW-MPLS-MIB usage
- The PW table (pwVcTable) in [PW-MIB] is used for all PW types
(ATM, FR, Ethernet, SONET, etc.). This table contains high level
generic parameters related to the PW creation. A row is created by
the operator for each PW service.
Zelig et al Expires June 2004 [page 4]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
- If the PSN type in pwVcTable is MPLS, the agent create a row in
the MPLS specific parameters table (pwMplsVcTable) in PW MPLS MIB,
which contain MPLS specific parameters such as EXP bits handling
and outer tunnel types.
- The operator configure the association to the desired MPLS
tunnel or tunnels through either the pwMplsTeMappingTable,
pwMplsNonTeMappingTable or both, depending on the desired outer
tunnel type. Each of the above tables may contain multiple entries
for the same PW, for example in protection configuration.
- The agent creates rows in the MPLS outbound tunnels table
(pwVcMplsOutboundTable) based on the configuration above. This
table allows quick access to the association tables through
pwVcIndex ordering.
The relation to the MPLS network is by configuration of the edge
LSR only - that is to say, the LSR providing the PW function. Since
Tunnels are uni-directional, a pair of tunnels must exist (one for
inbound, one for outbound). The following graphic depicts a VC that
originates and terminates at LSR-M. It uses LSPs A and B formed by
Tunnels Ax and Bx continuing through LSR-N to LSR-P. The
concatenations of Tunnels create the LSPs. Note: 'X' denotes a
Tunnel's cross-connect.
LSP-A
<- - - - - - - - - - - - - - - - - - - - - - - - - - - -
+---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P
|---+ | | | |
| | Tunnel | | Tunnel | |
+ | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+
| | <------| | | |<--------------| | | |
<-->| N |PWin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS|
N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF |
A E | S | | |<-->| | | |<-->| | |
T R | | --->X----->| | | |------>X------>| | | |
I V | P |PWout outSeg| | | | inSeg outSeg | | | |
V I | | ------>| | | |-------------->| | | |
E C + | Tunnel +----+ +----+ Tunnel +----+ +----+
E |---+ B1 (M->N) | | B2 (M->P) | |
| | | | |
+---------------------+ +-------------------------+ +-----
- - - - - - - - - - - - - - - - - - - - - - - - - - - ->
LSP-B
The PW-MPLS-MIB supports three options for MPLS network:
Zelig et al Expires June 2004 [page 5]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
- In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE
MIB [TEMIB]. The tunnels are associated to the PW by the (4)
indexes that uniquely identify the Tunnel at the TE-MIB.
- In the Non TE case, Tunnel A1 and B1 are either manually
configured or set up with LDP. The tunnels are associated to the PW
by the XC index in the MPLS-LSR-MIB [LSRMIB].
- In the PW label only case, there is no outer tunnel on top of the
PW label. This case is useful in case of adjacent PE only in manual
configuration. Note that when LSR-N acts as PHP for the outer
tunnel label, there are still entries for the outer tunnel in the
relevant MPLS MIB modules.
A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for
the same VC is allowed by creating the rows with the same pwVcIndex
with different MPLS tunnel indexes types.
It is worth noting that inbound (tunnel originated in the remote
PE) mapping is nor configured nor reported through the PW MPLS MIB
module since the local PE does not know the inbound association
between specific PW and MPLS tunnels.
6.2 Example of MIB module usage
Please see [PW-MIB] for detailed MIB usage example.
Zelig et al Expires June 2004 [page 6]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
7 Object definitions
PW-MPLS-DRAFT04-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
RowStatus, StorageType
FROM SNMPv2-TC
InterfaceIndexOrZero
FROM IF-MIB
MplsTunnelIndex, MplsTunnelInstanceIndex,
MplsLdpIdentifier, MplsLsrIdentifier
FROM MPLS-TC-STD-MIB
PwVcIndexType, pwStdMIB
FROM PW-TC-DRAFT04-MIB
pwVcIndex
FROM PW-DRAFT04-MIB
;
pwVcMplsMIB MODULE-IDENTITY
LAST-UPDATED "200311301200Z" -- 30 November 2003 12:00:00 EST
ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
Group"
CONTACT-INFO
"
David Zelig
Postal: Corrigent Systems
126, Yigal Alon St.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
E-mail: davidz@corrigent.com
Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-497-3051
Email: tnadeau@cisco.com
Dave Danenberg
Zelig et al Expires June 2004 [page 7]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
Postal: Litchfield Communications, Inc.
76 Westbury Park Rd
Princeton Building East
Watertown, CT 06795
Tel: +1-860-945-1573 x3180
Email: dave_danenberg@litchfieldcomm.com
Sharon Mantin
Postal: AxONLink (Israel) Ltd
9 Bareket St.
Petah Tikva 49517, Israel
Tel: +972-3-9263972
Email: sharon.mantin@axonlink.com
The PWE3 Working Group (email distribution pwe3@ietf.org,
http://www.ietf.org/html.charters/pwe3-charter.html)
"
DESCRIPTION
"This MIB complements the PW-STD-MIB for PW operation
over MPLS.
Copyright (C) The Internet Society (date). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices.
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
"
-- Revision history.
REVISION
"200311301200Z" -- 30 November 2003 12:00:00 EST
DESCRIPTION
"Draft-ietf-pwe3-pw-mpls-mib-04 version. Changes from
previous version:
1) Adapting description to MIB boilerplate.
2) Module OID changed to PWE3 tree.
3) Sync descriptions of various items to table structure and
removing unnecessary references.
"
REVISION
"200307291200Z" -- 29 July 2003 12:00:00 EST
DESCRIPTION
"Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from
previous version:
1) Removing inbound table (no strict mode and no knowledge
of inbound tunnel).
2) Provisioning (i.e. RowCreate) done via mapping tables.
Outbound table is now read only for sorted search for
pwVcIndex.
"
Zelig et al Expires June 2004 [page 8]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
REVISION
"200206021200Z" -- 02 June 2002 12:00:00 EST
DESCRIPTION
"Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from
previous version:
1) Spliting the mapping table into two tables, one for
Non TE application and one for TE application.
2) Object types alignment with MPLS MIBs.
"
REVISION
"200201291200Z" -- 29 January 2002 12:00:00 EST
DESCRIPTION
"Changes from previous version:
1) Add LDP entity association.
2) Clarify inbound/outbound directions.
3) Simplify indexing of outbound and inbound tables
and providing get next variables.
"
REVISION
"200111071200Z" -- 7 November 2001 12:00:00 EST
DESCRIPTION
"Changes from previous version:
1) Remove Vc instance from table indexing.
2) Update descriptions of indexing and protection.
3) Remove the need for MPLS-LSR in case of VC only.
4) Change pwVcMplsMplsType to BITS in order to enable
multiple types of outer tunnel.
5) Add ifindex to outer tunnel tables to support vcOnly
option.
6) change naming of outbound, inbound and mapping tables to
reflect addition of VC only port ifindexes.
7) Adapt order of items in mapping table to SNMP convention.
"
REVISION
"200107111200Z" -- July 11 2001 12:00:00 EST
DESCRIPTION
"draft-zelig-pw-mib-00.txt - initial version"
::= { pwStdMIB 3 } -- To be assigned by IANA
-- Top-level components of this MIB.
-- Tables, Scalars
pwVcMplsObjects OBJECT IDENTIFIER
::= { pwVcMplsMIB 1 }
-- Conformance
pwVcMplsConformance OBJECT IDENTIFIER
::= { pwVcMplsMIB 2 }
-- PW MPLS table
Zelig et al Expires June 2004 [page 9]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
pwVcMplsTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table controls MPLS specific parameters when the PW is
going to be carried over MPLS PSN."
::= { pwVcMplsObjects 1 }
pwVcMplsEntry OBJECT-TYPE
SYNTAX PwVcMplsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents parameters specific to MPLS
PSN for a pseudo wire (PW). The row is created
automatically by the local agent if the pwVcPsnType is
MPLS. It is indexed by pwVcIndex, which uniquely
identifying a singular PW.
"
INDEX { pwVcIndex }
::= { pwVcMplsTable 1 }
PwVcMplsEntry ::= SEQUENCE {
pwVcMplsMplsType BITS,
pwVcMplsExpBitsMode INTEGER,
pwVcMplsExpBits Unsigned32,
pwVcMplsTtl Unsigned32,
pwVcMplsLocalLdpID MplsLdpIdentifier,
pwVcMplsLocalLdpEntityID Unsigned32,
pwVcMplsPeerLdpID MplsLdpIdentifier,
pwVcMplsStorageType StorageType
}
pwVcMplsMplsType OBJECT-TYPE
SYNTAX BITS {
mplsTe (0),
mplsNonTe (1),
vcOnly (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the outer tunnel types, if
exists. mplsTe is used if the outer tunnel was set-up by
MPLS-TE, and mplsNonTe is used the outer tunnel was set up
by LDP or manually. Combination of mplsTe and mplsNonTe
may exist in case of outer tunnel protection.
vcOnly is used if there is no outer tunnel label, i.e. in
Zelig et al Expires June 2004 [page 10]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
static provisioning without MPLS tunnel. vcOnly
cannot be combined with mplsNonTe or mplsTe."
::= { pwVcMplsEntry 1 }
pwVcMplsExpBitsMode OBJECT-TYPE
SYNTAX INTEGER {
outerTunnel (1),
specifiedValue (2),
serviceDependant (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the way the PW shim label
EXP bits are to be determined. The value of outerTunnel(1)
is used where there is an outer tunnel - pwVcMplsMplsType
is mplsTe or mplsNonTe. Note that in this case there is no
need to mark the PW label with the EXP bits since the PW
label is not visible to the intermediate nodes.
If there is no outer tunnel, specifiedValue(2) indicate
that the value is specified by pwVcMplsExpBits, and
serviceDependant(3) indicate that the EXP bits are setup
based on a rule specified in the emulated service specific
tables, for example when the EXP bits are a function of
802.1p marking for Ethernet emulated service."
DEFVAL { outerTunnel }
::= { pwVcMplsEntry 2 }
pwVcMplsExpBits OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the MPLS EXP bits to be
used on the PW shim label if pwVcMplsExpBitsMode is
specifiedValue(2), zero otherwise."
DEFVAL { 0 }
::= { pwVcMplsEntry 3 }
pwVcMplsTtl OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set by the operator to indicate the PW TTL bits to be used
on the PW shim label."
DEFVAL { 2 }
::= { pwVcMplsEntry 4 }
Zelig et al Expires June 2004 [page 11]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
pwVcMplsLocalLdpID OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The local LDP identifier of the LDP entity creating
this PW in the local node. As the PW labels are always
set from the per platform label space, the last two octets
in the LDP ID MUST be always both zeros."
REFERENCE
"'LDP specifications', RFC 3036 section 2.2.2."
::= { pwVcMplsEntry 5 }
pwVcMplsLocalLdpEntityID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The local node LDP Entity index of the LDP entity creating
this PW. Should be set to all zeros if not used."
::= { pwVcMplsEntry 6 }
pwVcMplsPeerLdpID OBJECT-TYPE
SYNTAX MplsLdpIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The peer LDP identifier as identified from the LDP
session. Should be zero if not relevant or not known yet."
::= { pwVcMplsEntry 7 }
pwVcMplsStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the storage type for this row."
::= { pwVcMplsEntry 8 }
-- End of PW MPLS table
-- Pseudo Wire MPLS Outbound Tunnel table
pwVcMplsOutboundTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsOutboundEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table reports the association between PWs and the
outbound MPLS tunnels (i.e. toward the PSN) or the physical
Zelig et al Expires June 2004 [page 12]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
interface in case of PW label only. The configuration of
the association is done in other tables."
::= { pwVcMplsObjects 2 }
pwVcMplsOutboundEntry OBJECT-TYPE
SYNTAX PwVcMplsOutboundEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table indicate association between a PW (that
require MPLS tunnels) and MPLS tunnel toward the PSN.
In the case of PW only, it associates the PW with the
interface that shall carry the PW.
This table is indexed by the pwVcIndex and an additional
index enabling multiple rows (i.e. tunnels) for the same
pwVcindex.
At least one entry is created in this table by the agent
for each PW that requires MPLS PSN.
This table points to the appropriate MPLS MIB. In the case
of MPLS-TE, the 4 variables relevant to the indexing of
a TE MPLS tunnel are set as in Srinivasan, et al, <draft-
ietf-mpls-te-mib>.
In case of Non-TE MPLS (an outer tunnel label assigned by
LDP or manually) the table points to the XC entry in the
LSR MIB as in Srinivasan, et al, <draft-ietf-mpls-lsr-mib>.
In case of PW label only (no outer tunnel) the ifIndex of
the port to carry the PW is configured.
Each PW may have multiple rows in this tables if protection
is available at the outer tunnel level. For a specific PW,
each row may be of different type except for PW lable only,
on which only rows with ifIndex of the port are allowed.
"
INDEX { pwVcIndex, pwVcMplsOutboundIndex }
::= { pwVcMplsOutboundTable 1 }
PwVcMplsOutboundEntry ::= SEQUENCE {
pwVcMplsOutboundIndex Unsigned32,
pwVcMplsOutboundLsrXcIndex Unsigned32,
pwVcMplsOutboundTunnelIndex MplsTunnelIndex,
pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier,
pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
pwVcMplsOutboundIfIndex InterfaceIndexOrZero
}
pwVcMplsOutboundIndex OBJECT-TYPE
Zelig et al Expires June 2004 [page 13]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Arbitrary index for enabling multiple rows per PW in
this table. The numbering method is implementation
specific.
"
::= { pwVcMplsOutboundEntry 1 }
pwVcMplsOutboundLsrXcIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will be set by the operator. If the outer
label is defined in the MPLS-LSR-STD-MIB, i.e. set by LDP
or manually, this object points to the XC index
of the outer tunnel. Otherwise, it returns the value zero."
::= { pwVcMplsOutboundEntry 2 }
pwVcMplsOutboundTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise returns the value zero."
::= { pwVcMplsOutboundEntry 3 }
pwVcMplsOutboundTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise returns the value zero."
::= { pwVcMplsOutboundEntry 4 }
pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise returns the value zero."
::= { pwVcMplsOutboundEntry 5 }
pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE
SYNTAX MplsLsrIdentifier
Zelig et al Expires June 2004 [page 14]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Part of set of indexes for outbound tunnel in the case of
MPLS-TE outer tunnel, otherwise returns the value zero."
::= { pwVcMplsOutboundEntry 6 }
pwVcMplsOutboundIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In case of PW label only (no outer tunnel), this object
holds the ifIndex of the outbound port, otherwise returns
the value zero."
::= { pwVcMplsOutboundEntry 7 }
-- End of Pseudo Wire MPLS Outbound Tunnel table
-- PW to Non-TE MPLS tunnels configuration Table.
pwVcMplsNonTeMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table maps an outbound Tunnel to a PW in non-
TE applications."
::= { pwVcMplsObjects 3 }
pwVcMplsNonTeMappingEntry OBJECT-TYPE
SYNTAX PwVcMplsNonTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table configure the association
between the PW and it's non TE MPLS outer Tunnel or
it's physical interface if there is no outer tunnel
(PW label only).
If the operator (or the agent, based on local policy)
want to associate the PW with a non TE tunnel, it create
a row in this table with the tunnel parameters and the
relevant pwVcIndex.
An application can use this table to quickly retrieve the
PW carried over specific non-TE MPLS outer tunnel or
physical interface.
The table in indexed by the XC index for MPLS Non-TE
tunnel, or ifIndex of the port in PW label only case, and
the PW index.
Zelig et al Expires June 2004 [page 15]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
"
INDEX { pwVcMplsNonTeMappingXcTunnelIndex,
pwVcMplsNonTeMappingIfIndex,
pwVcMplsNonTeMappingVcIndex }
::= { pwVcMplsNonTeMappingTable 1 }
PwVcMplsNonTeMappingEntry ::= SEQUENCE {
pwVcMplsNonTeMappingXcTunnelIndex Unsigned32,
pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero,
pwVcMplsNonTeMappingVcIndex PwVcIndexType,
pwVcMplsNonTeMappingRowStatus RowStatus,
pwVcMplsNonTeMappingStorageType StorageType
}
pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for the conceptual XC row identifying Tunnel to PW
mappings when the outer tunnel is created by the MPLS-LSR-
STD-MIB, zero otherwise."
::= { pwVcMplsNonTeMappingEntry 1 }
pwVcMplsNonTeMappingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"In cases where there is PW label without outer tunnel,
this item indicate the ifIndex of the interface this PW
would use. In all other cases, this object should be set to
zero."
::= { pwVcMplsNonTeMappingEntry 2 }
pwVcMplsNonTeMappingVcIndex OBJECT-TYPE
SYNTAX PwVcIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value that represent the PW in the pwVcTable."
::= { pwVcMplsNonTeMappingEntry 3 }
pwVcMplsNonTeMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
Zelig et al Expires June 2004 [page 16]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
::= { pwVcMplsNonTeMappingEntry 4 }
pwVcMplsNonTeMappingStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object."
::= { pwVcMplsNonTeMappingEntry 5 }
-- End of PW to Non-TE MPLS tunnels configuration Table.
-- PW to TE MPLS tunnels configuration Table.
pwVcMplsTeMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table enable the configuration and retrieval of a PW
association to and outbound MPLS tunnel for MPLS-TE
applications."
::= { pwVcMplsObjects 4 }
pwVcMplsTeMappingEntry OBJECT-TYPE
SYNTAX PwVcMplsTeMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in this table represents the association
between a PW and it's MPLS-TE outer Tunnel.
If the operator (or the agent, based on local policy)
want to associate the PW with a TE tunnel, it create
a row in this table with the tunnel parameters and the
relevant pwVcIndex.
An application can use this table to quickly retrieve the
PW carried over specific TE MPLS outer tunnel.
The table in indexed by the 4 indexes of a TE tunnel
and the PW index.
"
INDEX { pwVcMplsTeMappingTunnelIndex,
pwVcMplsTeMappingTunnelInstance,
pwVcMplsTeMappingTunnelPeerLsrID,
pwVcMplsTeMappingTunnelLocalLsrID,
pwVcMplsTeMappingVcIndex }
::= { pwVcMplsTeMappingTable 1 }
Zelig et al Expires June 2004 [page 17]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
PwVcMplsTeMappingEntry ::= SEQUENCE {
pwVcMplsTeMappingTunnelIndex MplsTunnelIndex,
pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
pwVcMplsTeMappingVcIndex PwVcIndexType,
pwVcMplsTeMappingRowStatus RowStatus,
pwVcMplsTeMappingStorageType StorageType
}
pwVcMplsTeMappingTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Primary index for the conceptual row identifying the
MPLS-TE tunnel."
::= { pwVcMplsTeMappingEntry 1 }
pwVcMplsTeMappingTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies an instance of the MPLS-TE tunnel."
::= { pwVcMplsTeMappingEntry 2 }
pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies the Peer LSR when the outer tunnel is MPLS-TE
based."
::= { pwVcMplsTeMappingEntry 3 }
pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
SYNTAX MplsLsrIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identifies the local LSR."
::= { pwVcMplsTeMappingEntry 4 }
pwVcMplsTeMappingVcIndex OBJECT-TYPE
SYNTAX PwVcIndexType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Zelig et al Expires June 2004 [page 18]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
"The value that represent the PW in the pwVcTable."
::= { pwVcMplsTeMappingEntry 5 }
pwVcMplsTeMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"For creating, modifying, and deleting this row."
::= { pwVcMplsTeMappingEntry 6 }
pwVcMplsTeMappingStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object."
::= { pwVcMplsTeMappingEntry 7 }
-- End of PW to TE MPLS tunnels configuration Table.
-- conformance information
-- Note: Conformance at the object access and values level is
-- still FFS, therefore current conformance is defined at the
-- object existence level only.
pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 }
pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 }
pwMplsModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agent that support PW
over MPLS PSN operation."
MODULE -- this module
MANDATORY-GROUPS { pwVcMplsGroup,
pwVcMplsOutboundGroup,
pwVcMplsMappingGroup
}
::= { pwVcMplsCompliances 1 }
-- Units of conformance.
pwVcMplsGroup OBJECT-GROUP
OBJECTS {
Zelig et al Expires June 2004 [page 19]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
pwVcMplsMplsType,
pwVcMplsExpBitsMode,
pwVcMplsExpBits,
pwVcMplsTtl,
pwVcMplsLocalLdpID,
pwVcMplsLocalLdpEntityID,
pwVcMplsPeerLdpID,
pwVcMplsStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for PW
over MPLS PSN configuration."
::= { pwVcMplsGroups 1 }
pwVcMplsOutboundGroup OBJECT-GROUP
OBJECTS {
pwVcMplsOutboundLsrXcIndex,
pwVcMplsOutboundTunnelIndex,
pwVcMplsOutboundTunnelInstance,
pwVcMplsOutboundTunnelLclLSR,
pwVcMplsOutboundTunnelPeerLSR,
pwVcMplsOutboundIfIndex
}
STATUS current
DESCRIPTION
"Collection of objects needed for outbound association of
PW and MPLS tunnel."
::= { pwVcMplsGroups 2 }
pwVcMplsMappingGroup OBJECT-GROUP
OBJECTS {
pwVcMplsNonTeMappingRowStatus,
pwVcMplsNonTeMappingStorageType,
pwVcMplsTeMappingRowStatus,
pwVcMplsTeMappingStorageType
}
STATUS current
DESCRIPTION
"Collection of objects used for mapping of tunnels and PW
labels to PW index."
::= { pwVcMplsGroups 4 }
END -- of PW-MPLS-STD-MIB
8 Security Considerations
Zelig et al Expires June 2004 [page 20]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
It is clear that this MIB module is potentially useful for
monitoring of PW capable PEs. This MIB module can also be used for
configuration of certain objects, and anything that can be
configured can be incorrectly configured, with potentially
disastrous results.
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
o the pwVcMplsTable, pwVcMplsNonTeMappingTable and
pwVcMplsTeMappingTable collectively contain objects to
provision PW over MPLS tunnels. Unauthorized access to
objects in these tables, could result in disruption of
traffic on the network. The use of stronger mechanisms
such as SNMPv3 security should be considered where
possible. Specifically, SNMPv3 VACM and USM MUST be used
with any v3 agent which implements this MIB module.
Administrators should consider whether read access to these
objects should be allowed, since read access may be
undesirable under certain circumstances.
Some of the readable objects in this MIB module "i.e., objects with
a MAX-ACCESS other than not-accessible" may be considered sensitive
or vulnerable in some network environments. It is thus important
to control even GET and/or NOTIFY access to these objects and
possibly to even encrypt the values of these objects when sending
them over the network via SNMP. These are the tables and objects
and their sensitivity/vulnerability:
o the pwVcMplsTable, pwVcMplsNonTeMappingTable,
pwVcMplsTeMappingTable and pwVcMplsOutboundTable
collectively show the PW over MPLS association.
If an Administrator does not want to reveal this
information, then these tables should be
considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the
objects in this MIB module.
It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework "see [RFC3410], section 8",
Zelig et al Expires June 2004 [page 21]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access
to the objects only to those principals "users" that have
legitimate rights to indeed GET or SET "change/create/delete" them.
9 IANA considerations
As requested in the PW-TC-STD-MIB [PWTCMIB], PWE3 related standards
track MIB modules should be rooted under the pwStdMIB subtree. The
IANA is requested to assign { pwStdMIB 3 } to the PW-MPLS-STD-MIB
module specified in this document.
10 References
10.1 Normative references
[PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in-
progress.
[PWREQ] Xiao, X., et al, "Requirements for Pseudo Wire
Emulation Edge-to-Edge (PWE3)", work-in-progress.
[PWTC] Nadeau, T., et al, "Definitions for Textual Conventions
and OBJECT-IDENTITIES for Pseudo-Wires Management",
work-in-progress.
[PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management
Information Base", work-in-progress.
[IF-MIB] McCloghrie, K., Kastenholz, F., ôThe Interfaces Group
MIBö, RFC 2863, June 2000.
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC 3031,
Jan 2001.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, January 2001.
[LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
Label Switch Router Management Information Base Using
SMIv2", work-in-progress.
Zelig et al Expires June 2004 [page 22]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
[TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
Traffic Engineering Management Information Base Using
SMIv2", work-in-progress.
[MPLSTCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan,
A., Sjostrand, H. and K. Kompella, "Definition of
Textual Conventions and OBJECT-IDENTITIES for Multi-
Protocol Label Switching (MPLS) Management", work-in-
progress.
[LDP] Andersson, L., et al, "LDP specificationö, RFC 3036,
January 2001.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J.,Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
10.2 Informative references
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December
2002.
11 Author's Addresses
David Zelig
Corrigent Systems
126, Yigal Alon st.
Tel Aviv, ISRAEL
Phone: +972-3-6945273
Email: davidz@corrigent.com
Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Zelig et al Expires June 2004 [page 23]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
Chelmsford, MA 01824
Email: tnadeau@cisco.com
Dave Danenberg
Litchfield Communications, Inc.
76 Westbury Park Rd
Princeton Building East
Watertown, CT 06795
Email: dave_danenberg@litchfieldcomm.com
Andrew G. Malis
Tellabs, Inc.
2730 Orchard Parkway
San Jose, CA 95134
Email: Andy.Malis@tellabs.com
Sharon Mantin
AxONLink (Israel) Ltd
9 Bareket St.
Petah Tikva 49517, Israel
Phone: +972-3-9263972
Email: sharon.mantin@axonlink.com
12 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without restriction
of any kind, provided that the above copyright notice and this
paragraph are included on all such copies and derivative works.
However, this document itself may not be modified in any way, such
as by removing the copyright notice or references to the Internet
Society or other Internet organizations, except as needed for the
purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards process
must be followed, or as required to translate it into languages
other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. This
document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Zelig et al Expires June 2004 [page 24]
Pseudo Wire (PW) Over MPLS December 2003
Management Information Base
13 Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on
the IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF
Executive Director.
Zelig et al Expires June 2004 [page 25]
