Re: Another look at 6to4 (and other IPv6 transition issues)
Mark Andrews <marka@isc.org> Thu, 21 July 2011 23:10 UTC
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A4D21F850B for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 16:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level:
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5R84Lc7RcbS for <ietf@ietfa.amsl.com>; Thu, 21 Jul 2011 16:10:19 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3BA21F8507 for <ietf@ietf.org>; Thu, 21 Jul 2011 16:10:19 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 030455F98B6; Thu, 21 Jul 2011 23:09:56 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id E77DD216C7B; Thu, 21 Jul 2011 23:09:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id B41C2120FCCF; Fri, 22 Jul 2011 09:09:52 +1000 (EST)
To: John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <DB5571A0CF3C3F570576A23F@PST.JCK.COM> <BBB3AB81-1A20-4022-8687-CD88B000B281@bogus.com> <A6908373951C6911489DF57A@PST.JCK.COM> <71D5A97D-7119-4082-BC87-6505370CE800@bogus.com> <13205C286662DE4387D9AF3AC30EF456D3F3DEEA84@EMBX01-WF.jnpr.net> <C2C73F7968F19FEEF11B2C67@[192.168.1.128]> <E85A5A32-3665-4932-96A7-BADB11DDB2E8@sabahattin-gucukoglu.com> <4E25F868.1000109@dougbarton.us> <90D829BF-BB51-4B0E-B9A6-4C9CCA1D2840@sabahattin-gucukoglu.com> <4E27F407.8090006@alvestrand.no> <C125CD63E1264E518A4C7423@PST.JCK.COM>
Subject: Re: Another look at 6to4 (and other IPv6 transition issues)
In-reply-to: Your message of "Thu, 21 Jul 2011 13:00:02 -0400." <C125CD63E1264E518A4C7423@PST.JCK.COM>
Date: Fri, 22 Jul 2011 09:09:52 +1000
Message-Id: <20110721230952.B41C2120FCCF@drugs.dv.isc.org>
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 23:10:20 -0000
In message <C125CD63E1264E518A4C7423@PST.JCK.COM>, John C Klensin writes: > > > --On Thursday, July 21, 2011 11:40 +0200 Harald Alvestrand > <harald@alvestrand.no> wrote: > > >... > >> Actively being used. In production. So that taking it away > >> would hurt the entity using it, threaten the entity's comfort > >> and convenience, or just generally go against the stated > >> goals of making the Internet a better place for everybody > >> through the instrumentation and maintenance of standards. > > > > The idea that moving a standard to Historic would take away > > the ability of people to use it reminds me of the story from > > the Norwegian army, approx 1939: > > > > - "If the enemy invades, how will you prevent them from using > > the train network?" > > - "Burn all the tickets, sir!" > > I like this analogy. The proposed action would have no effect > whatsoever on the behavior that one is trying to discourage. > But the move makes the party recommending the action look > ridiculous, ridiculous enough that the story of the > recommendation is still being told move than 70 years later. > > john Except there are vendors who have already threatened to remove the 6to4 code if it is declared historic then you are left between a rock and a hard place if you need to upgrade the software on the 6to4 router for other reasons and still want to use 6to4. Not everyone is in the position to just board the train they want by force to take the analogy a little further. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
- Another look at 6to4 (and other IPv6 transition i… John C Klensin
- Re: Another look at 6to4 (and other IPv6 transiti… Joel Jaeggli
- Re: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- Re: Another look at 6to4 (and other IPv6 transiti… Joel Jaeggli
- RE: Another look at 6to4 (and other IPv6 transiti… Templin, Fred L
- Re: Another look at 6to4 (and other IPv6 transiti… Brian E Carpenter
- Re: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Ted Lemon
- Re: Another look at 6to4 (and other IPv6 transiti… Doug Barton
- RE: [v6ops] Another look at 6to4 (and other IPv6 … Templin, Fred L
- Re: Another look at 6to4 (and other IPv6 transiti… Joel Jaeggli
- RE: Another look at 6to4 (and other IPv6 transiti… Ronald Bonica
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- RE: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- RE: Another look at 6to4 (and other IPv6 transiti… Murray S. Kucherawy
- Re: Another look at 6to4 (and other IPv6 transiti… Doug Barton
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- RE: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- Re: Another look at 6to4 (and other IPv6 transiti… Roger Jørgensen
- Re: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- RE: Another look at 6to4 (and other IPv6 transiti… Noel Chiappa
- Re: Another look at 6to4 (and other IPv6 transiti… james woodyatt
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- RE: Another look at 6to4 (and other IPv6 transiti… Ronald Bonica
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Brian E Carpenter
- Re: Another look at 6to4 (and other IPv6 transiti… t.petch
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Erik Kline
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Philip Homburg
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Michael Richardson
- Re: Another look at 6to4 (and other IPv6 transiti… Sabahattin Gucukoglu
- Re: Another look at 6to4 (and other IPv6 transiti… Doug Barton
- Re: [v6ops] Another look at 6to4 (and other IPv6 … Sabahattin Gucukoglu
- Re: Another look at 6to4 (and other IPv6 transiti… Joel Jaeggli
- Re: Another look at 6to4 (and other IPv6 transiti… Sabahattin Gucukoglu
- Re: Another look at 6to4 (and other IPv6 transiti… Joel M. Halpern
- Re: Another look at 6to4 (and other IPv6 transiti… Sabahattin Gucukoglu
- Re: Another look at 6to4 (and other IPv6 transiti… Keith Moore
- Re: Another look at 6to4 (and other IPv6 transiti… Harald Alvestrand
- Re: Another look at 6to4 (and other IPv6 transiti… John C Klensin
- Re: Historic status (was Another look at 6to4 (an… t.petch
- Re: Another look at 6to4 (and other IPv6 transiti… Mark Andrews
- Historic status (was Another look at 6to4 (and ot… Mykyta Yevstifeyev
- Re: Historic status (was Another look at 6to4 (an… Randy Presuhn