Re: [homenet] [Anima] ANIMA scope + homenet interaction + charter v15

Ole Troan <ot@cisco.com> Thu, 30 October 2014 13:15 UTC

Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3421A0053; Thu, 30 Oct 2014 06:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PUQXXLiE7Lsx; Thu, 30 Oct 2014 06:15:24 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1F7C1A0024; Thu, 30 Oct 2014 06:15:23 -0700 (PDT)
Received: from [192.168.10.30] (cm-84.215.22.20.getinternet.no [84.215.22.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 2A0D762A6; Thu, 30 Oct 2014 06:15:21 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <10925F8D-D2FB-4E96-B4CC-5C6F9158FE3C@fugue.com>
Date: Thu, 30 Oct 2014 14:15:17 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A07B58F-9CDE-434D-9770-494D030312B6@cisco.com>
References: <544FF8FC.5090103@cisco.com> <95338658-B4F2-4634-AC7B-7B893C4DEF2E@iki.fi> <62A56FF8-EA71-4559-8929-0A03FA7785F9@fugue.com> <3743B3C2-D8F2-45C5-85F5-C53B18739FB3@iki.fi> <10925F8D-D2FB-4E96-B4CC-5C6F9158FE3C@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/6OfZk-cgOTolOuLvmCqCLQS-SYw
Cc: Benoit Claise <bclaise@cisco.com>, homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>, "anima@ietf.org" <anima@ietf.org>
Subject: Re: [homenet] [Anima] ANIMA scope + homenet interaction + charter v15
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Oct 2014 13:15:27 -0000

>> What does flow-through PD mean? Do you have any reference on that?
> 
> It means that the edge router has the delegation, and then sub-delegates individual /64s from the pool of /64s it was delegated by the ISP, rather than splitting its delegation and delegating chunks of that delegation to downstream routers which will then delegate in turn.   In order for this to work, downstream routers have to relay PD requests to the edge router, and install routes to the delegated prefixes.   Something analogous could work on an autonomous network; I don't know that it's the right way to solve the problem, but it's certainly one way to solve the problem.   Homenet went with HNCP because it's more sensitive to arbitrary topology changes.
> 
> The hierarchical model doesn't work because it doesn't anticipate new routers being added to the network, and doesn't account for unbalanced topologies.   I thought the hipnet proposal wound up going with the flow-through model, not the hierarchical model, but I may be mistaken.

I think the homenet wg did a good of analysing the 3 variants proposed.
the "flow-through" model as far as I can recall suffers from DHCP's general problem of dealing with multiple sources of information (think multihoming with separate CE routers), in addition you either need to build what's essentially a spanning tree of DHCP relays or you need some mechanism to discover the set of DHCP server(s). certainly do-able, but not quite out of the box.

cheers,
Ole