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

Stephen Kent <kent@bbn.com> Wed, 26 August 2015 00:39 UTC

Return-Path: <kent@bbn.com>
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 DE9841A92E3 for <sidr@ietfa.amsl.com>; Tue, 25 Aug 2015 17:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YZf0bK33ir20 for <sidr@ietfa.amsl.com>; Tue, 25 Aug 2015 17:39:56 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E8361A92DD for <sidr@ietf.org>; Tue, 25 Aug 2015 17:39:56 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:42104 helo=COMSEC.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1ZUOkn-000KjL-Qr; Tue, 25 Aug 2015 20:39:49 -0400
To: Chris Morrow <morrowc@ops-netman.net>, RFC Errata System <rfc-editor@rfc-editor.org>
References: <20150825224552.44588180472@rfc-editor.org> <yj9o61436iy4.wl%morrowc@ops-netman.net>
From: Stephen Kent <kent@bbn.com>
Message-ID: <55DD0AD5.4010406@bbn.com>
Date: Tue, 25 Aug 2015 20:39:49 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <yj9o61436iy4.wl%morrowc@ops-netman.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/2VHcOLhqODLCM5L5kOmiSNYJQfQ>
Cc: db3546@att.com, sidr@ietf.org, 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: Wed, 26 Aug 2015 00:39:58 -0000

yes, I concur as well.

Steve

> 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