IVIPTR: Resource Record for DNS
draft-tariq-dnsop-iviptr-01

Document Type Active Internet-Draft (individual)
Last updated 2018-05-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml ps 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)
DNSOP                                                      T. Saraj, Ed.
Internet-Draft                                                 M. Yousaf
Intended status: Standards Track Riphah Institute of Systems Engineering
Expires: November 12, 2018                                     A. Qayyum
                            Capital University of Science and Technology
                                                            May 11, 2018

                    IVIPTR: Resource Record for DNS
                      draft-tariq-dnsop-iviptr-01

Abstract

   This document proposes a new DNS Resource Record IVIPTR which
   provides the capability to resolve the IPv4 address to IPv6 address
   and IPv6 address to IPv4 address.  This document assumes that the
   reader is familiar with all the concepts and details discussed in
   Domain Names Concepts and Facilities [RFC1034] , Domain Names -
   Implementation and Specification [RFC1035]

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 November 12, 2018.

Copyright Notice

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

Saraj, et al.           Expires November 12, 2018               [Page 1]
Internet-Draft       IVIPTR: Resource Record for DNS            May 2018

   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.  Motivation and Usecases . . . . . . . . . . . . . . . . . . .   4
     2.1.  Usecase-01: Firewall Automation . . . . . . . . . . . . .   4
     2.2.  Usecase-02: Promoting IPv6 Usage  . . . . . . . . . . . .   5
     2.3.  Usecase-03: Customized Debugging Utilities  . . . . . . .   5
     2.4.  Usecase-04: Spam Filtering  . . . . . . . . . . . . . . .   5
   3.  The IVIPTR Resource Record  . . . . . . . . . . . . . . . . .   5
     3.1.  Ideal Scenario  . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Non-Ideal Scenario  . . . . . . . . . . . . . . . . . . .   6
     3.3.  Reverse zone file for IPv4 network prefix . . . . . . . .   7
     3.4.  Reverse zone file for IPv6 network prefix . . . . . . . .   7
   4.  Query Processing  . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Client Query: Case-01 . . . . . . . . . . . . . . . . . .   9
     4.2.  Client Query: Case-02 . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   The current DNS standard does not support to resolve IPv4 address to
   IPv6 address and IPv6 address to IPv4 address.  For example, if a
   user program initiate a query for AAAA resource record against an
   IPv4 address of a domain, the current DNS will return a negative
   answer normally with RCODE(3)-Non-Existent Domain.  Using the current
   DNS standard, a user program can resolve IPv6 address for a desired
   IPv4 address by the process as in figure-01:

Saraj, et al.           Expires November 12, 2018               [Page 2]
Internet-Draft       IVIPTR: Resource Record for DNS            May 2018

                      Local                           |  Foreign
                                                      |
       +---------+                                    |
       |         | rev. lookup response               |
Show full document text