1 - 2 - 3 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W - X
version
Click on the red underlined text to get to the source
... ______________________________________
(Figure not included in text version.)
Figure 1: Network ...
... ______________________________________
(Figure not included in text version.)
Figure 2: A sample Autonomous System ...
... __________________________________________
(Figures not included in text version.)
Figure 3: The resulting directed graph
...
... ______________________________________
(Figure not included in text version.)
Figure 5: The SPF ...
... __________________________________________
(Figure not included in text version.)
Figure 6: A sample OSPF ...
... ______________________________________
(Figure not included in text version.)
Figure 7: Area 1's Database ...
... _______________________________________
(Figure not included in text version.)
Figure 9: Router ...
...
consult Section A.3.1:
Version #
Set to 2, the version number of the protocol as documented in this
...
...
Version #
Set to 2, the version number of the protocol as documented in this
specification.
...
... ______________________________________
(Figure not included in text version.)
Figure 10: The graph of adjacencies
...
... do not, the packet should be discarded:
o The version number field must specify protocol version 2.
...
... _____________________________________________________
(Figures not included in text version.)
Figure 12: Neighbor ...
... ________________________________________
(Figure not included in text version.)
Figure 14: An adjacency bring-up example
...
... _________________________________________
(Figure not included in text version.)
Figure 15: Area 1 with IP addresses ...
... ______________________________________
(Figure not included in text version.)
Figure 17: Resolving virtual next hops ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | Type | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version #
The OSPF version number ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | 1 | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | 2 | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | 3 | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | 4 | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version # | 5 | Packet length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID ...
... F. Version 1 differences ...
...
This section documents the changes between OSPF version 1 and OSPF
version 2. The impetus for these changes derives from comments received
on RFC 1131(-> 1247(-> 1583(-> 2178(-> 2328std54)))) ...
... This section documents the changes between OSPF version 1 and OSPF
version 2. The impetus for these changes derives from comments received
on RFC 1131(-> 1247(-> 1583(-> 2178(-> 2328std54)))) and recent field experience with the OSPF protocol ...
... backward-compatible. For that
reason, OSPF version 1 will not interoperate with OSPF version 2.
However, the changes are small in scope and should not greatly affect
...
... reason, OSPF version 1 will not interoperate with OSPF version 2.
However, the changes are small in scope and should not greatly affect
any existing implementations. In addition, some of the proposed changes
...
... TOS may prove costly, both in terms of memory and processor
resources. For this reason, version 2 allows the system administrator
to configure routers ...
...
In some cases, version 1 of the OSPF specification will introduce
extra-hops when calculating routes to external destinations ...
...
The LS sequence number space has been changed from version 1's lollipop
shape to a linear sequence space (Section 12.1.6). Sequence numbers
...
...
Version 1 of the OSPF omitted the handling of a special case in the
flooding procedure: the reception of a MaxAge advertisement that has no
...
...
When summarizing information into a virtual link's transit area, version
2 of the OSPF specification prohibits the collapsing of multiple
backbone ...
...
OSPF Version 2 eases the restrictions on the sending of Link State
Request packets. Link State ...
... have been exchanged. This enables a more efficient use of a router's
memory resources; an OSPF version 2 implementation may limit the size of
the neighbor Link state ...
... Database Description process with the neighbor. In OSPF version 1,
the neighbor event BadLSReq erroneously did not restart ...
... routers that disregard the limit on self-originated
advertisements (already present in OSPF version 1) of one origination
every MinLSInterval seconds. For more information, see Section 13.
...
... TOS in its link state advertisements has been
redefined in version 2. OSPF's encoding of the Delay (D), Throughput ...