Omniscient AS112 Servers
draft-wkumari-dnsop-omniscient-as112-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-25
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                          W. Kumari
Internet-Draft                                                    Google
Updates: 6304 (if approved)                                 W. Sotomayor
Intended status: Informational                                  NRC-CNRC
Expires: August 29, 2013                                        J. Abley
                                                                   ICANN
                                                               R. Bellis
                                                              Nominet UK
                                                       February 25, 2013

                        Omniscient AS112 Servers
                draft-wkumari-dnsop-omniscient-as112-02

Abstract

   The AS112 Project loosely coordinates Domain Name System (DNS)
   servers to which DNS zones corresponding to private use addresses are
   delegated.  Queries for names within those zones have no useful
   responses in a global context.  The purpose of this project is to
   reduce the load of such junk queries on the authoritative name
   servers that would otherwise receive them, and instead direct the
   load to name servers operated within the AS112 project.

   Adding and dropping zones from the AS112 servers is difficult, due to
   the loosely-coordinated nature of the project.  This document
   proposes a mechanism by which AS112 name servers could answer
   authoritatively for all possible zones.  This eliminates the add/drop
   problem, changing it to a matter of delegation within the DNS and
   requiring no operational changes on the servers themselves.

   This document updates RFC 6304.

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 http://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."

Kumari, et al.           Expires August 29, 2013                [Page 1]
Internet-Draft          Omniscient AS112 Servers           February 2013

   This Internet-Draft will expire on August 29, 2013.

Copyright Notice

   Copyright (c) 2013 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
   (http://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.

Kumari, et al.           Expires August 29, 2013                [Page 2]
Internet-Draft          Omniscient AS112 Servers           February 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Protocol Considerations  . . . . . . . . . . . . . . . . . . .  5
   4.  Operational Considerations . . . . . . . . . . . . . . . . . .  6
   5.  Addressing Considerations  . . . . . . . . . . . . . . . . . .  7
   6.  Updates to RFC 6304  . . . . . . . . . . . . . . . . . . . . .  7
     6.1.  Changes to Section 3.4, Routing Software . . . . . . . . .  7
     6.2.  Changes to Section 3.5, DNS Software . . . . . . . . . . .  9
     6.3.  Changes to Section 3.6, Testing a Newly Installed Node . .  9
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
     10.2. Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Implementation / "Running Code" . . . . . . . . . . . 10
   Appendix B.  Document Notes  . . . . . . . . . . . . . . . . . . . 11
     B.1.  Venue  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     B.2.  Textual Substitutions  . . . . . . . . . . . . . . . . . . 11
     B.3.  Open Questions . . . . . . . . . . . . . . . . . . . . . . 11
     B.4.  Change History . . . . . . . . . . . . . . . . . . . . . . 11
       B.4.1.  draft-wkumari-dnsop-omniscient-as112-00  . . . . . . . 12
Show full document text