ObsoletedPROPOSED STANDARDIETF stream

RFC 9092: Finding and Using Geofeed Data

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9632.

Current version: RFC 9632Finding 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 inetnum: class to refer specifically to geofeed data comma-separated values (CSV) files and describes an optional scheme that uses the Routing Public Key Infrastructure to authenticate the geofeed data CSV files.

Document record

Document ID
RFC9092
Published
July 2021
Authors
R. Bush; M. Candela; W. Kumari; R. Housley
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
21
Also known as
Obsoleted by:
RFC 9632

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9092-finding-and-using-geofeed-data