[Lsr] [Editorial Errata Reported] RFC7810 (5486)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 31 August 2018 05:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476CC130E10 for <lsr@ietfa.amsl.com>; Thu, 30 Aug 2018 22:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=no 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 4utTXsgl0GAa for <lsr@ietfa.amsl.com>; Thu, 30 Aug 2018 22:56:33 -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 05AB412872C for <lsr@ietf.org>; Thu, 30 Aug 2018 22:56:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A58C7B8116F; Thu, 30 Aug 2018 22:56:11 -0700 (PDT)
To: sprevidi@cisco.com, spencer.giacalone@gmail.com, wardd@cisco.com, jdrake@juniper.net, sunseawq@huawei.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, chopps@chopps.org, hannes@gredler.at
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: buptly@gmail.com, lsr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180831055611.A58C7B8116F@rfc-editor.org>
Date: Thu, 30 Aug 2018 22:56:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/JCulqIs9reiguGfGte4eg0TSUUw>
Subject: [Lsr] [Editorial Errata Reported] RFC7810 (5486)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Aug 2018 05:56:34 -0000
The following errata report has been submitted for RFC7810, "IS-IS Traffic Engineering (TE) Metric Extensions". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5486 -------------------------------------- Type: Editorial Reported by: Teresa <buptly@gmail.com> Section: 4.6 Original Text ------------- Available Bandwidth: This field carries the available bandwidth on a link, forwarding adjacency, or bundled link in IEEE floating-point format with units of bytes per second. For a link or forwarding adjacency, available bandwidth is defined to be residual bandwidth (see Section 4.5) minus the measured bandwidth used for the actual forwarding of non-RSVP-TE label switched path packets. For a bundled link, available bandwidth is defined to be the sum of the component link available bandwidths minus the measured bandwidth used for the actual forwarding of non-RSVP-TE label switched path packets. For a bundled link, available bandwidth is defined to be the sum of the component link available bandwidths. Corrected Text -------------- Available Bandwidth: This field carries the available bandwidth on a link, forwarding adjacency, or bundled link in IEEE floating-point format with units of bytes per second. For a link or forwarding adjacency, available bandwidth is defined to be residual bandwidth (see Section 4.5) minus the measured bandwidth used for the actual forwarding of non-RSVP-TE label switched path packets. For a bundled link, available bandwidth is defined to be the sum of the component link (residual) bandwidths minus the measured bandwidth used for the actual forwarding of non-RSVP-TE label switched path packets.For a bundled link, available bandwidth is defined to be the sum of the component link available bandwidths. Notes ----- Two sentences to explain 'available bandwidth' on a bundled link, but one says "sum of component available bandwidth minus xxx", the other says "sum of component available bandwidth", is conflicting. need to change the first sentence to 'sum of component residual bandwidth minus xxx' Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7810 (draft-ietf-isis-te-metric-extensions-11) -------------------------------------- Title : IS-IS Traffic Engineering (TE) Metric Extensions Publication Date : May 2016 Author(s) : S. Previdi, Ed., S. Giacalone, D. Ward, J. Drake, Q. Wu Category : PROPOSED STANDARD Source : IS-IS for IP Internets Area : Routing Stream : IETF Verifying Party : IESG
- [Lsr] [Editorial Errata Reported] RFC7810 (5486) RFC Errata System
- Re: [Lsr] [Editorial Errata Reported] RFC7810 (54… stefano previdi