[Sidrops] draft-ietf-sidrops-roa-considerations-01
Russ Housley <housley@vigilsec.com> Mon, 28 February 2022 19:23 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id D54E13A12F6
for <sidrops@ietfa.amsl.com>; Mon, 28 Feb 2022 11:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01]
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 xqPce0FsSM9R for <sidrops@ietfa.amsl.com>;
Mon, 28 Feb 2022 11:23:47 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 473F73A14CE
for <sidrops@ietf.org>; Mon, 28 Feb 2022 11:23:43 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1])
by mail3.g24.pair.com (Postfix) with ESMTP id 57A9514C402
for <sidrops@ietf.org>; Mon, 28 Feb 2022 14:23:42 -0500 (EST)
Received: from a860b60074bd.fios-router.home
(pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mail3.g24.pair.com (Postfix) with ESMTPSA id 44E8814C29F
for <sidrops@ietf.org>; Mon, 28 Feb 2022 14:23:42 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Message-Id: <03FBC58E-8227-4007-8962-6DCC7F4F2C33@vigilsec.com>
Date: Mon, 28 Feb 2022 12:53:47 -0500
To: SIDR Operations WG <sidrops@ietf.org>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/eX6R9FCfhZw4rUXNPw5EX3bS3RI>
Subject: [Sidrops] draft-ietf-sidrops-roa-considerations-01
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 28 Feb 2022 19:23:54 -0000
I have a few comments on the document. Section 1: I find the first paragraph very confusing. The use of "must" sent me down the wrong path. I think the first sentence should tell the reader that we are talking about the RPKI. Then, it should explain the choices facing the address space holder. Then, say that the document will explore the pros and cons for the various choices. Then, recommend the most desirable among the alternatives. Section 1: s/space[RFC6482].If/space [RFC6482]. If/ Section 2: Please use the modern language here: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Section 3: s/Ripencc/RIPENCC/ After reading to document, I ask the authors to consider dropping "Problem Statement" from the title. Russ
- [Sidrops] draft-ietf-sidrops-roa-considerations-01 Russ Housley
- Re: [Sidrops] draft-ietf-sidrops-roa-consideratio… Jiankang Yao