Revision 725270cb nest/proto.sgml

View differences:

nest/proto.sgml
8 8

  
9 9
<sect1>Introduction
10 10

  
11
<p>The routing protocols are the BIRD's heart and a fine amount of code
11
<p>The routing protocols are the bird's heart and a fine amount of code
12 12
is dedicated to their management and for providing support functions to them.
13 13
(-: Actually, this is the reason why the directory with sources of the core
14 14
code is called <tt/nest/ :-).
15 15

  
16 16
<p>When talking about protocols, one need to distinguish between <em/protocols/
17 17
and protocol <em/instances/. A protocol exists exactly once, not depending on whether
18
it's configured on not and it can have an arbitrary number of instances corresponding
18
it's configured or not and it can have an arbitrary number of instances corresponding
19 19
to its "incarnations" requested by the configuration file. Each instance is completely
20 20
autonomous, has its own configuration, its own status, its own set of routes and its
21 21
own set of interfaces it works on.
......
49 49
state machine and a core state machine.
50 50

  
51 51
<p>The <em/protocol state machine/ corresponds to internal state of the protocol
52
and the protocol can alter its state whenever it wants to. There exist
52
and the protocol can alter its state whenever it wants to. There are
53 53
the following states:
54 54

  
55 55
<descrip>
......
73 73
The states are traversed according to changes of the protocol state machine, but
74 74
sometimes the transitions are delayed if the core needs to finish some actions
75 75
(for example sending of new routes to the protocol) before proceeding to the
76
new state. There exist the following core states:
76
new state. There are the following core states:
77 77

  
78 78
<descrip>
79 79
	<tag/FS_HUNGRY/ The protocol is down, it doesn't have any routes and

Also available in: Unified diff