[mpls] RFC 6445 on Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute

rfc-editor@rfc-editor.org Wed, 16 November 2011 09:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42EB321F95B8; Wed, 16 Nov 2011 01:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level:
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 Qhimrk7PIe5M; Wed, 16 Nov 2011 01:42:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB5D21F95AC; Wed, 16 Nov 2011 01:42:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 06582B1E00E; Wed, 16 Nov 2011 01:37:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111116093727.06582B1E00E@rfc-editor.org>
Date: Wed, 16 Nov 2011 01:37:27 -0800
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6445 on Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 09:42:41 -0000

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

        
        RFC 6445

        Title:      Multiprotocol Label Switching (MPLS) Traffic 
                    Engineering Management Information Base for Fast 
                    Reroute 
        Author:     T. Nadeau, Ed.,
                    A. Koushik, Ed.,
                    R. Cetin, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    thomas.nadeau@ca.com, 
                    kkoushik@cisco.com, 
                    riza.cetin@alcatel.be
        Pages:      53
        Characters: 101627
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-fastreroute-mib-21.txt

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

This memo defines a portion of the Management Information Base
for use with network management protocols in the Internet community.
In particular, it describes managed objects used to support two
fast reroute (FRR) methods for Multiprotocol Label Switching
(MPLS)-based traffic engineering (TE).  The two methods are the
one-to-one backup method and the facility backup method.
[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