RFC 6981 on A Framework for IP and MPLS Fast Reroute Using Not-Via Addresses

rfc-editor@rfc-editor.org Thu, 01 August 2013 08:55 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCF721F9E8B; Thu, 1 Aug 2013 01:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.256
X-Spam-Level:
X-Spam-Status: No, score=-102.256 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2s5IUnhxE2g; Thu, 1 Aug 2013 01:55:58 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 562F321F9ED1; Thu, 1 Aug 2013 01:55:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 186B36212E; Thu, 1 Aug 2013 01:52:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6981 on A Framework for IP and MPLS Fast Reroute Using Not-Via Addresses
From: rfc-editor@rfc-editor.org
Message-Id: <20130801085222.186B36212E@rfc-editor.org>
Date: Thu, 01 Aug 2013 01:52:22 -0700
Cc: drafts-update-ref@iana.org, rtgwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 08:55:59 -0000

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

        
        RFC 6981

        Title:      A Framework for IP and 
                    MPLS Fast Reroute Using Not-Via Addresses 
        Author:     S. Bryant,
                    S. Previdi,
                    M. Shand
        Status:     Informational
        Stream:     IETF
        Date:       August 2013
        Mailbox:    stbryant@cisco.com, 
                    sprevidi@cisco.com, 
                    imc.shand@googlemail.com
        Pages:      34
        Characters: 79311
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-ipfrr-notvia-addresses-11.txt

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

This document presents an illustrative framework for providing fast
reroute in an IP or MPLS network through encapsulation and forwarding
to "not-via" addresses.  The general approach described here uses a
single level of encapsulation and could be used to protect unicast,
multicast, and LDP traffic against link, router, and shared risk
group failure, regardless of network topology and metrics.

The mechanisms presented in this document are purely illustrative of
the general approach and do not constitute a protocol specification.
The document represents a snapshot of the work of the Routing Area
Working Group at the time of publication and is published as a
document of record.  Further work is needed before implementation or
deployment.

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/search/rfc_search.php
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