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

[Ted Lemon <[e-mail]>]

If we were to stack PD, that would not be a stub network, although I think it’s an interesting increment. But the way to do it is with DHCPv6 relays on the (no longer) stub routers. Otherwise you have a tree balancing problem that’s totally unnecessary. And you still need Babel or OSPF or something to manage routing.

I’d be happy to have a co-author, if you are interested, Michael. :)

> On Dec 3, 2020, at 1:51 PM, Michael Richardson <[e-mail]> wrote:
> 
> 
> Toerless Eckert <[e-mail]> wrote:
>> - For example: Why not simply start with DHCP-PD ? IMHO, every home router getting
>> a prefix via DHCP-PD from a service provider is a provider of such a stub network.
>> Of course, service discovery as you expect does usually not work in that environment,
>> so that would need to be added.
> 
> While there is a CableLabs spec that argues for stacked DHCPv6-PD (and it was
> presented in Homenet a few years back), to date, I'm aware of no deployed
> home routers that operate a DHCPv6-PD server on their southbound interface.
> 
> Conceptually it's simple to implement.
> Architecturally there are some who thinks it is gross, and some who think
> it's brilliant.   I'm still sitting on the fence myself.
> 
> But, fundamentally, the issue Ted is trying to address is enabling
> communications within the Home between layer-2s that can not, or should not,
> be bridged.
> 
> I agree with your other suggestions for re-organization.
> I have some ideas about how I would write this document.
> 
> --
> Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
>