Security implications of Network Address Translators (NATs)
draft-gont-behave-nat-security-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2009-10-27 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-gont-behave-nat-security-03.txt
Abstract
This document analyzes the security implications of Network Address Translators (NATs). It neither deprecates nor encourages the use of NATs, but rather aims to raise awareness about their security implications, and possible implementation approaches to improve their security.
Authors
Fernando Gont
(fernando@gont.com.ar)
Pyda Srisuresh
(srisuresh@yahoo.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)