Re: IPv4 Outage Planned for IETF 71 Plenary

Norbert Bollow <nb@bollow.ch> Tue, 18 December 2007 08:05 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 1J4XST-0006GC-GO; Tue, 18 Dec 2007 03:05:45 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4XSR-00069R-J0 for ietf@ietf.org; Tue, 18 Dec 2007 03:05:43 -0500
Received: from tarsus.bollow.ch ([82.195.230.222]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4XSR-0000sI-1I for ietf@ietf.org; Tue, 18 Dec 2007 03:05:43 -0500
Received: from tarsus.bollow.ch (localhost [127.0.0.1]) by tarsus.bollow.ch (Postfix) with ESMTP id D1F55B281AB for <ietf@ietf.org>; Tue, 18 Dec 2007 09:50:54 +0100 (CET)
Authentication-Results: tarsus.bollow.ch from=nb@bollow.ch; domainkey=neutral (no signature; no policy for bollow.ch)
Received: from quill.bollow.ch (156-16.203-62.cust.bluewin.ch [62.203.16.156]) by tarsus.bollow.ch (Postfix) with ESMTP for <ietf@ietf.org>; Tue, 18 Dec 2007 09:50:54 +0100 (CET)
Received: by quill.bollow.ch (Postfix, from userid 1000) id A0780220285; Tue, 18 Dec 2007 09:13:26 +0100 (CET)
From: Norbert Bollow <nb@bollow.ch>
Organization: Bollow Software Economics Research
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="iso-8859-1"
To: ietf@ietf.org
In-reply-to: <tslmys98grt.fsf@mit.edu> (message from Sam Hartman on Mon, 17 Dec 2007 10:47:34 -0500)
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>
Message-Id: <20071218081326.A0780220285@quill.bollow.ch>
Date: Tue, 18 Dec 2007 09:13:26 +0100
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

Sam Hartman <hartmans-ietf@mit.edu> wrote:
> >>>>> "Norbert" == Norbert Bollow <nb@bollow.ch> writes:
> 
>     Norbert> Iljitsch van Beijnum <iljitsch@muada.com> wrote:
>     >> But what about transition mechanisms, or would that be unfair?
> 
>     Norbert> IMO it would be unfair on IPv6 to do the test without
> 
> We should provide transition mechanisms only if we believe they are
> a good idea.
> 
> 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.

Dual stack is a transition mechanism.  The idea is that ISPs provide
dual-stack service up to the customer edge for some time, during
which a gradual migration to v6 takes place, ideally without end
users being forced to pay attention to any changes.

If this works out, after this phase there would be phase in the
transition during which ISPs no longer provide v4 service up to
the customer edge, but provide for some other sort of transition
mechanism to allow their customers to communicate with the IPv4-only
hosts that still exist.

I believe that it is that second transition phase that this test
should aim to simulate.

Greetings,
Norbert.


-- 
Norbert Bollow <nb@bollow.ch>                      http://Norbert.ch
President of the Swiss Internet User Group SIUG    http://SIUG.ch
Working on establishing a non-corrupt and
truly /open/ international standards organization  http://OpenISO.org

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