[Babel-users] Source-sensitive packet's format

[Dave Taht]

I do not mind if you break backward wire compatibility against
existing versions of babels, but do it soon, please, and warn people.
My users are
pretty tolerant of breakage, so long as they are warned....

I would not mind a shim of some sort protecting against older babels's
format and newer...

but switching to a new TLV number for the newer flag-less format and
sending warnings for receipt of the old ("old style babels packet
received, please update babel on that machine") seems most comforting
to me.

(I'm allergic to the number 13, anyway)



On Tue, Jul 1, 2014 at 10:40 AM, Juliusz Chroboczek
<jch at pps.univ-paris-diderot.fr> wrote:
>> What I'm suggesting is a little weaker.  There's still compression, but
>> only non-specific updates can set the prefix.  (It shouldn't matter much
>> in practice, though, I expect most SS-updates to be for the default
>> route.)
>>
>> Not sure what to do about compression for source prefixes.
>
> After thinking it over some more, removing the flags field looks like the
> right solution.  Compression is still allowed, you're just no longer
> allowed to set the compression state in source-specific updates.
>
> I think that the ordering for updates should consider the prefix with the
> longer plen for source-specific updates, and for the same prefix put
> non-specific before source-specific.  This should give reasonable compression.
>
> -- Juliusz
>
> _______________________________________________
> Babel-users mailing list
> Babel-users at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article