RFC 3364 on Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)
rfc-editor@rfc-editor.org Thu, 22 August 2002 04:52 UTC
Received: from psg.com (smmsp@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05897 for <dnsext-archive@lists.ietf.org>; Thu, 22 Aug 2002 00:52:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 17hjmh-000MCv-00 for namedroppers-data@psg.com; Wed, 21 Aug 2002 21:41:27 -0700
Received: from rip.psg.com ([147.28.0.39]) by psg.com with esmtp (Exim 3.36 #1) id 17hjmc-000MC7-00 for namedroppers@ops.ietf.org; Wed, 21 Aug 2002 21:41:22 -0700
Received: from localhost ([127.0.0.1] helo=rip.psg.com.psg.com) by rip.psg.com with esmtp (Exim 4.10) id 17hjmc-0000XO-00 for namedroppers@ops.ietf.org; Wed, 21 Aug 2002 21:41:22 -0700
Message-Id: <200208212302.g7LN2Kd14867@gamma.isi.edu>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Subject: RFC 3364 on Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)
Cc: rfc-editor@rfc-editor.org, namedroppers@ops.ietf.org
From: rfc-editor@rfc-editor.org
Date: Wed, 21 Aug 2002 16:02:20 -0700
X-Spam-Status: No, hits=2.7 required=5.0 tests=TO_MALFORMED,NO_REAL_NAME,DOUBLE_CAPSWORD version=2.31
X-Spam-Level: **
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.