Re: [sidr] [Technical Errata Reported] RFC6482 (5881)

Chris Morrow <morrowc@ops-netman.net> Thu, 24 October 2019 05:19 UTC

Return-Path: <morrowc@ops-netman.net>
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 951D212020A for <sidr@ietfa.amsl.com>; Wed, 23 Oct 2019 22:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.689
X-Spam-Level:
X-Spam-Status: No, score=-0.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 r-d_t_IUZXvs for <sidr@ietfa.amsl.com>; Wed, 23 Oct 2019 22:19:40 -0700 (PDT)
Received: from relay.ops-netman.net (relay.kvm02.ops-netman.net [IPv6:2606:700:e:550:5c82:28ff:fe4c:9503]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D541012000F for <sidr@ietf.org>; Wed, 23 Oct 2019 22:19:40 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [199.168.90.119]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by relay.ops-netman.net (Postfix) with ESMTPS id 854223C2302; Thu, 24 Oct 2019 05:19:39 +0000 (UTC)
Received: from mailserver.ops-netman.net.ops-netman.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id 55A837F0; Thu, 24 Oct 2019 05:19:39 +0000 (UTC)
Date: Thu, 24 Oct 2019 05:19:39 +0000
Message-ID: <874kzyiutw.wl-morrowc@ops-netman.net>
From: Chris Morrow <morrowc@ops-netman.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mlepinski@bbn.com, skent@bbn.com, dkong@bbn.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, morrowc@ops-netman.net, sandy@tislabs.com, housley@vigilsec.com, sidr@ietf.org
In-Reply-To: <20191023162426.2582CF40739@rfc-editor.org>
References: <20191023162426.2582CF40739@rfc-editor.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 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: <https://mailarchive.ietf.org/arch/msg/sidr/oqSXU4oOgYvxAq91NXK6fRkhhLo>
Subject: Re: [sidr] [Technical Errata Reported] RFC6482 (5881)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 24 Oct 2019 05:19:43 -0000

this seems legit.

On Wed, 23 Oct 2019 16:24:26 +0000,
RFC Errata System <rfc-editor@rfc-editor.org>; wrote:
> 
> The following errata report has been submitted for RFC6482,
> "A Profile for Route Origin Authorizations (ROAs)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5881
> 
> --------------------------------------
> Type: Technical
> Reported by: Russ Housley <housley@vigilsec.com>;
> 
> Section: Appendix A
> 
> Original Text
> -------------
>    END
> 
> 
> Corrected Text
> --------------
>    id-ct-routeOriginAuthz OBJECT IDENTIFIER ::= { 1 2 840 113549 1 9 16 1 24 }
> 
>    END
> 
> 
> Notes
> -----
> The object identifier for the ROA content type is mentioned in the document, but it is not included in the ASN.1 Module.
> 
> 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. 
> 
> --------------------------------------
> RFC6482 (draft-ietf-sidr-roa-format-12)
> --------------------------------------
> Title               : A Profile for Route Origin Authorizations (ROAs)
> Publication Date    : February 2012
> Author(s)           : M. Lepinski, S. Kent, D. Kong
> Category            : PROPOSED STANDARD
> Source              : Secure Inter-Domain Routing
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG