RFC 5684 on Unintended Consequences of NAT Deployments with Overlapping Address Space

rfc-editor@rfc-editor.org Thu, 04 February 2010 01:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id C243428C0E8 for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZV2+57fesEzC for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:45 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id D8DA328C0E6 for <ietf-announce@ietf.org>; Wed, 3 Feb 2010 17:46:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7197A13000E; Wed, 3 Feb 2010 17:47:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5684 on Unintended Consequences of NAT Deployments with Overlapping Address Space
From: rfc-editor@rfc-editor.org
Message-Id: <20100204014729.7197A13000E@rfc-editor.org>
Date: Wed, 3 Feb 2010 17:47:29 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 01:46:46 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5684

        Title:      Unintended Consequences of NAT Deployments 
                    with Overlapping Address Space 
        Author:     P. Srisuresh, B. Ford
        Status:     Informational
        Date:       February 2010
        Mailbox:    srisuresh@yahoo.com, 
        Pages:      63018
        Characters: 26
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ford-behave-top-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5684.txt

This document identifies two deployment scenarios that have arisen
from the unconventional network topologies formed using Network
Address Translator (NAT) devices.  First, the simplicity of
administering networks through the combination of NAT and DHCP has
increasingly lead to the deployment of multi-level inter-connected
private networks involving overlapping private IP address spaces.
Second, the proliferation of private networks in enterprises, hotels
and conferences, and the wide-spread use of Virtual Private Networks
(VPNs) to access an enterprise intranet from remote locations has
increasingly lead to overlapping private IP address space between
remote and corporate networks.  This document does not dismiss these
unconventional scenarios as invalid, but recognizes them as real and
offers recommendations to help ensure these deployments can
function without a meltdown.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

INFORMATIONAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC