Implications of NATs on the TCP/IP architecture
draft-ietf-nat-arch-implications-00

Document Type Expired Internet-Draft (nat WG)
Last updated 1998-08-07
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-nat-arch-implications-00.txt

Abstract

In light of the growing interest in, and deployment of network address translation (NAT - RFC 1631), this document will present some highlights of the architectural implications. A reader is assumed to be well familiar with the principles of NAT operations [RFC1631].

Authors

Yakov Rekhter (yakov@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)