An RDAP Extension for Geofeed Data
draft-ietf-regext-rdap-geofeed-00

Registration Protocols Extensions (regext)                      J. Singh
Internet-Draft                                                      ARIN
Intended status: Standards Track                             T. Harrison
Expires: 13 June 2024                                              APNIC
                                                        11 December 2023

                   An RDAP Extension for Geofeed Data
                   draft-ietf-regext-rdap-geofeed-00

Abstract

   This document defines a new RDAP extension geofeedv1 for including a
   geofeed file URL in an IP Network object.

Status of This Memo

   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 13 June 2024.

Copyright Notice

   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.

Singh & Harrison          Expires 13 June 2024                  [Page 1]
Internet-Draft                rdap-geofeed                 December 2023

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Extension . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.2.  Geofeed Member  . . . . . . . . . . . . . . . . . . . . .   2
     2.3.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [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.

1.1.  Requirements Language

   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.

2.  Specification

2.1.  Extension

   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.

2.2.  Geofeed Member

   The IP Network object class is extended to include a new geofeed
   member, as specified below:

Singh & Harrison          Expires 13 June 2024                  [Page 2]
Internet-Draft                rdap-geofeed                 December 2023

   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.

2.3.  Example

   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"
   }

3.  Privacy Considerations

   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.

Singh & Harrison          Expires 13 June 2024                  [Page 3]
Internet-Draft                rdap-geofeed                 December 2023

4.  Security Considerations

   [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.

5.  IANA Considerations

   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 (mailto:iesg@ietf.org)

   Intended usage: This extension describes version 1 of a method to
   access the IP geolocation feed data through RDAP.

6.  References

6.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC7480]  Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
              Registration Data Access Protocol (RDAP)", STD 95,
              RFC 7480, DOI 10.17487/RFC7480, March 2015,
              <https://www.rfc-editor.org/info/rfc7480>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8805]  Kline, E., Duleba, K., Szamonek, Z., Moser, S., and W.
              Kumari, "A Format for Self-Published IP Geolocation
              Feeds", RFC 8805, DOI 10.17487/RFC8805, August 2020,
              <https://www.rfc-editor.org/info/rfc8805>.

Singh & Harrison          Expires 13 June 2024                  [Page 4]
Internet-Draft                rdap-geofeed                 December 2023

   [RFC9083]  Hollenbeck, S. and A. Newton, "JSON Responses for the
              Registration Data Access Protocol (RDAP)", STD 95,
              RFC 9083, DOI 10.17487/RFC9083, June 2021,
              <https://www.rfc-editor.org/info/rfc9083>.

   [RFC9092]  Bush, R., Candela, M., Kumari, W., and R. Housley,
              "Finding and Using Geofeed Data", RFC 9092,
              DOI 10.17487/RFC9092, July 2021,
              <https://www.rfc-editor.org/info/rfc9092>.

6.2.  Informative References

   [I-D.ietf-regext-rdap-redacted]
              Gould, J., Smith, D., Kolker, J., and R. Carney, "Redacted
              Fields in the Registration Data Access Protocol (RDAP)
              Response", Work in Progress, Internet-Draft, draft-ietf-
              regext-rdap-redacted-16, 27 November 2023,
              <https://datatracker.ietf.org/doc/html/draft-ietf-regext-
              rdap-redacted-16>.

   [I-D.ymbk-opsawg-9092-update]
              Bush, R., Candela, M., Kumari, W. A., and R. Housley,
              "Finding and Using Geofeed Data", Work in Progress,
              Internet-Draft, draft-ymbk-opsawg-9092-update-02, 24 July
              2023, <https://datatracker.ietf.org/doc/html/draft-ymbk-
              opsawg-9092-update-02>.

Authors' Addresses

   Jasdip Singh
   ARIN
   Email: jasdips@arin.net

   Tom Harrison
   APNIC
   Email: tomh@apnic.net

Singh & Harrison          Expires 13 June 2024                  [Page 5]