ISP Location in DNS Queries
draft-pan-dnsop-edns-isp-location-02

Document Type Active Internet-Draft (individual)
Last updated 2017-07-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                             L. Pan
Internet-Draft
Intended status: Informational                                     Y. Fu
Expires: January 18, 2018                                          CNNIC
                                                           July 17, 2017

                      ISP Location in DNS Queries
                  draft-pan-dnsop-edns-isp-location-02

Abstract

   Nowadays, many Authoritative Nameservers support GeoIP feature, they
   guess the user's geolocation by the client subnet of EDNS Client
   Subnet (ECS) or by the source IP address of DNS query, return tailor
   DNS response based on the user's geolocation.  However, ECS raises
   some privacy concerns because it leaks client subnet information on
   the resolution path to the Authoritative Nameserver.

   This document is inspired by EDNS Client Subnet (ECS), describes an
   improved solution for GeoIP-enabled Authoritative Nameservers,
   defines an EDNS ISP Location (EIL) extension to address the privacy
   problem of ECS, tries to find the right balance between privacy
   improvement and user experience optimization.

   EIL is defined to convey isp location < COUNTRY, AREA, ISP >
   information that is relevant to the DNS message.  It will directly
   provide the same sufficient information for the GeoIP-enabled
   Authoritative Nameserver as ECS, to decide the response without
   guessing geolocation of the IP address.

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 http://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 January 18, 2018.

Pan & Fu                Expires January 18, 2018                [Page 1]
Internet-Draft         ISP Location in DNS Queries             July 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Path Calculation and Tailored DNS Response  . . . . . . .   4
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  The EIL EDNS0 option  . . . . . . . . . . . . . . . . . . . .   6
   6.  Protocol Description  . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Originating the Option  . . . . . . . . . . . . . . . . .   8
       6.1.1.  P-Model: Public Recursive Resolver  . . . . . . . . .   8
       6.1.2.  I-Model: ISP Recursive Resolver . . . . . . . . . . .   8
       6.1.3.  L-Model: Local Forwarding Resolver  . . . . . . . . .   9
     6.2.  Generating a Response . . . . . . . . . . . . . . . . . .   9
       6.2.1.  Whitelist . . . . . . . . . . . . . . . . . . . . . .   9
       6.2.2.  Authoritative Nameserver  . . . . . . . . . . . . . .   9
       6.2.3.  Intermediate Nameserver . . . . . . . . . . . . . . .  10
     6.3.  Handling EIL Responses and Caching  . . . . . . . . . . .  10
       6.3.1.  Caching the Response  . . . . . . . . . . . . . . . .  10
       6.3.2.  Answering from Cache  . . . . . . . . . . . . . . . .  10
       6.3.3.  Support ECS and EIL at the same time  . . . . . . . .  11
     6.4.  Delegations and Negative Answers  . . . . . . . . . . . .  12
     6.5.  Transitivity  . . . . . . . . . . . . . . . . . . . . . .  12
     6.6.  Response Accuracy . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     7.1.  DNSSEC  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.2.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text