Intended status: Standards Track
draft-eromenko-ipff-dns-02

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
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)
INTERNET-DRAFT
"Internet Protocol Five Fields - Domain Name System extensions", 
Alexey Eromenko, 2016-09-29,
<draft-eromenko-ipff-dns-02.txt>
expiration date: 2017-03-29

Intended status: Standards Track

                                                              A.Eromenko
                                                          September 2016

                 DNS Extensions to Support IP Version 5 
                (a.k.a Internet Protocol "Five Fields")
                        Specification Draft

Abstract

   This document defines the changes that need to be made to the Domain
   Name System (DNS) to support hosts running IP version 5 (IPFF).  The
   changes include a resource record type to store an IPFF address, a
   domain to support lookups based on an IPFF address, and updated
   definitions of existing query types that return Internet addresses as
   part of additional section processing.  The extensions are designed
   to be compatible with existing applications and, in particular, DNS
   implementations themselves.

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."

Copyright Notice

   Copyright (c) 2015 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  New resource record definition and domain. . . . . . . . . . .  2
       2.1.  AA record type . . . . . . . . . . . . . . . . . . . . .  3
       2.2.  AA data format . . . . . . . . . . . . . . . . . . . . .  3
       2.3.  AA query . . . . . . . . . . . . . . . . . . . . . . . .  3
       2.4.  Textual format of AA records . . . . . . . . . . . . . .  3
       2.5.  Reverse Lookups and PTR records. . . . . . . . . . . . .  3
   3.  Modifications to existing query types. . . . . . . . . . . . .  4
   4.  Enforcing 999-per-field limit. . . . . . . . . . . . . . . . .  4
   5.  Security Considerations. . . . . . . . . . . . . . . . . . . .  4

   Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . .  5
   Authors' Contacts  . . . . . . . . . . . . . . . . . . . . . . . .  7
   Full Copyright Statement . . . . . . . . . . . . . . . . . . . . .  8

1. Introduction

   Current support for the storage of Internet addresses in the Domain
   Name System (DNS) cannot easily be extended to support IPFF
   addresses [IPFF-Addressing-RFC-draft] since applications assume that 
   address queries return 32-bit IPv4 or 128-bit IPv6 addresses only.

   To support the storage of IPFF addresses in the DNS, this document
   defines the following extensions:

      o A resource record type is defined to map a domain name to an
        IPFF address.

      o A domain is defined to support lookups based on address.

      o Existing queries that perform additional section processing to
        locate IPFF addresses are redefined to perform additional
        section processing on both IPv4 and IPFF addresses.

   The changes are designed to be compatible with existing software.
   The existing support for IPv4 addresses is retained.  

   The IP protocol version used for querying resource records is
   independent of the protocol version of the resource records; e.g.,
   IPv4 or IPv6 transport can be used to query IPFF records and vice 
   versa.

2. New resource record definition and domain

   A record type is defined to store a host's IPFF address.  A host that
   has more than one IPFF address must have more than one such record.

   AA explanation:

   "AA record" was chosen, as it mimics the idea behind "A" being a 
   32-bit value of IPv4, compared to "AAAA" (Quad A) being a 128-bit 
Show full document text