Re: [Roll] do we need a dominating set?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Roll] do we need a dominating set?



Hi Matteo:

An orphan can issue a DIS, and that could trigger nodes to switch back
to hosts.
Non orphan becoming orphan would keep sending packets along the previous
sequence.

Upon that, the node that turned off routing might either poison so the
child becomes orphan, 
or switch back to routing with the new sequence.

To be designed :)

Pascal

>-----Original Message-----
>From: Matteo Paris [mailto:matteo at ember.com]
>Sent: mardi 17 novembre 2009 17:10
>To: Pascal Thubert (pthubert); roll at ietf.org
>Subject: Re: [Roll] do we need a dominating set?
>
>
>Hi Pascal,
>
>>  Each time a new sequence is spread, nodes are entitled to reassess
>>  their need to be a router. When the sequence spreads, a form of
>>  trickle could be used to decide Not TO advertise self as a router
>>  and act as a host for the new sequence. Like if enough neighbor
>>  routers advertise the new sequence before T elapse, then there
>>  might be no need for self to act as a router.
>>
>>  Thoughts?
>
>It is a nice idea and seems like it would work well in a network of
>uniform density, so that the k-connectivity of the associated graph
>is high.  My concern is for the case when the graph contains a
>cut-vertex.  If the node at the cut-vertex hears many DIOs and
>decides not to be a router, the graph becomes disconnected.
>
>Can this issue be avoided without requiring a lot of computational
resources?
>
>Matteo

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.