RE: IPv4 Outage Planned for IETF 71 Plenary

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 21 December 2007 23:34 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 1J5rNT-0005Xo-Tr; Fri, 21 Dec 2007 18:34:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5rNR-0005Ny-Qe for ietf@ietf.org; Fri, 21 Dec 2007 18:34:01 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5rNR-0007SX-Av for ietf@ietf.org; Fri, 21 Dec 2007 18:34:01 -0500
Received: from [10.20.30.108] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id lBLNXx7L080409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 21 Dec 2007 16:34:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080ac391fa3bb461@[10.20.30.108]>
In-Reply-To: <Pine.LNX.4.33.0712211317510.19334-100000@egate.xpasc.com>
References: <Pine.LNX.4.33.0712211317510.19334-100000@egate.xpasc.com>
Date: Fri, 21 Dec 2007 15:33:34 -0800
To: ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

At 1:30 PM -0800 12/21/07, David Morris wrote:
>Actually, I think the stronger complaints are about the fact that a
>meeting for another purpose ...

"another purpose"? Those of us who were at the IESG/IAOC plenary 2.5 
weeks ago will remember that the vast majority of the mic time was to 
discuss (and/or pontificate) about IPv6 transition, IPv6 adoption, 
and the operational implications that are slowing the transition and 
adoption down. The discussion about IPv6 was an hour, maybe 90 
minutes.

As someone whose IETF area doesn't intersect with IPv6 much, I found 
the mic time at this plenary a useful way to catch up with the 
current thinking of people who were more involved in the topic than I 
am. However, in the end, it was just talk. The upcoming plenary has 
the possibility of being much more useful. Sure, there is a chance 
that the mic time will be hogged by people who want to whine about 
how much more productive we would have been talking about something 
else at the mic (is that two layers of process indirection or 
three?); I'll risk having to sit through that.

For all the people who think the proposed plenary is a waste of time: 
please don't come to complain. Instead, go out to dinner someplace 
good, and post about that on the meeting mailing list immediately 
after eating (or maybe even during eating). *That* will be of great 
value to all of us who suffered through a few hours of no IPv4 
service and thus have become even more hungry. Hopefully, you will be 
surprised by the number of people who reply from inside the plenary.

And who will bring a roll of stickers that say "Still running IPv6" 
for the survivors to wear the next day?

--Paul Hoffman, Director
--VPN Consortium

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