| Internet-Draft | rdap-geofeed | July 2023 |
| Singh & Harrison | Expires 30 January 2024 | [Page] |
This document defines a new RDAP extension geofeedv1 for including a geofeed
file URL in an IP Network object.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 30 January 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC8805] and [I-D.ymbk-opsawg-9092-update] (obsoletes [RFC9092]) detail
the IP geolocation feed (in short, geofeed) concept. This document specifies
how the geofeed data can be accessed through RDAP. It defines a new RDAP
extension geofeedv1 for including a geofeed file URL in an IP Network object.¶
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
A new RDAP extension geofeedv1 is defined for accessing the geofeed data
through RDAP. It extends the IP Network object class [RFC9083] to include
a new geofeed member.¶
An RDAP server conforming to this specification MUST include the geofeedv1
extension string in the rdapConformance array for the IP Network lookup and
search responses, as well as in the help response.¶
The IP Network object class is extended to include a new geofeed member, as
specified below:¶
geofeed — a string specifying the HTTPS URL of the geofeed file for an IP network [RFC9092]¶
Since this specification extends the base definition of the IP Network object
class, per Section 6 of [RFC7480], the geofeed member name MUST be prefixed
with the geofeedv1 extension string, followed by an underscore:
geofeedv1_geofeed.¶
The geofeed member is OPTIONAL for the geofeedv1 extension. Furthermore,
the Redaction by Removal method [I-D.ietf-regext-rdap-redacted] SHOULD be
used when redacting this member.¶
Here is an elided example of an IP Network object with the geofeedv1 extension
and the geofeedv1_geofeed member:¶
{
"rdapConformance" : [
"rdap_level_0",
"geofeedv1"
],
"objectClassName" : "ip network",
"handle" : "XXXX-RIR",
"startAddress" : "2001:db8::",
"endAddress" : "2001:db8:0:ffff:ffff:ffff:ffff:ffff",
"ipVersion" : "v6",
"name": "NET-RTR-1",
"type" : "DIRECT ALLOCATION",
"country" : "AU",
"parentHandle" : "YYYY-RIR",
"status" : [ "active" ],
…
"geofeedv1_geofeed" : "https:example.net/geofeed"
}
¶
When including a geofeed file URL in an IP Network object, an RDAP server operator SHOULD follow the guidance from Section 7 of [I-D.ymbk-opsawg-9092-update] to not accidentally expose the location of an individual.¶
[I-D.ymbk-opsawg-9092-update] requires an HTTPS URL for a geofeed file, and optionally RPKI-signing the data within. Besides that, this document does not introduce any new security considerations past those already discussed in the RDAP protocol specifications.¶
IANA is requested to register the following value in the RDAP Extensions Registry:¶
Extension identifier: geofeedv1¶
Registry operator: Any¶
Published specification: This document.¶
Contact: IETF iesg@ietf.org¶
Intended usage: This extension describes version 1 of a method to access the IP geolocation feed data through RDAP.¶