Re: IPv4 Outage Planned for IETF 71 Plenary

Dave Crocker <dhc2@dcrocker.net> Mon, 17 December 2007 16:56 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 1J4JGx-00012d-Qe; Mon, 17 Dec 2007 11:56:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4JGw-00012X-GK for ietf@ietf.org; Mon, 17 Dec 2007 11:56:54 -0500
Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4JGv-0007uR-W0 for ietf@ietf.org; Mon, 17 Dec 2007 11:56:54 -0500
Received: from [192.168.0.2] (adsl-68-122-33-67.dsl.pltn13.pacbell.net [68.122.33.67]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lBHGuMZH027056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Dec 2007 08:56:24 -0800
Message-ID: <47669EAE.1030200@dcrocker.net>
Date: Mon, 17 Dec 2007 08:07:10 -0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <E1J3IFS-0002yV-CG@ietf.org> <20071214220518.GA14379@sources.org> <47631201.1070303@bogus.com> <p06240806c388d88dc9de@[165.227.249.204]> <a06240800c388daca0917@[192.168.1.101]> <4763EBD3.50804@cisco.com> <37AF8EDE-2B6F-49DB-8D02-0674B4F47677@multicasttech.com> <0C29D33E-3BAD-4564-B0F3-6F7A5D1A8B59@muada.com> <20071217093519.CDA83220285@quill.bollow.ch> <tslmys98grt.fsf@mit.edu>
In-Reply-To: <tslmys98grt.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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
Reply-To: dcrocker@bbiw.net
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


Sam Hartman wrote:
> So far I think we want to recommend dual stack.  So, we need to think
> about this outage more as a way to get ourselves experience with IPV6,
> not as a network configuration anyone should be expected to use on a
> regular basis.


As a simple model, let's assume 4 administrations are in the critical path:

1. Participant's laptop
2. IETF network ops
3. Collection of backbone operators
4. Participant's service provider

Each of these must support v6, for true dual stack to work.


Two major questions:

a)  What is the current assessment about IPv6 support for major backbone 
service providers?

b)  What is the lowly participant to do if they are a mere customer of a real, 
commercial service provider or a real organizational IT department who does 
not support v6 on production machines?

With respect to the latter, what information will be usefully obtained by the 
blocking of these participants from their home services that could not have 
been learned from a simple survey to their home service operators?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


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