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

Internet-Drafts@ietf.org Thu, 05 November 1998 16:05 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id LAA05836 for ietf-123-outbound.10@ietf.org; Thu, 5 Nov 1998 11:05:02 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA04845; Thu, 5 Nov 1998 10:19:09 -0500 (EST)
Message-Id: <199811051519.KAA04845@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: iab@isi.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-iab-nat-implications-02.txt
Date: Thu, 05 Nov 1998 10:19:09 -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 Internet Architecture Board.

	Title		: Architectural Implications of NAT
	Author(s)	: T. Hain
	Filename	: draft-iab-nat-implications-02.txt
	Pages		: 12
	Date		: 04-Nov-98
	
   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].

Internet-Drafts are 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-02.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-iab-nat-implications-02.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ftp.ietf.org
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-iab-nat-implications-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.
ftp://ftp.ietf.org/internet-drafts/draft-iab-nat-implications-02.txt"><ftp://ftp.ietf.org/internet-drafts/draft-iab-nat-implications-02.txt>