[Sidrops] RFC 9582 on A Profile for Route Origin Authorizations (ROAs)

rfc-editor@rfc-editor.org Thu, 23 May 2024 20:26 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 D62D0C180B41; Thu, 23 May 2024 13:26:03 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 1BFB7C000063; Thu, 23 May 2024 13:26:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240523202603.1BFB7C000063@rfcpa.rfc-editor.org>
Date: Thu, 23 May 2024 13:26:03 -0700
Message-ID-Hash: DUPZRNVS2A74RUGABGPYNV3LE724LVNQ
X-Message-ID-Hash: DUPZRNVS2A74RUGABGPYNV3LE724LVNQ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidrops@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Sidrops] RFC 9582 on A Profile for Route Origin Authorizations (ROAs)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9582

        Title:      A Profile for Route Origin 
                    Authorizations (ROAs) 
        Author:     J. Snijders,
                    B. Maddison,
                    M. Lepinski,
                    D. Kong,
                    S. Kent
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2024
        Mailbox:    job@fastly.com,
                    benm@workonline.africa,
                    mlepinski@carleton.edu,
                    derrick.kong@raytheon.com,
                    kent@alum.mit.edu
        Pages:      15
        Obsoletes:  RFC 6482

        I-D Tag:    draft-ietf-sidrops-rfc6482bis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc9582

        DOI:        10.17487/RFC9582

This document defines a standard profile for Route Origin
Authorizations (ROAs). A ROA is a digitally signed object that
provides a means of verifying that an IP address block holder has
authorized an Autonomous System (AS) to originate routes to one or
more prefixes within the address block. This document obsoletes RFC
6482.

This document is a product of the SIDR Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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