RFC 9632: Finding and Using Geofeed Data
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9632
- Published
- August 2024
- Authors
- R. Bush; M. Candela; W. Kumari; R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
- Obsoletes:
- RFC 9092
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9977Publishing End-Site Prefix LengthsCurrent
May 2026
- RFC 9179A YANG Grouping for Geographic LocationsCurrent
February 2022
- RFC 8805A Format for Self-Published IP Geolocation FeedsCurrent
August 2020
- RFC 7871Client Subnet in DNS QueriesCurrent
May 2016
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
- RFC 2769Routing Policy System ReplicationCurrent
February 2000
- RFC 2725Routing Policy System SecurityUpdated
December 1999
- RFC 2622Routing Policy Specification Language (RPSL)Updated
June 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?