(ngtrans) I-D ACTION:draft-ietf-ngtrans-dns-ops-req-04.txt

Internet-Drafts@ietf.org Thu, 07 March 2002 12:02 UTC

Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18872 for <ngtrans-archive@odin.ietf.org>; Thu, 7 Mar 2002 07:02:19 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA13472; Thu, 7 Mar 2002 04:58:37 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA06150; Thu, 7 Mar 2002 03:58:21 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2) with ESMTP id g27BvwKL007997 for <ngtrans-dist@sunroof.eng.sun.com>; Thu, 7 Mar 2002 03:57:58 -0800 (PST)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2/Submit) id g27BvvOl007996 for ngtrans-dist; Thu, 7 Mar 2002 03:57:57 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2) with ESMTP id g27BvsKL007989 for <ngtrans@sunroof.eng.sun.com>; Thu, 7 Mar 2002 03:57:54 -0800 (PST)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id DAA12089 for <ngtrans@sunroof.eng.sun.com>; Thu, 7 Mar 2002 03:57:54 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA03197 for <ngtrans@sunroof.eng.sun.com>; Thu, 7 Mar 2002 03:57:53 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18344; Thu, 7 Mar 2002 06:57:50 -0500 (EST)
Message-Id: <200203071157.GAA18344@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-dns-ops-req-04.txt
Date: Thu, 07 Mar 2002 06:57:49 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: NGtrans IPv6 DNS operational requirements and roadmap
	Author(s)	: A. Durand, J. Ihren
	Filename	: draft-ietf-ngtrans-dns-ops-req-04.txt
	Pages		: 
	Date		: 06-Mar-02
	
This document describes IPv6 DNS operational requirements and
deployment roadmap. It is the result of discussion from members of
the IPv6, NGtrans, DNSops and DNSext working groups. The DNS is
looked as a critical part of the Internet infrastructure and is used
for much more purposes than name to address resolution.  Thus a
smooth operation of the DNS is critical in the IPv6 transition.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-dns-ops-req-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-dns-ops-req-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-dns-ops-req-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-dns-ops-req-04.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ngtrans-dns-ops-req-04.txt>