draft-ietf-mpls-p2mp-te-mib-01.txt   draft-ietf-mpls-p2mp-te-mib-02.txt 
Network Working Group A. Farrel (Editor) Network Working Group A. Farrel (Editor)
Updates: RFC3812 Old Dog Consulting Updates: RFC3812 Old Dog Consulting
Intended Status: Standards Track Intended Status: Standards Track
Expires: May 2007 S. Yasukawa Expires: Sugust 2007 S. Yasukawa
NTT NTT
T. Nadeau T. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
November 2006 February 2007
Point-to-Multipoint Multiprotocol Label Switching (MPLS) Point-to-Multipoint Multiprotocol Label Switching (MPLS)
Traffic Engineering (TE) Management Information Base (MIB) module Traffic Engineering (TE) Management Information Base (MIB) module
draft-ietf-mpls-p2mp-te-mib-01.txt draft-ietf-mpls-p2mp-te-mib-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 13 skipping to change at page 2, line 13
Multiprotocol Label Switching-based traffic engineering. Multiprotocol Label Switching-based traffic engineering.
Table of Contents Table of Contents
1. Introduction .................................................. 2 1. Introduction .................................................. 2
2. The Internet-Standard Management Framework .................... 3 2. The Internet-Standard Management Framework .................... 3
3. Feature List .................................................. 3 3. Feature List .................................................. 3
4. Outline ....................................................... 4 4. Outline ....................................................... 4
4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module .. 5 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module .. 5
4.2. Use of MPLS-TE-STD-MIB ................................... 5 4.2. Use of MPLS-TE-STD-MIB ................................... 5
4.3. mplsTeP2mpTunnelTable .................................... 7 4.3. Scalars .................................................. 7
4.4. mplsTeP2mpTunnelDestTable ................................ 7 4.3. mplsTeP2mpTunnelTable .................................... 8
4.5. mplsTeP2mpTunnelBranchPerfTable .......................... 7 4.5. mplsTeP2mpTunnelDestTable ................................ 8
4.6. Relationships Between MIB Tables .......................... 8 4.6. mplsTeP2mpTunnelBranchPerfTable .......................... 8
5. Using the P2MP MPLS-TE MIB Module ............................. 8 4.7. Relationships Between MIB Tables ......................... 8
5.1. Example Use of the P2MP MPLS-TE MIB Module ............... 9 5. Using the P2MP MPLS-TE MIB Module ............................. 9
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ........ 14 5.1. Example Use of the P2MP MPLS-TE MIB Module .............. 10
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ........ 15
6.1. Example Use of the LSR MIB Module ....................... 16 6.1. Example Use of the LSR MIB Module ....................... 16
7. MPLS Traffic Engineering P2MP MIB Definitions ................ 18 7. MPLS Traffic Engineering P2MP MIB Definitions ................ 19
8. Security Considerations ...................................... 42 8. Security Considerations ...................................... 43
9. Acknowledgments .............................................. 44 9. Acknowledgments .............................................. 45
10. IANA Considerations .......................................... 44 10. IANA Considerations .......................................... 45
10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 44 10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 45
11. References ................................................... 44 11. References ................................................... 45
11.1. Normative References .................................... 44 11.1. Normative References .................................... 45
11.2. Informative References .................................... 45 11.2. Informative References ..................................... 46
12. Authors' Addresses ........................................... 46 12. Authors' Addresses ........................................... 47
13. Intellectual Property ........................................ 46 13. Intellectual Property ........................................ 47
14. Full Copyright Statement ..................................... 47 14. Full Copyright Statement ..................................... 48
0. Changes Since Previous Revision 0. Changes Since Previous Revision
[This section to be removed before publication as an RFC.] [This section to be removed before publication as an RFC.]
- Update references.
- Change boilerplate for IETF Trust. - Minor text revisions for clarity and typos.
- Add section 4.6 to show the relationship between MIB tables. - Fix use of signaling protocol and broken hop index in example.
- Fill out section 5 to show an example usage. - Section 4.3 to document MIB scalars.
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling In particular, it describes managed objects for modeling
point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS)
traffic engineering (TE). traffic engineering (TE).
MPLS is defined in [RFC3031] and a signaling protocol for MPLS is defined in [RFC3031] and a signaling protocol for
point-to-point (P2P) MPLS-TE (TE extensions to the Resource point-to-point (P2P) MPLS-TE (TE extensions to the Resource
Reservation Protocol - RSVP-TE) is defined in [RFC3209]. RSVP-TE is Reservation Protocol - RSVP-TE) is defined in [RFC3209]. RSVP-TE is
extended for use in a P2MP environment by [P2MP-TE] following the extended for use in a P2MP environment by [P2MP-TE] following the
requirements set out in [RFC4461]. requirements set out in [RFC4461].
[RFC3812] provides a MIB module for modeling and controlling P2P [RFC3812] provides a MIB module for modeling and controlling P2P
MPLS-TE in conjunction with Textual Conventions defined in [RFC3811]. MPLS-TE in conjunction with Textual Conventions defined in [RFC3811].
In addition, [RFC3813] defines a MIB module for modeling and In addition, [RFC3813] defines a MIB module for modeling and
controlling an MPLS label switching router (LSR) that may support controlling an MPLS Label Switching Router (LSR) that may support
MPLS-TE. An overview of MPLS MIB modules can be found in [RFC4221]. MPLS-TE. An overview of MPLS MIB modules can be found in [RFC4221].
This document defines a MIB module for managing and controlling P2MP This document defines a MIB module for managing and controlling P2MP
MPLS-TE. It builds on the objects and tables defined in [RFC3812] so MPLS-TE. It builds on the objects and tables defined in [RFC3812] so
that P2MP MPLS-TE management is an extension of P2P MPLS-TE that P2MP MPLS-TE management is an extension of P2P MPLS-TE
management. management.
In addition, this document provides a description of how to use the In addition, this document provides a description of how to use the
LSR MIB module [RFC3813] to model and control an LSR that supports LSR MIB module [RFC3813] to model and control an LSR that supports
P2MP MPLS-TE. P2MP MPLS-TE.
skipping to change at page 4, line 40 skipping to change at page 4, line 40
identification of the branch points in the P2MP LSPs. identification of the branch points in the P2MP LSPs.
The setup of P2MP tunnels can be achieved as: The setup of P2MP tunnels can be achieved as:
- management actions only, by using [RFC3813] - management actions only, by using [RFC3813]
- control plane actions under the direction of management by using - control plane actions under the direction of management by using
[RFC3812] and the MIB module defined in this document [RFC3812] and the MIB module defined in this document
- control plane actions under the direction of some other management - control plane actions under the direction of some other management
process, monitored using [RFC3812] and the MIB module defined in process, monitored using [RFC3812] and the MIB module defined in
this document. this document.
Note that [GMPLS-TE-MIB] defines a MIB module that can be used to Note that [RFC4802] defines a MIB module that can be used to manage
manage and model Generalized MPLS (GMPL) LSPs - it is a series of MIB and model Generalized MPLS (GMPLS) LSPs - it is a series of MIB
objects and tables some of which extend tables in MPLS-TE-STD-MIB objects and tables some of which extend tables in MPLS-TE-STD-MIB
[RFC3812]. [RFC4461] and [P2MP-TE] are clear that they apply to [RFC3812]. [RFC4461] and [P2MP-TE] are clear that they apply to
MPLS-TE [RFC3031] and GMPLS [RFC3945]. This document describes a MIB MPLS-TE [RFC3031] and GMPLS [RFC3945]. This document describes a MIB
module that can be used for both MPLS-TE and GMPLS P2MP LSPs. module that can be used for both MPLS-TE and GMPLS P2MP LSPs.
The following section describes the components of the P2MP MPLS-TE The following sections describe the components of the P2MP MPLS-TE
MIB module. The subsequent section provides an explanation and MIB module. The subsequent section provides an explanation and
example of how the P2MP MPLS-TE MIB module can be used for the example of how the P2MP MPLS-TE MIB module can be used for the
processes listed above in combination with the MPLS-TE MIB module processes listed above in combination with the MPLS-TE MIB module
defined in [RFC3812]. A further section describes how P2MP tunnels defined in [RFC3812]. A further section describes how P2MP tunnels
can be managed solely through the LSR MIB module defined in can be managed solely through the LSR MIB module defined in
[RFC3813], and gives an example. [RFC3813], and gives an example.
4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module
The MIB module consists of the following objects and tables: The MIB module consists of the following objects and tables:
- P2MP Tunnel table (mplsTeP2mpTunnelTable) that sparse augments the - P2MP Tunnel table (mplsTeP2mpTunnelTable) sparse augments the
MPLS-TE Tunnel table (mplsTunnelTable) and is used to set up and MPLS-TE Tunnel table (mplsTunnelTable) and is used to set up and
monitor P2MP MPLS-TE tunnels. monitor P2MP MPLS-TE tunnels.
- P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) that - P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) lists the
lists the destinations (leaves) of each P2MP MPLS-TE tunnel, destinations (leaves) of each P2MP MPLS-TE tunnel, provides the
provides the status of the tunnel to each destination, and status of the tunnel to each destination, and supplies pointers
supplies pointers into the configured hop table, actual route hop into the configured hop table, actual route hop table, and computed
table, and computed hop table (mplsTunnelHopTable, hop table (mplsTunnelHopTable, mplsTunnelARHopTable, and
mplsTunnelARHopTable, and mplsTunnelCHopTable) for the routes to mplsTunnelCHopTable) for the routes to each of the destinations.
each of the destinations.
These tables are described in the following sections after a - A small collection of scalars (mplsTeP2mpTunnelConfigured,
description of how the MPLS-TE-STD-MIB module [RFC3812] is used as a mplsTeP2mpTunnelActive, and mplsTeP2mpTunnelTotalMaxHops) give
basis for MIB management and modeling of P2MP MPLS-TE. information about the P2MP behavior of the LSR.
These tables and scalars are described in the following sections
after a description of how the MPLS-TE-STD-MIB module [RFC3812] is
used as a basis for MIB management and modeling of P2MP MPLS-TE.
4.2. Use of MPLS-TE-STD-MIB 4.2. Use of MPLS-TE-STD-MIB
The MIB module defined in this document builds on the objects and The MIB module defined in this document builds on the objects and
tables of MPLS-TE-STD-MIB defined in [RFC3812]. That is, most of the tables of MPLS-TE-STD-MIB defined in [RFC3812]. That is, most of the
basic properties of the MPLS tunnel are modeled and managed by basic properties of the MPLS tunnel are modeled and managed by
objects in MPLS-TE-STD-MIB, and new objects are only defined within objects in MPLS-TE-STD-MIB, and new objects are only defined within
this document where additional features or different behavior is this document where additional features or different behavior is
required. required.
When an MPLS-TE tunnel is a P2MP tunnel, certain objects in the When an MPLS-TE tunnel is a P2MP tunnel, certain objects in the
mplsTunnelTable have new meanings just as the signaling objects in mplsTunnelTable have new meanings just as the signaling objects in
RSVP-TE [RFC3209] have different meanings when the signaling messages RSVP-TE [RFC3209] have different meanings when the signaling messages
are used to establish P2MP LSPs [P2MP-TE]. are used to establish P2MP LSPs [P2MP-TE].
As indicated in the next section, the presence of the As indicated in the next section, the presence of the
mplsTeP2mpTunnelTable of the MIB module defined in this document with mplsTeP2mpTunnelTable of the MIB module defined in this document with
the object mplsTeP2mpTunnel containing the value True (1) shows that the object mplsTeP2mpTunnel containing the value true(1) shows that
a tunnel defined in the mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP a tunnel defined in the mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP
tunnel. Under those circumstances the following objects from tunnel. Under those circumstances the following objects from
MPLS-TE-STD-MIB MUST be interpreted as follows. The text below is MPLS-TE-STD-MIB MUST be interpreted as follows. The text below is
supplementary for the Description clauses in [RFC3812]. supplementary for the Description clauses in [RFC3812].
mplsTunnelMaxHops mplsTunnelMaxHops
This object continues to refer to the maximum number of hops that This object continues to refer to the maximum number of hops that
can be configured to a single destination for a tunnel on this can be configured to a single destination for a tunnel on this
device. Thus, for a P2MP tunnel, this refers to the maximum number device. Thus, for a P2MP tunnel, this refers to the maximum number
skipping to change at page 6, line 20 skipping to change at page 6, line 22
This object continues to map to the field in the RSVP-TE Session This object continues to map to the field in the RSVP-TE Session
Object that occupies the space used by the IPv4 Tunnel Endpoint Object that occupies the space used by the IPv4 Tunnel Endpoint
Address [RFC3209], but for a P2MP tunnel, this object does not Address [RFC3209], but for a P2MP tunnel, this object does not
identify an address of the egress of the tunnel. Instead it identify an address of the egress of the tunnel. Instead it
contains the P2MP ID value that identifies the identifier of the contains the P2MP ID value that identifies the identifier of the
set of destinations for the P2MP tunnel and is carried in the P2MP set of destinations for the P2MP tunnel and is carried in the P2MP
Session Object [P2MP-TE]. The Description clause for this object Session Object [P2MP-TE]. The Description clause for this object
can be read as follows. can be read as follows.
"Identity of the egress LSR associated with this "Identity of the egress LSR associated with this tunnel
tunnel instance. instance.
When an entry in the mplsTeP2mpTunnelTable is present When an entry in the mplsTeP2mpTunnelTable is present
corresponding to this entry in the mplsTunnelTable and when corresponding to this entry in the mplsTunnelTable and when
the mplsTeP2mpTunnel object in that table entry is present the mplsTeP2mpTunnel object in that table entry is present
with the value True(1), this object contains the P2MP ID that with the value true(1), this object contains the P2MP ID that
identifies the set of destinations of this tunnel and that is identifies the set of destinations of this tunnel and that is
signaled in the P2MP ID field of the P2MP Session Object if signaled in the P2MP ID field of the P2MP Session Object if
the MPLS signaling protocol for this tunnel indicated by the MPLS signaling protocol for this tunnel indicated by
mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp (2)." mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp (2)."
The destinations of the P2MP tunnel are found in the new The destinations of the P2MP tunnel are found in the new
mplsTeP2mpTunnelDestTable. mplsTeP2mpTunnelDestTable.
mplsTunnelHopTableIndex mplsTunnelHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel
and when the mplsTeP2mpTunnel object in that table entry is and when the mplsTeP2mpTunnel object in that table entry is
present with the value True (1), this object is not used. This is present with the value true(1), this object is not used. This is
because the destinations and paths to those destinations are found because the destinations and paths to those destinations are found
in the mplsTeP2mpTunnelDestTable. in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it should contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelPathInUse mplsTunnelPathInUse
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel
and when the mplsTeP2mpTunnel object in that table entry is and when the mplsTeP2mpTunnel object in that table entry is
present with the value True(1), this object is not used. This is present with the value true(1), this object is not used. This is
because the destinations and paths to those destinations are found because the destinations and paths to those destinations are found
in the mplsTeP2mpTunnelDestTable. in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it should contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelARHopTableIndex mplsTunnelARHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel
and when the mplsTeP2mpTunnel object in that table entry is and when the mplsTeP2mpTunnel object in that table entry is
present with the value True(1), this object is not used. This is present with the value true(1), this object is not used. This is
because the destinations and paths to those destinations are found because the destinations and paths to those destinations are found
in the mplsTeP2mpTunnelDestTable. in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it should contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
mplsTunnelCHopTableIndex mplsTunnelCHopTableIndex
If the tunnel is a P2MP tunnel as indicated by the presence of an If the tunnel is a P2MP tunnel as indicated by the presence of an
entry in the mplsTeP2mpTunnelTable corresponding to this tunnel entry in the mplsTeP2mpTunnelTable corresponding to this tunnel
and when the mplsTeP2mpTunnel object in that table entry is and when the mplsTeP2mpTunnel object in that table entry is
present with the value True(1), this object is not used. This is present with the value true(1), this object is not used. This is
because the destinations and paths to those destinations are found because the destinations and paths to those destinations are found
in the mplsTeP2mpTunnelDestTable. in the mplsTeP2mpTunnelDestTable.
If this object is present for a P2MP tunnel, it should contain the If this object is present for a P2MP tunnel, it SHOULD contain the
value 0. value 0.
4.3. mplsTeP2mpTunnelTable 4.3. Scalars
There are three scalars defined for this MIB module.
mplsTeP2mpTunnelConfigured provides a read-only counter of the number
of P2MP MPLS-TE tunnels that are configured on this LSR through this
MIB module.
mplsTeP2mpTunnelActive provides a read-only counter of the number of
P2MP MPLS-TE tunnels configured on this LSR that are currently
active.
As described in Section 4.2, mplsTeP2mpTunnelTotalMaxHops is a read-
only scalar that reports the maximum number of explicit route hops
supported by this LSR for any single P2MP LSP.
4.4. mplsTeP2mpTunnelTable
The mplsTeP2mpTunnelTable extends (through a sparse augmentation) the The mplsTeP2mpTunnelTable extends (through a sparse augmentation) the
MPLS Tunnel table (mplsTunnelTable) from MPLS-TE-STD-MIB [RFC3812] to MPLS Tunnel table (mplsTunnelTable) from MPLS-TE-STD-MIB [RFC3812] to
allow P2MP MPLS-TE tunnels to be created, controlled and monitored at allow P2MP MPLS-TE tunnels to be created, controlled and monitored at
any LSR in the network. any LSR in the network.
A P2MP MPLS-TE tunnel may be represented in the MIB, by defining it A P2MP MPLS-TE tunnel may be represented in the MIB, by defining it
in the mplsTunnelTable and providing objects in this table to in the mplsTunnelTable and providing objects in this table to
indicate that it is a P2MP tunnel and to define P2MP-specific indicate that it is a P2MP tunnel and to define P2MP-specific
properties of this tunnel. properties of this tunnel.
4.4. mplsTeP2mpTunnelDestTable 4.5. mplsTeP2mpTunnelDestTable
P2MP LSPs have multiple destinations and, although the LSP parameters P2MP LSPs have multiple destinations and, although the LSP parameters
(such as bandwidth) for each destination are the same, the explicit (such as bandwidth) for each destination are the same, the explicit
route requested, computed, and signaled is different for each route requested, computed, and signaled is different for each
destination. The mplsTeP2mpTunnelDestTable encodes each destination destination. The mplsTeP2mpTunnelDestTable encodes each destination
and the information specific to the LSP to that destination. and the information specific to the LSP to that destination.
4.5. mplsTeP2mpTunnelBranchPerfTable 4.6. mplsTeP2mpTunnelBranchPerfTable
Per-tunnel statistics are counted in mplsTunnelPerfTable in Per-tunnel statistics are counted in mplsTunnelPerfTable in
MPLS-TE-STD-MIB [RFC3812], but these objects are only partially MPLS-TE-STD-MIB [RFC3812], but these objects are only partially
useful for a P2MP tunnel. The five objects in that table useful for a P2MP tunnel. The five objects in that table
(mplsTunnelPerfPackets, mplsTunnelPerfHCPackets, (mplsTunnelPerfPackets, mplsTunnelPerfHCPackets,
mplsTunnelPerfErrors, mplsTunnelPerfBytes, mplsTunnelPerfHCBytes) mplsTunnelPerfErrors, mplsTunnelPerfBytes, mplsTunnelPerfHCBytes)
continue to be used for tunnels that forward packets, and reflect continue to be used for tunnels that forward packets, and reflect
the counts of data received on the incoming interface and forwarded the counts of data received on the incoming interface and forwarded
to the downstream interfaces. to the downstream interfaces.
However, in a P2MP tunnel, the downstream interfaces (out-segments) However, in a P2MP tunnel, the downstream interfaces (out-segments)
may behave differently and so it is appropriate to record the may behave differently and so it is appropriate to record the
performance on each out-going branch. This is achieved through the performance on each out-going branch. This is achieved through the
mplsTeP2mpTunnelBranchPerfTable which is indexed by the tunnel mplsTeP2mpTunnelBranchPerfTable which is indexed by the tunnel
identifiers and by the same identifier of the branch as is used in identifiers and by the same identifier of the branch as is used in
mplsTeP2mpTunnelDestTable. mplsTeP2mpTunnelDestTable.
4.6. Relationships Between MIB Tables 4.7. Relationships Between MIB Tables
This section provides a diagramatic representation of the This section provides a diagramatic representation of the
relationships between MIB tables defined in this document as part of relationships between MIB tables defined in this document as part of
MPLS-TE-P2MP-STD-MIB, and the tables defined in MPLS-TE-STD-MIB in MPLS-TE-P2MP-STD-MIB, and the tables defined in MPLS-TE-STD-MIB in
[RFC3812] and MPLS-LSR-STD-MIB in [RFC3813]. The dependencies [RFC3812] and MPLS-LSR-STD-MIB in [RFC3813]. The dependencies
between the various pre-existing MPLS-TE and LSR MIB tables can be between the various pre-existing MPLS-TE and LSR MIB tables can be
seen in [RFC4221]. seen in [RFC4221].
mplsTunnelPerfTable mplsTunnelPerfTable
^ ^
skipping to change at page 9, line 37 skipping to change at page 10, line 19
LSP. Note that the objects described should be created on the LSP. Note that the objects described should be created on the
"head-end" LSR. "head-end" LSR.
The RowStatus values shown in this section are those to be used in The RowStatus values shown in this section are those to be used in
the set request, typically createAndGo(4) which is used to create the the set request, typically createAndGo(4) which is used to create the
conceptual row and have its status immediately set to active. A conceptual row and have its status immediately set to active. A
subsequent retrieval operation on the conceptual row will return a subsequent retrieval operation on the conceptual row will return a
different value, such as active(1). Please see [RFC2579] for a different value, such as active(1). Please see [RFC2579] for a
detailed discussion on the use of RowStatus. detailed discussion on the use of RowStatus.
Figure 2 shows the simple topology of the pospective LSP from its Figure 2 shows the simple topology of the prospective LSP from its
root at LSR R, through a branch node at LSR B, to its two root at LSR R, through a branch node at LSR B, to its two
destinations, LSRs D1 and D2. destinations, LSRs D1 and D2.
C1---D1 C1---D1
/ /
/ /
R---A---B R---A---B
\ \
\ \
C2---D2 C2---D2
skipping to change at page 10, line 45 skipping to change at page 11, line 27
mplsTunnelIngressLSRId = 192.168.100.1, mplsTunnelIngressLSRId = 192.168.100.1,
-- The tunnel egress LSR ID is used to -- The tunnel egress LSR ID is used to
-- hold the P2MP ID for the P2MP LSP tunnel -- hold the P2MP ID for the P2MP LSP tunnel
mplsTunnelEgressLSRId = 328, mplsTunnelEgressLSRId = 328,
mplsTunnelName = "My first P2MP tunnel", mplsTunnelName = "My first P2MP tunnel",
mplsTunnelDescr = "Here to there and there", mplsTunnelDescr = "Here to there and there",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
-- There is no cross-connect present yet -- There is no cross-connect present yet
mplsTunnelXCPointer = 0.0, mplsTunnelXCPointer = 0.0,
-- This table entry is created by configuration no signaling -- This table entry is created by configuration no signaling
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = rsvp(2),
mplsTunnelSetupPrio = 0, mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 7, mplsTunnelHoldingPrio = 7,
mplsTunnelSessionAttributes = 0, mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (2), mplsTunnelLocalProtectInUse = false (2),
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.9, mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.9,
mplsTunnelInstancePriority = 1, mplsTunnelInstancePriority = 1,
-- The index to the mplsTunnelHopTable from this table -- The index to the mplsTunnelHopTable from this table
-- is not used -- is not used
mplsTunnelHopTableIndex = 0, mplsTunnelHopTableIndex = 0,
mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0, mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0, mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1, mplsTunnelPathInUse = 1,
mplsTunnelRole = head (1), mplsTunnelRole = head (1),
-- Tunnel is not ready for admin status up -- Tunnel is not ready for admin status up
mplsAdminStatus = down (2), mplsAdminStatus = down (2),
mplsTunnelRowStatus = createAndGo (4) mplsTunnelRowStatus = createAndGo (4)
} }
Note that any active or signaled instances of the above tunnel would Note that any active or signaled instances of the above tunnel
appear with the same primary mplsTunnelIndex, but would have values would appear with the same primary mplsTunnelIndex, but would have
greater than 0 for mplsTunnelInstance. They would also have other values greater than 0 for mplsTunnelInstance. They would also have
objects such as the mplsTunnelXCPointer set accordingly. other objects such as the mplsTunnelXCPointer set accordingly.
Step 3 - Create the P2MP Tunnel Step 3 - Create the P2MP Tunnel
In mplsTeP2mpTunnelTable define as follows: In mplsTeP2mpTunnelTable define as follows:
{ {
mplsTeP2mpTunnelIsP2MP = true (1), mplsTeP2mpTunnelIsP2MP = true (1),
mplsTeP2mpTunnelP2mpIntegrity = true (1), mplsTeP2mpTunnelP2mpIntegrity = true (1),
-- This is the head end of the LSP and not a branch -- This is the head end of the LSP and not a branch
mplsTeP2mpTunnelBranchRole = notBranch (1), mplsTeP2mpTunnelBranchRole = notBranch (1),
skipping to change at page 12, line 40 skipping to change at page 13, line 21
mplsTunnelHopType = strict (2), mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2), mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3, mplsTunnelHopIndex = 4,
mplsTunnelHopAddrType = ipv4 (1), mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.104.1", mplsTunnelHopIpAddr = "192.168.104.1",
mplsTunnelHopIpPrefixLen = 32, mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2), mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1), mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there", mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2), mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4) mplsTunnelHopRowStatus = createAndGo (4)
} }
skipping to change at page 18, line 34 skipping to change at page 19, line 34
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId mplsTunnelEgressLSRId
FROM MPLS-TE-STD-MIB -- RFC3812 FROM MPLS-TE-STD-MIB -- RFC3812
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC3289 FROM DIFFSERV-MIB -- RFC3289
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- RFC3291 FROM INET-ADDRESS-MIB -- RFC3291
; ;
mplsTeP2mpStdMIB MODULE-IDENTITY mplsTeP2mpStdMIB MODULE-IDENTITY
LAST-UPDATED "200611230000Z" -- November 23, 2006 LAST-UPDATED "200702050000Z" -- February 05, 2007
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Adrian Farrel " Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Seisho Yasukawa Seisho Yasukawa
NTT Corporation NTT Corporation
Email: s.yasukawa@hco.ntt.co.jp Email: s.yasukawa@hco.ntt.co.jp
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Comments about this document should be emailed Comments about this document should be emailed
directly to the MPLS working group mailing list at directly to the MPLS working group mailing list at
mpls@lists.ietf.org" mpls@lists.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2006). The initial version of "Copyright (C) The IETF Trust (2007). The initial version of
this MIB module was published in RFC XXXX. For full legal this MIB module was published in RFC XXXX. For full legal
notices see the RFC itself or see: notices see the RFC itself or see:
http://www.ietf.org/copyrights/ianamib.html http://www.ietf.org/copyrights/ianamib.html
-- RFC Editor. Please replace XXXX with the RFC number for this -- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note. -- document and remove this note.
This MIB module contains managed object definitions This MIB module contains managed object definitions
for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
defined in: defined in:
1. Signaling Requirements for Point-to-Multipoint 1. Signaling Requirements for Point-to-Multipoint
Traffic-Engineered MPLS Label Switched Paths (LSPs), Traffic-Engineered MPLS Label Switched Paths (LSPs),
S. Yasukawa, RFC 4461, April 2006. S. Yasukawa, RFC 4461, April 2006.
2. Extensions to RSVP-TE for Point to Multipoint TE LSPs, 2. Extensions to RSVP-TE for Point to Multipoint TE LSPs,
R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in
progress." progress."
-- Revision history. -- Revision history.
REVISION REVISION
"200611230000Z" -- November 23, 2006 "200702050000Z" -- February 05, 2007
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXXX." "Initial version issued as part of RFC XXXX."
-- RFC Editor. Please replace XXXX with the RFC number for this -- RFC Editor. Please replace XXXX with the RFC number for this
-- document and remove this note. -- document and remove this note.
::= { mplsStdMIB YYY } ::= { mplsStdMIB YYY }
-- RFC Editor. Please replace YYY with the codepoint issued by IANA -- RFC Editor. Please replace YYY with the codepoint issued by IANA
-- and remove this note. -- and remove this note.
skipping to change at page 46, line 13 skipping to change at page 47, line 13
October 1998. October 1998.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statement for Internet "Introduction and Applicability Statement for Internet
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Label Switching (MPLS) Management Overview", RFC 4221, Label Switching (MPLS) Management Overview", RFC 4221,
November 2005. November 2005.
[GMPLS-TE-MIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [RFC4802] Nadeau, T. and A. Farrel, "Generalized Multiprotocol
Label Switching (GMPLS) Traffic Engineering Management Label Switching (GMPLS) Traffic Engineering Management
Information Base", draft-ietf-ccamp-gmpls-te-mib, work Information Base", RFC 4802, February 2007.
in progress.
12. Authors' Addresses 12. Authors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Seisho Yasukawa Seisho Yasukawa
NTT Corporation NTT Corporation
9-11, Midori-Cho 3-Chome 9-11, Midori-Cho 3-Chome
skipping to change at page 47, line 13 skipping to change at page 48, line 13
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
14. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The IETF Trust (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 38 change blocks. 
70 lines changed or deleted 90 lines changed or added

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