<div dir="auto">Is HNCP available for the various Linux distros?<div dir="auto">If not, it has to be PD, I think.<br><br><div data-smartmail="gmail_signature" dir="auto">Regards,<br> Brian Carpenter<br> (via tiny screen & keyboard)</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 28 Jun 2021, 20:51 Ole Troan, <<a href="mailto:otroan@employees.org">otroan@employees.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On 27 Jun 2021, at 23:07, Brian E Carpenter <<a href="mailto:brian.e.carpenter@gmail.com" target="_blank" rel="noreferrer">brian.e.carpenter@gmail.com</a>> wrote:<br>
> <br>
> That doesn't work. B needs to get its own /64 prefix(es) from A via DHCPv6-PD (<a href="https://www.rfc-editor.org/info/rfc8415" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc8415</a>). That's what DHCPv6-PD is for. So A will indeed need to be a DHCPv6 server on its downstream interfaces.<br>
<br>
To the extent it matters, it’s not what DHCP PD was designed for.<br>
<br>
HNCP does internal prefix assignment in a network. <br>
<br>
Now, if you were to use DHCP PD for this, I would recommend a single PD server in the network (on A). DHCP PD clients on all internal routers. Either DHCP relays or more simply each internal router PD client configured with the address of the PD server directly. Then an IGP to advertise prefixes. <br>
<br>
The PD clients should request individual /64s for each of their downstream interfaces. <br>
<br>
This scheme does not work great in networks with loops or multiple routers on a link. If using DHCP relays you manually have to make a spanning tree.<br>
And you risk links being assigned multiple prefixes. <br>
<br>
HNCP solves all of this. <br>
<br>
Cheers <br>
Ole</blockquote></div>