How many of these goals can be reached without changing the packet
format? I've implemented regenerating lost OGMs without changing the
protocol to a degree it needs to bump the version number. Does
removing the averaging of TQ from remote neighbors change the message
We were discussing about including local Hello messages in the design, so
there will be a additional packet type. Hmm.
Maybe we could go without breaking backward compatibility. On the other hand -
why should we not break backward compatibility when we introduce a new
generation of the protocol? Running old and new together may introduce
'interesting' side effects and we'll eventually find ourself debugging
incompatibility problems when trying to trace bugs in the new protocol
version. Hence we have decided to add a compatibility version number in the
packets at a very early stage of the project.
Regarding a open posting list - what would be a possible migration scenario
for a new list hosted at sourceware et al, given that we have an existing list
with a number of subscribers?