[sidr] [Technical Errata Reported] RFC6482 (7525)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 26 May 2023 18:49 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 9698AC151B2E for <sidr@ietfa.amsl.com>; Fri, 26 May 2023 11:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.947
X-Spam-Level:
X-Spam-Status: No, score=-3.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 215eBX9ggiRo for <sidr@ietfa.amsl.com>; Fri, 26 May 2023 11:49:30 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADCFCC151B29 for <sidr@ietf.org>; Fri, 26 May 2023 11:49:30 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 82A2255D5E; Fri, 26 May 2023 11:49:30 -0700 (PDT)
To: mlepinski@bbn.com, skent@bbn.com, dkong@bbn.com, aretana.ietf@gmail.com, jgs@juniper.net, andrew-ietf@liquid.tech, morrowc@ops-netman.net, sandy@tislabs.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: sachaboudjema@gmail.com, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230526184930.82A2255D5E@rfcpa.amsl.com>
Date: Fri, 26 May 2023 11:49:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/xWoFdEE-TwOnj2wFJbGSOE_qpJI>
Subject: [sidr] [Technical Errata Reported] RFC6482 (7525)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.39
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 May 2023 18:49:34 -0000
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/eid7525 -------------------------------------- Type: Technical Reported by: Sacha Boudjema <sachaboudjema@gmail.com> Section: 3.3 Original Text ------------- Within the ROAIPAddressFamily structure, addressFamily contains the Address Family Identifier (AFI) of an IP address family. This specification only supports IPv4 and IPv6. Therefore, addressFamily MUST be either 0001 or 0002. Within a ROAIPAddress structure, the addresses field represents prefixes as a sequence of type IPAddress. (See [RFC3779] for more details). If present, the maxLength MUST be an integer ... Corrected Text -------------- Within the ROAIPAddressFamily structure, addressFamily contains the Address Family Identifier (AFI) of an IP address family. This specification only supports IPv4 and IPv6. Therefore, addressFamily MUST be either 0001 or 0002. The addresses field represents prefixes as a sequence of type ROAIPAddress. Within the ROAIPAddress structure, the address field represents an IPv4 or IPv6 prefix of type IPaddress (See [RFC3779] for more details). If present, the maxLength MUST be an integer ... Notes ----- Original text contradicts does not align with normative ASN.1 schema. 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
- [sidr] [Technical Errata Reported] RFC6482 (7525) RFC Errata System
- Re: [sidr] [Technical Errata Reported] RFC6482 (7… John Scudder
- Re: [sidr] [Sidrops] [Technical Errata Reported] … Job Snijders
- Re: [sidr] [Sidrops] [Technical Errata Reported] … John Scudder
- Re: [sidr] [Technical Errata Reported] RFC6482 (7… Russ Housley