Subject: (NAT) I-D ACTION:draft-ietf-nat-terminology-02.txt (fwd)

From: [email-masked] (Pyda Srisuresh)
Date: Fri, 23 Apr 1999 08:28:47 -0700 (PDT)

Folks,

The revised version of the "NAT Terminology and Considerations"
draft below is fundamantally unchanged from its previous revs. 
However, it does (a) replace "HOST-NAT" terminology with 
"Realm-Specific IP" terminology and (b) adds substantial clarification 
to the text - thanks principally to Thomas Narten and Vern Paxson. 

The review process has taken lot longer than I (and perhaps some of 
you) had originally anticipated. But, the good news is that the draft 
has become significantly better and is less likely to be misunderstood 
as a result.

I beleieve, the draft is ready for an official IESG review in the 
next meeting (05/06/99?). 

Thanks.

cheers,
suresh

Forwarded message:
> From owner-nat Fri Apr 23 06:33:23 1999
> Message-Id: <[email-masked]>
> Mime-Version: 1.0
> Content-Type: Multipart/Mixed; Boundary="NextPart"
> To: IETF-Announce:;
> Cc: [email-masked]
> From: [email-masked]
> Subject: (NAT) I-D ACTION:draft-ietf-nat-terminology-02.txt
> Date: Fri, 23 Apr 1999 09:27:36 -0400
> Sender: [email-masked]
> Precedence: bulk
> Reply-To: [email-masked]
> 
> --NextPart
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network Address Translators Working Group of the IETF.
> 
> 	Title           : IP Network Address Translator (NAT)
> 			  Terminology and Considerations
> 	Author(s)	: P. Srisuresh, M. Holdrege
> 	Filename	: draft-ietf-nat-terminology-02.txt
> 	Pages		: 29
> 	Date		: 22-Apr-99
> 	
> Network Address Translation is a method by which IP addresses are
>    mapped from one realm to another, providing transparent routing to
>    hosts. Traditionally, NATs are used to connect an isolated routing
>    realm with private unregistered addresses to an external routing
>    realm with globally unique registered addresses. This document
>    attempts to describe the operation of NATs in general and to
>    define the terminology used to identify various flavors of NAT.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nat-terminology-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-nat-terminology-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:
> 	[email-masked].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-nat-terminology-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="[email-masked]"
> 
> Content-Type: text/plain
> Content-ID:	<[email-masked]>
> 
> ENCODING mime
> FILE /internet-drafts/draft-ietf-nat-terminology-02.txt
> 
> --OtherAccess
> Content-Type: Message/External-body;
> 	name="draft-ietf-nat-terminology-02.txt";
> 	site="ftp.ietf.org";
> 	access-type="anon-ftp";
> 	directory="internet-drafts"
> 
> Content-Type: text/plain
> Content-ID:	<[email-masked]>
> 
> --OtherAccess--
> 
> --NextPart--
> 
> 
> -
> To unsubscribe, email [email-masked]' with
> 'unsubscribe nat' in the body of the message.
> 

-
To unsubscribe, email [email-masked]' with
'unsubscribe nat' in the body of the message.