IETF Logo Mail Archive

Re: IPv4 Outage Planned for IETF 71 Plenary

John C Klensin <john-ietf@jck.com> Tue, 18 December 2007 20:15 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 1J4ir6-0003PA-Gn; Tue, 18 Dec 2007 15:15:56 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4iqY-00023Z-Sn; Tue, 18 Dec 2007 15:15:22 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4iqY-0001wM-Ey; Tue, 18 Dec 2007 15:15:22 -0500
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1J4iqV-000CXF-7t; Tue, 18 Dec 2007 15:15:19 -0500
Date: Tue, 18 Dec 2007 15:15:15 -0500
From: John C Klensin <john-ietf@jck.com>
To: Theodore Tso <tytso@mit.edu>
Message-ID: <A92D64B3BDA027280A28A1B6@[192.168.101.1]>
In-Reply-To: <20071218194310.GW7070@thunk.org>
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]> <20071218194310.GW7070@thunk.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: iesg@ietf.org, iaoc@ietf.org, ietf@ietf.org, dcrocker@bbiw.net
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

Yes!
    john


--On Tuesday, 18 December, 2007 14:43 -0500 Theodore Tso
<tytso@mit.edu> wrote:

> Let me suggest another approach.  Don't do this at the next
> IETF meeting, but make an announcement that at some near-term
> IETF meeting, the only internet services provided at the IETF
> meeting will be IPv6. Note just for an hour.  Not just for the
> plenery.  Not just for the social; but FOR THE WHOLE WEEK.  In
> other words, let people who are using the IETF wireless
> network experience what it might be like in some future world
> where the ISP's are only providing IPv6 connectivity and IPv6
> addresses to new customers.
> 
> Yes, right now IPv6 deployment isn't good enough that we can't
> do this without using all sorts of workarounds.  OK, let's
> document those workarounds and make them available to the
> attendees.  If it means that the IETF network provider has to
> hijack the root, then let them hijack the root on the IETF
> network, and document that fact.  If there needs to be NAT-PT
> bridges to allow IETF'res to get back to their home networks
>...


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

v2.23.0 | Report a Bug | By Email