Client Dualstack Subnets in DNS Queries
draft-song-dnsop-dualstack-ecs-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Internet Engineering Task Force                                  L. Song
Internet-Draft                                Beijing Internet Institute
Intended status: Standards Track                                 W. Liao
Expires: April 25, 2019                                          Tencent
                                                        October 22, 2018

                Client Dualstack Subnets in DNS Queries
                   draft-song-dnsop-dualstack-ecs-00

Abstract

   During the period of IPv6 transition, IP-based Geolocation (GeoIP)
   applications are identified as a challenge and speed bump for ICPs
   (Internet Content Providers) to migrating their service to IPv6.
   Some studies and operational experiences show that the accuracy of
   IPv6 GeoIP is relatively poor in comparison to their IPv4
   counterparts.  This memo proposed to include client's dualstack
   subnets into DNS queries to provide better IPv6 GeoIP.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [Dualstack-ECS-GitHub].
   Comments and pull request are welcome.

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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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

Song & Liao              Expires April 25, 2019                 [Page 1]
Internet-Draft   Client Dualstack Subnets in DNS Queries    October 2018

   (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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  GeoIP and its Challenge in IPv6 . . . . . . . . . . . . . . .   3
   3.  Methodology and targeted Senarios . . . . . . . . . . . . . .   4
   4.  Dual-stack EDNS Client Subnet . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   During the period of IPv6 transition, IP-based Geolocation (GeoIP)
   applications are identified as a challenge and speed bump for ICPs
   (Internet Content Providers) to migrating their service to IPv6.  The
   key issue on GeoIP is the accuracy which however vary between IPv4
   and IPv6.  Some studies and operational experiences [ipv6geo] show
   that the accuracy of IPv6 GeoIP is relatively poor in comparison to
   their IPv4 counterparts.

   One typical example of GeoIP application in DNS field is that many
   authoritative nameservers today return different and tailored
   responses based on the perceived topological location of the users.
   If IPv6 GeoIP is not precise enough, the performance of topology-
   sensitive authoritative nameserver is poorer in IPv6 than IPv4.
   Users' experience is impacted , and it may end up with hesitation for
   the authoritative DNS operator to update its DNS to Dual Stack.  It
   is a problem.

   To provide a better IPv6 tailored DNS response in dual-stack
   environment, this memo proposes to enable recursive server and Client
   to include their IPv4 and IPv6 subnets into ECS Option [RFC7871] in
   DNS queries.  Authoritative nameservers can make a better use of this
   dual-stack subnet information for a tailored response.

Song & Liao              Expires April 25, 2019                 [Page 2]
Internet-Draft   Client Dualstack Subnets in DNS Queries    October 2018

2.  GeoIP and its Challenge in IPv6

   Knowing where your customer access your Internet service is very
   important in modern Internet.  It can be used for geolocation-aware
Show full document text