Recursive Resolvers IP Ranges location distribution and discovery
draft-bretelle-dnsop-recursive-iprange-location-01

Document Type Active Internet-Draft (individual)
Author Emmanuel Bretelle 
Last updated 2020-10-29
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dnsop                                                        E. Bretelle
Internet-Draft                                                  Facebook
Intended status: Standards Track                         29 October 2020
Expires: 2 May 2021

   Recursive Resolvers IP Ranges location distribution and discovery
           draft-bretelle-dnsop-recursive-iprange-location-01

Abstract

   This document specifies a way for recursive resolvers operators to
   signal the IP ranges and locations used by their server pools.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/chantra/draft-dns-recursive-iprange-location.

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 2 May 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

Bretelle                   Expires 2 May 2021                   [Page 1]
Internet-Draft             dns-recursive-iploc              October 2020

   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Publishing Resolver pool IP ranges  . . . . . . . . . . . . .   3
     3.1.  TXT Resource Record . . . . . . . . . . . . . . . . . . .   3
     3.2.  HTTPS Resource Record . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Consideration  . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Underscored Node Name . . . . . . . . . . . . . . . . . .   4
     5.2.  URI DNS Service Parameter . . . . . . . . . . . . . . . .   5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Document history . . . . . . . . . . . . . . . . . .   6
     A.1.  Changes between -00 and -01 . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Big distributed recursive resolver pools tend to be distributed
   across the world, operating under multiple countries and possibly
   using IP ranges for which the country is not necessarily perfectly
   matching the location of the service.  This has lead to sub-optimal
   answers being returned to those server pools.  An solution to this
   problem has been to use EDNS Client Subnet (ECS) [RFC7871], but this
   require support from both the recursive resolvers and the name
   servers authorities, comes with its own Security Considerations, and
   increased resources usage.

   DNS server operators are commonly receiving spoofed DNS traffic over
   UDP, common techniques have been to reply with TC bit set to force
   legitimate clients to use TCP, if the load is still too high, they
   may start to drop traffic from selected subnets.  While this may
   protect their resources, it has the possibility of denying the
   service to legitimate resolvers.

   So far, operators have resorted to ad-hoc mechanism, ranging from
   exchanging list by email, providing IP ranges and location via
   webpages, or specific DNS queries, like Google Public DNS
   (https://developers.google.com/speed/public-dns/faq#locations_of_ip_a
   ddress_ranges_google_public_dns_uses_to_send_queries), or Cloudflare
   (https://www.cloudflare.com/ips/), or OpenDNS

Bretelle                   Expires 2 May 2021                   [Page 2]
Internet-Draft             dns-recursive-iploc              October 2020
Show full document text