From owner-namedroppers@ops.ietf.org  Mon Jan  1 12:19:25 2001
Received: from psg.com ([147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27936
	for <dnsext-archive@lists.ietf.org>; Mon, 1 Jan 2001 12:19:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14D80E-00073U-00
	for namedroppers-data@psg.com; Mon, 01 Jan 2001 08:40:06 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14D80E-00073O-00
	for namedroppers@ops.ietf.org; Mon, 01 Jan 2001 08:40:06 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14D80E-0004cl-00
	for namedroppers@ops.ietf.org; Mon, 01 Jan 2001 08:40:06 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: namedroppers@ops.ietf.org
Subject: list policy
Message-Id: <E14D2h7-0009u1-00@psg.com>
From: Randy Bush <randy@psg.com>
Date: Mon, 01 Jan 2001 03:00:01 -0800
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

namedroppers@ops.ietf.org is the mailing list for the ietf dnsext wg.  see
<http://www.ietf.org/html.charters/dnsext-charter.html> for the wg charter.
messages should be on topics appropriate to the dnsext wg, which are various
discussion of the dns protocols or administrivia of the wg itself.  the list
is moderated.

calls for papers, announcements of events not directly relevant to the dns
protocols, etc. are not appropriate.  discussion of problems with particular
implementations, announcements of releases, sites' misconfigurations, etc.
should be done on mailing lists for the particular implementations.

there is a wg for dns operational practice, dnsop, whose charter can be
found at <http://www.ietf.org/html.charters/dnsop-charter.html>.

there is a mailing list for discussion of whose implementation is better,
and why someone else's is broken.  it is weenie-war@ops.ietf.org.  all
discussions of such nature should occur there or on /dev/null.  unlike the
namedroppers list, weenie-war@ops.ietf.org is not archived.

discussion of this policy is a topic for the poisson wg.  poisson's charter
can be found at <http://www.ietf.org/html.charters/poisson-charter.html>.


to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Thu Jan  4 10:43:38 2001
Received: from psg.com (psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07677
	for <dnsext-archive@lists.ietf.org>; Thu, 4 Jan 2001 10:43:33 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14EBpy-000Mgy-00
	for namedroppers-data@psg.com; Thu, 04 Jan 2001 06:57:54 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14EBpx-000Mgs-00
	for namedroppers@ops.ietf.org; Thu, 04 Jan 2001 06:57:53 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14EBpx-000J2S-00
	for namedroppers@ops.ietf.org; Thu, 04 Jan 2001 06:57:53 -0800
Message-Id: <200101041225.HAA02107@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-dnssec-roadmap-01.txt
Date: Thu, 04 Jan 2001 07:25:42 -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: DNS Security Document Roadmap
	Author(s)	: S. Rose
	Filename	: draft-ietf-dnsext-dnssec-roadmap-01.txt
	Pages		: 11
	Date		: 03-Jan-01
	
DNS Security (DNSSEC)technology is composed of extensions
to the Domain Name System (DNS) protocol that provide
data integrity and authentication to security aware
resolvers and applications through the use of
cryptographic digital signatures.  Several documents
exist to describe these extensions and the implementation
specific details regarding specific digital signing
schemes.  The interrelationship between these different
documents is discussed here.  A brief overview of what to
find in which document and author guidelines for what to
include in new DNS Security documents, or revisions to
existing documents, is described.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnssec-roadmap-01.txt

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-dnsext-dnssec-roadmap-01.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-dnsext-dnssec-roadmap-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010103133439.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-dnssec-roadmap-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-dnssec-roadmap-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010103133439.I-D@ietf.org>

--OtherAccess--

--NextPart--




to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Fri Jan  5 11:37:15 2001
Received: from psg.com (psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16226
	for <dnsext-archive@lists.ietf.org>; Fri, 5 Jan 2001 11:37:13 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14EZOS-000AQJ-00
	for namedroppers-data@psg.com; Fri, 05 Jan 2001 08:07:04 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14EZOS-000AQD-00
	for namedroppers@ops.ietf.org; Fri, 05 Jan 2001 08:07:04 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14EZOS-000Bdd-00
	for namedroppers@ops.ietf.org; Fri, 05 Jan 2001 08:07:04 -0800
Message-Id: <200101051214.HAA08866@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-zone-status-04.txt
Date: Fri, 05 Jan 2001 07:14:11 -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: DNS Security Extension Clarification on Zone Status
	Author(s)	: E. Lewis
	Filename	: draft-ietf-dnsext-zone-status-04.txt
	Pages		: 9
	Date		: 04-Jan-01
	
The definition of a secured zone is presented, clarifying and updating
sections of RFC 2535. RFC 2535 defines a zone to be secured based on a
per algorithm basis, e.g., a zone can be secured with RSA keys, and
not secured with DSA keys.  This document changes this to define a
zone to be secured or not secured regardless of the key algorithm used
(or not used).  To further simplify the determination of a zone's
status, 'experimentally secure' status is deprecated.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-zone-status-04.txt

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-dnsext-zone-status-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-dnsext-zone-status-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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010104121615.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-zone-status-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-zone-status-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010104121615.I-D@ietf.org>

--OtherAccess--

--NextPart--




to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Fri Jan 12 10:35:11 2001
Received: from psg.com (psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10682
	for <dnsext-archive@lists.ietf.org>; Fri, 12 Jan 2001 10:35:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14H5ge-000OR7-00
	for namedroppers-data@psg.com; Fri, 12 Jan 2001 07:00:16 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14H5ge-000OR1-00
	for namedroppers@ops.ietf.org; Fri, 12 Jan 2001 07:00:16 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14H5ge-0009bG-00
	for namedroppers@ops.ietf.org; Fri, 12 Jan 2001 07:00:16 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Randy Bush <randy@psg.com>
Subject: Reminder - use correct "From:".
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Message-Id: <E14H5ge-000OR7-00@psg.com>
To: namedroppers-data@psg.com
Date: Fri, 12 Jan 2001 07:00:16 -0800
Content-Transfer-Encoding: 7bit

please remember to use the correct "From:" addres when you send messages
to this list.  'correct' means that the address in your "From:" mail
header field should be the same as the address with which you sub scribed
to the list.

failing to use the correct address will bounce your message to the
list admin (me) for manual approval.  this can lead to significant
delay, and you turn your trust to _my_ memory to remember to forward
the message to the list - which is something I would be very
careful with myself ... ;-)

randy


to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Wed Jan 17 03:00:46 2001
Received: from psg.com ([147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA14470
	for <dnsext-archive@lists.ietf.org>; Wed, 17 Jan 2001 03:00:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ImwX-000IU9-00
	for namedroppers-data@psg.com; Tue, 16 Jan 2001 23:23:41 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ImwW-000ITk-00
	for namedroppers@ops.ietf.org; Tue, 16 Jan 2001 23:23:40 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14ImwW-0001Vb-00
	for namedroppers@ops.ietf.org; Tue, 16 Jan 2001 23:23:40 -0800
Message-Id: <4.3.2.7.2.20010116105515.00c4e600@localhost>
X-Sender: ogud@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 16 Jan 2001 10:57:46 -0500
To: DNSEXT WG Mailing list <namedroppers@ops.ietf.org>
From: Olafur Gudmundsson <ogud@tislabs.com>
Subject: DNSEXT WGLC Summary: RFC161[12] to historic
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk


This working group last call has completed.
The consensus of the working group is to advance this document and retire
the two RFC's.

In addition the working group has decided to not take on specifying replacement
documents, but will process any complete MIB documents vendors want
to publish as INFORMATIONAL/EXPERIMENTAL.

	Olafur



to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Wed Jan 17 19:55:28 2001
Received: from psg.com ([147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00093
	for <dnsext-archive@lists.ietf.org>; Wed, 17 Jan 2001 19:55:27 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14J2qm-0002uU-00
	for namedroppers-data@psg.com; Wed, 17 Jan 2001 16:22:48 -0800
Received: from rip.psg.com ([147.28.0.39] ident=exim)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14J2qm-0002uN-00
	for namedroppers@ops.ietf.org; Wed, 17 Jan 2001 16:22:48 -0800
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14J2qm-00086k-00
	for namedroppers@ops.ietf.org; Wed, 17 Jan 2001 16:22:48 -0800
Message-Id: <4.3.2.7.2.20010117231030.02748310@nordic.cisco.com>
X-Sender: hta@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 17 Jan 2001 23:12:47 +0100
To: namedroppers@ops.ietf.org
From: Harald Alvestrand <Harald@Alvestrand.no>
Subject: EDNS0.5
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

beating on a dead horse:

the debate about EDNS0.5 seems to have ended with three negative comments, 
two replies from me, and no further discussion on the issues.

Arguments for:

- Allows experiments where people can see what's happening
- Quite simple mechanism

Arguments against:

- Implementation complexity
- People will do experiments

I would like to have this debate finish.
--
Harald Tveit Alvestrand, alvestrand@cisco.com
+47 41 44 29 94
Personal email: Harald@Alvestrand.no



to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Tue Jan 23 10:57:26 2001
Received: from psg.com ([147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA15835
	for <dnsext-archive@lists.ietf.org>; Tue, 23 Jan 2001 10:57:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14L5C0-0009cX-00
	for namedroppers-data@psg.com; Tue, 23 Jan 2001 07:17:08 -0800
Received: from dhcp70.ripemtg.ripe.net ([193.0.4.70] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14L5Bz-0009cQ-00
	for namedroppers@ops.ietf.org; Tue, 23 Jan 2001 07:17:08 -0800
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 14L5By-0001av-00
	for namedroppers@ops.ietf.org; Tue, 23 Jan 2001 16:17:06 +0100
Message-Id: <200101231233.HAA09242@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-ad-is-secure-01.txt
Date: Tue, 23 Jan 2001 07:33:32 -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Redefinition of DNS AD bit
	Author(s)	: B. Wellington, O. Gudmundsson
	Filename	: draft-ietf-dnsext-ad-is-secure-01.txt
	Pages		: 4
	Date		: 22-Jan-01
	
Based on implementation experience, the current definition of the AD
bit in the DNS header is not useful. This draft changes the
specification so that the AD bit is only set on answers where
signatures have been cryptographically verified.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-ad-is-secure-01.txt

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-dnsext-ad-is-secure-01.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-dnsext-ad-is-secure-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010122143329.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-ad-is-secure-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-ad-is-secure-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010122143329.I-D@ietf.org>

--OtherAccess--

--NextPart--




to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


From owner-namedroppers@ops.ietf.org  Tue Jan 23 10:58:15 2001
Received: from psg.com ([147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA15856
	for <dnsext-archive@lists.ietf.org>; Tue, 23 Jan 2001 10:58:13 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14L5Bw-0009cM-00
	for namedroppers-data@psg.com; Tue, 23 Jan 2001 07:17:04 -0800
Received: from dhcp70.ripemtg.ripe.net ([193.0.4.70] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14L5Bv-0009cG-00
	for namedroppers@ops.ietf.org; Tue, 23 Jan 2001 07:17:03 -0800
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 14L5Br-0001at-00
	for namedroppers@ops.ietf.org; Tue, 23 Jan 2001 16:16:59 +0100
Message-Id: <200101231233.HAA09226@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-message-size-02.txt
Date: Tue, 23 Jan 2001 07:33:28 -0500
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: DNSSEC and IPv6 A6 aware server/resolver message size 
                          requirements
	Author(s)	: O. Gudmundsson
	Filename	: draft-ietf-dnsext-message-size-02.txt
	Pages		: 6
	Date		: 22-Jan-01
	
This document mandates support for EDNS0 in DNS entities claiming to
support DNS Security Extensions and A6 records. This requirement is
necessary because these new features increase the size of DNS
messages. If EDNS0 is not supported fallback to TCP will happen,
having a detrimental impact on query latency and DNS server load.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-message-size-02.txt

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-dnsext-message-size-02.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-dnsext-message-size-02.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010122143321.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-message-size-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-message-size-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010122143321.I-D@ietf.org>

--OtherAccess--

--NextPart--




to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.


