RFC 5714 on IP Fast Reroute Framework

RFC Editor <rfc-editor@rfc-editor.org> Tue, 19 January 2010 18:56 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 D696B3A6859 for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, 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 R8zyKDoRG6yY for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:56:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C896528C13C for <ietf-announce@ietf.org>; Tue, 19 Jan 2010 10:56:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 8FA2AE0686; Tue, 19 Jan 2010 10:56:01 -0800 (PST)
Date: Tue, 19 Jan 2010 10:56:01 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: RFC 5714 on IP Fast Reroute Framework
Message-ID: <20100119185601.GN14300@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:56:09 -0000

Resending.

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

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5714 on IP Fast Reroute Framework
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, rtgwg@ietf.org
Date: Thu, 14 Jan 2010 23:09:45 -0800 (PST)


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

        
        RFC 5714

        Title:      IP Fast Reroute Framework 
        Author:     M. Shand, S. Bryant
        Status:     Informational
        Date:       January 2010
        Mailbox:    mshand@cisco.com, 
                    stbryant@cisco.com
        Pages:      15
        Characters: 32854
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-ipfrr-framework-13.txt

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

This document provides a framework for the development of IP fast-
reroute mechanisms that provide protection against link or router
failure by invoking locally determined repair paths.  Unlike MPLS
fast-reroute, the mechanisms are applicable to a network employing
conventional IP routing and forwarding.  This document is not an 
Internet Standards Track specification; it is published for informational 
purposes.

This document is a product of the Routing Area Working Group Working Group of the IETF.


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-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 -----