Re: IPv4 Outage Planned for IETF 71 Plenary

David Kessens <david.kessens@nsn.com> Fri, 21 December 2007 07:31 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 1J5cLb-0004dp-Bl; Fri, 21 Dec 2007 02:31:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5cLY-0004b2-IT; Fri, 21 Dec 2007 02:31:04 -0500
Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5cLX-0001Aw-SZ; Fri, 21 Dec 2007 02:31:04 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id lBL7UL03019200; Fri, 21 Dec 2007 09:31:00 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 09:30:57 +0200
Received: from dadhcp-172019068052.americas.nokia.com ([172.19.68.52]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 09:30:56 +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 lBL7UsbU011096; Thu, 20 Dec 2007 23:30:54 -0800
Received: (from david@localhost) by dadhcp-172019068052.americas.nokia.com (8.13.5/8.13.5/Submit) id lBL7UsfB011095; Thu, 20 Dec 2007 23:30:54 -0800
Date: Thu, 20 Dec 2007 23:30:54 -0800
From: David Kessens <david.kessens@nsn.com>
To: Fred Baker <fred@cisco.com>
Message-ID: <20071221073054.GA10713@nsn.com>
References: <E1J3IFS-0002yV-CG@ietf.org> <200712142154.lBELs1ne090300@drugs.dv.isc.org> <200712181644.lBIGisBx090029@romeo.rtfm.com> <476800BC.5030504@dcrocker.net> <38033976C354EAB237181075@[192.168.101.1]> <p06250103c38dc78214d8@[74.134.5.163]> <20071218203932.GB21605@nsn.com> <20071219153031.B76645081A@romeo.rtfm.com> <20071219160710.GA29000@nsn.com> <D2CCD62D-A99A-4E91-908A-23D49B73A515@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D2CCD62D-A99A-4E91-908A-23D49B73A515@cisco.com>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 21 Dec 2007 07:30:56.0927 (UTC) FILETIME=[6D1AEAF0:01C843A3]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: iaoc@ietf.org, iesg@ietf.org, 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

Fred,

On Wed, Dec 19, 2007 at 04:16:22PM -0800, Fred Baker wrote:
> 
> On Dec 18, 2007, at 12:39 PM, Hallam-Baker, Phillip wrote:
> >In the same way that there is a difference between a bricklayer and  
> >an architect there is a difference between an engineer and a  
> >network admin.
> 
> On Dec 19, 2007, at 8:07 AM, David Kessens wrote:
> >This issue will only develop into an outage if you bring the wrong  
> >survival tools: I suggest you leave your hammer home and make sure  
> >that you can use ipv6 only. There is no rocket science here. People  
> >have done this before.
> 
> David, I think you missed Phillip's point. The average engineer at  
> the IETF meeting isn't in control of significant aspects of his IT  
> infrastructure, such as whether his IT department has enabled IPv6  
> access to his mail server. Sure, I have IPv6 running on my Mac (it  
> defaults "on" and I dont turn it off) and someone with IPv6 in their  
> network can presumably get web pages from www.ipv6.cisco.com. That's  
> not the same as "being productive".

No, I don't think I missed Phillip's point at all. Some engineers are
apparently more creative than others in their ability to reach the
mothership over an ipv6 only network despite the fact that the
mothership doesn't have ipv6 vpn support (yet). This certainly hasn't
stopped me from connecting back to the company that I work for and it
should not stop any competent engineer.

David Kessens
---

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