RFC 8571 on BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions
rfc-editor@rfc-editor.org Fri, 15 March 2019 23:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD426124C04; Fri, 15 Mar 2019 16:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 Ys8vtozLm-3n; Fri, 15 Mar 2019 16:07:46 -0700 (PDT)
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 A86FB1312F8; Fri, 15 Mar 2019 16:07:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AC56FB826B9; Fri, 15 Mar 2019 16:07:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8571 on BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190315230741.AC56FB826B9@rfc-editor.org>
Date: Fri, 15 Mar 2019 16:07:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2lqKdo8dDOU3sheJkyFqwLK7L2o>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 15 Mar 2019 23:07:54 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8571 Title: BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions Author: L. Ginsberg, Ed., S. Previdi, Q. Wu, J. Tantsura, C. Filsfils Status: Standards Track Stream: IETF Date: March 2019 Mailbox: ginsberg@cisco.com, stefano@previdi.net, bill.wu@huawei.com, jefftant.ietf@gmail.com, cfilsfil@cisco.com Pages: 10 Characters: 18205 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-te-pm-bgp-18.txt URL: https://www.rfc-editor.org/info/rfc8571 DOI: 10.17487/RFC8571 This document defines new BGP - Link State (BGP-LS) TLVs in order to carry the IGP Traffic Engineering Metric Extensions defined in the IS-IS and OSPF protocols. This document is a product of the Inter-Domain Routing 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