Re: [homenet] multiple routers vs IoT

2019-04-03 Thread Michael Richardson

Tim Coote  wrote:
> On 2 Apr 2019, at 17:04, Michael Richardson 
> wrote:

mcr> The way for multiple routers in the house is to recognize that the IoT
mcr> gateway is the second router. It's not a second uplink.

mcr> So there are in fact three situations:

mcr> 1) multiple uplinks. (rare at this point, we all agree, partly I think
mcr> because it's hard to do)

mcr> 2) multiple routers. (rather common, often by mistake) 3) IoT routers
mcr> (usually on purpose)

> By ‘IoT router’, do you mean nodes providing the routing to 6LoWPAN 
network
> (s) running over various protocols, the router that links IoT nodes to the
> internet, or something else such as incorporating sensors/actuators that 
are
> powered and use wifi as the network protocol?

I mean the gateway between 6lowpan and the home network (whether it's wifi or
wired).  That node likely also links them to the Internet (is appropriate,
ULA otherwise).

sensors/actuators with power and Wifi (and probably an marriage to a cloud
service) are "Web Enabled Devices", not IoT :-)

--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-





signature.asc
Description: PGP signature
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet


Re: [homenet] wifi broadcast domain - Mikael Abrahamsson's comments

2019-04-03 Thread Juliusz Chroboczek
>> If there is a more complex HNCP network, then we could probably simulate
>> the L2 scenario with VXLAN, configured by HNCP.

> If memory serves, VXLAN requires support for multicast, which HNCP+Babel
> doesn't provide.  There's a set of IBM (?) extensions to VXLAN that avoid
> the use of multicast, I'm not a fan.

Another issue is that since VXLAN emulates a layer 2 network, it doesn't
have any means to regulate MTU; hence, it requires either network-layer
fragmentation or the use of jumbograms.

Not a fan, sorry.

-- Juliusz

___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet


Re: [homenet] wifi broadcast domain - Mikael Abrahamsson's comments

2019-04-03 Thread Juliusz Chroboczek
> If there is a more complex HNCP network, then we could probably simulate
> the L2 scenario with VXLAN, configured by HNCP.

If memory serves, VXLAN requires support for multicast, which HNCP+Babel
doesn't provide.  There's a set of IBM (?) extensions to VXLAN that avoid
the use of multicast, I'm not a fan.

-- Juliusz

___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet