[Teas] RFC 8001 on RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) Information
rfc-editor@rfc-editor.org Thu, 12 January 2017 23:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E601294EB; Thu, 12 Jan 2017 15:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 BaaNIBzZy9lz; Thu, 12 Jan 2017 15:33:37 -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 048AC1294EA; Thu, 12 Jan 2017 15:33:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EEA68B81001; Thu, 12 Jan 2017 15:33:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170112233336.EEA68B81001@rfc-editor.org>
Date: Thu, 12 Jan 2017 15:33:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/rIbx7ryyBsXKqy0TzhxKOjC8dKc>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
Subject: [Teas] RFC 8001 on RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) Information
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2017 23:33:39 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8001 Title: RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) Information Author: F. Zhang, Ed., O. Gonzalez de Dios, Ed., C. Margaria, M. Hartley, Z. Ali Status: Standards Track Stream: IETF Date: January 2017 Mailbox: zhangfatai@huawei.com, oscar.gonzalezdedios@telefonica.com, cmargaria@juniper.net, mhartley@cisco.com, zali@cisco.com Pages: 16 Characters: 34732 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-teas-rsvp-te-srlg-collect-08.txt URL: https://www.rfc-editor.org/info/rfc8001 DOI: 10.17487/RFC8001 This document provides extensions for Resource Reservation Protocol - Traffic Engineering (RSVP-TE), including GMPLS, to support automatic collection of Shared Risk Link Group (SRLG) information for the TE link formed by a Label Switched Path (LSP). This document is a product of the Traffic Engineering Architecture and Signaling 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/retrieve/bulk 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