Skip to main content

PCP Support for Nested NAT Environments
draft-penno-pcp-nested-nat-01

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Reinaldo Penno , Dan Wing , Paul Selkirk , Mohamed Boucadair
Last updated 2012-04-23 (Latest revision 2011-10-21)
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Nested NATs or multi-layer NATs are already widely deployed. They are characterized by two or more NAT devices in the path of packets from the subscriber to the Internet. Moreover, NAT devices current deployed are PCP unaware and It is assumed that NAT aware PCP devices will take a long time to be rolled out. Therefore in order to lower the adoption barrier of PCP and make it work for current deployed networks, this document proposes a few mechanisms for PCP-enabled applications to work through nested NATs with varying level of PCP protocol support.

Authors

Reinaldo Penno
Dan Wing
Paul Selkirk
Mohamed Boucadair

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