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

Doug Barton <dougb@dougbarton.us> Thu, 13 November 2014 20:25 UTC

Return-Path: <dougb@dougbarton.us>
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 001C41AD03A for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 12:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-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 tDEPu8sIrCUf for <v6ops@ietfa.amsl.com>; Thu, 13 Nov 2014 12:24:56 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 867EB1AD00D for <v6ops@ietf.org>; Thu, 13 Nov 2014 12:24:56 -0800 (PST)
Received: from bcn-dbarton.lan (unknown [67.159.169.102]) by dougbarton.us (Postfix) with ESMTPSA id 4F94922B1C; Thu, 13 Nov 2014 20:24:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dkim; t=1415910296; bh=/ULF2BZ69bCaEcIM4cl+ApnNViB/MhrlKaUb8nDXA10=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=JmQlae6E2esfRWckXe1LBHK0yME/HmWuaCkbkTnHLs3Vyef6kwer64GVjmokzz99n zjH3IBnHEqCc08RzapGo78Mb9BkYlgRxWzspm40Q6phrpNos8OdinGPezu/u3Vql2M skTwm+Ee49hYkax9GQbUi0WmoMG37sbFCQQ+Lvs4=
Message-ID: <54651396.4020103@dougbarton.us>
Date: Thu, 13 Nov 2014 12:24:54 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <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> <BAD445F2-2A65-4169-B12A-ED7DC6067F81@employees.org> <20141113195958.GZ31092@Space.Net> <54650E87.5050407@dougbarton.us> <20141113201201.GB31092@Space.Net>
In-Reply-To: <20141113201201.GB31092@Space.Net>
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DQ72540L3X3-8_Voe39lwnJ8eRo
Cc: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6to4-to-historic-07.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: Thu, 13 Nov 2014 20:25:02 -0000

On 11/13/14 12:12 PM, Gert Doering wrote:
> Hi,
>
> On Thu, Nov 13, 2014 at 12:03:19PM -0800, Doug Barton wrote:
>>> (Client has working global IPv4, Router has working global IPv4, neither
>>> has v6, but peer-to-peer 6to4 enables access to inside LAN with 2002:
>>> addresses derived from Router's v4 address)
>>
>> Isn't that the use case that ULAs are meant to cover? Or am I missing
>> something here?
>
> So how exactly do ULAs help connect to your home network from abroad,
> when all you have is IPv4 at the client?
>
> "client" is obviously *outside* "home network"

Ok, then I misunderstood your point, thanks for clarifying.

>> I made the point earlier that (for example) OpenWRT already has support
>> for PD, it also creates a ULA network on the LAN side, whether you have
>> a public prefix (or tunnel) or not. So all of that is doable today, with
>> running code.
>
> That wasn't the question.  Ole was asking "what are use cases for
> peer-to-peer 6to4" (RFC 3056 without 3068).

Yeah, I have the same question. :)  If users are stuck on an IPv4-only 
ISP, and want IPv6, they have proven alternatives already. IMO it's 
going to be very hard to send a clear message to implementers and 
operators, "Deprecate *this* kind of 6to4, but *not* this other kind."

Doug