Re: [v6ops] 6to4v2 (as in ripv2)?
Tim Chown <tjc@ecs.soton.ac.uk> Wed, 27 July 2011 15:35 UTC
Return-Path: <tjc@ecs.soton.ac.uk>
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 0D6EE21F8BDB; Wed, 27 Jul 2011 08:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 ItQBnxRW1JXU; Wed, 27 Jul 2011 08:35:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 7B55621F8BD8; Wed, 27 Jul 2011 08:35:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6RFZCao005041; Wed, 27 Jul 2011 16:35:12 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6RFZCao005041
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311780912; bh=euyLtAa7+f1ooboyltGPlCkk5DU=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=o8ogwwELSpzNaxbIHLQ+AAPbo+C4/lcrmGUuJLPVhg0AsXKe85RXOW87+hK9eBvWo HL9WUbwlhzJRfR3VgJVnBk9/LcPFHKAXGWtsuKjVYR0RWY02qrKzuwauNEkA77/tag /21jAXwxhxq8/gKjWmwvTn6Vngwha+w0amhX7HIY=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n6QGZC0366144739vf ret-id none; Wed, 27 Jul 2011 16:35:12 +0100
Received: from [IPv6:2001:df8::16:704d:e106:4b6a:660a] ([IPv6:2001:df8:0:16:704d:e106:4b6a:660a]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6RFZ7i7031397 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Jul 2011 16:35:08 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110727151517.CF9371235D70@drugs.dv.isc.org>
Date: Wed, 27 Jul 2011 16:35:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>, IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6QGZC036614473900; tid=n6QGZC0366144739vf; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p6RFZCao005041
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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 15:35:19 -0000
On 27 Jul 2011, at 16:15, Mark Andrews wrote: > > Because it will come down to "run 6to4 and be exposed to some bug" > or "not run 6to4 but be safe from the bug". We already have vendors > saying they are thinking about pulling 6to4 from their code bases > if it becomes historic. I would note that RIPE-501 does not mention 6to4: http://www.ripe.net/ripe/docs/ripe-501 As far as I can see, it only mentions RFC4213. I would ask what is the alternative if as Mark suggests the vendors begin removing 6to4 support? a) use 6to4 anyway on an open platform like OpenWRT b) use a tunnel broker - this works much better through NATs and with dynamic IPv4 addresses c) use your $work VPN if it supports IPv6, which it could/should if your company values IPv6 d) get IPv6 from your ISP, or move to one that has it if yours does not I suspect, but have no proof, that the huge majority of 6to4 users don't use it intentionally, and the content they are trying to reach is also available over IPv4. But for people who want to develop and use new IPv6-specific apps, then either a broker or something like OpenWRT ought to meet their needs? Tim
- 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