Re: IPv4 Outage Planned for IETF 71 Plenary

Theodore Tso <tytso@mit.edu> Fri, 21 December 2007 13:14 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 1J5hhp-000296-ML; Fri, 21 Dec 2007 08:14:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5hho-00027l-1R; Fri, 21 Dec 2007 08:14:24 -0500
Received: from [2002:4519:c427:1:220:edff:fe18:5794] (helo=thunker.thunk.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5hhn-0007HJ-L6; Fri, 21 Dec 2007 08:14:24 -0500
Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtps (tls_cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 #1 (Debian)) id 1J5hsQ-0002wb-EW; Fri, 21 Dec 2007 08:25:22 -0500
Received: from tytso by closure.thunk.org with local (Exim 4.67) (envelope-from <tytso@thunk.org>) id 1J5hhH-0001bV-RG; Fri, 21 Dec 2007 08:13:51 -0500
Date: Fri, 21 Dec 2007 08:13:51 -0500
From: Theodore Tso <tytso@mit.edu>
To: David Kessens <david.kessens@nsn.com>
Bcc: tytso@mit.edu
Message-ID: <20071221131351.GB2044@thunk.org>
References: <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> <20071221073054.GA10713@nsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20071221073054.GA10713@nsn.com>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: iaoc@ietf.org, ietf@ietf.org, Fred Baker <fred@cisco.com>, iesg@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

On Thu, Dec 20, 2007 at 11:30:54PM -0800, David Kessens wrote:
> 
> 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.

So how about getting people to work together to document workarounds
on a wiki run by the IETF?  The point is if we want IPv6 to be
successful we have bootstrap it by eliminating excuses.  VPN access is
merely the latest excuse, and it won't be the last one, either.  :-)

The point here is to have an engineering approach to fixing problems,
by whatever means necessary.  Even if the initial solutions are
accomplished with bailing wire and duct tape, that's OK.  They can
always be fixed up later.

      	 	    	      	  	    - Ted

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