IETF Logo Mail Archive

Re: [v6ops] Bar BoF on a 6to4 replacement? Was: my recommendation re: 6to4

Jeroen Massar <jeroen@massar.ch> Sun, 02 November 2014 17:01 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 73F731A88FF for <v6ops@ietfa.amsl.com>; Sun, 2 Nov 2014 09:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 41NR3o3oUp7T for <v6ops@ietfa.amsl.com>; Sun, 2 Nov 2014 09:01:52 -0800 (PST)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [IPv6:2a02:2528:503:2::4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50FAD1A90AE for <v6ops@ietf.org>; Sun, 2 Nov 2014 09:01:52 -0800 (PST)
Received: from kami.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 05F01100A111B; Sun, 2 Nov 2014 17:01:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1414947709; bh=Fv7qma5csaEXk3BWgiZ8NlOgk2KJCQRKjk52Ef9tZfY=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=hlQndvjVnwpOoMLhZTcqAdikPDMWnb3nNLyKZTJMFTo/qbotMmEdlndUU4xpCVF92 a6DBD0YmpMRZUL5bPmA6GbKfEbyejcX/hGBq+vjg6WVNRC7iPuq3hYAetbjsZVZrIF Qzu6XwN6p4sSkzOJvtumN0qYqkzz2MkS1k4t8ddZu4y9fH0DxLNiAssunU7M7i2zSN Tvr+w+63mplVrpND2St26udnm9oJ9gvI2MyruLUPNGfZ3xEmtIut5WWdbgbesIJI+R WhVjNCsKR6OSHWhd2aaesMGS32gyH0rKdpOQstL4gqckF7YKSF4/q5CMOpTdf4A0Bl Dv5wNom7hhp2A==
Message-ID: <5456637B.5090302@massar.ch>
Date: Sun, 02 Nov 2014 18:01:47 +0100
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Iljitsch van Beijnum <iljitsch@muada.com>
References: <5454119C.3090601@network-heretics.com> <2134F8430051B64F815C691A62D9831832D75F09@XCH-BLV-504.nw.nos.boeing.com> <686FABB5-9A9E-4D0C-BD1A-19CA02A9C247@muada.com> <2134F8430051B64F815C691A62D9831832D76378@XCH-BLV-504.nw.nos.boeing.com> <AD4F3B9C-18D2-4B6F-867C-423368D6F489@muada.com> <54562E86.7000208@massar.ch> <6049A1FD-7514-46F4-8B50-DB0F71ACE64E@muada.com> <2134F8430051B64F815C691A62D9831832D76CC2@XCH-BLV-504.nw.nos.boeing.com> <D4DD4D4C-ECD2-4C35-A7A8-0564D5C7B6BD@muada.com> <2134F8430051B64F815C691A62D9831832D76CFC@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832D76CFC@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/nW8j8bKKyFIhEj1wE_S3HtQ8yko
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Bar BoF on a 6to4 replacement? Was: my recommendation re: 6to4
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: Sun, 02 Nov 2014 17:01:53 -0000

On 2014-11-02 16:50, Templin, Fred L wrote:
>> -----Original Message-----
>> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
>> Sent: Sunday, November 02, 2014 7:38 AM
>> To: Templin, Fred L
>> Cc: Jeroen Massar; Owen DeLong; v6ops@ietf.org WG
>> Subject: Re: [v6ops] Bar BoF on a 6to4 replacement? Was: my recommendation re: 6to4
>>
>> On 02 Nov 2014, at 16:28, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>>
>>> I say turn the tunnel brokers into DHCPv6 servers and the home gateways into DHCPv6 clients.
>>
>> That doesn't work, because you need the remote tunnel endpoint configuration info before you can talk to the tunnel broker over
>> IPv6 so you can send your DHCPv6 request in order to get your configuration info...
> 
> The tunnel broker address is automatically derived from the DNS.

Or you just get those details from a protocol like TIC or TSP and let
the actual Tunnel Broker decide on these details.

> However, the client does need to be enrolled in the service offered by the tunnel broker in order to get an IPv6
> prefix delegation. Is that any different than what current tunnel broker services require?

No difference at all.

But there is absolutely no reason to do DHCPv6.
Both SixXS and HE do static prefix delegation.

Per default there is a _routed_ /64, and otherwise you request a large one.

As the user gets a _static_ prefix, if somebody wants to bother with
DHCPv6, let them do that on their end.

Greets,
 Jeroen

v2.46.0 | Report a Bug | By Email | System Status