[sidr] [Errata Verified] RFC8360 (5638)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 13 February 2019 19:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E0D129532; Wed, 13 Feb 2019 11:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 V9hx41p94zVY; Wed, 13 Feb 2019 11:41:14 -0800 (PST)
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 4E776128766; Wed, 13 Feb 2019 11:41:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A1B3AB82674; Wed, 13 Feb 2019 11:41:03 -0800 (PST)
To: ydahhrk@gmail.com, gih@apnic.net, ggm@apnic.net, carlos@lacnic.net, tim@ripe.net, andy@arin.net, daniel@afrinic.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190213194103.A1B3AB82674@rfc-editor.org>
Date: Wed, 13 Feb 2019 11:41:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/9qn11HvUl17UF1f6l2xBx_L0YAo>
Subject: [sidr] [Errata Verified] RFC8360 (5638)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 19:41:17 -0000
The following errata report has been verified for RFC8360, "Resource Public Key Infrastructure (RPKI) Validation Reconsidered". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5638 -------------------------------------- Status: Verified Type: Technical Reported by: Alberto Leiva Popper <ydahhrk@gmail.com> Date Reported: 2019-02-13 Verified by: Warren Kumari (Ops AD) (IESG) Section: 4.2.4.4 Original Text ------------- 7. Compute the VRS-IP and VRS-AS set values as indicated below: * If the IP Address Delegation extension is present in certificate x and x=1, set the VRS-IP to the resources found in this extension. * If the IP Address Delegation extension (...) * If the IP Address Delegation extension (...) * If the IP Address Delegation extension is present in certificate x and x=1, set the VRS-IP to the resources found in this extension. * If the AS Identifier Delegation extension (...) * If the AS Identifier Delegation extension (...) Corrected Text -------------- 7. Compute the VRS-IP and VRS-AS set values as indicated below: * If the IP Address Delegation extension is present in certificate x and x=1, set the VRS-IP to the resources found in this extension. * If the IP Address Delegation extension (...) * If the IP Address Delegation extension (...) * If the AS Identifier Delegation extension is present in certificate x and x=1, set the VRS-AS to the resources found in this extension. * If the AS Identifier Delegation extension (...) * If the AS Identifier Delegation extension (...) Notes ----- There seems to be a copy-paste error. There are two bullet points explaining the initialization of VRS-IP, and none explaining the initialization of VRS-AS. All the evidence suggests that the two extensions (IP Address Delegation and AS Identifier Delegation) are meant to be handled similarly, so I believe that the last three bullet points are supposed to perfectly mirror the first three. -------------------------------------- RFC8360 (draft-ietf-sidr-rpki-validation-reconsidered-10) -------------------------------------- Title : Resource Public Key Infrastructure (RPKI) Validation Reconsidered Publication Date : April 2018 Author(s) : G. Huston, G. Michaelson, C. Martinez, T. Bruijnzeels, A. Newton, D. Shaw Category : PROPOSED STANDARD Source : Secure Inter-Domain Routing Area : Routing Stream : IETF Verifying Party : IESG
- [sidr] [Errata Verified] RFC8360 (5638) RFC Errata System
- Re: [sidr] [Errata Verified] RFC8360 (5638) Sandra Murphy
- Re: [sidr] [Errata Verified] RFC8360 (5638) Sandra Murphy
- Re: [sidr] [Errata Verified] RFC8360 (5638) Tim Bruijnzeels