Re: IPv4 Outage Planned for IETF 71 Plenary

Franck Martin <franck@sopac.org> Wed, 19 December 2007 05:18 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 1J4rJg-0004ls-At; Wed, 19 Dec 2007 00:18:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4rJe-0004hL-EV for ietf@ietf.org; Wed, 19 Dec 2007 00:17:58 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-rm.sopac.org.fj) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4rJc-0001q6-3z for ietf@ietf.org; Wed, 19 Dec 2007 00:17:58 -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 294371A2CA5 for <ietf@ietf.org>; Wed, 19 Dec 2007 17:17:54 +1200 (FJT)
Message-ID: <4768A97D.3050407@sopac.org>
Date: Wed, 19 Dec 2007 17:17:49 +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> <0efa01c841e0$47ee79f0$d7cb6dd0$@us>
In-Reply-To: <0efa01c841e0$47ee79f0$d7cb6dd0$@us>
X-Enigmail-Version: 0.95.0
OpenPGP: id=81D91320
X-Spam-Score: 1.6 (+)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
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>
Content-Type: multipart/mixed; boundary="===============2029787883=="
Errors-To: ietf-bounces@ietf.org

http://www.networkworld.com/news/2007/121707-how-feds-are-dropping-the-ball-side-1.html

Seems to me IETF71 will be very close to the US deadline:

"*U.S. federal agencies must meet a mandate to be capable of supporting
IPv6 on their backbone networks by June 2008. But carriers tell me that
only 10% or 15% of federal agencies are actually buying IPv6 service"

*It is my understanding that IETF network has been IPv4 and IPv6 during
most meetings for a while now and more often with access to an IPv6
backbone (no tunnel)?

I tried to configure my laptop at IETF70 to use IPv6, I could see my
cards with valid IPv6 addresses, but it was not obvious to get it all
working... So decided to report it for later...

I'm very curious on the results of this experiment. What is 30mn to talk
about IPv6 when all are focused on getting it to work on their own
machines. May be people will go back with IPv6 enabled laptops where
they can test if their applications are working on IPv6 too.

Key people can be prepared, the jabber rooms must be IPv6 and IPv4
accessible already, so it means people outside the meeting will be able
to get to them with IPv4, people at the meeting will have to use IPv6 to
get to them. Just ensure that the rapporteurs are familiar with IPv6.

ICANN can be involved, to ensure the DNS works before the experiment, etc...

Etc...

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