[Lsr] [Errata Held for Document Update] RFC7810 (5486)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 04 November 2018 03:25 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 500AF130DC8; Sat, 3 Nov 2018 20:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 L0xDcsEt1eIC; Sat, 3 Nov 2018 20:25:11 -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 589F7130DC2; Sat, 3 Nov 2018 20:25:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3DF97B8139A; Sat, 3 Nov 2018 20:24:59 -0700 (PDT)
To: buptly@gmail.com, sprevidi@cisco.com, spencer.giacalone@gmail.com, wardd@cisco.com, jdrake@juniper.net, sunseawq@huawei.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aretana.ietf@gmail.com, iesg@ietf.org, lsr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20181104032459.3DF97B8139A@rfc-editor.org>
Date: Sat, 03 Nov 2018 20:24:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/unu_nG78DEbWAcbZMeCtBuMg7qA>
Subject: [Lsr] [Errata Held for Document Update] RFC7810 (5486)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 04 Nov 2018 03:25:12 -0000
The following errata report has been held for document update for RFC7810, "IS-IS Traffic Engineering (TE) Metric Extensions". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5486 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Teresa <buptly@gmail.com> Date Reported: 2018-08-31 Held by: Alvaro Retana (IESG) 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' -------------------------------------- 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] [Errata Held for Document Update] RFC7810 (… RFC Errata System