Re: IPv4 Outage Planned for IETF 71 Plenary

Sam Hartman <hartmans-ietf@mit.edu> Wed, 19 December 2007 21:27 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 1J56Rv-0006PV-4x; Wed, 19 Dec 2007 16:27:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J56Rs-0006OW-Ij; Wed, 19 Dec 2007 16:27:28 -0500
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J56Rs-00061O-71; Wed, 19 Dec 2007 16:27:28 -0500
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EADE54815; Wed, 19 Dec 2007 16:27:26 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: alh-ietf@tndh.net
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> <083301c84284$c835e270$58a1a750$@net>
Date: Wed, 19 Dec 2007 16:27:26 -0500
In-Reply-To: <083301c84284$c835e270$58a1a750$@net> (Tony Hain's message of "Wed, 19 Dec 2007 13:19:03 -0800")
Message-ID: <tsl8x3qnznl.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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
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

>>>>> "Tony" == Tony Hain <alh-ietf@tndh.net> writes:

    Tony> 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.

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

I think that real ISPs will ship NATs that comply with behave.  If you
think that address independent and endpoint independent mapping
behavior with endpoint dependent filtering behavior counts as punching
holes then I disagree with you.

Why will ISPs support this?  Because their customers voip phones and
games will want it.


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