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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 31 October 2014 17:15 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 480E81A0030; Fri, 31 Oct 2014 10:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 y7YPOkTzNaoI; Fri, 31 Oct 2014 10:15:09 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD9A1A001C; Fri, 31 Oct 2014 10:15:09 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9VHEakh026024; Fri, 31 Oct 2014 18:14:36 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2BFF720B1D7; Fri, 31 Oct 2014 18:14:37 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1806B20B117; Fri, 31 Oct 2014 18:14:37 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9VHEZ7x009625; Fri, 31 Oct 2014 18:14:36 +0100
Message-ID: <5453C37B.50002@gmail.com>
Date: Fri, 31 Oct 2014 18:14:35 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>, Sheng Jiang <jiangsheng@huawei.com>
References: <544FF8FC.5090103@cisco.com> <95338658-B4F2-4634-AC7B-7B893C4DEF2E@iki.fi> <5D36713D8A4E7348A7E10DF7437A4B923AF6C46E@nkgeml512-mbx.china.huawei.com> <DEB8F897-3CED-4C59-BEBF-BF64096282F2@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6C7AE@nkgeml512-mbx.china.huawei.com>, <8490A544-45A9-45D2-9C98-D3CBEB28651D@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923AF6C8A9@nkgeml512-mbx.china.huawei.com> <E597E398-6AFB-4355-B2C4-8559D19A6AF0@fugue.com>
In-Reply-To: <E597E398-6AFB-4355-B2C4-8559D19A6AF0@fugue.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/anima/An08nURvz1QSbllgpcvxj9DDznM
Cc: Benoit Claise <bclaise@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, "anima@ietf.org" <anima@ietf.org>
Subject: Re: [Anima] ANIMA scope + homenet interaction + charter v15
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2014 17:15:11 -0000

Le 31/10/2014 16:47, Ted Lemon a écrit :
> On Oct 31, 2014, at 10:55 AM, Sheng Jiang <jiangsheng@huawei.com>
> wrote:
>> The current general mechanism are too general to work for the use
>> case of hierarchical prefix delegation. But if we add hierarchical
>> topology and no bypass requests as constraint conditions, we may be
>> able to make hierarchical prefix delegation work.
>
> No, that is not the point I am making.   The point I am making is
> that hierarchical delegation simply won't work, no matter what
> mechanism you put in place to do it, because the network has to be
> able to grow incrementally.   With that as a base assumption, you
> cannot predict where the network will grow, so you don't know how to
> construct the hierarchy.   Once the hierarchy is constructed, you
> would have to renumber on a regular basis to make hierarchical
> delegation work.

At which point one wonders whether Router Renumbering RFC2894 may need 
some updates.

Alex


    I think it is preferable to simply allow for a
> complete routing table, and then try as best as possible to make
> routing hierarchical, without demanding perfection.
>
> _______________________________________________ homenet mailing list
> homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
>
>