[sidr] [Editorial Errata Reported] RFC7115 (4973)

RFC Errata System <rfc-editor@rfc-editor.org> Sat, 18 March 2017 08:12 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 D2E0E120724 for <sidr@ietfa.amsl.com>; Sat, 18 Mar 2017 01:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 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] 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 FSSnKnEXf7ku for <sidr@ietfa.amsl.com>; Sat, 18 Mar 2017 01:12:10 -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 EBC9D12422F for <sidr@ietf.org>; Sat, 18 Mar 2017 01:12:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C6D5B80D54; Sat, 18 Mar 2017 01:11:57 -0700 (PDT)
To: randy@psg.com, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, morrowc@ops-netman.net, sandy@tislabs.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: achatz@forthnet.gr, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170318081157.9C6D5B80D54@rfc-editor.org>
Date: Sat, 18 Mar 2017 01:11:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/dCKYbLoBftQOTLqagURZTkXKtm4>
Subject: [sidr] [Editorial Errata Reported] 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, 18 Mar 2017 08:12:13 -0000

The following errata report has been submitted 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

--------------------------------------
Type: Editorial
Reported by: Tassos Chatzithomaoglou <achatz@forthnet.gr>

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

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
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