IETF Logo Mail Archive

Re: [Iotops] Automatically connecting to stub networks...

Michael Richardson <mcr@sandelman.ca> Fri, 04 December 2020 13:42 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01C443A0CE3; Fri, 4 Dec 2020 05:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fYTH-zD9LnMh; Fri, 4 Dec 2020 05:42:11 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F84B3A0CD9; Fri, 4 Dec 2020 05:42:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3A80A389C7; Fri, 4 Dec 2020 08:44:05 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cNS1wbLMb1lQ; Fri, 4 Dec 2020 08:44:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C37A3389C1; Fri, 4 Dec 2020 08:44:00 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CBB625DE; Fri, 4 Dec 2020 08:42:04 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
cc: ipv6@ietf.org, iotops@ietf.org
In-Reply-To: <m1kl8gf-0000EWC@stereo.hq.phicoh.net>
References: <695953.1606952552@dooku> <B989299A-ED3C-4205-A4E2-DA080F574B33@fugue.com> <20201203174901.GW44833@faui48f.informatik.uni-erlangen.de> <36EA3F9D-A79D-4BC0-B894-54B7D3054476@fugue.com> <20201204064930.GY44833@faui48f.informatik.uni-erlangen.de> <B9DC56CD-E2A7-469C-9E8F-596554DA1A80@employees.org> <20201204085738.GZ44833@faui48f.informatik.uni-erlangen.de> <m1kl8gf-0000EWC@stereo.hq.phicoh.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17100.1607089324.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 Dec 2020 08:42:04 -0500
Message-ID: <17101.1607089324@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/bjAx196eZKejyLHzyZLC8QpCGHM>
Subject: Re: [Iotops] Automatically connecting to stub networks...
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2020 13:42:14 -0000

Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com> wrote:
    > Indeed. We need to have a model where there can be a 'core network' that
    > either runs HNCP/Babel in the case of homes, small business or OSPF (or equiv)
    > and static configuration in the case of entrerprise.

    > Attached to those core routers are small trees that do not run a routing
    > protocol, but use a hierarchical mechanism to obtain prefixes.

    > A core router should provide the root of each tree with as many /64s as is
    > needed to number the tree.

In essence, this describes ISPs today, with the customers are the "small trees"

    > We currently have a mechanisms for the hierarchical part, which is DHCPv6 PD.
    > It is far from ideal, but we can try to specify how it should be deployed.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email