Re: [homegate] [v6ops] CPE Prefix Sub-Delegation on LAN

Ole Troan <otroan@employees.org> Thu, 23 December 2010 12:04 UTC

Return-Path: <ichiroumakino@gmail.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FC943A6BFD; Thu, 23 Dec 2010 04:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.256
X-Spam-Level:
X-Spam-Status: No, score=-3.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icM6JcVHHBa8; Thu, 23 Dec 2010 04:04:27 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 0C16F3A6BFF; Thu, 23 Dec 2010 04:04:26 -0800 (PST)
Received: by eyd10 with SMTP id 10so2758383eyd.31 for <multiple recipients>; Thu, 23 Dec 2010 04:06:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=riTV5MJtqQFn/2zVhu9bI2+i8L+bWcWHXr0pXwk8Z4o=; b=ZZKBKB91snAUs91FW6Zcwo2Qi4B6IonKwUBJp86RD+4NFKE+YCxQ8JXkVqVlAsJ6O6 pcph+jpzNIcSGfhjXNfHp6OqWeQUkC76dpVSunt3VTPT7it6V7cT8HlV9CSvPCoyNKb8 l2sY55xNuGHusWJ0Wbof8tlpsK95sguRscLLs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=T4FsPe4OiFRBHUjKTTXLHvx0im2LriDDmLecOiZeubSJ09PTdnHC4oYb14Ku1nhYIY aFW4Cmj60pyRfUNd+UzPeAu51PaaIMJyOFd0kQlJ0NJf6vmnXBghRZjL4aJhVUWkyunM VlDardp2WzovtPd76/EXvv063BSH33w8lv3JA=
Received: by 10.213.108.138 with SMTP id f10mr62602ebp.88.1293105986603; Thu, 23 Dec 2010 04:06:26 -0800 (PST)
Received: from dhcp-10-61-108-18.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id x54sm5535892eeh.23.2010.12.23.04.06.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 23 Dec 2010 04:06:24 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <7E338A9A7F416C4AB2BA4D4E2DEBA0844F58EC45CA@sg2019z.corproot.net>
Date: Thu, 23 Dec 2010 13:06:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <129F694F-9979-45EC-B3D3-35AD5EBCC3F1@employees.org>
References: <7E338A9A7F416C4AB2BA4D4E2DEBA0844F58EC451F@sg2019z.corproot.net> <A9704C3A-2D7C-432D-A74B-C4F26566CE0A@cisco.com> <7E338A9A7F416C4AB2BA4D4E2DEBA0844F58EC45CA@sg2019z.corproot.net>
To: <Guillaume.Leclanche@swisscom.com> <Guillaume.Leclanche@swisscom.com>
X-Mailer: Apple Mail (2.1082)
Cc: IPv6 Operations <v6ops@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [v6ops] CPE Prefix Sub-Delegation on LAN
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Dec 2010 12:04:28 -0000

[included the homenet list]

> There might be some work to do to say how the dhcpv6 server in the CPE should get the prefix received from the ISP, also when the ISP is not using DHCPv6. For example, with 6rd. However, since the 6rd parameters have to be pre-provisioned or given via DHCP(v4), I can imagine that there's a way to sort this out without too much pain.

with regards to 6rd, there is nothing special. a 6rd delegated prefix is just like an DHCP PD prefix, for the purpose of internal prefix assignment.

this problem within the charter of the (rejected) homenet WG effort.

there are many ways internal prefix assignment and distribution of other configuration information can be done. many of the ideas were discussed during the zerouter BOF (which also failed making it into a WG).

- Multi-link subnet routing (a shared off link /64 among all nodes. host routes in OSPF)
- ND proxy (restricted topology)
- hierarchical DHCP prefix delegation (restricted topology)
- zOSPF (https://datatracker.ietf.org/doc/draft-dimitri-zospf/)
  using a new LSA in OSPF to distribute the site prefix plus a mechanism for
  collision detection.

in my view this requires new work.

cheers,
Ole