[sidr] [Errata Held for Document Update] RFC7115 (4973)

RFC Errata System <rfc-editor@rfc-editor.org> Sat, 25 March 2017 11:17 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 B4EED129415; Sat, 25 Mar 2017 04:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 tV77hc1_7Cuh; Sat, 25 Mar 2017 04:17:19 -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 5C1FD128BB6; Sat, 25 Mar 2017 04:17:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 915D2B80A4D; Sat, 25 Mar 2017 04:17:12 -0700 (PDT)
To: achatz@forthnet.gr, randy@psg.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aretana@cisco.com, iesg@ietf.org, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170325111712.915D2B80A4D@rfc-editor.org>
Date: Sat, 25 Mar 2017 04:17:12 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/oxtqxJU1PEkltmYo04DHxBQQNKc>
Subject: [sidr] [Errata Held for Document Update] RFC7115 (4973)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 25 Mar 2017 11:17:22 -0000

The following errata report has been held for document update 
for RFC7115, "Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7115&eid=4973

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Tassos Chatzithomaoglou <achatz@forthnet.gr>
Date Reported: 2017-03-18
Held by: Alvaro Retana (IESG)

Section: 3 & 5

Original Text
-------------
section 3
---------
For example, if, instead of 10.0.0.0/16-24, one issues
   10.0.0.0/16 and 10.0.42.0/24, a forged origin attack cannot succeed
   against 10.0.666.0/24. 

section 5
---------
Consider having a ROA for AS 42 for prefix
   10.0.0.0/16-24.  A BGP announcement for 10.0.666.0/24 from AS 666
   would be Invalid

Corrected Text
--------------
section 3
---------
For example, if, instead of 10.0.0.0/16-24, one issues
   10.0.0.0/16 and 10.0.42.0/24, a forged origin attack cannot succeed
   against 10.0.66.0/24. 

section 5
---------
Consider having a ROA for AS 42 for prefix
   10.0.0.0/16-24.  A BGP announcement for 10.0.66.0/24 from AS 666
   would be Invalid


Notes
-----
666 is not a valid octet for an ipv4 address

===
I am marking this report as "Held for Document Update" [1], which means that the author might consider its merits for a future update.  If the use of the "666" octet was intentional, then a short note explaining might be appropriate to avoid further confusion.

- Alvaro.

[1] https://www.ietf.org/iesg/statement/errata-processing.html

--------------------------------------
RFC7115 (draft-ietf-sidr-origin-ops-23)
--------------------------------------
Title               : Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)
Publication Date    : January 2014
Author(s)           : R. Bush
Category            : BEST CURRENT PRACTICE
Source              : Secure Inter-Domain Routing
Area                : Routing
Stream              : IETF
Verifying Party     : IESG