[Sidrops] BCP 185, RFC 9319 on The Use of maxLength in the Resource Public Key Infrastructure (RPKI)
rfc-editor@rfc-editor.org Fri, 21 October 2022 19:16 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C14EC159483; Fri, 21 Oct 2022 12:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 pNEiV8KsRwMt; Fri, 21 Oct 2022 12:16:03 -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 616FCC159489; Fri, 21 Oct 2022 12:16:03 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F297B55D32; Fri, 21 Oct 2022 12:16:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidrops@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221021191602.F297B55D32@rfcpa.amsl.com>
Date: Fri, 21 Oct 2022 12:16:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/R0qKilYrrnILjYsWrd9OhM3-oro>
Subject: [Sidrops] BCP 185, RFC 9319 on The Use of maxLength in the Resource Public Key Infrastructure (RPKI)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2022 19:16:07 -0000
A new Request for Comments is now available in online RFC libraries. BCP 185 RFC 9319 Title: The Use of maxLength in the Resource Public Key Infrastructure (RPKI) Author: Y. Gilad, S. Goldberg, K. Sriram, J. Snijders, B. Maddison Status: Best Current Practice Stream: IETF Date: October 2022 Mailbox: yossigi@cs.huji.ac.il, goldbe@cs.bu.edu, kotikalapudi.sriram@nist.gov, job@fastly.com, benm@workonline.africa Pages: 13 See Also: BCP 185 I-D Tag: draft-ietf-sidrops-rpkimaxlen-15.txt URL: https://www.rfc-editor.org/info/rfc9319 DOI: 10.17487/RFC9319 This document recommends ways to reduce the forged-origin hijack attack surface by prudently limiting the set of IP prefixes that are included in a Route Origin Authorization (ROA). One recommendation is to avoid using the maxLength attribute in ROAs except in some specific cases. The recommendations complement and extend those in RFC 7115. This document also discusses the creation of ROAs for facilitating the use of Distributed Denial of Service (DDoS) mitigation services. Considerations related to ROAs and RPKI-based Route Origin Validation (RPKI-ROV) in the context of destination-based Remotely Triggered Discard Route (RTDR) (elsewhere referred to as "Remotely Triggered Black Hole") filtering are also highlighted. This document is a product of the SIDR Operations Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC