RFC 9632 on Finding and Using Geofeed Data
rfc-editor@rfc-editor.org Wed, 07 August 2024 22:51 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B9A2C16941F; Wed, 7 Aug 2024 15:51:42 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id E69607FA60; Wed, 7 Aug 2024 15:51:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9632 on Finding and Using Geofeed Data
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240807225141.E69607FA60@rfcpa.rfc-editor.org>
Date: Wed, 07 Aug 2024 15:51:41 -0700
Message-ID-Hash: 7JVTETBSOREWQNQUX2L4Z3LAVXLDW66L
X-Message-ID-Hash: 7JVTETBSOREWQNQUX2L4Z3LAVXLDW66L
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.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, opsawg@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/NLecPCkiidAcKdMXbW30OBUPFc8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9632
Title: Finding and Using Geofeed Data
Author: R. Bush,
M. Candela,
W. Kumari,
R. Housley
Status: Standards Track
Stream: IETF
Date: August 2024
Mailbox: randy@psg.com,
massimo@ntt.net,
warren@kumari.net,
housley@vigilsec.com
Pages: 23
Obsoletes: RFC 9092
I-D Tag: draft-ietf-opsawg-9092-update-11.txt
URL: https://www.rfc-editor.org/info/rfc9632
DOI: 10.17487/RFC9632
This document specifies how to augment the Routing Policy
Specification Language (RPSL) inetnum: class to refer specifically to
geofeed comma-separated values (CSV) data files and describes an
optional scheme that uses the Resource Public Key Infrastructure
(RPKI) to authenticate the geofeed data files. This document
obsoletes RFC 9092.
This document is a product of the Operations and Management Area Working Group 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
- RFC 9632 on Finding and Using Geofeed Data rfc-editor