IETF Logo Mail Archive

Re: Automatically connecting to stub networks...

Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com> Thu, 03 December 2020 21:02 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 092773A0C94 for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 13:02:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=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 ikb7_apWV19r for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 13:02:30 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B9C53A0C9A for <ipv6@ietf.org>; Thu, 3 Dec 2020 13:02:28 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kkvk7-0000FOC; Thu, 3 Dec 2020 22:02:23 +0100
Message-Id: <m1kkvk7-0000FOC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Automatically connecting to stub networks...
From: Philip Homburg <pch-ipv6-ietf-7@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <DA9CEF7E-44EA-44B0-AF07-2DAC4D29A59F@fugue.com> <59aeb842c7534e5ab24cde0426b5a4c9@huawei.com> <22203.1607003159@localhost> <5143DC1F-321C-4FCD-9B56-372E492D4CDD@fugue.com> <30146.1607019913@localhost> <BFEE2BEA-D4C0-44AC-95D2-EB413CA6E3BE@fugue.com>
In-reply-to: Your message of "Thu, 3 Dec 2020 13:36:28 -0500 ." <BFEE2BEA-D4C0-44AC-95D2-EB413CA6E3BE@fugue.com>
Date: Thu, 03 Dec 2020 22:02:20 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ywW9_jZPUwg1a_3JfYoMFvYNY6A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 21:02:32 -0000

>    Not quite. We still need to advertise reachability to the prefix,
>    and do all the work to set up numbering on the local link. Assume
>    no management, and an arbitrary number of stub routers potentially
>    connecting to an 802.15.4 mesh. How does DHCPv6-PD even work in
>    this scenario? I'm not saying it can't, but it's not "just do
>    DHCPv6-PD"!

If the network has a tree structure and DHCPv6-PD is done through a series
of relays then the DHCP server and each of the relays could install a
forwarding path for the delegated prefix. No need for any routing protocol.

v2.23.0 | Report a Bug | By Email