Re: [sidr] [Editorial Errata Reported] RFC7132 (4454)

Chris Morrow <morrowc@ops-netman.net> Tue, 25 August 2015 23:34 UTC

Return-Path: <morrowc@ops-netman.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828BE1A8868 for <sidr@ietfa.amsl.com>; Tue, 25 Aug 2015 16:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 l364kbKH8fLR for <sidr@ietfa.amsl.com>; Tue, 25 Aug 2015 16:34:48 -0700 (PDT)
Received: from uu.ops-netman.net (maild1.aptea.com [206.112.93.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237D01A884B for <sidr@ietf.org>; Tue, 25 Aug 2015 16:34:47 -0700 (PDT)
Received: from mail.ops-netman.net (unknown [208.76.12.119]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by uu.ops-netman.net (Postfix) with ESMTPS id 7FA57C006B; Tue, 25 Aug 2015 23:34:46 +0000 (UTC)
Received: from morrowc-glaptop4.roam.corp.google.com.ops-netman.net (71-15-232-160.dhcp.sffl.va.charter.com [71.15.232.160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id A9F968801A5; Tue, 25 Aug 2015 23:34:45 +0000 (UTC)
Date: Tue, 25 Aug 2015 19:34:43 -0400
Message-ID: <yj9o61436iy4.wl%morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
In-Reply-To: <20150825224552.44588180472@rfc-editor.org>
References: <20150825224552.44588180472@rfc-editor.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.3 Mule/6.0 (HANACHIRUSATO)
Organization: Operations Network Management, Ltd.
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/lW6wpDHq_2tX27452HPTEYbr3s8>
Cc: db3546@att.com, sidr@ietf.org, morrowc@ops-netman.net, sandy@tislabs.com, david@mandelberg.org
Subject: Re: [sidr] [Editorial Errata Reported] RFC7132 (4454)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 25 Aug 2015 23:34:49 -0000

This seems correct to me (the proposed change I mean)

At Tue, 25 Aug 2015 15:45:52 -0700 (PDT),
RFC Errata System wrote:
> 
> The following errata report has been submitted for RFC7132,
> "Threat Model for BGP Path Security".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7132&eid=4454
> 
> --------------------------------------
> Type: Editorial
> Reported by: David Mandelberg <david@mandelberg.org>
> 
> Section: 1
> 
> Original Text
> -------------
>    PATHSEC is intended to address the concerns cited above, to provide
>    significantly improved path security, which builds upon the route
>    origination validation capability offered by use of the RPKI
>    [RFC6810].
> 
> Corrected Text
> --------------
>    PATHSEC is intended to address the concerns cited above, to provide
>    significantly improved path security, which builds upon the route
>    origination validation capability offered by use of the RPKI
>    [RFC6811].
> 
> Notes
> -----
> I think this text should reference RFC6811 (origin validation), not RFC6810 (the rpki-rtr protocol).
> 
> 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 (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC7132 (draft-ietf-sidr-bgpsec-threats-09)
> --------------------------------------
> Title               : Threat Model for BGP Path Security
> Publication Date    : February 2014
> Author(s)           : S. Kent, A. Chi
> Category            : INFORMATIONAL
> Source              : Secure Inter-Domain Routing
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG