Re: [v6ops] "Getting IPv6 Private Addressing Right" AusNOG presentation

[Alexandre Petrescu <[e-mail]>]

Le 17/09/2019 à 14:55, Gert Doering a écrit :
> Hi,
> 
> On Tue, Sep 17, 2019 at 01:56:29PM +0200, Alexandre Petrescu wrote:
>> 64share can not share a /64 to more than one ingress interfaces, as an
>> IoT Router, or a CPE, needs.
> 
> You can share the /64 to as many interfaces as you want.

One can share a /64 to several interfaces as long as they are of same 
technology, so they could be bridged.

One could share a /64 from upstream to an Ethernet and a WiFi downstream 
because these two latter are both using same LLC and can be bridged.

One cant share such a /64 to a downstream WiFi and a downstream 
802.11-OCB because they are not precisely the same LLC, and they cant be 
bridged.  (same problem with downstream Ethernet and Bluetooth, Ethernet 
and USB, and many others).

My IoT Router I deployed in a traffic lights controller has this problem.

> Is "having a larger prefix that you can segment and route" *nicer*?  Yes,
> certainly, but that doesn't preclude other approaches from working.

It is indeed an aspect of being nicer.

But there are also places where simply 64share cant work:
- an IoT Router with unbridgeable downstream interfaces.
- an IoT Router with other routers further downstream.  My IoT Router I 
deployed in several cars has this problem.

Alex