Parameterized Nameserver Delegation with NS2 and NS2T
draft-tapril-ns2-01

Document Type Active Internet-Draft (individual)
Author Tim April 
Last updated 2020-07-13
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                                                           T. April
Internet-Draft                                       Akamai Technologies
Intended status: Informational                              13 July 2020
Expires: 14 January 2021

         Parameterized Nameserver Delegation with NS2 and NS2T
                          draft-tapril-ns2-01

Abstract

   Within the DNS, there is no mechanism for authoritative servers to
   advertise which transport methods they are capable of.  If secure
   transport methods are adopted by authoritative operators, transport
   signaling would be required to negotiate how authoritative servers
   would be contacted by resolvers.  This document provides two new
   Resource Record Types, NS2 and NS2T, to facilitate this negotiation
   by allowing zone owners to signal how the authoritative nameserver(s)
   for their zone(s) may accept queries.

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/timapril/ns2 (https://github.com/timapril/ns2).

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 14 January 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

April                    Expires 14 January 2021                [Page 1]
Internet-Draft                     NS2                         July 2020

   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
   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.  Introductory Examples . . . . . . . . . . . . . . . . . .   3
     1.2.  Goal of the NS2 and NS2T Records  . . . . . . . . . . . .   4
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  NS2 and NS2T Record Types . . . . . . . . . . . . . . . . . .   5
     2.1.  Difference between the records  . . . . . . . . . . . . .   5
     2.2.  AliasForm Record Type . . . . . . . . . . . . . . . . . .   6
       2.2.1.  Multiple Service Providers  . . . . . . . . . . . . .   6
       2.2.2.  Loop Prevention . . . . . . . . . . . . . . . . . . .   7
     2.3.  ServiceForm Record Type . . . . . . . . . . . . . . . . .   7
       2.3.1.  SvcFieldPriority  . . . . . . . . . . . . . . . . . .   7
       2.3.2.  SvcDomainName . . . . . . . . . . . . . . . . . . . .   7
       2.3.3.  SvcParamKeys  . . . . . . . . . . . . . . . . . . . .   8
     2.4.  Deployment Considerations . . . . . . . . . . . . . . . .  10
       2.4.1.  AliasForm and ServiceForm in the Parent . . . . . . .  10
       2.4.2.  Rollout . . . . . . . . . . . . . . . . . . . . . . .  11
       2.4.3.  Availability  . . . . . . . . . . . . . . . . . . . .  11
       2.4.4.  Multiple ServiceForm records for the same host or IP
               address . . . . . . . . . . . . . . . . . . . . . . .  11
   3.  Responses with NS2  . . . . . . . . . . . . . . . . . . . . .  12
     3.1.  Response Size Considerations  . . . . . . . . . . . . . .  12
     3.2.  When to include glue  . . . . . . . . . . . . . . . . . .  13
   4.  DNSSEC and NS2  . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Privact Considerations  . . . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     6.1.  Availability of zones without NS  . . . . . . . . . . . .  13
     6.2.  Reflection Attacks  . . . . . . . . . . . . . . . . . . .  13
     6.3.  Parsing . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.4.  Availability  . . . . . . . . . . . . . . . . . . . . . .  14
     6.5.  Connetion Failures  . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  New registry for NS2 transports . . . . . . . . . . . . .  14
Show full document text