[manet] Re: OLSRv2 draft

Juliusz Chroboczek <[email protected]>
Newsgroups gmane.ietf.manet
Message-ID <[email protected]>
> However it does motivate it by noting that in a very specific scenario
> this message is needed. That scenario is one where routers only arrive
> and depart. As such the case you provide is outside that scenario, and
> doesn’t consider it.

Ok, then let's add a new router Z:

       4
    A-----C
    |     |
    |     |
  1 |     | 1
    |     |
    |     |
    B-----Z
       1

A is going A-B-Z-C, B is going B-Z-C.  Router Z leaves the network,
B reroutes through A, the TC that B sends to A gets lost, and you've got
a persistent routing loop.

I know of two ways to solve the problem:

  - send periodic TCs, as in OLSR(v2);
  - use reliable flooding for distributing topolgy, as in OSPF and IS-IS.

If you have a novel solution, then I'm very much interested.

-- Juliusz

_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.