Re: IPv4 Outage Planned for IETF 71 Plenary

Joel Jaeggli <joelja@bogus.com> Fri, 14 December 2007 23:30 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 1J3JzA-00018W-R6; Fri, 14 Dec 2007 18:30:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Jz8-00018P-Ox for ietf@ietf.org; Fri, 14 Dec 2007 18:30:26 -0500
Received: from [2001:418:1::81] (helo=nagasaki.bogus.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3Jz8-00048K-CQ for ietf@ietf.org; Fri, 14 Dec 2007 18:30:26 -0500
Received: from [192.103.16.81] ([192.103.16.81]) (authenticated bits=0) by nagasaki.bogus.com (8.14.1/8.13.8) with ESMTP id lBENUPNs089260; Fri, 14 Dec 2007 23:30:25 GMT (envelope-from joelja@bogus.com)
Message-ID: <47631201.1070303@bogus.com>
Date: Fri, 14 Dec 2007 15:30:09 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <E1J3IFS-0002yV-CG@ietf.org> <20071214220518.GA14379@sources.org>
In-Reply-To: <20071214220518.GA14379@sources.org>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.91.1/5123/Fri Dec 14 21:32:15 2007 on nagasaki.bogus.com
X-Virus-Status: Clean
X-Spam-Score: -1.4 (-)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ietf@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

Stephane Bortzmeyer wrote:
> On Fri, Dec 14, 2007 at 04:39:10PM -0500,
>  IETF Chair <chair@ietf.org> wrote 
>  a message of 29 lines which said:
> 
>> During the IESG/IAOC Plenary at IETF 71, we are going to turn off
>> IPv4 support on the IETF network for 30 to 60 minutes.  We will
>> encourage the audience to use the Internet and determine which
>> services that they have come to take for granted remain available.
> 
> If there is no gateway somewhere with an IPv4 address, we will do very
> little.
> 
> We performed this experience last month at an IPv6 training in
> Nouakchott (Mauritania). The students had only IPv6 connectivity to
> the Internet. As Mark Andrews said, we were not able to even resolve
> the names with AAAA records because the root does not have IPv6. In
> the end, we cheated by adding a DNS gateway (BIND on a machine with an
> IPv4 address) and a Web gateway (Apache with mod_proxy on a machine
> with an IPv4 address).

you could add some AAAA glue to your named.root which in any event I'd
do if I were running a recursive nameserver with only v6 transit.

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


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