draft-ietf-mpls-p2mp-te-mib-00.txt   draft-ietf-mpls-p2mp-te-mib-01.txt 
Network Working Group A. Farrel (Editor)
Network Working Group Adrian Farrel (Editor)
Updates: RFC3812 Old Dog Consulting Updates: RFC3812 Old Dog Consulting
Category: Standards Track Seisho Yasukawa Intended Status: Standards Track
Expires: March 2007 NTT Expires: May 2007 S. Yasukawa
Thomas D. Nadeau NTT
T. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
September 2006 November 2006
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-00.txt draft-ietf-mpls-p2mp-te-mib-01.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 7 skipping to change at page 2, line 7
Abstract Abstract
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
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 point-to-multipoint In particular, it describes managed objects for point-to-multipoint
Multiprotocol Label Switching-based traffic engineering. Multiprotocol Label Switching-based traffic engineering.
Table of Contents Table of Contents
1. Introduction .................................................. 3 1. Introduction .................................................. 2
2. The Internet-Standard Management Framework .................... 4 2. The Internet-Standard Management Framework .................... 3
3. Feature List .................................................. 4 3. Feature List .................................................. 3
4. Outline ....................................................... 5 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 ................................... 6 4.2. Use of MPLS-TE-STD-MIB ................................... 5
4.3. mplsTeP2mpTunnelTable .................................... 8 4.3. mplsTeP2mpTunnelTable .................................... 7
4.4. mplsTeP2mpTunnelDestTable ................................ 8 4.4. mplsTeP2mpTunnelDestTable ................................ 7
4.5. mplsTeP2mpTunnelBranchPerfTable .......................... 9 4.5. mplsTeP2mpTunnelBranchPerfTable .......................... 7
5. Using the P2MP MPLS-TE MIB Module ............................. 9 4.6. Relationships Between MIB Tables .......................... 8
5. Using the P2MP MPLS-TE MIB Module ............................. 8
5.1. Example Use of the P2MP MPLS-TE MIB Module ............... 9 5.1. Example Use of the P2MP MPLS-TE MIB Module ............... 9
5.2. Remerge Cases in the P2MP MPLS-TE MIB Module ............. 9 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ........ 14
6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ......... 9 6.1. Example Use of the LSR MIB Module ....................... 16
6.1. Example Use of the LSR MIB Module ....................... 11 7. MPLS Traffic Engineering P2MP MIB Definitions ................ 18
6.2. Remerge Cases in the LSR MIB Module ..................... 12 8. Security Considerations ...................................... 42
7. MPLS Traffic Engineering P2MP MIB Definitions ................ 13 9. Acknowledgments .............................................. 44
8. Security Considerations ...................................... 37 10. IANA Considerations .......................................... 44
9. Acknowledgments .............................................. 39 10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 44
10. IANA Considerations .......................................... 39 11. References ................................................... 44
10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 39 11.1. Normative References .................................... 44
11. References ................................................... 39 11.2. Informative References .................................... 45
11.1. Normative References .................................... 39 12. Authors' Addresses ........................................... 46
11.2. Informative References .................................... 40 13. Intellectual Property ........................................ 46
12. Authors' Addresses ........................................... 41 14. Full Copyright Statement ..................................... 47
13. Intellectual Property ........................................ 41
14. Full Copyright Statement ..................................... 42
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.]
Rename mplsMp2pGroups to mplsP2mpGroups. - Change boilerplate for IETF Trust.
- Add section 4.6 to show the relationship between MIB tables.
Rename everything mplsP2mp* to mplsTeP2mp*, and everything MplsP2mp* - Fill out section 5 to show an example usage.
to MplsTeP2mp*
Rename members of mplsTeP2mpDestEntry to be consistently named.
mplsTeP2mpTunnelSubGroupIDNext SYNTAX changed to reflect same range
as mplsTeP2mpTunnelSubGroupID.
mplsTeP2mpTunnelDestination and mplsTeP2mpTunnelSubGroupOrigin given
SIZE clauses in their SYNTAX.
Change special value of mplsTeP2mpTunnelBranchOutSegment to be a
single octet with value 0x00.
Change reference to sysUpTIme (from SysUpTime) in
mplsTeP2mpTunnelDestCreationTime.
Added mplsTeP2mpTunnelDestDiscontinuityTime.
Added mplsTeP2mpTunnelBranchDiscontinuityTime.
Add clarification of mplsTeP2mpTunnelDestOperStatus with regard to
mplsTunnelOperStatus.
Add mplsTeP2mpTunnelBranch as an index to
mplsTeP2mpTunnelBranchPerftable.
Add mplsTeP2mpTunnelSubGroupOriginType,
mplsTeP2mpTunnelSubGroupOrigin, and mplsTeP2mpTunnelSubGroupID to
record the Sub-Group Fields received on an incoming Path message.
Minor typos throughout.
Supply missing text in section 4.5.
Add a placeholder for text to describe the remerge cases (sections
5.2 and 6.2).
Acknowledgments updated.
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 34 skipping to change at page 3, line 45
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Feature List 3. Feature List
The feature list for this MIB module is built on the feature list for The feature list for this MIB module is built on the feature list for
the P2P MPLS-TE MIB module [RFC3812]. The features in the list below the P2P MPLS-TE MIB module [RFC3812]. The features in the list below
are marked with a star (*) if they are new features for this MIB are marked with a star (*) if they are new features for this MIB
module and with a circle (o) if they are features satisfied by module and with a circle (o) if they are satisfied by [RFC3812].
[RFC3812].
* The MIB module supports configuration of point-to-multipoint * The MIB module supports configuration of point-to-multipoint
unidirectional tunnels. unidirectional tunnels.
o MPLS tunnels need not be interfaces, but it is possible to o MPLS tunnels need not be interfaces, but it is possible to
configure a tunnel as an interface. configure a tunnel as an interface.
o The MIB module supports tunnel establishment via an MPLS o The MIB module supports tunnel establishment via an MPLS
signaling protocol wherein the tunnel parameters are specified signaling protocol wherein the tunnel parameters are specified
using this MIB module at the head end of the LSP, and end-to-end using this MIB module at the head end of the LSP, and end-to-end
skipping to change at page 9, line 23 skipping to change at page 8, line 18
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
This section provides a diagramatic representation of the
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
[RFC3812] and MPLS-LSR-STD-MIB in [RFC3813]. The dependencies
between the various pre-existing MPLS-TE and LSR MIB tables can be
seen in [RFC4221].
mplsTunnelPerfTable
^
|
v
mplsTunnelTable----------->mplsP2mpTunnelTable
^ | |
| | |
| +--->mplsXCTable--+ v
v | mplsP2mpTunnelDestTable
mplsTunnelResourceTable | | | |
^ | | | +--->mplsTunnelHopTable
| | | | +--->mplsTunnelCHopTable
mplsInSegmentTable<-----+ | | +--->mplsTunnelARHopTable
| | |
v | |
mplsOutSegmentTable<---+ |
v
mplsP2mpTunnelBranchPerfTable
Figure 1 : Dependencies Between MIB Tables
5. Using the P2MP MPLS-TE MIB Module 5. Using the P2MP MPLS-TE MIB Module
TBD This section describes how to use the P2MP MPLS-TE MIB module defined
in this document to manage and model P2MP MPLS-TE LSPs. A subsection
gives an example of usage.
A P2MP MPLS-TE LSP is modeled as a single LSP tunnel. That is, there
is a single entry in the mplsTunnelTable of the MPLS-TE-STD-MIB
defined in [RFC3812] for each instance of a P2MP LSP tunnel. As
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
is used for a P2MP LSP tunnel.
When the MIB modules are used to configure a P2MP MPLS-TE LSP, an
entry is first created in the mplsTunnelTable, and then corresponding
entries are created in the mplsTeP2mpTunnelTable and the
mplsTeP2mpTunnelDestTable from the MPLS-TE-P2MP-STD-MIB module
defined in this document. The presence of a corresponding entry in
the mplsTeP2mpTunnelTable indicates that an entry in the
mplsTunnelTable relates to P2MP not a P2P MPLS-TE LSP. Thus, the
mplsTunnelAdminStatus object should not be set to up(1) until the
entries in the mplsTeP2mpTunnelTable and the
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
TBD 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
LSP. Note that the objects described should be created on the
"head-end" LSR.
5.2. Remerge Cases in the P2MP MPLS-TE MIB Module 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
conceptual row and have its status immediately set to active. A
subsequent retrieval operation on the conceptual row will return a
different value, such as active(1). Please see [RFC2579] for a
detailed discussion on the use of RowStatus.
TBD Figure 2 shows the simple topology of the pospective LSP from its
root at LSR R, through a branch node at LSR B, to its two
destinations, LSRs D1 and D2.
C1---D1
/
/
R---A---B
\
\
C2---D2
Figure 2 : Topology of a simple P2MP MPLS-TE LSP
Let us assign IP addresses to the LSRs as follows:
R 192.168.100.1
A 192.168.101.1
B 192.168.102.1
C1 192.168.103.1
C2 192.168.103.10
D1 192.168.104.1
D2 192.168.104.10
Step 1 - Define the resource requirements for the LSP
Let us assume that we require a best effort LSP.
In mplsTunnelResourceTable define as follows:
{
mplsTunnelResourceIndex = 9,
mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceMeanBurstSize = 0,
mplsTunnelResourceExBurstSize = 0,
mplsTunnelResourceExBurstSize = unspecified (1),
mplsTunnelResourceWeight = 0,
mplsTunnelResourceRowStatus = createAndGo (4)
}
Step 2 - Define the core parameters for the LSP tunnel.
In mplsTunnelTable define as follows:
{
mplsTunnelIndex = 4,
mplsTunnelInstance = 0,
mplsTunnelIngressLSRId = 192.168.100.1,
-- The tunnel egress LSR ID is used to
-- hold the P2MP ID for the P2MP LSP tunnel
mplsTunnelEgressLSRId = 328,
mplsTunnelName = "My first P2MP tunnel",
mplsTunnelDescr = "Here to there and there",
mplsTunnelIsIf = true (1),
-- There is no cross-connect present yet
mplsTunnelXCPointer = 0.0,
-- This table entry is created by configuration no signaling
mplsTunnelSignallingProto = none (1),
mplsTunnelSetupPrio = 0,
mplsTunnelHoldingPrio = 7,
mplsTunnelSessionAttributes = 0,
mplsTunnelLocalProtectInUse = false (2),
mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.9,
mplsTunnelInstancePriority = 1,
-- The index to the mplsTunnelHopTable from this table
-- is not used
mplsTunnelHopTableIndex = 0,
mplsTunnelIncludeAnyAffinity = 0,
mplsTunnelIncludeAllAffinity = 0,
mplsTunnelExcludeAnyAffinity = 0,
mplsTunnelPathInUse = 1,
mplsTunnelRole = head (1),
-- Tunnel is not ready for admin status up
mplsAdminStatus = down (2),
mplsTunnelRowStatus = createAndGo (4)
}
Note that any active or signaled instances of the above tunnel would
appear with the same primary mplsTunnelIndex, but would have values
greater than 0 for mplsTunnelInstance. They would also have other
objects such as the mplsTunnelXCPointer set accordingly.
Step 3 - Create the P2MP Tunnel
In mplsTeP2mpTunnelTable define as follows:
{
mplsTeP2mpTunnelIsP2MP = true (1),
mplsTeP2mpTunnelP2mpIntegrity = true (1),
-- This is the head end of the LSP and not a branch
mplsTeP2mpTunnelBranchRole = notBranch (1),
mplsTeP2mpTunnelSubGroupOriginType = ipv4 (1),
mplsTeP2mpTunnelSubGroupOrigin = 192.168.100.1,
mplsTeP2mpTunnelSubGroupID = 132,
mplsTeP2mpTunnelRowStatus = createAndGo (4)
}
Step 4 - Create the configured explicit routes for the LSP
Two pieces of explicit path are required. The first runs from R to
D1, and the second from B to D2. See [P2MP-TE] for a discussion of
the construction of explicit routes for P2MP MPLS-TE LSPs.
In mplsTunnelHopTable define as follows:
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.101.1",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.102.1",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.103.1",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.104.1",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.102.1",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.103.10",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
{
mplsTunnelHopListIndex = 2,
mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 3,
mplsTunnelHopAddrType = ipv4 (1),
mplsTunnelHopIpAddr = "192.168.104.10",
mplsTunnelHopIpPrefixLen = 32,
mplsTunnelHopType = strict (2),
mplsTunnelHopInclude = true (1),
mplsTunnelHopPathOptionName = "Here to there",
mplsTunnelHopEntryPathComp = explicit (2),
mplsTunnelHopRowStatus = createAndGo (4)
}
Step 5 - Create the destinations for the P2MP LSP tunnel
In mplsTeP2mpTunnelDestTable define as follows:
{
mplsTeP2mpTunnelDestSubGroupOriginType = ipv4 (1),
mplsTeP2mpTunnelDestSubGroupOrigin = 192.168.100.1,
mplsTeP2mpTunnelDestSubGroupID = 132,
mplsTeP2mpTunnelDestDestinationType = ipv4 (1),
mplsTeP2mpTunnelDestDestination = 192.168.104.1,
mplsTeP2mpTunnelDestHopTableIndex = 1,
mplsTeP2mpTunnelDestPathInUse = 1,
mplsTeP2mpTunnelDestAdminStatus = up (1),
mplsTeP2mpTunnelDestRowStatus = createAndGo (4)
}
{
mplsTeP2mpTunnelDestSubGroupOriginType = ipv4 (1),
mplsTeP2mpTunnelDestSubGroupOrigin = 192.168.100.1,
mplsTeP2mpTunnelDestSubGroupID = 132,
mplsTeP2mpTunnelDestDestinationType = ipv4 (1),
mplsTeP2mpTunnelDestDestination = 192.168.104.10,
mplsTeP2mpTunnelDestHopTableIndex = 2,
mplsTeP2mpTunnelDestPathInUse = 1,
mplsTeP2mpTunnelDestAdminStatus = up (1),
mplsTeP2mpTunnelDestRowStatus = createAndGo (4)
}
Step 6 - Activate the tunnel
In mplsTunnelTable define as follows:
{
mplsTunnelIndex = 4,
mplsTunnelInstance = 0,
mplsTunnelIngressLSRId = 192.168.100.1,
mplsTunnelEgressLSRId = 328,
-- Activate the tunnel
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 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
skipping to change at page 11, line 13 skipping to change at page 16, line 13
exist for each out-segment. exist for each out-segment.
6.1. Example Use of the LSR MIB Module 6.1. Example Use of the LSR MIB Module
This section demonstrates how the objects in MPLS-LSR-STD-MIB would This section demonstrates how the objects in MPLS-LSR-STD-MIB would
be set for an example P2MP LSP cross-connect. The information here be set for an example P2MP LSP cross-connect. The information here
does not show how and in what order these objects should be set to does not show how and in what order these objects should be set to
create the cross-connect, but shows what information would be read if create the cross-connect, but shows what information would be read if
the tables were examined. the tables were examined.
The figure shows the LSP at the LSR that is being examined. There are Figure 3 shows the LSP at the LSR that is being examined. There are
three interfaces to LSR X: 10, 21 and 22. The LSP enters through three interfaces to LSR X: 10, 21 and 22. The LSP enters through
interface 10 using label 7, and exits through interfaces 21 and 22 interface 10 using label 7, and exits through interfaces 21 and 22
using labels 8 and 9 respectively. Let us assume that LSR X is also using labels 8 and 9 respectively. Let us assume that LSR X is also
an egress for the LSP. an egress for the LSP.
------- -------
| |21 Label 8 | |21 Label 8
Label 7 | +-------------> Label 7 | +------------->
--->----------+ LSR X | --->----------+ LSR X |
10| +-------------> 10| +------------->
| |22 Label 9 | |22 Label 9
------- -------
Figure 3 : A P2MP LSP at a Branch LSR
In mplsInSegmentTable there is a single entry In mplsInSegmentTable there is a single entry
{ {
mplsInSegmentIndex = 0x00000015, mplsInSegmentIndex = 0x00000015,
mplsInSegmentLabel = 7, -- incoming label mplsInSegmentLabel = 7, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 10, -- incoming interface mplsInSegmentInterface = 10, -- incoming interface
mplsInSegmentXCIndex = 0x37 -- index into XC table mplsInSegmentXCIndex = 0x37 -- index into XC table
} }
In mplsOutSegmentTable there are two entries. In mplsOutSegmentTable there are two entries.
skipping to change at page 12, line 29 skipping to change at page 18, line 5
mplsXCLabelStackIndex = 0x00, -- only one outgoing label mplsXCLabelStackIndex = 0x00, -- only one outgoing label
} }
{ {
mplsXCIndex = 0x37, -- common index mplsXCIndex = 0x37, -- common index
mplsXCInSegmentIndex = 0x00000015,-- the in-segment mplsXCInSegmentIndex = 0x00000015,-- the in-segment
mplsXCOutSegmentIndex = 0x00, -- no out-segment mplsXCOutSegmentIndex = 0x00, -- no out-segment
mplsXCLspId = 0x0102 -- unique LSP ID mplsXCLspId = 0x0102 -- unique LSP ID
mplsXCLabelStackIndex = 0x00, -- no other outgoing label mplsXCLabelStackIndex = 0x00, -- no other outgoing label
} }
6.2. Remerge Cases in the LSR MIB Module
TBD
7. MPLS Traffic Engineering P2MP MIB Definitions 7. MPLS Traffic Engineering P2MP MIB Definitions
This MIB module uses imports from [RFC2578], [RFC2580], [RFC2579], This MIB module uses imports from [RFC2578], [RFC2580], [RFC2579],
[RFC3811], [RFC3812], [RFC3813], [RFC3289], and [RFC3291]. [RFC3811], [RFC3812], [RFC3813], [RFC3289], and [RFC3291].
MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Counter64, TimeTicks Unsigned32, Counter32, Counter64, TimeTicks
skipping to change at page 13, line 34 skipping to change at page 18, 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 "200605240000Z" -- May 24, 2006 LAST-UPDATED "200611230000Z" -- November 23, 2006
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 Internet Society (2006). The "Copyright (C) The IETF Trust (2006). The initial version of
initial version of this MIB module was published this MIB module was published in RFC XXXX. For full legal
in RFC XXXX. For full legal notices see the RFC notices see the RFC itself or see:
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
"200605240000Z" -- May 24, 2006 "200611230000Z" -- November 23, 2006
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 40, line 51 skipping to change at page 45, line 51
[RFC4461] S. Yasukawa, Editor "Signaling Requirements for [RFC4461] S. Yasukawa, Editor "Signaling Requirements for
Point-to-Multipoint Traffic Engineered MPLS LSPs", Point-to-Multipoint Traffic Engineered MPLS LSPs",
RFC4461, April 2006. 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
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol
Label Switching (MPLS) Management Overview", RFC 4221,
November 2005.
[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
Label Switching (MPLS) Management Overview", RFC 4221,
November 2005.
[GMPLS-TE-MIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [GMPLS-TE-MIB] 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", draft-ietf-ccamp-gmpls-te-mib, work
in progress. 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
skipping to change at page 42, line 13 skipping to change at page 47, 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 Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2006).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
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 AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 24 change blocks. 
100 lines changed or deleted 363 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/