Re: Informational RFC to be: draft-ford-behave-top-07.txt

The IESG <> Mon, 14 September 2009 18:21 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id C7C773A6924; Mon, 14 Sep 2009 11:21:36 -0700 (PDT)
X-idtracker: yes
From: The IESG <>
To: RFC Editor <>
Subject: Re: Informational RFC to be: draft-ford-behave-top-07.txt
Message-Id: <>
Date: Mon, 14 Sep 2009 11:21:36 -0700
Cc:, The IESG <>,
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Sep 2009 18:21:36 -0000

The IESG has no problem with the publication of 'Unintended Consequence of two NAT deployments with Overlapping Address Space' <draft-ford-behave-top-07.txt> as an Informational RFC.

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Magnus Westerlund.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Technical Summary

   This document identifies two deployment scenarios that have arisen
   from the unconventional network topologies formed using Network
   Address Translator devices (NATs). 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 enterprise intranet from remote locations has
   increasingly lead to overlapping private IP address space between
   remote and corporate networks. The 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.

Working Group Summary

   This is an RFC-editor independent submission. 

Document Quality

   This is an RFC-editor independent submission.


   Magnus Westerlund was the responsible AD for the RFC 3932 

RFC Editor Note

   The IESG thinks that this work is related to IETF work done in WG
   BEHAVE, but this does not prevent publishing.


      This RFC is not a candidate for any level of Internet Standard.
      The IETF disclaims any knowledge of the fitness of this RFC for
      any purpose and notes that the decision to publish is not based on
      IETF review apart from IESG review for conflict with IETF work.
      The RFC Editor has chosen to publish this document at its
      discretion.  See RFC 3932 for more information.