draft-ietf-mpls-bundle-01.txt   draft-ietf-mpls-bundle-02.txt 
Network Working Group Kireeti Kompella Network Working Group Kireeti Kompella
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: May 2002 Yakov Rekhter Expiration Date: November 2002 Yakov Rekhter
Juniper Networks Juniper Networks
Lou Berger Lou Berger
Movaz Networks Movaz Networks
Link Bundling in MPLS Traffic Engineering Link Bundling in MPLS Traffic Engineering
draft-ietf-mpls-bundle-01.txt draft-ietf-mpls-bundle-02.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 3, line 46 skipping to change at page 3, line 46
each of the component links within the bundled link - a bundled link each of the component links within the bundled link - a bundled link
is alive when at least one its component links is determined to be is alive when at least one its component links is determined to be
alive. The liveness of a component link can be determined by any of alive. The liveness of a component link can be determined by any of
several means: IS-IS or OSPF hellos over the component link, or RSVP several means: IS-IS or OSPF hellos over the component link, or RSVP
Hello, or LMP hellos (see [LMP]), or from layer 1 or layer 2 Hello, or LMP hellos (see [LMP]), or from layer 1 or layer 2
indications. indications.
Once a bundled link is determined to be alive, it can be advertised Once a bundled link is determined to be alive, it can be advertised
as a TE link and the TE information can be flooded. If IS-IS/OSPF as a TE link and the TE information can be flooded. If IS-IS/OSPF
hellos are run over the component links, IS-IS/OSPF flooding can be hellos are run over the component links, IS-IS/OSPF flooding can be
restricted to just one of the component links [ZININ] [MOY]. restricted to just one of the component links. Procedures for doing
this are outside the scope of this document.
In the future, as new Traffic Engineering parameters are added to IS- In the future, as new Traffic Engineering parameters are added to IS-
IS and OSPF, they should be accompanied by descriptions as to how IS and OSPF, they should be accompanied by descriptions as to how
they can be bundled, and possible restrictions on bundling. they can be bundled, and possible restrictions on bundling.
3.3. Signaling Considerations 3.3. Signaling Considerations
Typically, an LSP's ERO will choose the bundled link to be used for Typically, an LSP's ERO will choose the bundled link to be used for
the LSP, but not the component link, since information about the the LSP, but not the component link, since information about the
bundled link is flooded, but information about the component links is bundled link is flooded, but information about the component links is
skipping to change at page 6, line 5 skipping to change at page 6, line 5
to the identifier chosen for the bundle by the advertising LSR. The to the identifier chosen for the bundle by the advertising LSR. The
link remote identifier is set to the identifier chosen by the link remote identifier is set to the identifier chosen by the
neighboring LSR for the reverse link corresponding to this bundle, if neighboring LSR for the reverse link corresponding to this bundle, if
known; otherwise, this is set to 0. known; otherwise, this is set to 0.
4.5. Traffic Engineering Metric 4.5. Traffic Engineering Metric
The Traffic Engineering Metric for a bundled link is that of the The Traffic Engineering Metric for a bundled link is that of the
component links. component links.
4.6. Maximum Link Bandwidth 4.6. Maximum Bandwidth
This TLV is not used. The maximum LSP Bandwidth (as described below) This parameter is not used. The maximum LSP Bandwidth (as described
replaces the maximum link bandwidth for bundled links. below) replaces the Maximum Bandwidth for bundled links.
4.7. Total Reservable Bandwidth 4.7. Maximum Reservable Bandwidth
We assume that for a given bundled link either each of its component We assume that for a given bundled link either each of its component
links is configured with the Total Reservable Bandwidth, or the links is configured with the Maximum Reservable Bandwidth, or the
bundled link is configured with the Total Reservable Bandwidth. In bundled link is configured with the Maximum Reservable Bandwidth. In
the former case, the Total Reservable Bandwidth of the bundled link the former case, the Maximum Reservable Bandwidth of the bundled link
is set to the sum of the Total Reservable Bandwidths of all component is set to the sum of the Maximum Reservable Bandwidths of all
links associated with the bundled link. component links associated with the bundled link.
4.8. Unreserved Bandwidth 4.8. Unreserved Bandwidth
The unreserved bandwidth of a bundled link at priority p is the sum The unreserved bandwidth of a bundled link at priority p is the sum
of the unreserved bandwidths at priority p of all the component links of the unreserved bandwidths at priority p of all the component links
associated with the bundled link. associated with the bundled link.
4.9. Resource Classes (Administrative Groups) 4.9. Resource Classes (Administrative Groups)
The Resource Classes for a bundled link are the same as those of the The Resource Classes for a bundled link are the same as those of the
component links. component links.
4.10. Maximum LSP Bandwidth 4.10. Maximum LSP Bandwidth
The Maximum LSP Bandwidth takes the place of the Maximum Link The Maximum LSP Bandwidth takes the place of the Maximum Bandwidth.
Bandwidth. For an unbundled link the Maximum Link Bandwidth is is For an unbundled link the Maximum Bandwidth is is defined in [GMPLS-
defined in [GMPLS-ROUTING]. The Maximum LSP Bandwidth of a bundled ROUTING]. The Maximum LSP Bandwidth of a bundled link at priority p
link at priority p is defined to be the maximum of the Maximum LSP is defined to be the maximum of the Maximum LSP Bandwidth at priority
Bandwidth at priority p of all of its component links. p of all of its component links.
The details of how Maximum LSP Bandwidth is carried in IS-IS is given The details of how Maximum LSP Bandwidth is carried in IS-IS is given
in [GMPLS-ISIS]. The details of how Maximum LSP Bandwidth is carried in [GMPLS-ISIS]. The details of how Maximum LSP Bandwidth is carried
in OSPF is given in [GMPLS-OSPF]. in OSPF is given in [GMPLS-OSPF].
5. Bandwidth Accounting 5. Bandwidth Accounting
The RSVP (or CR-LDP) Traffic Control module, or its equivalent, on an The RSVP (or CR-LDP) Traffic Control module, or its equivalent, on an
LSR with bundled links must apply admission control on a per- LSR with bundled links must apply admission control on a per-
component link basis. An LSP with a bandwidth requirement b and setup component link basis. An LSP with a bandwidth requirement b and setup
skipping to change at page 7, line 39 skipping to change at page 7, line 39
bundle must be recomputed. If all the component links associated with bundle must be recomputed. If all the component links associated with
a given bundled link are down, the bundled link MUST not be a given bundled link are down, the bundled link MUST not be
advertised into OSPF/IS-IS. advertised into OSPF/IS-IS.
6. Security Considerations 6. Security Considerations
This document raises no new security issues for RSVP or CR-LDP. This document raises no new security issues for RSVP or CR-LDP.
7. References 7. References
7.1. Normative References
[GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS [GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS
Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls- Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls-
extensions-02.txt (work in progress) extensions-11.txt (work in progress)
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf- Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf-
gmpls-extensions-00.txt (work in progress) gmpls-extensions-08.txt (work in progress)
[GMPLS-ROUTING] Kompella, K., Rekhter, Y., Banerjee, A. et al, [GMPLS-ROUTING] Kompella, K., Rekhter, Y., Banerjee, A. et al,
"Routing Extensions in Support of Generalized MPLS", draft-ietf- "Routing Extensions in Support of Generalized MPLS", draft-ietf-
ccamp-gmpls-routing-00.txt ccamp-gmpls-routing-04.txt (work in progress)
[GMPLS-SIG] Ashwood, P., et al., "Generalized MPLS - Signalling [GMPLS-SIG] Ashwood, P., et al., "Generalized MPLS - Signalling
Functional Description", draft-ietf-generalized-mpls- Functional Description", draft-ietf-generalized-mpls-
signalling-05.txt signalling-08.txt
[GMPLS-RSVP] Ashwood, P., et al., "Generalized MPLS Signalling RSVP- [GMPLS-RSVP] Ashwood, P., et al., "Generalized MPLS Signalling RSVP-
TE Extensions", draft-ietf-mpls-generalized-rsvp-te-04.txt TE Extensions", draft-ietf-mpls-generalized-rsvp-te-07.txt
[GMPLS-CRLDP] Ashwood, P., et al., "Generalized MPLS Signaling - CR- [GMPLS-CRLDP] Ashwood, P., et al., "Generalized MPLS Signaling - CR-
LDP Extensions", draft-ietf-mpls-generalized-cr-ldp-04.txt LDP Extensions", draft-ietf-mpls-generalized-cr-ldp-06.txt
[ISIS-TE] Smit, H., Li, T., "IS-IS extensions for Traffic [ISIS-TE] Smit, H., Li, T., "IS-IS extensions for Traffic
Engineering", draft-ietf-isis-traffic-02.txt (work in progress) Engineering", draft-ietf-isis-traffic-02.txt (work in progress)
[LMP] Lang, J., Mitra, K., et al., "Link Management Protocol (LMP)",
draft-ietf-ccamp-lmp-00.txt (work in progress)
[MOY] Moy, J., draft-ietf-ospf-ppp-flood-00.txt (work in progress)
[OSPF-TE] Katz, D., Yeung, D., "Traffic Engineering Extensions to [OSPF-TE] Katz, D., Yeung, D., "Traffic Engineering Extensions to
OSPF", draft-katz-yeung-ospf-traffic-04.txt (work in progress) OSPF", draft-katz-yeung-ospf-traffic-04.txt (work in progress)
[UNNUM-CRLDP] Kompella, K., Rekhter, Y., Kullberg, A., "Signalling [UNNUM-CRLDP] Kompella, K., Rekhter, Y., Kullberg, A., "Signalling
Unnumbered Links in CR-LDP", draft-ietf-mpls-crldp-unnum-01.txt (work Unnumbered Links in CR-LDP", draft-ietf-mpls-crldp-unnum-01.txt (work
in progress) in progress)
[UNNUM-RSVP] Kompella, K., Rekhter, Y., "Signalling Unnumbered Links [UNNUM-RSVP] Kompella, K., Rekhter, Y., "Signalling Unnumbered Links
in RSVP-TE", draft-ietf-mpls-rsvp-unnum-01.txt (work in progress) in RSVP-TE", draft-ietf-mpls-rsvp-unnum-01.txt (work in progress)
[ZININ] Zinin, A., Shand, M., "Flooding optimizations in link-state 7.2. Non-normative References
routing protocols", draft-ietf-ospf-isis-flood-opt-00.txt (work in
progress) [LMP] Lang, J., Mitra, K., et al., "Link Management Protocol (LMP)",
draft-ietf-ccamp-lmp-03.txt (work in progress)
8. Author Information 8. Author Information
Kireeti Kompella Kireeti Kompella
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: kireeti@juniper.net Email: kireeti@juniper.net
Yakov Rekhter Yakov Rekhter
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/