On 06/03/2015 09:19, Acee Lindem (acee) wrote: > > > On 3/5/15, 2:46 PM, "Juliusz Chroboczek" <[email protected]> > wrote: > >>> Or more generally, how does a stub router know that it's a stub router, >>> when there is no human to tell it so? >> >> Yeah, it's not very clear. We were actually asked to describe the two >> protocols' support for stub networks, and nobody never told us which of >> the many definitions of stub network they meant, let alone describing the >> use case precisely. (The document uses the same definition as Cisco's >> EIGRP documentation, in case you're interested.) >> >> I'm imagining a dedicated device that has both a WiFi interface and >> a low-power interface that acts as a gateway between the Homenet network >> and the sensor network. Such a device would come from the factory with >> the low power interface configured as a stub. > > It is my understanding that this is the use case for auto-configured stub > routers as well. They are constrained devices that are only capable acting > as a stub router.
Yes, the idea that this an intrinsic property of certain devices makes sense to me. If I buy a home climate control system that includes a router to connect it to the rest of the homenet, it can "know" that it's a stub router out of the box. What doesn't work for me is any suggestion that somebody needs to configure this, because in 99% of homes that isn't going to happen. The text in the draft could be a bit clearer on this point. Thanks Brian _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
