IP geolocation load balancing Resource Record
draft-sonoda-dnsop-lb-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-18
Replaces draft-sonoda-dnsop-dnslb
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)
Domain Name System Operations                                     Sonoda
Internet-Draft                            Internet Initiative Japan Inc.
Intended status: Informational                              Sep 18, 2018
Expires: March 22, 2019

             IP geolocation load balancing Resource Record
                        draft-sonoda-dnsop-lb-00

Abstract

   This document defines a new DNS load balance function that is able to
   transfer information in zone transfer and not need online signing.
   DNS base load balance is popular technology.  It provides weight base
   response and location base response.  It have become an indispensable
   part of traffic engineering.  However, DNS base load balance can't
   transfer load balance information in zone transfer and need online
   singing because it is not standardized.  This document defines a new
   DNS resource record called "LB".  LB RR provides the balancing
   information weight, location and target domain name.

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 March 22, 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
   (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

Sonoda                   Expires March 22, 2019                 [Page 1]
Internet-Draft              Abbreviated Title                   Sep 2018

   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.

1.  Introduction

1.1.  Legacy DNS load balancing

   Legacy DNS load balancing provides traffic engineering.It use special
   authoritative name server.  It response is one address record that is
   dynamic changes using network location and weight.  It's used for
   large traffic WEB site domain name that is important domain name.
   Important domain name should be secure.

   But legacy DNS load balancing is not secure.  Because Legacy DNS load
   balancing can't send zone data by zone transfer.  It's mean very
   difficult to use multi service providers.  That means weak for DDoS
   Attack.  If zone is signed, All name servers require private key for
   dynamic signing because response is dynamic changes.  Distributing
   private key is not secure, It is increased risk of leakage private
   key.

1.2.  New DNS load balancing

   New DNS load balancing concept is that Authoritative name server uses
   "LB" RR to provide load balancing information and Clients application
   uses "LB" RR to select target name.

   "LB" RR defines load balancing settings that is network location and
   weight and target domain name.  Network location is string that
   meaningful name of network.  For example Country code (ex.
   JP),subdivision code(ex.  US-CA) and Autonomous System Number (ex.
   AS65536).  Weight is ratio value to use select target name.  Target
   name is pointer to address record.

   "server.location" is special TXT record that is location information
   at full service resolver.  Application can use this value for
   location selection.

2.  The LB Resource Record

   The LB RR has mnemonic LB.  LB RR define load balancing information.

   LB format below.

         <owner> <ttl> <class> LB <weight> <location> <target>

Sonoda                   Expires March 22, 2019                 [Page 2]
Internet-Draft              Abbreviated Title                   Sep 2018

   The format is not class-sensitive.  All fields are required.

   <weight> field is a 2 octets, 1 or more natural number.

   <location> field is a "<character-string>" [RFC1035].

   <target> field is a "<domain-name>" [RFC1035].

2.1.  Define location

   <location> ::= "*" | <continental code> | <country code> |
   <subdivision code> | <asn code> | <private code>

   <region code> ::= "AF" | "NA" | "AS" | "EU" | "NA" | "OC" | "SA"

   <country code> ::= ISO 3166-1 alpha-2 Country code.

   <subdivision code> ::= ISO 3166-2 Codes for the representation of
Show full document text