RFC 5712 on MPLS Traffic Engineering Soft Preemption

RFC Editor <rfc-editor@rfc-editor.org> Tue, 19 January 2010 18:55 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36DAB28C12E for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfG9wKhbgU4k for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:55:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 90CDF28C138 for <ietf-announce@ietf.org>; Tue, 19 Jan 2010 10:55:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 58EF8E0686; Tue, 19 Jan 2010 10:55:07 -0800 (PST)
Date: Tue, 19 Jan 2010 10:55:07 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: RFC 5712 on MPLS Traffic Engineering Soft Preemption
Message-ID: <20100119185507.GL14300@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2010 18:55:21 -0000

Resending.

----- Forwarded message from rfc-editor@rfc-editor.org -----

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5712 on MPLS Traffic Engineering Soft Preemption
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, mpls@ietf.org
Date: Thu, 14 Jan 2010 23:09:15 -0800 (PST)


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

        
        RFC 5712

        Title:      MPLS Traffic Engineering Soft Preemption 
        Author:     M. Meyer, Ed.,
                    JP. Vasseur, Ed.
        Status:     Standards Track
        Date:       January 2010
        Mailbox:    matthew.meyer@bt.com, 
                    jpv@cisco.com
        Pages:      13
        Characters: 27371
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-soft-preemption-18.txt

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

This document specifies Multiprotocol Label Switching (MPLS) Traffic
Engineering Soft Preemption, a suite of protocol modifications
extending the concept of preemption with the goal of reducing or
eliminating traffic disruption of preempted Traffic Engineering Label
Switched Paths (TE LSPs).  Initially, MPLS RSVP-TE was defined with
support for only immediate TE LSP displacement upon preemption.  The
utilization of a reroute request notification helps more gracefully
mitigate the reroute process of preempted TE LSP.  For the brief
period soft preemption is activated, reservations (though not
necessarily traffic levels) are in effect under-provisioned until the
TE LSP(s) can be rerouted.  For this reason, the feature is
primarily, but not exclusively, interesting in MPLS-enabled IP
networks with Differentiated Services and Traffic Engineering
capabilities.  [STANDARDS TRACK]

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


----- End forwarded message -----