Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
B
babeld
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
babeld
Commits
21148a84
Commit
21148a84
authored
Nov 19, 2007
by
Juliusz Chroboczek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tweaks to the protocol spec.
parent
6fa22d7b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
11 deletions
+16
-11
babel.text
babel.text
+16
-11
No files found.
babel.text
View file @
21148a84
...
...
@@ -38,22 +38,23 @@ will interoperate reliably.
2. Protocol operation
Every Babel speaker has a router id, which is an arbitrary string of 16
bytes that MUST be unique across the routing domain. A simple choice is to
use one of the speaker's IPv6 addresses as the router id; the encoding of
some messages is more efficient when this is indeed the case.
bytes that MUST be unique across the routing domain. A natural choice is
to use one of the speaker's global IPv6 addresses as the router id; the
encoding of some messages is slightly more efficient when this is indeed
the case.
2.1 Message emission and reception
Babel speakers exchange Babel protocol messages. One or more Babel
messages are appended to form a Babel packet, which is sent as a UDP
datagram.
datagram
over IPv6
.
The source address of a Babel packet is always a link-local unicast
The source address of a Babel packet is always a link-local unicast
IPv6
address; a Babel speaker MUST silently discard any packets whose source
address is not a unicast link-local address. Babel packets may be sent to
a well-known link-local multicast address (this is the usual case) or
a link-local unicast address.
to
a link-local unicast address.
With the exception of Hello messages, all Babel messages can be sent either
in unicast and multicast packets, and their semantics does not depend on
...
...
@@ -246,17 +247,21 @@ source table entry is updated according to the following rules:
- if metric' is infinite, then nothing is done;
- if seqno' > seqno, then seqno := seqno', metric := metric', and the
garbage collection timer for the entry is reset
;
garbage collection timer for the entry is reset;
- if seqno' = seqno and metric < metric', then seqno := seqno',
metric := metric', and the garbage collection timer for the entry is
reset;
- otherwise, the garbage collection timer for the entry is reset.
An entry in the table of sources is purged when its garbage collection
timer hasn't been reset for 200 seconds.
An update (id, prefix, seqno', metric') received from a neighbouring node
is feasible when either metric' is infinite, or (seqno', metric') is
strictly smaller than the reference distance of (id, prefix). In other
words, an update (id, prefix, seqno', metric') is feasible when one of the
following conditions is true:
(Section 2.3.2) is feasible when either metric' is infinite, or
(seqno', metric') is strictly smaller than the reference distance of (id,
prefix). In other words, an update (id, prefix, seqno', metric') is
f
easible when one of the f
ollowing conditions is true:
- no entry exists in the source table for (id, prefix); or
- metric' is infinite; or
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment