One document matched: draft-iab-nat-implications-09.txt

Differences from draft-iab-nat-implications-08.txt

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.