I-D ACTION:draft-iab-nat-implications-03.txt

Internet-Drafts@ietf.org Sat, 06 March 1999 01:45 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id UAA08589 for ietf-123-outbound.10@ietf.org; Fri, 5 Mar 1999 20:45:03 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24473; Fri, 5 Mar 1999 17:09:21 -0500 (EST)
Message-Id: <199903052209.RAA24473@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: iab@isi.edu, iesg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-iab-nat-implications-03.txt
Date: Fri, 05 Mar 1999 17:09:20 -0500
Sender: cclark@ns.cnri.reston.va.us

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IAB.

	Title		: Architectural Implications of NAT
	Author(s)	: T. Hain
	Filename	: draft-iab-nat-implications-03.txt
	Pages		: 22
	Date		: 04-Mar-99
	
   In light of the growing interest in, and deployment of network
   address translation (NAT) RFC-1631, this paper will discuss some of
   the architectural implications and guidelines for implementations.
   It is assumed the reader is familiar with the address translation
   concepts presented in RFC-1631.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iab-nat-implications-03.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-iab-nat-implications-03.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-iab-nat-implications-03.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-iab-nat-implications-03.txt"><ftp://ftp.ietf.org/internet-drafts/draft-iab-nat-implications-03.txt>