[rfc-dist] RFC 4829 on Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Apr 23 20:06:51 PDT 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4829

        Title:      Label Switched Path (LSP) Preemption 
                    Policies for MPLS Traffic Engineering 
        Author:     J. de Oliveira, Ed.,
                    JP. Vasseur, Ed.,
                    L. Chen, C. Scoglio
        Status:     Informational
        Date:       April 2007
        Mailbox:    jau at ece.drexel.edu, 
                    jpv at cisco.com, 
                    leonardo.c.chen at verizon.com, caterina at eece.ksu.edu
        Pages:      19
        Characters: 43892
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-deoliveira-diff-te-preemption-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4829.txt

When the establishment of a higher priority (Traffic Engineering
Label Switched Path) TE LSP requires the preemption of a set of lower
priority TE LSPs, a node has to make a local decision to select which
TE LSPs will be preempted.  The preempted LSPs are then rerouted by
their respective \%Head-end Label Switch Router (LSR).  This document
presents a flexible policy that can be used to achieve different
objectives: preempt the lowest priority LSPs; preempt the minimum
number of LSPs; preempt the set of TE LSPs that provide the closest
amount of bandwidth to the required bandwidth for the preempting TE
LSPs (to minimize bandwidth wastage); preempt the LSPs that will have
the maximum chance to get rerouted.  Simulation results are given and
a comparison among several different policies, with respect to
preemption cascading, number of preempted LSPs, priority, wasted
bandwidth and blocking probability is also included.  This memo provides 
information for the Internet community.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list