RFC 9877: Registration Data Access Protocol (RDAP) Extension for Geofeed Data

This document defines a new Registration Data Access Protocol (RDAP) extension, "geofeed1", for indicating that an RDAP server hosts geofeed URLs for its IP…

Read RFC 9877 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 9082: Registration Data Access Protocol (RDAP) Query Format
Normative reference — RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)
Normative reference — RFC 9224: Finding the Authoritative Registration Data Access Protocol (RDAP) Service
Normative reference — RFC 9632: Finding and Using Geofeed Data
Informative reference — RFC 6838: Media Type Specifications and Registration Procedures
Informative reference — RFC 6973: Privacy Considerations for Internet Protocols
Informative reference — RFC 6480: An Infrastructure to Support Secure Internet Routing
Informative reference — RFC 7481: Security Services for the Registration Data Access Protocol (RDAP)
Informative reference — RFC 2622: Routing Policy Specification Language (RPSL)
Informative reference — RFC 7480: HTTP Usage in the Registration Data Access Protocol (RDAP)
Informative reference — RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files
Informative reference — RFC 8805: A Format for Self-Published IP Geolocation Feeds
Informative reference — RFC 7111: URI Fragment Identifiers for the text/csv Media Type
Informative reference — RFC 9560: Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9977: Publishing End-Site Prefix Lengths