RE: IPv4 Outage Planned for IETF 71 Plenary

"Tony Hain" <alh-ietf@tndh.net> Wed, 19 December 2007 21:19 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J56Jx-0001v0-CE; Wed, 19 Dec 2007 16:19:17 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J56Jv-0001r2-Cs for ietf@ietf.org; Wed, 19 Dec 2007 16:19:15 -0500
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216] helo=tndh.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J56Ju-0005oe-Pr for ietf@ietf.org; Wed, 19 Dec 2007 16:19:15 -0500
Received: from eagle (192.168.123.10:1460) by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server] id <SB584B4> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Wed, 19 Dec 2007 13:19:09 -0800
From: Tony Hain <alh-ietf@tndh.net>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, 'Sam Hartman' <hartmans-ietf@mit.edu>
References: <E1J3IFS-0002yV-CG@ietf.org><200712142154.lBELs1ne090300@drugs.dv.isc.org><200712181644.lBIGisBx090029@romeo.rtfm.com><476800BC.5030504@dcrocker.net><38033976C354EAB237181075@[192.168.101.1]><p06250103c38dc78214d8@[74.134.5.163]><080c01c84276$ec9a79e0$c5cf6da0$@net> <tsl8x3qphdd.fsf@mit.edu> <2788466ED3E31C418E9ACC5C31661557084FAF@mou1wnexmb09.vcorp.ad.vrsn.com>
In-Reply-To: <2788466ED3E31C418E9ACC5C31661557084FAF@mou1wnexmb09.vcorp.ad.vrsn.com>
Date: Wed, 19 Dec 2007 13:19:03 -0800
Message-ID: <083301c84284$c835e270$58a1a750$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AchCfI0p9du+bWfxSdS+y5ZCmxiLBQAAmW4YAAEvztA=
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ietf@ietf.org, iaoc@ietf.org, 'Pete Resnick' <presnick@qualcomm.com>, 'IETF Chair' <chair@ietf.org>, dcrocker@bbiw.net, 'John C Klensin' <john-ietf@jck.com>, iesg@ietf.org
Subject: RE: IPv4 Outage Planned for IETF 71 Plenary
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Hallam-Baker, Phillip wrote:
> The double NAT approach is much closer to what the actual 
> transition is going to look like. The only difference is that 
> I think we might just be able to work out a viable means of 
> punching holes so that video-conferencing works if we actually 
> set our minds to it.

Since you are the one that is routinely taking the operator's position, why
should we allow punching holes in the IETF nat when that will never happen
in a real ISP? No ISP is going to trust their customer base to modify the
configuration of their infrastructure, so whatever the IETF experiment ends
up being has to mimic that reality. 

The only exception I would make is to route the audio streams around the nat
so people that can't attend are not completely cut off. Other than that, if
you are there you are living the future. IPv6 plus multiple layers of
IPv4-nat, with trust boundary issues included.

Tony 





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf