RFC 7726 on Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs)
rfc-editor@rfc-editor.org Fri, 29 January 2016 22:58 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A42881A90A3; Fri, 29 Jan 2016 14:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWv3tz_-dkoY; Fri, 29 Jan 2016 14:58:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 329CB1A90A1; Fri, 29 Jan 2016 14:58:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AF5C218019E; Fri, 29 Jan 2016 14:57:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7726 on Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160129225703.AF5C218019E@rfc-editor.org>
Date: Fri, 29 Jan 2016 14:57:03 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/cQ3IzCo6GZQlTUbetbqIVB3HuiY>
Cc: rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 22:58:45 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7726
Title: Clarifying Procedures for Establishing BFD
Sessions for MPLS Label Switched Paths
(LSPs)
Author: V. Govindan, K. Rajaraman,
G. Mirsky, N. Akiya, S. Aldrin
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: venggovi@cisco.com,
kalyanir@cisco.com,
gregory.mirsky@ericsson.com,
nobo.akiya.dev@gmail.com,
aldrin.ietf@gmail.com
Pages: 7
Characters: 13899
Updates: RFC 5884
I-D Tag: draft-ietf-bfd-rfc5884-clarifications-04.txt
URL: https://www.rfc-editor.org/info/rfc7726
DOI: http://dx.doi.org/10.17487/RFC7726
This document clarifies the procedures for establishing, maintaining,
and removing multiple, concurrent BFD (Bidirectional Forwarding
Detection) sessions for a given <MPLS LSP, FEC> as described in RFC
5884.
This document is a product of the Bidirectional Forwarding Detection Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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