RE: IPv4 Outage Planned for IETF 71 Plenary

David Morris <dwm@xpasc.com> Fri, 21 December 2007 21: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 1J5pS6-0007Io-HO; Fri, 21 Dec 2007 16:30:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5pS5-0007Ij-EE for ietf@ietf.org; Fri, 21 Dec 2007 16:30:41 -0500
Received: from email.xpasc.com ([65.85.17.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5pS3-0002Ax-Nd for ietf@ietf.org; Fri, 21 Dec 2007 16:30:41 -0500
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 6CA8F100586 for <ietf@ietf.org>; Fri, 21 Dec 2007 13:30:39 -0800 (PST)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from email.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 2.1.7.8167-src $Rev: 8148 $) id iz6Ur7clluC0; Fri, 21 Dec 2007 13:30:39 -0800
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 8A0C0100091 for <ietf@ietf.org>; Fri, 21 Dec 2007 13:30:38 -0800 (PST)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.11.2/8.11.2) with ESMTP id lBLLUbB21602 for <ietf@ietf.org>; Fri, 21 Dec 2007 13:30:37 -0800
Date: Fri, 21 Dec 2007 13:30:37 -0800
From: David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <AFE0AC8DCDE68842B94E8EC69D5F21D635E6CD437C@NA-EXMSG-W602.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.LNX.4.33.0712211317510.19334-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Propel-ID: iz6Ur7clluC0
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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

Actually, I think the stronger complaints are about the fact that a
meeting for another purpose will be disrupted by the sub set of folks who
think they are obligated to try and get there lap top working because
there is a network experiment overlayed on the meeting. Plenaries are
already unwieldy at best. With an undercurrent of an 'official' activity
there is the potential of nothing useful happening.

As the IT department, and everything else, associated with my business
there is no economic reason to be an early adopter. As a small business, I
have no weight to make anything happen except discomfort for myself. If
something like the proposal for setting up a working session in another
context which won't disrrupt the plenary is arranged, I will consider
bringing a second lap top which can be fiddled to whatever degree is
necessary to evaluate IPv6 connectivity issues.

IT departments are generally good at careful planning because they don't
get paid to disrrupt the corporate IT infrastructure. They aren't likely
to be motivated by IETF participant complaints about lack of IPv6 support
UNLESS they are already trying to provision IPv6 and see this as a good
test opportunity. My clients IT departments would simply provide EDGE/EVDO
cards for those folks who couldn't be offline for an hour.

The irony is that for IPV4 only folks, just disconnecting the network for
an hour will have the same effect ... except they wouldn't be disrrupting
the meeting trying to fix their laptops.

Dave Morris

On Fri, 21 Dec 2007, Christian Huitema wrote:

> > Disrupting a meeting funded for a different purpose will/would be an
> > offensive colossal waste of resources.
>
> I think some disruption is in order.
>
> The stronger argument I have heard against the proposed "IPv6
> interlude" is that it is not compatible with the services loaded on
> participants' laptops by their enterprise's IT department. Fine. So
> the participant will come back and send a note to their IT department,
> complaining that lack of IPv6 support forced them to stop reading
> corporate e-mail for an hour. Better warn them now. IT department are
> notoriously conservative, and it takes warnings like that to get them
> to move.
>
> -- Christian Huitema
>
>

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