Re: IPv4 Outage Planned for IETF 71 Plenary

Ralph Droms <rdroms@cisco.com> Mon, 17 December 2007 15:58 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 1J4IM5-0007TI-SX; Mon, 17 Dec 2007 10:58:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4IM3-0007TA-Oh for ietf@ietf.org; Mon, 17 Dec 2007 10:58:07 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4IM3-0006Xs-G5 for ietf@ietf.org; Mon, 17 Dec 2007 10:58:07 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 17 Dec 2007 10:58:07 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBHFw7q1008596 for <ietf@ietf.org>; Mon, 17 Dec 2007 10:58:07 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lBHFveaO028809 for <ietf@ietf.org>; Mon, 17 Dec 2007 15:58:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Dec 2007 10:57:50 -0500
Received: from [192.168.1.105] ([10.86.241.79]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Dec 2007 10:57:50 -0500
Message-Id: <A8F094FD-41F5-4049-BC90-5CB70A1B0045@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: IETF-Discussion list discussion <ietf@ietf.org>
In-Reply-To: <4766979B.9090701@dcrocker.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Mon, 17 Dec 2007 10:57:51 -0500
References: <C38BEBBC.1B1B37%jordi.palet@consulintel.es> <4766979B.9090701@dcrocker.net>
X-Mailer: Apple Mail (2.915)
X-OriginalArrivalTime: 17 Dec 2007 15:57:50.0172 (UTC) FILETIME=[9328D1C0:01C840C5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=822; t=1197907087; x=1198771087; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20IPv4=20Outage=20Planned=20for=20IETF=20 71=20Plenary |Sender:=20 |To:=20IETF-Discussion=20list=20discussion=20<ietf@ietf.org >; bh=2fL2uOdclffueipK8Y7gqm67980s+YEHy/eOscOsUV4=; b=XjYDB6LSTcB43q7wwsz/Fyso/gk+IAxquO622hLAfFtq3ZAOvkuiRBCbS1 BUVfCcc56teU2i4O4NCIcTWquWY3xNehGW75i7NofGCuIIv7SbF6KrZfhyo2 Aol7tK/qHG;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

Seems to me we need ensure some formality in the experiment if we  
expect to get anything out of it.  Asking everyone to send in notes  
from their experience won't be enough - especially, as some have  
predicted, if many participants get exactly 0% Internet connectivity  
while IPv4 is off.

Some suggestions:

* Explicit documentation of any special preparations
   implemented by the IETF NOC

* Several jabber rooms during the experiment (and archive
   the logs); some suggestions:
   - explicit operational issues: successes, questions, help
   - read-only headlines from IETF NOC
   - general discussion
   - pointers to "places that work"

   Note that there is a chicken-and-egg issue accessing the jabber
   rooms over IPv6...

* IETF NOC post mortem

* IESG/IAB-sponsored post mortem


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