On 3/5/15, 2:46 PM, "Juliusz Chroboczek" <j...@pps.univ-paris-diderot.fr> 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. Thanks, Acee > >-- Juliusz > > >_______________________________________________ >homenet mailing list >homenet@ietf.org >https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
