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

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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                             March 9, 2020
Expires: September 10, 2020

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

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, protocol
   negotiation would be required.  This document provides two new
   Resource Record Types, NS2 and NS2T, to facilitate that negotiation
   by allowing zone owners to signal how the authoritative nameserver(s)
   for their zone(s) may accept queries.

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 10, 2020.

Copyright Notice

   Copyright (c) 2020 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

April                  Expires September 10, 2020               [Page 1]
Internet-Draft                     NS2                        March 2020

   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 . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  NS2 and NS2T Record Types . . . . . . . . . . . . . . . . . .   4
     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 . . . . . . . . . . . . . . . . . . .   6
     2.3.  ServiceForm . . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.1.  SvcFieldPriority  . . . . . . . . . . . . . . . . . .   7
       2.3.2.  SvcDomainName . . . . . . . . . . . . . . . . . . . .   7
       2.3.3.  SvcParamKeys  . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Deployment Considerations . . . . . . . . . . . . . . . .  11
       2.4.1.  AliasForm and ServiceForm in the Parent . . . . . . .  11
       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  . . . . . . . . . . . . . . . . . .  12
   4.  DNSSEC and NS2  . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     5.1.  Availability of zones without NS  . . . . . . . . . . . .  13
     5.2.  Reflection Attacks  . . . . . . . . . . . . . . . . . . .  13
     5.3.  Parsing . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.4.  Availability  . . . . . . . . . . . . . . . . . . . . . .  13
     5.5.  Connetion Failures  . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  New registry for NS2 transports . . . . . . . . . . . . .  14
       6.1.1.  Procedure . . . . . . . . . . . . . . . . . . . . . .  14
       6.1.2.  Initial Contents  . . . . . . . . . . . . . . . . . .  14
     6.2.  New SvcParamKey Values  . . . . . . . . . . . . . . . . .  15
   7.  Informative References  . . . . . . . . . . . . . . . . . . .  16
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  17
Show full document text