< draft-ietf-mpls-rsvp-shared-labels-08.txt   draft-ietf-mpls-rsvp-shared-labels-09.txt >
MPLS Working Group H. Sitaraman MPLS Working Group H. Sitaraman
Internet-Draft V. Beeram Internet-Draft V. Beeram
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: July 22, 2019 T. Parikh Expires: August 4, 2019 T. Parikh
Verizon Verizon
T. Saad T. Saad
Cisco Systems Cisco Systems
January 18, 2019 January 31, 2019
Signaling RSVP-TE tunnels on a shared MPLS forwarding plane Signaling RSVP-TE tunnels on a shared MPLS forwarding plane
draft-ietf-mpls-rsvp-shared-labels-08.txt draft-ietf-mpls-rsvp-shared-labels-09.txt
Abstract Abstract
As the scale of MPLS RSVP-TE networks has grown, so the number of As the scale of MPLS RSVP-TE networks has grown, so the number of
Label Switched Paths (LSPs) supported by individual network elements Label Switched Paths (LSPs) supported by individual network elements
has increased. Various implementation recommendations have been has increased. Various implementation recommendations have been
proposed to manage the resulting increase in control plane state. proposed to manage the resulting increase in control plane state.
However, those changes have had no effect on the number of labels However, those changes have had no effect on the number of labels
that a transit Label Switching Router (LSR) has to support in the that a transit Label Switching Router (LSR) has to support in the
skipping to change at page 2, line 20 skipping to change at page 2, line 20
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 22, 2019. This Internet-Draft will expire on August 4, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 10, line 11 skipping to change at page 10, line 11
set of labels {550, 600} will get pushed. The signaling extension set of labels {550, 600} will get pushed. The signaling extension
required for the ingress to indicate the chosen stacking approach is required for the ingress to indicate the chosen stacking approach is
defined in Section 9.6. defined in Section 9.6.
5.2. Explicit Delegation 5.2. Explicit Delegation
In this delegation option, the ingress LER can explicitly delegate In this delegation option, the ingress LER can explicitly delegate
one or more specific transit LSRs to handle pushing labels for a one or more specific transit LSRs to handle pushing labels for a
certain number of their downstream hops. In order to accurately pick certain number of their downstream hops. In order to accurately pick
the delegation hops, the ingress needs to be aware of the label stack the delegation hops, the ingress needs to be aware of the label stack
depth push limit (number of MPLS labels that can be imposed) of each depth push limit (total number of MPLS labels that can be imposed,
of the transit LSRs prior to initiating the signaling sequence. The including all service/transport/special labels) of each of the
transit LSRs prior to initiating the signaling sequence. The
mechanism by which the ingress or controller (hosting the path mechanism by which the ingress or controller (hosting the path
computation element) learns this information is outside the scope of computation element) learns this information is outside the scope of
this document. An example of such a mechanism is specified in this document. An example of such a mechanism is specified in
[RFC8491]. [RFC8491] (BMI-MSD advertisement).
The signaling extension required for the ingress LER to explicitly The signaling extension required for the ingress LER to explicitly
delegate one or more specific transit hops is defined in Section 9.4. delegate one or more specific transit hops is defined in Section 9.4.
The extension required for the delegation hop to indicate that the The extension required for the delegation hop to indicate that the
recorded label is a delegation label is defined in Section 9.5. recorded label is a delegation label is defined in Section 9.5.
5.3. Automatic Delegation 5.3. Automatic Delegation
In this approach, the ingress LER lets the downstream LSRs In this approach, the ingress LER lets the downstream LSRs
automatically pick suitable delegation hops during the initial automatically pick suitable delegation hops during the initial
 End of changes. 6 change blocks. 
7 lines changed or deleted 8 lines changed or added

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