Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.txt - software bugs

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 13 November 2014 22:42 UTC

Return-Path: <alexandru.petrescu@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 CDF8D1AE116 for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 14:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 SiT1gPgO_qvV for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 14:42:37 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21C851AE10F for <v6ops@ietf.org>; Thu, 13 Nov 2014 14:42:36 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id sADMgZmV016535; Thu, 13 Nov 2014 23:42:35 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2DEC82047E4; Thu, 13 Nov 2014 23:42:55 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1FCED2046C1; Thu, 13 Nov 2014 23:42:55 +0100 (CET)
Received: from [127.0.0.1] ([132.166.84.11]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id sADMgVVi012918; Thu, 13 Nov 2014 23:42:33 +0100
Message-ID: <546533D7.9080507@gmail.com>
Date: Thu, 13 Nov 2014 23:42:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20141111054026.11197.49784.idtracker@ietfa.amsl.com> <5461A23D.5020506@gmail.com> <546264A5.4050309@umn.edu> <546271A2.907@gmail.com> <5463C716.1030805@umn.edu> <54646DBE.9060800@dougbarton.us> <20141113084029.GT31092@Space.Net> <5464E4F6.9070401@gmail.com> <5465021A.2080305@dougbarton.us> <546509F1.5060508@massar.ch> <54652069.30805@gmail.com> <546525E7.7050006@massar.ch> <54652E0C.7050901@gmail.com> <546531AF.6@gmail.com>
In-Reply-To: <546531AF.6@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/IaeE2WXoGoc3acBUO0oiM1CXxPI
Cc: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.txt - software bugs
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: Thu, 13 Nov 2014 22:42:42 -0000

Le 13/11/2014 23:33, Brian E Carpenter a écrit :
> On 14/11/2014 11:17, Alexandru Petrescu wrote:
>> Le 13/11/2014 22:43, Jeroen Massar a écrit :
>>> On 2014-11-13 22:19, Alexandru Petrescu wrote:
>>>> Le 13/11/2014 20:43, Jeroen Massar a écrit :
>>>> [...]
>>>>> This is also what has been discussed on the list:
>>>>>     - deprecate anycast 6to4
>>>>>     - keep direct 6to4
>>>>
>>>> YEs, I agree, and I would like to re-mention the point about software
>>>> bugs.
>>>>
>>>> There is one particular 6to4 implementation in the wild which has two
>>>> different means to put up a 6to4 tunnel.  One is to just say '6to4' in
>>>> the cli, the other is to be specific and type that IPv4 anycast address.
>>>>
>>>> With the first means - it does not work.  Worse, it gets into a mode
>>>> where packets are output destined to random IPv4 addresses.
>>>>
>>>> Fix the bug.
>>>
>>> That is a vendor issue. Nothing the IETF can do about.
>>
>> I agree.
>>
>>>
>>>> What does this mean with respect to the deprecation effort?
>>>
>>> That because of the bug that platform already is useless anyway, thus
>>> effectively it is already deprecated... ;)
>>>
>>>> Do not deprecate the IPv4 anycast address because if so then the entire
>>>> 6to4 software on that platform will no longer work.
>>>
>>> If that platform (which one btw - sponsor) is so broken, then they
>>> currently have
>>> a broken setup anyway. Hence, nothing to be fixed there.
>>>
>>>> Do not deprecate until you offer a solution satisfying a number of
>>>> requirements (currently unsatisfied by eg tunnel brokers).
>>>
>>> Which requirements are these?
>>
>> Ones one would have to lay down and agree on before engaging in new work.
>>
>> For example -1- must allow for reverse DNS ok, -2- must be secureable by
>> existing e2e IPsec, -3- to the extent of possible be easy to set up for
>> Clients and not involve intervention of another party (like when
>> requesting an IPv6 address from an administrator, delayed paper forms,
>> etc).
>
> Anycast 6to4 meets those requirements afaik ;-)

Hm yes and no.  IPsec and anycast never married AFAIK.

6to4 is not alowing for reverse DNS either, if I am not terribly wrong.

Alex

>
>     Brian
>
>
>