Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)
draft-ietf-dnsext-ipv6-dns-tradeoffs-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3364.
Author Rob Austein
Last updated 2020-01-21 (Latest revision 2002-06-12)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3364 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Dr. Thomas Narten
IESG note
Send notices to <okolkman@ripe.net>
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-dnsext-ipv6-dns-tradeoffs-02 
A new Request for Comments is now available in online RFC libraries.

        RFC 3364

        Title:      Tradeoffs in Domain Name System (DNS) Support
                    for Internet Protocol version 6 (IPv6)
        Author(s):  R. Austein
        Status:     Informational
        Date:       August 2002
        Mailbox:    sra@hactrn.net
        Pages:      11
        Characters: 26544
        Obsoletes:  2673, 2874

        I-D Tag:    draft-ietf-dnsext-ipv6-dns-tradeoffs-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3364.txt

The IETF has two different proposals on the table for how to do DNS
support for IPv6, and has thus far failed to reach a clear consensus
on which approach is better.  This note attempts to examine the pros
and cons of each approach, in the hope of clarifying the debate so
that we can reach closure and move on.

This document is a product of the DNS Extensions Working Group of the
IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.