IETF Logo Mail Archive

Re: IPv4 Outage Planned for IETF 71 Plenary

David Kessens <david.kessens@nsn.com> Fri, 21 December 2007 20:27 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 1J5oTI-0002Nr-Uh; Fri, 21 Dec 2007 15:27:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5oTI-0002Kq-3G for ietf@ietf.org; Fri, 21 Dec 2007 15:27:52 -0500
Received: from smtp.nokia.com ([192.100.122.233] helo=mgw-mx06.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5oTH-0004bu-Il for ietf@ietf.org; Fri, 21 Dec 2007 15:27:52 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id lBLKRP6m024480; Fri, 21 Dec 2007 22:27:49 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 22:27:22 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 22:27:22 +0200
Received: from dadhcp-172019068052.americas.nokia.com ([172.19.68.52]) by esebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 22:27:21 +0200
Received: from dadhcp-172019068052.americas.nokia.com (localhost.localdomain [127.0.0.1]) by dadhcp-172019068052.americas.nokia.com (8.13.5/8.13.5) with ESMTP id lBLKRIGV016168; Fri, 21 Dec 2007 12:27:19 -0800
Received: (from david@localhost) by dadhcp-172019068052.americas.nokia.com (8.13.5/8.13.5/Submit) id lBLKRHQF016167; Fri, 21 Dec 2007 12:27:17 -0800
Date: Fri, 21 Dec 2007 12:27:17 -0800
From: David Kessens <david.kessens@nsn.com>
To: David Morris <dwm@xpasc.com>
Message-ID: <20071221202717.GA16134@nsn.com>
References: <20071221073054.GA10713@nsn.com> <Pine.LNX.4.33.0712210737370.6397-100000@egate.xpasc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0712210737370.6397-100000@egate.xpasc.com>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 21 Dec 2007 20:27:21.0639 (UTC) FILETIME=[E3C1DB70:01C8440F]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@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

David,

On Fri, Dec 21, 2007 at 07:41:47AM -0800, David Morris wrote:
> 
> The question here is not if we'll have a room full of competent engineer
> who might be able to solve any problems, the question for competent
> engineers is whether the proposed approach is effective use of very
> expensive resources. Competent engineers plan things ahead of time so the
> likelyhood of failure is minimized.

Indeed!

That is why I did the planning and solved all issues for my particular
situation already many IETFs ago. Basically, this whole discussion
shows that there are a few people behind the curve and they probably
should take action before next IETF.

Note that this is independent of whether a scheduled ipv4 outage
happens or not - unscheduled events do happen and it is simply prudent
behavior to allow for a fall back on a different version of ip if
there is a problem with one of the versions on the network.

David Kessens
---

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

v2.23.0 | Report a Bug | By Email