Re: IPv4 Outage Planned for IETF 71 Plenary

Mohsen Souissi <mohsen.souissi@nic.fr> Sat, 15 December 2007 14:26 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 1J3Xy8-0001Ai-Ge; Sat, 15 Dec 2007 09:26:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Xy5-00018l-Uh; Sat, 15 Dec 2007 09:26:17 -0500
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3Xy4-0005dW-Et; Sat, 15 Dec 2007 09:26:17 -0500
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 698381C01D4; Sat, 15 Dec 2007 15:26:15 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 641471C01D3; Sat, 15 Dec 2007 15:26:15 +0100 (CET)
Received: from kerkenna.nic.fr (kerkenna.nic.fr [192.134.4.98]) by relay2.nic.fr (Postfix) with ESMTP id 610D458EBBE; Sat, 15 Dec 2007 15:26:15 +0100 (CET)
Received: from kerkenna.nic.fr (localhost [127.0.0.1]) by kerkenna.nic.fr (8.13.8/8.13.8) with ESMTP id lBFEQFoN050838; Sat, 15 Dec 2007 15:26:15 +0100 (CET) (envelope-from souissi@kerkenna.nic.fr)
Received: (from souissi@localhost) by kerkenna.nic.fr (8.13.8/8.13.8/Submit) id lBFEQEE9050837; Sat, 15 Dec 2007 15:26:14 +0100 (CET) (envelope-from souissi)
Date: Sat, 15 Dec 2007 15:26:14 +0100
From: Mohsen Souissi <mohsen.souissi@nic.fr>
To: Mark Andrews <Mark_Andrews@isc.org>
Message-ID: <20071215142614.GC50491@kerkenna.nic.fr>
References: <E1J3IFS-0002yV-CG@ietf.org> <200712142154.lBELs1ne090300@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200712142154.lBELs1ne090300@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.2i
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: iaoc@ietf.org, ietf@ietf.org, IETF Announcement list <ietf-announce@ietf.org>, 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

 On 15 Dec, Mark Andrews wrote:
 | 
[...]
 | 
 | 	Step one fix the root.

==> To continue with the template above in the same spirit:

Step two: determine how laptops in the pleanary meeting room will
be fed with the IPv6-only address of the appropriate recursive name server
(eg. /etc/resolv.conf for Unixes) in the absence of that information
in a DHCPv4 environment. One would have to choose between:

- DHCPv6 option (RFC 3646 by way of RFC 3315-stateful or RFC
3736-stateless). That would mean that a DHCPv6 server would be
UP&RUNNING during the meeting and laptops equipped with a DHCPv6
client

- Modified RA (RFC 5006 - Experimental!)

- Manual setting: everybody would have to emacs/vi their
  /etc/resolv.conf or use any GUI available on their OS, while reading
  the recursive server's IPv6 address on the projection board

I think this issue which is not an obvious one (it is still a daily
hurdle for many people among "IPv6 volunteers") deserves being looked
during the experiment preparation if it hasn't been taken into account
yet.

Mohsen.


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