Re: IPv4 Outage Planned for IETF 71 Plenary

Joel Jaeggli <joelja@bogus.com> Thu, 20 December 2007 04:21 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 1J5CuI-0000sU-KU; Wed, 19 Dec 2007 23:21:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5CuH-0000sO-AT for ietf@ietf.org; Wed, 19 Dec 2007 23:21:13 -0500
Received: from [2001:418:1::81] (helo=nagasaki.bogus.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5CuE-0007Ln-Kd for ietf@ietf.org; Wed, 19 Dec 2007 23:21:12 -0500
Received: from [192.168.11.103] (c-24-23-195-240.hsd1.mn.comcast.net [24.23.195.240]) (authenticated bits=0) by nagasaki.bogus.com (8.14.1/8.13.8) with ESMTP id lBK4L9dN016786; Thu, 20 Dec 2007 04:21:09 GMT (envelope-from joelja@bogus.com)
Message-ID: <4769EDB0.3080503@bogus.com>
Date: Wed, 19 Dec 2007 20:21:04 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.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> <4769E011.4050106@sopac.org> <4966A353-F35E-4029-BE7B-F853E97095C7@cisco.com>
In-Reply-To: <4966A353-F35E-4029-BE7B-F853E97095C7@cisco.com>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.91.1/5186/Thu Dec 20 03:38:25 2007 on nagasaki.bogus.com
X-Virus-Status: Clean
X-Spam-Score: -1.4 (-)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Franck Martin <franck@sopac.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 Baker wrote:
> 
> On Dec 19, 2007, at 7:22 PM, Franck Martin wrote:
> 
>> It the outage happens at the last plenary session then everyone will
>> have the whole week before the plenary to set up their laptop to IPv6
> 
> the laptop is the trivial part. It is the supporting infrastructure at
> the home corporation that is an issue.

Rhetorical question.

Does your vpn client policy file use dotted quads or a hostname?

If you had access to a nat64 translator would your vpn client assuming
it supports ipv6 cope?

No need to answer but it's worth exploring for those of us who
develop/deploy vpn platforms should think about.

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


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