[Sidrops] Lars Eggert's Discuss on draft-ietf-sidrops-rov-no-rr-05: (with DISCUSS and COMMENT)
Lars Eggert via Datatracker <noreply@ietf.org> Wed, 24 August 2022 10:31 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE6FFC1524BA; Wed, 24 Aug 2022 03:31:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sidrops-rov-no-rr@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, morrowc@ops-netman.net, morrowc@ops-netman.net
X-Test-IDTracker: no
X-IETF-IDTracker: 8.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <166133709577.33806.9261183387360225660@ietfa.amsl.com>
Date: Wed, 24 Aug 2022 03:31:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/DQlx3yLj6Z9hhSqcgX6dQC1kYrQ>
Subject: [Sidrops] Lars Eggert's Discuss on draft-ietf-sidrops-rov-no-rr-05: (with DISCUSS and COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2022 10:31:35 -0000
Lars Eggert has entered the following ballot position for draft-ietf-sidrops-rov-no-rr-05: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sidrops-rov-no-rr/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- # GEN AD review of draft-ietf-sidrops-rov-no-rr-03 CC @larseggert Thanks to Paul Kyzivat for the General Area Review Team (Gen-ART) review (https://mailarchive.ietf.org/arch/msg/gen-art/Qhb_8-Kc5e5QEE47En6NhULHnjI). ## Discuss ### Unclear RFC status ``` Intended status: Standards Track Arrcus, Inc. ``` The datatracker metadata for this document indicated a intended status of "Internet Standard". I assume this is incorrect and needs to be changed (probably to "Proposed Standard".) ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- ## Nits All comments below are about very minor potential issues that you may choose to address in some way - or ignore - as you see fit. Some were flagged by automated tools (via https://github.com/larseggert/ietf-reviewtool), so there will likely be some false positives. There is no need to let me know what you did with these suggestions. ### Typos #### Section 3, paragraph 1 ``` - the received paths aginst the new data. + the received paths against the new data. + + ``` ### Grammar/style #### Paragraph 0 ``` metadata for this document indicated a intended status of "Internet Standar ^ ``` Use "an" instead of "a" if the following word starts with a vowel sound, e.g. "an article", "an hour". #### Section 1, paragraph 1 ``` k paths affected by RPKI-based policy so Route Refresh is no longer needed. ^^^ ``` Use a comma before "so" if it connects two independent clauses (unless they are closely connected and short). #### Section 4, paragraph 1 ``` s, then it MUST issue a route refresh so those alternatives may be evaluated ^^^ ``` Use a comma before "so" if it connects two independent clauses (unless they are closely connected and short). ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT]. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments [IRT]: https://github.com/larseggert/ietf-reviewtool
- [Sidrops] Lars Eggert's Discuss on draft-ietf-sid… Lars Eggert via Datatracker
- Re: [Sidrops] Lars Eggert's Discuss on draft-ietf… Randy Bush