Re: [v6ops] Who is stilll running 6to4 relays (Was: I-D Action: draft-ietf-v6ops-6to4-to-historic-08.txt)
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 19 November 2014 19:29 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D59E1A6F02 for <v6ops@ietfa.amsl.com>; Wed, 19 Nov 2014 11:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3iuy7bWNfng for <v6ops@ietfa.amsl.com>; Wed, 19 Nov 2014 11:29:00 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 445FB1A6EE7 for <v6ops@ietf.org>; Wed, 19 Nov 2014 11:29:00 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id fp1so1451939pdb.29 for <v6ops@ietf.org>; Wed, 19 Nov 2014 11:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JwVZ7/P550cuL00UtWwEP5Bbt8kDoGqkFgUB6IKXtxA=; b=GjEkROQ2NaI305Ypt58jAfTotXZqtoR+wylk0pXLROvS3I/Nu0ZS1WCvH/Kqc/WE12 aaNU9FghiZSaWiY36GndK44BWxpl6tcO7Cosm6kamISDc5oD9lEK6u0ewoITEStkgXkY kb+WmgJTsaxFBNkicUmmdH43LbsV5EBiBGOcwPhmYz1kn1XVdeixth6wMQRhZgjVjLAX 7iLOGJm7D1+8Af3aPRkUpJipVlSEK6uoC3CGbn1pvvdGncO7GHmpyDWsEHKgG29XGZUR 5p3IL1aOBRbQiWn7+ldScrXN2WDhwawFYxFq/q6gP0cK/1uT/6acjgQ00kw9zpT/7zTW zPWQ==
X-Received: by 10.70.26.35 with SMTP id i3mr49929001pdg.84.1416425339549; Wed, 19 Nov 2014 11:28:59 -0800 (PST)
Received: from [192.168.178.23] (225.198.69.111.dynamic.snap.net.nz. [111.69.198.225]) by mx.google.com with ESMTPSA id g12sm65009pdj.27.2014.11.19.11.28.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Nov 2014 11:28:58 -0800 (PST)
Message-ID: <546CEF7D.2070504@gmail.com>
Date: Thu, 20 Nov 2014 08:29:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>
References: <54663F67.5080603@gmail.com> <546927A0.8030201@inex.ie> <546BAC1F.5020401@umn.edu> <20141118.223012.41712464.sthaug@nethelp.no> <AA6EE468-E5D6-47B5-84EB-1867267F2EDD@ecs.soton.ac.uk> <EMEW3|70ac22f3eb7a500327bbf34b35183761qAI7aA03tjc|ecs.soton.ac.uk|AA6EE468-E5D6-47B5-84EB-1867267F2EDD@ecs.soton.ac.uk> <546C4D41.2030406@massar.ch>
In-Reply-To: <546C4D41.2030406@massar.ch>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YOoVegeVU_qMYuZy0U5mxNq80i0
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Who is stilll running 6to4 relays (Was: I-D Action: draft-ietf-v6ops-6to4-to-historic-08.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 19:29:02 -0000
With the same Bcc: > Internet service > providers SHOULD filter out routes to 192.88.99.1. It is pretty clear enough to me (as document editor) that there is no consensus in the v6ops WG for this sentence, which was added after some earlier discussion in the WG. The final consensus has to be judged by the WG chairs, but my guess is that we'll delete that sentence and leave the decision up to individual operators. (The argument is that this route helps people who are still successfully using anycast 6to4, whether intentionally or by default, and filtering it would hurt them without helping anyone else.) Regards Brian On 19/11/2014 20:56, Jeroen Massar wrote: > BCC'ing ipv6-ops@cluenet.net thus a bit of background info: > > draft-ietf-v6ops-6to4-to-historic-08.txt currently contains: > > Section 4 "Deprecation" > 8<------------------------ > Current operators of an anycast 6to4 relay with the IPv4 address > 192.88.99.1 SHOULD review the information in [RFC6343] and the > present document, and then consider carefully when the anycast relay > can be discontinued as traffic diminishes. Internet service > providers SHOULD filter out routes to 192.88.99.1. However, networks > > SHOULD NOT filter out packets whose source address is 192.88.99.1, > because this is normal 6to4 traffic from a 6to4 return relay > somewhere in the Internet. > ------------------------>8 > > Hence this BCC to poll what the operators of these current relays think > about this and what they think they will do. > > Note that the discussion is really taking place on v6ops@ietf.org hence > to post you either have to be (temporarily) subscribed and/or post > anyway and wait for one of the listadmins to approve your messages. > > Below the view that RIPEs RIS thinks are the current 6to4 anycast relays. > > On 2014-11-19 08:35, Tim Chown wrote: > [..] >> I wonder what the first publicly announced IPv4 6to4 relay was. >> Perhaps SWITCH (via Simon Leinen) or FUNET (Pekka Savola)? >> I remember the days of SWITCH’s relay being a world 6to4 magnet. >> >> Would be poetic to let them be the last to switch off too, if they’re still running :) > > Afaik the SWITCH one is gone for a long long time already. > FUNET is still up, but only limited in BGP, only RRC13 in Moscow sees > it, which is funny as for instance RRC07 in Stockholm does not. > > The list: > https://stat.ripe.net/widget/looking-glass#w.resource=192.88.99.1 > > 8903 = ES BT Espana > 6939 = US Hurricane Electric* > 7575 = AU AARnet > 16150 = SE Availo (Port80)* > 12779 = IT ItGate* > 1103 = NL Surfnet* > 8954 = NL Intouch* > 15598 = DE QSC AG > 28917 = RU FIORD AS > 21416 = RU TCINET > 1741 = FI FUNET* > 8359 = RU MTS > 44581 = SE AllTele > > > Note that only 6939/7575/8903 are 'globally' visible, others seem to > have very limited announcement. > > * = person who operates it is well known, all of which will be on > ipv6-ops@ hence, BCCd them that way to get them into the loop on this > discussion as they will be the folks disabling those boxes or not. > > Greets, > Jeroen > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops >
- [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-hist… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Nick Hilliard
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Nick Hilliard
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… David Farmer
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… sthaug
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… David Farmer
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Mark Andrews
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Doug Barton
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Tore Anderson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… sthaug
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Tim Chown
- [v6ops] Who is stilll running 6to4 relays (Was: I… Jeroen Massar
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Brian E Carpenter
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Brian E Carpenter
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Brian E Carpenter
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Jeroen Massar
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Metzler, Dan J
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Brian E Carpenter
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Nick Hilliard
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Mark ZZZ Smith
- Re: [v6ops] Who is stilll running 6to4 relays (Wa… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… gall
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Nick Hilliard
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Jeroen Massar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Lorenzo Colitti
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… James Woodyatt
- Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-… Alexandru Petrescu