26 Mar
2016
26 Mar
'16
10:26 p.m.
All,
I considered that since we:
- have a full mesh
- and all those who use RIP44 will have a TRUE copy of all routes
Perhaps consider ways that RIP44 could be updated:
- to bootstrap one another in the case of a failure of AMPRGW (election
of a master to send RIP44 announcements, participation in elections
disabled by default)
- allow possibility for addition of routes while 'acting AMPRGW' is
offline (re-elections with time-stamping/flagging)?
- ability to resume normal operations (AMPRGW is automatically
elected/flagged/timestamps-recognized as master/signals send end of
elections)
Ideas?
- KB3VWG