[Sidrops] Roman Danyliw's No Objection on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 03 April 2019 20:36 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 ED69A12006A; Wed, 3 Apr 2019 13:36:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sidrops-bgpsec-algs-rfc8208-bis@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops-chairs@ietf.org, morrowc@ops-netman.net, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155432378096.22764.10084768405862321330.idtracker@ietfa.amsl.com>
Date: Wed, 03 Apr 2019 13:36:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/b5levIupY0x64y_GYi-Q3I7IYiE>
Subject: [Sidrops] Roman Danyliw's No Objection on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Apr 2019 20:36:21 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: No Objection 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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sidrops-bgpsec-algs-rfc8208-bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for this easy to read update to RFC8208. Below are a few editorial comments: (1) Section 1. Editorial nit. s/BGPsec uses a different algorithm [RFC6090] [DSS] as compared to the rest of the RPKI by using a different algorithm that provides similar security with smaller keys making the certificates smaller;/ BGPsec uses a different algorithm [RFC6090] [DSS] as compared to the rest of the RPKI that provides similar security with smaller keys making the certificates smaller;/ (2) Section 2. Editorial nit. s/This section addresses BGPsec algorithms; for example, these algorithms are used by BGPsec routers to sign and verify BGPsec UPDATE messages./ This section addresses the algorithms used by BGPSec [RFC6090] [DSS]. For examples, these algorithms are used by BGPSec routers to sign and verify BGPsec UPDATE messages./ (3) Section 2. The sentence “To identify which algorithm is used, the BGPsec UPDATE message contains the corresponding algorithm ID in each Signature_Block of the BGPsec UPDATE message” seems redundant given that the first sentence of Section 2.1 says something very similar. (4) Section 2.1. Editorial nit. Make the use of constants here consistent with the description of “special-use Algo ID”. s/0x00 and 0xFF/0x00 (0) and 0xFF (255)/
- [Sidrops] Roman Danyliw's No Objection on draft-i… Roman Danyliw via Datatracker