Re: [homenet] Updates to Homenet Architecture Principles doc

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 17 June 2014 14:39 UTC

Return-Path: <alexandru.petrescu@gmail.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 C10DC1A0091 for <homenet@ietfa.amsl.com>; Tue, 17 Jun 2014 07:39:59 -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 ZUk36ADOFjaY for <homenet@ietfa.amsl.com>; Tue, 17 Jun 2014 07:39:58 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5398D1A0024 for <homenet@ietf.org>; Tue, 17 Jun 2014 07:39:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s5HEdt33027040; Tue, 17 Jun 2014 16:39:55 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 93790206353; Tue, 17 Jun 2014 16:41:40 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 86063206334; Tue, 17 Jun 2014 16:41:40 +0200 (CEST)
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 s5HEdk26025014; Tue, 17 Jun 2014 16:39:54 +0200
Message-ID: <53A05332.8060000@gmail.com>
Date: Tue, 17 Jun 2014 16:39:46 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <CAKD1Yr0hr8Pa_QU_9mjRjbxffQ=mdgOWYSQUyLc5ewkpuf5OmA@mail.gmail.com> <F08A2136-E88F-4785-BE01-14D386B9C2D9@fugue.com> <CAKD1Yr1nhnvG2H_9eeW-Dono3cZqYaxMZaCR1vcueOQgW4xqYQ@mail.gmail.com> <E66DDB31-C318-4025-BF8A-15F2336A2A08@fugue.com> <88089D9C-9CBD-4C91-A69E-BDCE0A4FEEB1@townsley.net> <01E23AA3-96CE-44A0-A513-C52D71ED6D92@fugue.com> <539B5EC9.1090001@gmail.com> <949CCE9B-67A5-4293-94ED-5DB946BD1B4F@fugue.com> <B52794B6-0516-46F0-9981-7EB4471228FA@townsley.net> <539F4EFE.5020407@gmail.com> <20140616201800.GZ46558@Space.Net>
In-Reply-To: <20140616201800.GZ46558@Space.Net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Awja_hYKn-tFAvUxJlpzZdbe1YI
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mark Townsley <mark@townsley.net>
Subject: Re: [homenet] Updates to Homenet Architecture Principles doc
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: Tue, 17 Jun 2014 14:39:59 -0000

Le 16/06/2014 22:18, Gert Doering a écrit :
> Hi,
>
> On Mon, Jun 16, 2014 at 10:09:34PM +0200, Alexandru Petrescu wrote:
>> Some deployments of IPv6 homenets with multiple IP subnets dont run
>> routing protocols, but static routing.  I've discovered that recently
>> with much enthusiasm.  Maybe it's just a first step, but I havent seen
>> documented this simple and numerous existing deployments.
>
> This is not a "homenet" as per this architecture document.  The key is
> "it needs to work for your parents, without you driving over and
> setting it up for them".

I suppose parents will likely ask the IPv6 specialists something like this:
- should I click on '6rd' or '6to4' or on 'DHCPv6' or on 'PPPoE'?
- should I click on ULA or not?
- should I click on private addresses or not?
- should I click on Delegate inside when using Delegate from outside,
   or not?
- what should I fill in as next-hop address?
- what does "dotted-decimal notation" mean with IPv6 addresses?
(these are examples from existing consumer equipment for in-house)

Little chances are there that parents will ask whether to use BGP or 
OSPF or please design a protocol for me. (haven't seen these options on 
consumer equipment GUIs).

> I know people that have BGP routing with PI space at home, but the fact
> that it's "at home" does not make it a *homenet*.

I agree.

Alex

>
> Gert Doering
>          -- NetMaster
>