Re: IPv4 Outage Planned for IETF 71 Plenary

John C Klensin <john-ietf@jck.com> Sat, 22 December 2007 19:53 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 1J6APb-0004As-HX; Sat, 22 Dec 2007 14:53:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J6APZ-0004AK-SO; Sat, 22 Dec 2007 14:53:29 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J6APZ-0006dz-EI; Sat, 22 Dec 2007 14:53:29 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1J6APY-000MjR-VB; Sat, 22 Dec 2007 14:53:29 -0500
Date: Sat, 22 Dec 2007 14:53:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Message-ID: <62895A2C7B558A286179B397@p3.JCK.COM>
In-Reply-To: <E1J68kX-0000kg-Rd@ietf.org>
References: <E1J68kX-0000kg-Rd@ietf.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: b19722fc8d3865b147c75ae2495625f2
Cc: iaoc@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 Saturday, 22 December, 2007 13:07 -0500 IETF Chair
<chair@ietf.org> wrote:

> Dear Colleagues:
> 
> I had no idea that my previous announcement would generate
> such a long stream of responses.  The lively discussion has
> been surprising, interesting, and also informative.  I need to
> share some history, some plans, and some reactions to this
> lengthy discussion.
> 
> The IETF meeting network supported IPv6 for at least the last
> five years. Both IPv4 and IPv6 routing have been available on
>...
> Following the mail list discussion, we have considered several
> different configurations for achieving the desired network
> experiment environment. It is important that everyone have
> adequate opportunity for advance configuration, and it is
> important that severe impact on other network resources at the
> meeting venue be avoided.  With these goals in mind, we intend
> to add an additional IPv6-only subnet, with a different SSID on
>...

Russ,

>From my perspective at least, an excellent approach that
balances the issues well.

thanks,
   john


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