RFC 2993 on Architectural Implications of NAT
RFC Editor <rfc-ed@ISI.EDU> Wed, 29 November 2000 00:21 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05380; Tue, 28 Nov 2000 19:21:38 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA29256 for ietf-123-outbound.10@ietf.org; Tue, 28 Nov 2000 19:15:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA28978 for <all-ietf@loki.ietf.org>; Tue, 28 Nov 2000 18:42:32 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18056 for <all-ietf@ietf.org>; Tue, 28 Nov 2000 18:42:32 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA08466; Tue, 28 Nov 2000 15:42:28 -0800 (PST)
Message-Id: <200011282342.PAA08466@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2993 on Architectural Implications of NAT
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 28 Nov 2000 15:42:28 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2993 Title: Architectural Implications of NAT Author(s): T. Hain Status: Informational Date: November 2000 Mailbox: tonyhain@microsoft.com Pages: 29 Characters: 74136 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-nat-implications-09.txt URL: ftp://ftp.isi.edu/in-notes/rfc2993.txt 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. This document is a product of the Internet Architecture Board. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.