draft-ietf-mpls-p2mp-te-mib-02.txt   draft-ietf-mpls-p2mp-te-mib-03.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: Sugust 2007 S. Yasukawa Expires: August 2007 S. Yasukawa
NTT NTT
T. Nadeau T. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
February 2007 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-02.txt draft-ietf-mpls-p2mp-te-mib-03.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 37 skipping to change at page 2, line 37
11. References ................................................... 45 11. References ................................................... 45
11.1. Normative References .................................... 45 11.1. Normative References .................................... 45
11.2. Informative References ..................................... 46 11.2. Informative References ..................................... 46
12. Authors' Addresses ........................................... 47 12. Authors' Addresses ........................................... 47
13. Intellectual Property ........................................ 47 13. Intellectual Property ........................................ 47
14. Full Copyright Statement ..................................... 48 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. - Typos.
- Minor text revisions for clarity and typos. - Move the Informational RFC 4461 to be an Informative Reference.
- Fix use of signaling protocol and broken hop index in example. - Updates to sections 4.2, 4.3, and 4.7 for clarity.
- 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
skipping to change at page 4, line 23 skipping to change at page 4, line 23
4. Outline 4. Outline
P2MP MPLS-TE requires that MPLS tunnels are established from a single P2MP MPLS-TE requires that MPLS tunnels are established from a single
source point (the root) to one or more destination points (the source point (the root) to one or more destination points (the
leaves). leaves).
Associated with the MPLS tunnel is a set of configured parameters Associated with the MPLS tunnel is a set of configured parameters
that describe the forwarding behavior of each LSR along the path of that describe the forwarding behavior of each LSR along the path of
the label switched paths (LSPs) that support the tunnel. It should the label switched paths (LSPs) that support the tunnel. It should
be noted that, according to [RFC4461] these configuration parameters be noted that, according to [RFC4461] these configuration parameters
are invariant across the branches of a P2MP LSP towards different are invariant across the branches of a P2MP LSP toward different
leaves. leaves.
One of the configuration parameters associated with an MPLS tunnel is One of the configuration parameters associated with an MPLS tunnel is
the path (or route) that supporting LSPs are required to follow. This the path (or route) that supporting LSPs are required to follow. This
can be specified as a series of loose or strict hops. In P2MP TE, can be specified as a series of loose or strict hops. In P2MP TE,
this specification of the LSP route includes implicit or explicit this specification of the LSP route includes implicit or explicit
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 a management process
[RFC3812] and the MIB module defined in this document by using [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 [RFC4802] defines a MIB module that can be used to manage Note that [RFC4802] defines a MIB module that can be used to manage
and model Generalized MPLS (GMPLS) 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.
skipping to change at page 5, line 9 skipping to change at page 5, line 9
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) sparse augments the - 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) lists the - The P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) lists
destinations (leaves) of each P2MP MPLS-TE tunnel, provides the the destinations (leaves) of each P2MP MPLS-TE tunnel, provides the
status of the tunnel to each destination, and supplies pointers status of the tunnel to each destination, and supplies pointers
into the configured hop table, actual route hop table, and computed into the configured hop table, actual route hop table, and computed
hop table (mplsTunnelHopTable, mplsTunnelARHopTable, and hop table (mplsTunnelHopTable, mplsTunnelARHopTable, and
mplsTunnelCHopTable) for the routes to each of the destinations. mplsTunnelCHopTable) for the routes to each of the destinations.
- A small collection of scalars (mplsTeP2mpTunnelConfigured, - A small collection of scalars (mplsTeP2mpTunnelConfigured,
mplsTeP2mpTunnelActive, and mplsTeP2mpTunnelTotalMaxHops) give mplsTeP2mpTunnelActive, and mplsTeP2mpTunnelTotalMaxHops) give
information about the P2MP behavior of the LSR. information about the P2MP behavior of the LSR.
These tables and scalars are described in the following sections These tables and scalars are described in the following sections
skipping to change at page 5, line 42 skipping to change at page 5, line 42
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 a conceptual row in
mplsTeP2mpTunnelTable of the MIB module defined in this document with the mplsTeP2mpTunnelTable of the MIB module defined in this document
the object mplsTeP2mpTunnel containing the value true(1) shows that with the object mplsTeP2mpTunnel containing the value true(1) shows
a tunnel defined in the mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP that a tunnel defined in the corresponding conceptual row of the
tunnel. Under those circumstances the following objects from mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP tunnel. Under those
MPLS-TE-STD-MIB MUST be interpreted as follows. The text below is circumstances the following scalars and objects from the appropriate
supplementary for the Description clauses in [RFC3812]. conceptual rows in MPLS-TE-STD-MIB MUST be interpreted as follows.
The text below is 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
of hops that can be configured on this device to any individual of hops that can be configured on this device to any individual
destination of the tunnel. destination of the tunnel.
A new object, mplsTeP2mpTunnelTotalMaxHops, is defined in this MIB A new object, mplsTeP2mpTunnelTotalMaxHops, is defined in this MIB
skipping to change at page 7, line 44 skipping to change at page 7, line 46
4.3. Scalars 4.3. Scalars
There are three scalars defined for this MIB module. There are three scalars defined for this MIB module.
mplsTeP2mpTunnelConfigured provides a read-only counter of the number mplsTeP2mpTunnelConfigured provides a read-only counter of the number
of P2MP MPLS-TE tunnels that are configured on this LSR through this of P2MP MPLS-TE tunnels that are configured on this LSR through this
MIB module. MIB module.
mplsTeP2mpTunnelActive provides a read-only counter of the number of mplsTeP2mpTunnelActive provides a read-only counter of the number of
P2MP MPLS-TE tunnels configured on this LSR that are currently P2MP MPLS-TE tunnels configured on this LSR through this MIB module
active. that are currently active.
As described in Section 4.2, mplsTeP2mpTunnelTotalMaxHops is a read- As described in Section 4.2, mplsTeP2mpTunnelTotalMaxHops is a read-
only scalar that reports the maximum number of explicit route hops only scalar that reports the maximum number of explicit route hops
supported by this LSR for any single P2MP LSP. supported by this LSR for any single P2MP LSP configured or monitored
through this MIB module.
4.4. mplsTeP2mpTunnelTable 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
any LSR in the network. at 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 the tunnel.
4.5. 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.6. 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, and 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 interfaces 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.7. 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].
An arrow in the figure shows that the MIB table pointed from contains
a reference to the MIB table pointed to.
mplsTunnelPerfTable mplsTunnelPerfTable
^ ^
| |
v v
mplsTunnelTable----------->mplsP2mpTunnelTable mplsTunnelTable----------->mplsP2mpTunnelTable
^ | | ^ | |
| | | | | |
| +--->mplsXCTable--+ v | +--->mplsXCTable--+ v
v | mplsP2mpTunnelDestTable v | mplsP2mpTunnelDestTable
mplsTunnelResourceTable | | | | mplsTunnelResourceTable | | | |
skipping to change at page 9, line 45 skipping to change at page 9, line 45
described in Section 4.2, certain of the objects in an entry in the described in Section 4.2, certain of the objects in an entry in the
mplsTunnelTable are not valid or have special meanings when the entry mplsTunnelTable are not valid or have special meanings when the entry
is used for a P2MP LSP tunnel. is used for a P2MP LSP tunnel.
When the MIB modules are used to configure a P2MP MPLS-TE LSP, an When the MIB modules are used to configure a P2MP MPLS-TE LSP, an
entry is first created in the mplsTunnelTable, and then corresponding entry is first created in the mplsTunnelTable, and then corresponding
entries are created in the mplsTeP2mpTunnelTable and the entries are created in the mplsTeP2mpTunnelTable and the
mplsTeP2mpTunnelDestTable from the MPLS-TE-P2MP-STD-MIB module mplsTeP2mpTunnelDestTable from the MPLS-TE-P2MP-STD-MIB module
defined in this document. The presence of a corresponding entry in defined in this document. The presence of a corresponding entry in
the mplsTeP2mpTunnelTable indicates that an entry in the the mplsTeP2mpTunnelTable indicates that an entry in the
mplsTunnelTable relates to P2MP not a P2P MPLS-TE LSP. Thus, the mplsTunnelTable relates to a P2MP not a P2P MPLS-TE LSP. Thus, the
mplsTunnelAdminStatus object should not be set to up(1) until the mplsTunnelAdminStatus object should not be set to up(1) until the
entries in the mplsTeP2mpTunnelTable and the entries in the mplsTeP2mpTunnelTable and the
mplsTeP2mpTunnelDestTable have been completed. mplsTeP2mpTunnelDestTable have been completed.
5.1. Example Use of the P2MP MPLS-TE MIB Module 5.1. Example Use of the P2MP MPLS-TE MIB Module
This section contains an example of the use of objects in This section contains an example of the use of objects in
MPLS-TE-STD-MIB and MPLS-TE-P2MP-STD-MIB to create a P2MP MPLS-TE MPLS-TE-STD-MIB and MPLS-TE-P2MP-STD-MIB to create a P2MP MPLS-TE
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.
skipping to change at page 15, line 21 skipping to change at page 15, line 21
mplsTunnelIngressLSRId = 192.168.100.1, mplsTunnelIngressLSRId = 192.168.100.1,
mplsTunnelEgressLSRId = 328, mplsTunnelEgressLSRId = 328,
-- Activate the tunnel -- Activate the tunnel
mplsAdminStatus = up(1) mplsAdminStatus = up(1)
} }
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module
The nature of P2MP tunnels is such that an LSR that is crossed by a The nature of P2MP tunnels is such that an LSR that is crossed by a
tunnel may either be the ingress of that tunnel or have precisely one tunnel may either be the ingress of that tunnel or have precisely one
upstream LSP segment (also known as in-segment [RFC3812]) for that upstream LSP segment (also known as an in-segment [RFC3812]) for that
LSP. On the other hand, any LSR that is crossed by a tunnel may be an LSP. On the other hand, any LSR that is crossed by a tunnel may be an
egress for that tunnel, have one or more downstream segments (also egress for that tunnel, have one or more downstream segments (also
known as out-segments [RFC3812]) for that tunnel, or be both an known as out-segments [RFC3812]) for that tunnel, or be both an
egress and have one or more out-segments. Thus, for an LSP at an LSR egress and have one or more out-segments. Thus, for an LSP at an LSR
there may be zero or one in-segments, and zero, one, or more than one there may be zero or one in-segments, and zero, one, or more than one
out-segments. out-segments.
In-segments, out-segments and their relationship through In-segments, out-segments, and their relationship through
cross-connections are modeled and managed in the MPLS-LSR-STD-MIB cross-connections are modeled and managed in the MPLS-LSR-STD-MIB
module [RFC3813]. The mplsInSegmentTable contains in-segments, and module [RFC3813]. The mplsInSegmentTable contains in-segments, and
the mplsOutSegmentTable contains out-segments. The mplsXCTable the mplsOutSegmentTable contains out-segments. The mplsXCTable
maintains the relationships between in- and out-segments such that maintains the relationships between in- and out-segments such that
any many-to-many relationship is allowed. Each segment points into any many-to-many relationship is allowed. Each segment points into
the mplsXCTable using mplsInSegmentXCIndex and mplsOutSegmentXCIndex. the mplsXCTable using mplsInSegmentXCIndex and mplsOutSegmentXCIndex.
The mplsXCTable contains a series of entries indexed by the primary The mplsXCTable contains a series of entries indexed by the primary
mplsXCIndex object and subsidiary indexes mplsXCInSegmentIndex and mplsXCIndex object and subsidiary indexes mplsXCInSegmentIndex and
mplsXCOutSegmentIndex. mplsXCOutSegmentIndex.
A single P2MP cross-connect has zero or one in-segment. At the A single P2MP cross-connect has zero or one in-segment. At the
ingress LSR, there is no in-segment and mplsXCInSegmentIndex is set ingress LSR, there is no in-segment and mplsXCInSegmentIndex is set
to the single octet 0x00. At transit LSRs, there is exactly one to the single octet 0x00. At transit LSRs, there is exactly one
in-segment and mplsXCInSegmentIndex is set to the value of in-segment and mplsXCInSegmentIndex is set to the value of
mplsInSegmentIndex for the in-segment as it appears in the mplsInSegmentIndex for the in-segment as it appears in the
mplsInSegmentTable. mplsInSegmentTable.
A single P2MP cross-connect has zero, one or many out-segments. If A single P2MP cross-connect has zero, one, or many out-segments. If
there is no out-segment (the cross-connect is on an egress LSR), there is no out-segment (the cross-connect is on an egress LSR),
there is one entry in the mplsXCTable indexed by mplsXCIndex set to there is one entry in the mplsXCTable indexed by mplsXCIndex set to
mplsInSegmentXCIndex from the in-segment's entry in mplsInSegmentXCIndex from the in-segment's entry in
mplsInSegmentTable, mplsXCInSegmentIndex set to the value of mplsInSegmentTable, mplsXCInSegmentIndex set to the value of
mplsInSegmentIndex that identifies the in-segment in mplsInSegmentIndex that identifies the in-segment in
mplsInSegmentTable, and mplsXCOutSegmentIndex set to the single octet mplsInSegmentTable, and mplsXCOutSegmentIndex set to the single octet
0x00. This behavior is exactly as described in [RFC3813]. 0x00. This behavior is exactly as described in [RFC3813].
If there is exactly one out-segment (the cross-connect is on a If there is exactly one out-segment (the cross-connect is on a
transit LSR) then the behavior is also exactly as described in transit LSR) then the behavior is also exactly as described in
skipping to change at page 19, 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 "200702050000Z" -- February 05, 2007 LAST-UPDATED "200702240000Z" -- February 24, 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
skipping to change at page 20, line 25 skipping to change at page 20, line 25
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
"200702050000Z" -- February 05, 2007 "200702240000Z" -- February 24, 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 35, line 43 skipping to change at page 35, line 43
This object should be read in conjunction with This object should be read in conjunction with
mplsTeP2mpTunnelDestDiscontinuityTime." mplsTeP2mpTunnelDestDiscontinuityTime."
::= { mplsTeP2mpTunnelDestEntry 16 } ::= { mplsTeP2mpTunnelDestEntry 16 }
mplsTeP2mpTunnelDestDiscontinuityTime OBJECT-TYPE mplsTeP2mpTunnelDestDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this row's Counter32 objects expeirenced any one or more of this row's Counter32 objects experienced
a discontinuity. If no such discontinuity has occurred since a discontinuity. If no such discontinuity has occurred since
the last re-initialization of the local management the last re-initialization of the local management
subsystem, then this object contains a zero value." subsystem, then this object contains a zero value."
::= { mplsTeP2mpTunnelDestEntry 17 } ::= { mplsTeP2mpTunnelDestEntry 17 }
mplsTeP2mpTunnelDestAdminStatus OBJECT-TYPE mplsTeP2mpTunnelDestAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- ready to pass data up(1), -- ready to pass data
down(2), -- out of service down(2), -- out of service
testing(3) -- in some test mode testing(3) -- in some test mode
} }
skipping to change at page 40, line 21 skipping to change at page 40, line 21
This object should be read in conjunction with This object should be read in conjunction with
mplsTeP2mpTunnelBranchDiscontinuityTime." mplsTeP2mpTunnelBranchDiscontinuityTime."
::= { mplsTeP2mpTunnelBranchPerfEntry 6 } ::= { mplsTeP2mpTunnelBranchPerfEntry 6 }
mplsTeP2mpTunnelBranchDiscontinuityTime OBJECT-TYPE mplsTeP2mpTunnelBranchDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this row's Counter32 or COunter64 objects any one or more of this row's Counter32 or Counter64 objects
expeirenced a discontinuity. If no such discontinuity has experienced a discontinuity. If no such discontinuity has
occurred since the last re-initialization of the local occurred since the last re-initialization of the local
management subsystem, then this object contains a zero management subsystem, then this object contains a zero
value." value."
::= { mplsTeP2mpTunnelBranchPerfEntry 7 } ::= { mplsTeP2mpTunnelBranchPerfEntry 7 }
-- End of mplsTeP2mpTunnelBranchPerfTable -- End of mplsTeP2mpTunnelBranchPerfTable
-- Notifications. -- Notifications.
mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE
skipping to change at page 46, line 41 skipping to change at page 46, line 41
RFC 3812, June 2004. RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC 3813, (LSR) Router Management Information Base (MIB)", RFC 3813,
June 2004. June 2004.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC4461] S. Yasukawa, Editor "Signaling Requirements for
Point-to-Multipoint Traffic Engineered MPLS LSPs",
RFC4461, April 2006.
[P2MP-TE] Aggarwal, R., Papadimitriou, D., and Yasukawa, S., [P2MP-TE] Aggarwal, R., Papadimitriou, D., and Yasukawa, S.,
"Extensions to RSVP-TE for Point to Multipoint TE "Extensions to RSVP-TE for Point to Multipoint TE
LSPs", draft-ietf-mpls-rsvp-te-p2mp, work in progress. LSPs", draft-ietf-mpls-rsvp-te-p2mp, work in progress.
11.2. Informative References 11.2. Informative References
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
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.
[RFC4461] S. Yasukawa, Editor "Signaling Requirements for
Point-to-Multipoint Traffic Engineered MPLS LSPs",
RFC4461, April 2006.
[RFC4802] 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", RFC 4802, February 2007. Information Base", RFC 4802, February 2007.
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
 End of changes. 25 change blocks. 
40 lines changed or deleted 45 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/