Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Juliusz Chroboczek
 A new *incompatible* version of Babels is available.  It is incompatible
 because we have changed the Source Specific Update TLV's format.

Matthieu, I cannot find the Source Omitted field any longer.  Did you
remove it?

-- Juliusz


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Matthieu Boutier
 Matthieu, I cannot find the Source Omitted field any longer.  Did you
 remove it?

Yes, it's not a mistake.  The Idea is that you will sort your TLVs by
lexicographic (dst, src) in a Babel packet.

Usually, the source prefix will not begin the same than the destination
prefix cached:

  - external destinations are for addresses in our prefix, so in a different
prefix,

  - destinations in our local network are probably /128 which are not
source specific.

In both case, we will change the source prefix.  Now, consider we re-add both
a flag field, and a src-prefix field, to memorize the source prefix, and
consider we have 2 (or more) source prefix.  Since we have sorted the
message by lexicographic (dst, src), we will have, for example:

(d1, s1)
(d1, s2)
(d2, s1)
(d2, s2)

and anyway, you will be obliged to rewrite the prefix.  Now, if you believe
it's important to rethink things and have a more memory efficient protocol,
perhaps having a dictionary TLV with, as you explain me (or more precisely
what I understood), with all current TLVs redefined as sub-TLVs... (probably
isn't it the time for that.)

Matthieu


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Matthieu Boutier
 Suppose my network has prefixes 2001:bad:c0ff:ee::/64 and 2001:0dd:f00d:1/64.
 Then I'll see:
 
 1. 64 routes towards both prefixes, typically /128;
 2. default routes from both /64.
 
 If I place the source-specific after the right /128, I can compress the
 source prefix.

so you earn 14 bytes in one packet... (?)

Matthieu


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Juliusz Chroboczek
 If I place the source-specific after the right /128, I can compress the
 source prefix.

 so you earn 14 bytes in one packet... (?)

 Hmm... you may have a point.

Ok, I'm now convinced you're right.

I haven't looked at the latest version of your code yet, but if the packet
parser is not too horrible, we might want to freeze this version of the
packet format.  Let's discuss it on Monday.

-- Juliusz

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


[Babel-users] ANNOUNCE: important babels update.

2014-07-04 Thread Matthieu Boutier
Dear all,

A new *incompatible* version of Babels is available.  It is incompatible because
we have changed the Source Specific Update TLV's format.

The source-sensitive branch of my public repositories has been forced-updated.
All branches are rebased on the 1.5.1 version.  Please update all your routers
with the new version.

   git clone -b source-specific 
git://git.wifi.pps.univ-paris-diderot.fr/babels.git
   http://git.wifi.pps.univ-paris-diderot.fr/?p=babels.git
   https://github.com/boutier/babeld

Note the babels openwrt's package targets my source-specific branch : your
should be able to compile it directly after updating your sources.

If you see Couldn't parse packet messages, it is probably that some of your
routers are not updated.

Have fun !

Matthieu


___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-04 Thread Juliusz Chroboczek
 A new *incompatible* version of Babels is available.  It is incompatible
 because we have changed the Source Specific Update TLV's format.

Note that we've not frozen the packet format yet -- we reserve the right
to break your routers again, just to be annoying.  However, we've started
documenting the protocol -- our WIP is on:

  
http://www.pps.univ-paris-diderot.fr/~jch/software/babel/draft-boutier-babel-source-sensitive.html

-- Juliusz

___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users