IETF Logo Mail Archive

Re: IPv4 Outage Planned for IETF 71 Plenary

Sam Hartman <hartmans-ietf@mit.edu> Wed, 19 December 2007 22:09 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 1J576x-0000uN-PU; Wed, 19 Dec 2007 17:09:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J576v-0000tP-HS; Wed, 19 Dec 2007 17:09:53 -0500
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J576v-0001FE-7Y; Wed, 19 Dec 2007 17:09:53 -0500
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id D85744815; Wed, 19 Dec 2007 17:09:51 -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> <tsl8x3qnznl.fsf@mit.edu> <085301c8428b$0d6ffeb0$284ffc10$@net>
Date: Wed, 19 Dec 2007 17:09:51 -0500
In-Reply-To: <085301c8428b$0d6ffeb0$284ffc10$@net> (Tony Hain's message of "Wed, 19 Dec 2007 14:03:56 -0800")
Message-ID: <tslve6umj4g.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: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ietf@ietf.org, iaoc@ietf.org, 'John C Klensin' <john-ietf@jck.com>, 'IETF Chair' <chair@ietf.org>, dcrocker@bbiw.net, 'Pete Resnick' <presnick@qualcomm.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> I am willing to conceded on the behave point because client
    Tony> side actions really don't matter, but I want to see multiple
    Tony> people running mta's and independent web servers on the
    Tony> nat'd IETF network, with active connection attempts to them
    Tony> from the outside. Nobody can physically configure the most
    Tony> public nat, and no signaling of it is allowed because it is
    Tony> operated by a third party that doesn't trust you. If you
    Tony> want a real indication of future problems, run real services
    Tony> from behind the magic solution and document its complete
    Tony> failure.

I think this would be fun and educational.

I do something similar for my own infrastructure.
And yes there are problems.
Some things do work though.

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

v2.23.0 | Report a Bug | By Email