Finding and Using Geofeed Data
draft-ietf-opsawg-finding-geofeeds-00

Document Type Active Internet-Draft (opsawg WG)
Authors Massimo Candela  , Randy Bush  , Warren Kumari  , Russ Housley 
Last updated 2020-11-15
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         M. Candela
Internet-Draft                                                       NTT
Intended status: Standards Track                                 R. Bush
Expires: May 19, 2021                                       IIJ & Arrcus
                                                               W. Kumari
                                                                  Google
                                                              R. Housley
                                                          Vigil Security
                                                       November 15, 2020

                     Finding and Using Geofeed Data
                 draft-ietf-opsawg-finding-geofeeds-00

Abstract

   This document describes how to find and authenticate geofeed data.

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 May 19, 2021.

Copyright Notice

   Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of

Candela, et al.           Expires May 19, 2021                  [Page 1]
Internet-Draft              Finding Geofeeds               November 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Geofeed Files . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  inetnum: Class  . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Authenticating Geofeed Data . . . . . . . . . . . . . . . . .   4
   5.  Operational Considerations  . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Example  . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Providers of Internet content and other services may wish to
   customize those services based on the geographic location of the user
   of the service.  This is often done using the source IP address used
   to contact the service.  Also, infrastructure and other services
   might wish to publish the locale of their services.  [RFC8805]
   defines geofeed, a syntax to associate geographic locales with IP
   addresses.  But it does not specify how to find the relevant geofeed
   data given an IP address.

   This document specifies how to augment the Routing Policy
   Specification Language (RPSL) [RFC2622] inetnum: class [INETNUM] to
   refer to geofeed data, and how to prudently use them.  In all places
   inetnum: is used, inet6num: should also be assumed [INET6NUM].

   An optional, but utterly awesome, means for authenticating geofeed
   data is also defined.

1.1.  Requirements Language

   The key words "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.

Candela, et al.           Expires May 19, 2021                  [Page 2]
Internet-Draft              Finding Geofeeds               November 2020

2.  Geofeed Files

   Geofeed files are described in [RFC8805].  They provide a facility
   for an IP address resource 'owner' to associate those IP addresses to
Show full document text