Re: Automatically connecting to stub networks...

otroan@employees.org Thu, 03 December 2020 21:19 UTC

Return-Path: <otroan@employees.org>
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 B32803A0CCF for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 13:19:04 -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 iBQ06PDX96ML for <ipv6@ietfa.amsl.com>; Thu, 3 Dec 2020 13:19:03 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B3CF3A0CD2 for <ipv6@ietf.org>; Thu, 3 Dec 2020 13:18:59 -0800 (PST)
Received: from astfgl.hanazo.no (unknown [IPv6:2001:420:c0c1:81:182a:5255:be67:ac11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 6C0484E11B08; Thu, 3 Dec 2020 21:18:59 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 8587146CFA0C; Thu, 3 Dec 2020 22:18:56 +0100 (CET)
From: otroan@employees.org
Message-Id: <A59E0AB3-72DD-469C-8085-35F6DF8178F5@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_65A8284B-3346-40DA-B0BB-5D66A154FCD2"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: Automatically connecting to stub networks...
Date: Thu, 03 Dec 2020 22:18:55 +0100
In-Reply-To: <m1kkvrC-0000DtC@stereo.hq.phicoh.net>
Cc: 6man WG <ipv6@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
To: Philip Homburg <pch-ipv6-ietf-7@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> <6450.1607022122@localhost> <m1kkvrC-0000DtC@stereo.hq.phicoh.net>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FiwB8jwJn3uqTlByY5bXfMK7X1w>
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:19:05 -0000

>> What else is there?
>> It's true that the DHCPv6-RELAY stuff is a mess for PD, but there shouldn't
>> be any DHCPv6-relaying in a home.
> 
> I think there should be. I.e., if you have one router that is DHCPv6 server
> for the entire home network, then all other router should have a
> relay on their downstream networks.
> 
> i.e., I assume that a relay is easier to implement than a downstream
> dhcp server that has to get additional prefixes from upstream.

No need to rehash this, we have rehased this a few times before.

https://mailarchive.ietf.org/arch/msg/homenet/T_6Y9nooYQVm8TNolie46FBBtnk/

Cheers,
Ole