I've just changed the local interface protocol.

First, there is now an initial message.  This is just

  BABEL 0.0

0.0 is the protocol version, and is followed by a list of tokens,
currently empty.

Second, every message contains a unique identifier for the object it
describes.  For example,

  add neighbour 805f7a0 id 2001:660:3301:8063:218:f3ff:fea9:914e address 
fe80::7c47:b5aa:4669:ac6d if alpha reach e000 rxcost 96 txcost 96 cost 96

which states that this neighbour is uniquely identified by the string
805f7a0.  This string does not need to be unique across time, but at
a given moment it is unique -- in other words, in the time between
``add neighbour foo'' and ``flush neighbour foo'', the string ``foo''
will only identify this particular neighbour.

The unique identifiers should be treated as opaque tokens, and are
suitable for using as keys in a hash table.

                                        Juliusz

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

Reply via email to