Re: [homenet] draft-baker-homenet-prefix-assignment

Ole Troan <ot@cisco.com> Fri, 18 November 2011 08:14 UTC

Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E4321F953C for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 00:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.863
X-Spam-Level:
X-Spam-Status: No, score=-9.863 tagged_above=-999 required=5 tests=[AWL=0.736, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOIYaeXKwSgQ for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 00:14:17 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id C089721F9536 for <homenet@ietf.org>; Fri, 18 Nov 2011 00:14:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=764; q=dns/txt; s=iport; t=1321604053; x=1322813653; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=l4qhk7JNmCgeegkUlRmPIdx16AN9WPgeZnpOloCbF3s=; b=STR56vRHHHNQPRorpMGOtV+dCoWDMHNLeCfCODChtjOMVmBmkuiuKf8r KNDEPy5F1PbkWeWTYlatYq2lQfW0twaLhnS+/b8JrOSGtLV9JNaVUbbxc Dv0+i72PvUJ18LNKFpP/3xOmiasWHcySVBrgNHxy5LlC3uBzCMs0FNfVP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACkTxk6Q/khL/2dsb2JhbABCqkOBBYFyAQEBAwESASc/BQsLDjhXBjWHYZgtAZ5JiTRjBJQ3kgA
X-IronPort-AV: E=Sophos;i="4.69,532,1315180800"; d="scan'208";a="122008627"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 18 Nov 2011 08:14:12 +0000
Received: from ams3-vpn-dhcp5098.cisco.com (ams3-vpn-dhcp5098.cisco.com [10.61.83.233]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAI8EC4k013283; Fri, 18 Nov 2011 08:14:12 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Ole Troan <ot@cisco.com>
In-Reply-To: <17953.1321493297@marajade.sandelman.ca>
Date: Fri, 18 Nov 2011 09:14:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <400C7BA2-3D4D-4663-9B3E-FA2E6C2D8992@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com> <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com> <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com> <17953.1321493297@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 08:14:18 -0000

Michael,

> Is there some reason that the flooding mechanism can't distribute the
> list of edge CPE routers, and then DHCPv6 can be used in unicast
> request/reply to ask those CPE routers for things.
> 
> (I would even wonder if the CPE routers shouldn't be identified by their
> ULA rather than self-identifying by the address in the subnet the deal with)
> 
> This is how I imagined the DHCPv6 PD mechanism working before
> draft-chakrabarti-homenet-prefix-alloc-01 was written, which imagined a
> strict hierarchal tree.

that's how I imagined also.
DHCP PD on the edges. flooding protocol between all the internal routers. then hosts use RA/DHCP for addresses / other configurations to their onlink routers.

cheers,
Ole