Internet DRAFT - draft-sonoda-dnsop-lb
draft-sonoda-dnsop-lb
Domain Name System Operations Sonoda, Ed.
Internet-Draft Internet Initiative Japan Inc.
Intended status: Informational Mar 24, 2019
Expires: September 25, 2019
IP Location Load Balancing Resource Record
draft-sonoda-dnsop-lb-01
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 September 25, 2019.
Copyright Notice
Copyright (c) 2019 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 September 25, 2019 [Page 1]
Internet-Draft Abbreviated Title Mar 2019
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. Current DNS load balancing
Current 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 Current DNS load balancing is not secure. Because Current 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. Propose new DNS load balancing
Propose 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.
"location.server" 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 September 25, 2019 [Page 2]
Internet-Draft Abbreviated Title Mar 2019
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
names of countries and their subdivisions.
<asn code> ::= "AS" <asn> [ ":" <asn>]
<private code> ::= "+" <let>
<ans> ::= <nonzero digit> <digit>
<nonzero digit> ::= any one of the ten digits 1 through 9
<digit> ::= any one of the ten digits 0 through 9
<let> ::= any one of the 26 alphabetic characters A through Z in
upper case or any one of the ten digits 0 through 9.
2.2. Record example
example.jp. 3600 IN LB 1 * www.example.com. ; for any region
example.jp. 3600 IN LB 1 AS as.example.com. ; for ASIA region
example.jp. 3600 IN LB 1 JP jp1.example.jp. ; for JP region, weight 1
example.jp. 3600 IN LB 3 JP jp2.example.jp. ; for JP region, weight 3
example.jp. 3600 IN LB 1 JP-13 tokyo.example.jp. ; for tokyo region
example.jp. 3600 IN LB 1 AS2496 as65536.example.jp. ; for AS2496
example.jp. 3600 IN LB 1 AS2496:1 as65536.example.jp. ; for AS2496
example.jp. 3600 IN LB 1 +BEER beer.example.jp. ; private use
Sonoda Expires September 25, 2019 [Page 3]
Internet-Draft Abbreviated Title Mar 2019
3. Full service resolver's location
"location.server" is special TXT record that is locations at full
service resolver. Locations in order of priority location that
resolver administrator like it. Apiplcation can use it for selecting
location.
3.1. Record example
location.server 0 CH TXT "AS2479" "JP-13" "JP" "AS" "*"
4. IANA Considerations
IANA is requested to assign a DNS RR data type value for the LB RR
type under the "Resource Record (RR) TYPEs" sub-registry under the
"Domain Name System (DNS) Parameters" registry.
5. Normative References
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <https://www.rfc-editor.org/info/rfc1035>.
Author's Address
Manabu Sonoda (editor)
Internet Initiative Japan Inc.
Email: manabu-s@iij.ad.jp
Sonoda Expires September 25, 2019 [Page 4]
