[rfc-dist] RFC 8570 on IS-IS Traffic Engineering (TE) Metric Extensions
rfc-editor@rfc-editor.org Fri, 15 March 2019 23:07 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8CB1312F9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 15 Mar 2019 16:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 rag_Xw_kogar for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 15 Mar 2019 16:07:44 -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 0A76713131F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 15 Mar 2019 16:07:43 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 93270B826B1; Fri, 15 Mar 2019 16:07:29 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 67AF9B826AF; Fri, 15 Mar 2019 16:07:28 -0700 (PDT)
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: <20190315230728.67AF9B826AF@rfc-editor.org>
Date: Fri, 15 Mar 2019 16:07:28 -0700
Subject: [rfc-dist] RFC 8570 on IS-IS Traffic Engineering (TE) Metric Extensions
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8570
Title: IS-IS Traffic Engineering (TE) Metric
Extensions
Author: L. Ginsberg, Ed.,
S. Previdi, Ed.,
S. Giacalone,
D. Ward,
J. Drake,
Q. Wu
Status: Standards Track
Stream: IETF
Date: March 2019
Mailbox: ginsberg@cisco.com,
stefano@previdi.net,
spencer.giacalone@gmail.com,
wardd@cisco.com,
jdrake@juniper.net,
bill.wu@huawei.com
Pages: 21
Characters: 38620
Obsoletes: RFC 7810
I-D Tag: draft-ietf-lsr-isis-rfc7810bis-05.txt
URL: https://www.rfc-editor.org/info/rfc8570
DOI: 10.17487/RFC8570
In certain networks, such as, but not limited to, financial
information networks (e.g., stock market data providers),
network-performance criteria (e.g., latency) are becoming as
critical to data-path selection as other metrics.
This document describes extensions to IS-IS Traffic Engineering
Extensions (RFC 5305). These extensions provide a way to distribute
and collect network-performance information in a scalable fashion.
The information distributed using IS-IS TE Metric Extensions can then
be used to make path-selection decisions based on network
performance.
Note that this document only covers the mechanisms with which
network-performance information is distributed. The mechanisms for
measuring network performance or acting on that information, once
distributed, are outside the scope of this document.
This document obsoletes RFC 7810.
This document is a product of the Link State 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org