Re: IPv4 Outage Planned for IETF 71 Plenary

Franck Martin <franck@sopac.org> Thu, 20 December 2007 03:23 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 1J5Bzy-0006rw-Kr; Wed, 19 Dec 2007 22:23:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5Bzx-0006r7-0n for ietf@ietf.org; Wed, 19 Dec 2007 22:23:01 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-rm.sopac.org.fj) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5Bzw-0006dJ-92 for ietf@ietf.org; Wed, 19 Dec 2007 22:23:00 -0500
Received: from franck-rm.sopac.org.fj (franck-rm.sopac.org.fj [127.0.0.1]) by franck-rm.sopac.org.fj (Postfix) with ESMTP id C2B0A1A2CAB for <ietf@ietf.org>; Thu, 20 Dec 2007 15:22:57 +1200 (FJT)
Message-ID: <4769E011.4050106@sopac.org>
Date: Thu, 20 Dec 2007 15:22:57 +1200
From: Franck Martin <franck@sopac.org>
Organization: SOPAC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060915 Mandriva/1.5.0.7-1mdv2007.0 (2007.0) Thunderbird/1.5.0.7 Mnenhy/0.7.5.666
MIME-Version: 1.0
CC: ietf@ietf.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]> <p06250103c38dc78214d8@[74.134.5.163]> <20071218203932.GB21605@nsn.com> <20071219153031.B76645081A@romeo.rtfm.com> <20071219160710.GA29000@nsn.com> <D2CCD62D-A99A-4E91-908A-23D49B73A515@cisco.com>
In-Reply-To: <D2CCD62D-A99A-4E91-908A-23D49B73A515@cisco.com>
X-Enigmail-Version: 0.95.0
OpenPGP: id=81D91320
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

It the outage happens at the last plenary session then everyone will
have the whole week before the plenary to set up their laptop to IPv6 as
IETF now has the 2 stacks on its network.

Reading the threads:
-David said there will be AAAA records in the root well before the event
-seems that jabber.ietf.org is not IPv6 but that can be fixed before the
event
-some IETF sites/mailing lists are not IPv6, what is the list, and how
to fix that before the event?
-an IPv6 room seems to be needed, where there will be volunteers ready
to help configure delegates machines to IPv6
-...

I think a TODO list is needed, and each item actioned as to reduce the
unpleasantness of the experience. Get also your
corporations/organizations to assess if they will be visible or not on
IPv6 before the event. Get them to join the experiment and get ready, I
think it will do some good PR for the ones that are ready.

Not a small feast, but most of it doable.

-- 
Franck Martin
ICT Specialist
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard


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