Re: [sidr] [Errata Held for Document Update] RFC7132 (4454)

Stephen Kent <kent@bbn.com> Fri, 26 February 2016 20:41 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 989101B2FE4; Fri, 26 Feb 2016 12:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 quUp_rRy7myg; Fri, 26 Feb 2016 12:41:51 -0800 (PST)
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 18B171B3007; Fri, 26 Feb 2016 12:41:46 -0800 (PST)
Received: from ssh.bbn.com ([192.1.122.15]:52699 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1aZPCj-000EAu-Ts; Fri, 26 Feb 2016 15:41:38 -0500
To: RFC Errata System <rfc-editor@rfc-editor.org>, david@mandelberg.org, achi@cs.unc.edu
References: <20160216212937.B0D3B180009@rfc-editor.org>
From: Stephen Kent <kent@bbn.com>
Message-ID: <56D0B881.6030104@bbn.com>
Date: Fri, 26 Feb 2016 15:41:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160216212937.B0D3B180009@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/56jS8Z0HOgnrbft4l3_YP3FjPIM>
Cc: iesg@ietf.org, sidr@ietf.org
Subject: Re: [sidr] [Errata Held for Document Update] 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: Fri, 26 Feb 2016 20:41:52 -0000

I concur with David's observation. The reference has a typo and is fixed
by his suggested change.

Steve


> The following errata report has been held for document update
> 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
>
> --------------------------------------
> Status: Held for Document Update
> Type: Editorial
>
> Reported by: David Mandelberg <david@mandelberg.org>
> Date Reported: 2015-08-25
> Held by: Alvaro Retana (IESG)
>
> 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).
>
> --------------------------------------
> 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
>
>