Re: draft-ietf-v6ops-6to4-to-historic (yet again)
Rémi Després <despres.remi@laposte.net> Wed, 27 July 2011 07:46 UTC
Return-Path: <despres.remi@laposte.net>
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 20EC521F86E0 for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 00:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 HUx-OQBvKiSK for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2011 00:46:55 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.12]) by ietfa.amsl.com (Postfix) with ESMTP id 47DB321F86DD for <ietf@ietf.org>; Wed, 27 Jul 2011 00:46:55 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id 70426700008C; Wed, 27 Jul 2011 09:46:54 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id 16C387000088; Wed, 27 Jul 2011 09:46:54 +0200 (CEST)
X-SFR-UUID: 20110727074654933.16C387000088@msfrf2213.sfr.fr
Subject: Re: draft-ietf-v6ops-6to4-to-historic (yet again)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <despres.remi@laposte.net>
In-Reply-To: <46B9B2CA-3A7A-40F4-9164-5608C48DCF18@apple.com>
Date: Wed, 27 Jul 2011 09:46:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC48CFAA-4060-4462-827F-CD80C26334C2@laposte.net>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <46B9B2CA-3A7A-40F4-9164-5608C48DCF18@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <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: Wed, 27 Jul 2011 07:46:56 -0000
Le 27 juil. 2011 à 00:11, james woodyatt a écrit : > On Jul 25, 2011, at 10:30 AM, Ronald Bonica wrote: >> >> Please post your views on this course of action by August 8, 2011. > > I remain convinced that this document is unnecessary and publishing it would be silly, at best, and at worst, the simultaneous publication of 6to4-to-historic alongside 6to4-advisory, which implicitly contradict one another-- the latter says that 6to4 has an indefinite future and here's how to keep everything operational in its presence on the Internet; the former says 6to4 has no future, and it should not be used by anyone for any purpose-- may turn out to be an embarrassment for IETF. > IESG should feel very nervous about claiming there is consensus to publish this draft. It does not appear to me like there is a rough consensus for it. +1 > > That said, I won't complain too loudly if this draft is published. It would give me cover to ask my employers for 6to4 capability to be removed from forthcoming products that I mainly work to support. I don't like taking features away from users when there isn't a suitable upgrade path for them, but the truth is that fielding problems from the field resulting from 6to4 failure can be pretty tiresome, and I would welcome the cover from IETF to be able to say, "Oh, you're still using 6to4? You should turn that off. It's deprecated by IETF now, and accordingly, we no longer support it. Get native IPv6 service." > > In other words, whether IESG means to convey this message or not, publishing 6to4-to-historic alongside the existing 6to4-advisory-- without any clear phase-out plan-- will pretty clearly imply to people like me that the official phase-out plan is to remove 6to4 from the Internet, starting as soon as vendors and operators are independently able to do so. "Start the engines of destruction." > > > -- > james woodyatt <jhw@apple.com> > member of technical staff, core os networking > > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) SM
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Douglas Otis
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mykyta Yevstifeyev
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Noel Chiappa
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Roger Jørgensen
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Philip Homburg
- draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Keith Moore
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Michael Richardson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Ole Troan
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Michel Py
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Noel Chiappa
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) John Leslie
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Martin Rex
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Christian Huitema
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mark Andrews
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Cameron Byrne
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Ted Faber
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Michel Py
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Randy Presuhn
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mykyta Yevstifeyev
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Lorenzo Colitti
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Geoff Huston
- Re: 6to4v2 (as in ripv2)? (was: draft-ietf-v6ops-… Alexandru Petrescu
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) t.petch
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Joel Jaeggli
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Mikael Abrahamsson
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Templin, Fred L
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) james woodyatt
- Re: 6to4v2 (as in ripv2)? Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Brian E Carpenter
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Randy Bush
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) GT RAMIREZ, Medel G.
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Sabahattin Gucukoglu
- Re: 6to4v2 (as in ripv2)? Masataka Ohta
- Re: 6to4v2 (as in ripv2)? Mark Andrews
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) George Michaelson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) t.petch
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: 6to4v2 (as in ripv2)? Fred Baker
- Re: 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Joel Jaeggli
- RE: 6to4v2 (as in ripv2)? Michel Py
- Re: RE: 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Tim Chown
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Tore Anderson
- Re: [v6ops] 6to4v2 (as in ripv2)? Philip Homburg
- Re: "6to4 damages the Internet" (was Re: draft-ie… Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Townsley
- Re: [v6ops] 6to4v2 (as in ripv2)? John Mann (ITS)
- Re: [v6ops] 6to4v2 (as in ripv2)? Ted Lemon
- Re: [v6ops] 6to4v2 (as in ripv2)? Erik Kline
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Douglas Otis
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: [v6ops] 6to4v2 (as in ripv2)? Thomas Nadeau
- Re: [v6ops] 6to4v2 (as in ripv2)? Tim Chown
- "6to4 damages the Internet" (was Re: draft-ietf-v… Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: "6to4 damages the Internet" (was Re: draft-ie… Michael Richardson
- Re: "6to4 damages the Internet" (was Re: draft-ie… Lorenzo Colitti
- Re: [v6ops] 6to4v2 (as in ripv2)? Roger Jørgensen
- Re: [v6ops] 6to4v2 (as in ripv2)? Alexandru Petrescu
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Warren Kumari
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: [v6ops] 6to4v2 (as in ripv2)? Michael Richardson
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Alexandru Petrescu
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- Re: [v6ops] 6to4v2 (as in ripv2)? james woodyatt
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Michael Richardson
- IPv6 traffic distribution Michel Py
- Re: "6to4 damages the Internet" (was Re: draft-ie… Brzozowski, John
- Re: "6to4 damages the Internet" (was Re: draft-ie… TJ
- Re: IPv6 traffic distribution james woodyatt
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: "6to4 damages the Internet" (was Re: draft-ie… Keith Moore
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- Re: "6to4 damages the Internet" (was Re: draft-ie… Philip Homburg
- RE: IPv6 traffic distribution Worley, Dale R (Dale)
- Re: [v6ops] 6to4v2 (as in ripv2)? Cameron Byrne
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: [v6ops] 6to4v2 (as in ripv2)? Philip Homburg
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- Re: IPv6 traffic distribution Lorenzo Colitti
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Lorenzo Colitti
- Re: IPv6 traffic distribution Tim Chown
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Thierry Ernst
- Re: "6to4 damages the Internet" (was Re: draft-ie… Masataka Ohta
- Re: IPv6 traffic distribution Brian E Carpenter
- Re: "6to4 damages the Internet" (was Re: Martin Rex
- Re: "6to4 damages the Internet" (was Re: Philip Homburg
- Re: IPv6 traffic distribution George Michaelson
- Re: "6to4 damages the Internet" (was Re: Cameron Byrne
- Re: IPv6 traffic distribution Keith Moore
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Joel Jaeggli
- RE: IPv6 traffic distribution Michel Py
- Re: IPv6 traffic distribution Keith Moore
- Re: IPv6 traffic distribution Keith Moore
- Re: IPv6 traffic distribution Ole Troan
- Re: IPv6 traffic distribution Joel Jaeggli
- Re: IPv6 traffic distribution George Michaelson
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- Re: 6to4v2 (as in ripv2)? Rémi Després
- Re: draft-ietf-v6ops-6to4-to-historic (yet again) Rémi Després
- Re: IPv6 traffic distribution Rémi Després
- Re: IPv6 traffic distribution Joel Jaeggli
- Re: IPv6 traffic distribution Rémi Després
- Re: 6to4v2 (as in ripv2)? Keith Moore
- Re: IPv6 traffic distribution Rémi Després
- RE: 6to4v2 (as in ripv2)? Michel Py
- Re: IPv6 traffic distribution George Michaelson
- Re: 6to4v2 (as in ripv2)? Rémi Després
- RE: 6to4v2 (as in ripv2)? Michel Py
- RE: 6to4v2 (as in ripv2)? Christian Huitema
- Re: 6to4v2 (as in ripv2)? Philip Homburg
- RE: 6to4v2 (as in ripv2)? Templin, Fred L
- Re: [v6ops] 6to4v2 (as in ripv2)? Mark Andrews
- What is Native IPv6 Michel Py
- Re: IPv6 traffic distribution Brzozowski, John
- Re: What is Native IPv6 JORDI PALET MARTINEZ
- Re: What is Native IPv6 Roger Jørgensen
- Re: What is Native IPv6 Keith Moore
- Re: What is Native IPv6 Philip Homburg
- RE: What is Native IPv6 Michel Py
- Re: What is Native IPv6 Philip Homburg
- Re: "6to4 damages the Internet" (was Re: Mark Atwood
- Re: "6to4 damages the Internet" (was Re: Masataka Ohta
- Re: [v6ops] 6to4v2 (as in ripv2)? Jeroen Massar
- RE: [v6ops] 6to4v2 (as in ripv2)? Frank Bulk
- Re: [v6ops] 6to4v2 (as in ripv2)? Keith Moore
- RE: draft-ietf-v6ops-6to4-to-historic (yet again) Ronald Bonica