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

Jeroen Massar <jeroen@massar.ch> Fri, 31 October 2014 07:28 UTC

Return-Path: <jeroen@massar.ch>
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 9F8141A8AE7 for <v6ops@ietfa.amsl.com>; Fri, 31 Oct 2014 00:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] 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 z4DIZI421bF8 for <v6ops@ietfa.amsl.com>; Fri, 31 Oct 2014 00:28:22 -0700 (PDT)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F70C1A8AEB for <v6ops@ietf.org>; Fri, 31 Oct 2014 00:28:21 -0700 (PDT)
Received: from yomi.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 700631009F362; Fri, 31 Oct 2014 07:28:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1414740498; bh=nf6f0f87fJCqSEyyhDaMuk/CRI2KrK9GifVrtAmF5OM=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=Ji44viKjEbQYpElDT4ngAZ2dFhtBX2S0XLhBVQeWCJ65xRxRTGNf8GdE/h5eRowR6 HbW6YMC3fBovZgOcFP7L6Q0Rymw8VltmguHZCuKTglTXr9X9I1RsNY/Y+PwTBTyU0N 5pMNh2kc9j7teS3bXP1wZp0R2+LcozcGLkYURW3gJBvbXfQy9s8QOFWpfGaHTGdYw8 Wg+3hyoVadvOVcX+5W0SMDdTAQeMeJiShkgPv37GVRXECIbgXi0PMr1PcEK0CwPTaD m0LZQze7lOw/K9pJZiTTDO4IXR/Wwyumo8T3SJphFh0NhFO3iatC/CFeITVUiY/kYs 2pRddb95YK0Ng==
Message-ID: <54533A0F.1050502@massar.ch>
Date: Fri, 31 Oct 2014 08:28:15 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>, Gert Doering <gert@space.net>
References: <20141021063829.20337.35646.idtracker@ietfa.amsl.com> <545050FE.8020807@network-heretics.com> <CAKD1Yr2rPqDy7+oZF16ORU8SnuE2y7NZaDMN1O_TZRO6q8B2iQ@mail.gmail.com> <545054DD.9020406@network-heretics.com> <54505F43.5020203@gmail.com> <alpine.DEB.2.10.1410300643030.11141@sol> <20141030185237.GR31092@Space.Net> <54528FAE.3050907@network-heretics.com> <20141030204115.GT31092@Space.Net> <5452A333.7060300@network-heretics.com>
In-Reply-To: <5452A333.7060300@network-heretics.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/CzHpIf0vQSQbHfOLnLAYCEh6cs0
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-06.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: Fri, 31 Oct 2014 07:28:24 -0000

On 2014-10-30 21:44, Keith Moore wrote:
> On 10/30/2014 04:41 PM, Gert Doering wrote:
>>>> Before you get a 6to4 tunnel, stick to IPv4-only.  6to4 tunneled IPv6
>>>> > >to the "wild Internet" (unlike "to your friend who also uses
>>>> 6to4, no
>>>> > >gateway involved") will be SO much worse than "just use native IPv4"
>>>> > >that you're doing nobody a favour doing this.
>>> >It's a mistake to assume that the reason for using IPv6 is to talk to
>>> >the "wild Internet" (especially if you define "wild Internet" as the
>>> set
>>> >of hosts that talk  IPv4 and might also happen to talk IPv6).   The
>>> >motivation to use IPv6 is driven by different applications than IPv4
>>> was.
>> So in which way does this draft impact your ability to talk IPv6 between
>> your nodes?
> It impacts my ability to talk IPv6 with any other nodes for which 6to4
> currently works, which are not necessarily "my" nodes, nor nodes that
> also support IPv4.   To give one example, I've found that video
> conferencing over 6to4 can work in situations in which STUN-based NAT
> traversal fails.

You are saying you can transport proto-41 packets through a NAT setup,
that while STUN does not work?

I would really love to see the details. As NATs that know about proto-41
or are able to stick it to a specific endpoint are rare.

In most cases to get proto-41 working behind NAT you will have to force
the NAT box into "DMZ mode" (or whatever the flavor of the name is). And
even then, typically they do not do proto-41.

The DMZ trick will fail anyway, as you cannot teach your local host to
use the local IP address (eg 192.0.2.1) and configure it to listen to a
6to4 address of 2002:<public>:<ipaddr>::<something>

Thus I am *really* wondering how that is supposed to work.

Unless you mean you let the NAT box do the 6to4, as then, indeed things
get better. That requires also the other host to do 6to4. But in that
situation you will have an up-to-date enough host that will properly
handle STUN, uPNP or NAT-PMP and should thus not have any issues with NAT.

You will have a much better chance using Teredo in this situation (which
is what Xbox One does btw :)

Or much better: just use TSP or AYIYA, then you have determinism on your
side.

Greets,
 Jeroen