0% found this document useful (0 votes)

26 views158 pages

OSPFV3 Extended Results PDF

This document is an RFC compliance test report for OSPFv3 results across multiple FreeBSD and Ubuntu releases from 2.0.2 to 8.2.2. It tests implementations against RFC standards and documents whether they pass, fail or were not tested for various MUST requirements. Overall it evaluates conformance of OSPFv3 protocol implementations over time and across operating systems.

Uploaded by

Abhishek garg

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

26 views158 pages

OSPFV3 Extended Results PDF

Uploaded by

Abhishek garg

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 158

RFC Compliance Test Report

OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

Type FRR FRR FRR FRR FRR FRR FRR FRR FRR FRR FRR

Commit ID 36a7e78 5dff4ec 7a377a1 85f25d8 33e56da 056c0cd 23db048 c0038fc 13a8efb 9931db7 79188bf

Commit Date 2017-11-08 2018-01-09 2018-03-12 2018-07-05 2019-05-09 2019-05-13 2019-06-18 2020-02-14 2021-02-27 2021-07-21 2022-03-13

ANVL- RFC 5340, s2.4 p6

OSPFV3-1.1 Explicit support for multiple instances per link

MUST Explicit Support for Multiple Instances per Link

OSPF now supports the ability to run multiple OSPF protocol
instances on a single link.
(This test is for single instance of OSPFv3 daemon on a link)

FreeBSD FreeBSD FreeBSD FreeBSD FreeBSD 10.3: FreeBSD 10.3: FreeBSD 10.3: FreeBSD 10.3: FreeBSD 10.3: FreeBSD 10.3: FreeBSD 10.3:
untested untested untested untested untested untested untested
10.3: pass 10.3: pass 10.3: pass 10.3: pass

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu
16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass

FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD FreeBSD FreeBSD FreeBSD FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0:
untested untested untested untested untested untested untested
12.0: pass 12.0: pass 12.0: pass 12.0: pass

FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD FreeBSD
untested untested untested untested untested untested untested untested untested
12.2: pass 12.2: pass

ANVL- RFC 5340, s2.5 p7 Use of link-local addresses

OSPFV3-2.1
Use of Link-Local Addresses
MUST On all OSPF interfaces except virtual links, OSPF packets are sent
using the interface"s associated link-local unicast address as
source

Test Report created at 2022-03-22 13:39:59 UTC Page 1 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s2.5 p7 Use of Link-Local Addresses

OSPFV3-2.3
Use of Link-Local Addresses
MUST On virtual links, a global scope IPv6 address MUST be used as the
source address for OSPF protocol packets.

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL

ANVL- RFC 5340, s2.5 p7 Use of link-local addresses

OSPFV3-2.4
Use of Link-Local Addresses
MUST Link-local addresses appear in OSPF Link-LSAs

FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD FreeBSD FreeBSD FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0:
untested untested untested untested unpredict untested untested untested
12.0: pass 12.0: pass 12.0: pass

Test Report created at 2022-03-22 13:39:59 UTC Page 2 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s2.5 p7 Use of Link-Local Addresses

OSPFV3-2.5
Use of Link-Local Addresses
MUST link-local addresses MUST NOT be advertised in
inter-area-prefix-LSAs, AS-external-LSAs or intra-area-prefix-LSAs

ANVL- RFC 5340, s2.7 p8 Packet format changes

OSPFV3-3.1
Packet Format Changes
MUST The OSPF version number has been incremented from 2 to 3

Test Report created at 2022-03-22 13:39:59 UTC Page 3 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s2.7 p8 Packet format changes

OSPFV3-3.2
Packet Format Changes
MUST The Hello packet now contains no address information at all. Rather,
it now includes an Interface ID that the originating router has assigned
to uniquely identify (among its own interfaces) its interface to
the link

ANVL- RFC 5340, s2.7 p8 Packet format changes

OSPFV3-3.3
Packet Format Changes
MUST This Interface ID will be used as the network-LSA"s Link State ID
if the router becomes the Designated Router on the link.

Test Report created at 2022-03-22 13:39:59 UTC Page 4 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s2.7 p8 Packet format changes

OSPFV3-3.4
Packet Format Changes
MUST If the R-bit is clear, an OSPF speaker can participate in
OSPF topology distribution without being used to forward
transit traffic; this can be used in multi-homed hosts that
want to participate in the routing protocol

ANVL- RFC 5340 s2.9 p10 Handling Unknown LSA Types

OSPFV3-3.5 RFC 5340 sA.4.2.1 p72 LS type

MUST Packet Format Changes

Handling of unknown LSA types has been made more flexible so that,
based on LS type, unknown LSA types are either treated as having
link-local flooding scope, or are stored and flooded as if they
were understood
0 Treat the LSA as if it had link-local flooding scope
(Test for Link-local flooding scope)

Test Report created at 2022-03-22 13:39:59 UTC Page 5 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340 s2.9 p10 Handling Unknown LSA Types

OSPFV3-3.6 RFC 5340 sA.4.2.1 p72 LS type

MUST Packet Format Changes

Handling of unknown LSA types has been made more flexible so that,
based on LS type, unknown LSA types are either treated as having
link-local flooding scope, or are stored and flooded as if they
were understood
1 Store and flood the LSA, as if type understood
(Test for Area-flooding scope)

ANVL- RFC 5340 s3.4 p12 Stub Area Unknown LSA Flooding Restriction Deprecated
OSPFV3-4.1 RFC 5340 sA.4.2.1 p72 LS type

MUST Handling Unknown LSA Types

an LSA whose LS type is unrecognized may only be
flooded into/throughout a stub area if both a) the LSA has
area or link-local flooding scope and b) the LSA has U-bit
set to 0
0 Treat the LSA as if it had link-local flooding scope
(Test for Link-local flooding scope)

Test Report created at 2022-03-22 13:39:59 UTC Page 6 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340 s3.4 p12 Stub Area Unknown LSA Flooding Restriction Deprecated
OSPFV3-4.2 RFC 5340, s4.5.2 p42 Sending Link State Update packets
RFC 5340 sA.4.2.1 p72 LS type
MUST
Handling Unknown LSA Types
an LSA whose LS type is unrecognized may only be
flooded into/throughout a stub area if both a) the LSA has
area or link-local flooding scope and b) the LSA has U-bit
set to 0
Case 2
The LS type is unrecognized and the U-bit in the LS Type is set
to 0 (treat the LSA as if it had link-local flooding scope). In
this case there is a single eligible interface, namely, the
interface on which the LSA was received.
0 Treat the LSA as if it had link-local flooding scope
(This test is for Area-flooding scope)

Test Report created at 2022-03-22 13:39:59 UTC Page 7 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.1 RFC 2328, s4 p40 Functional Summary

MUST Implementation Details

The router sends Hello packets to its neighbors, and in
turn receives their Hello packets.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.2 RFC 2328, s4 p40 Functional Summary

MUST Implementation Details

On broadcast networks, the router dynamically detects its
neighboring routers by sending its Hello packets to the
multicast

Test Report created at 2022-03-22 13:39:59 UTC Page 8 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.4 RFC 2328, s4 p40 Functional Summary

MUST Implementation Details

Link state is also advertised when a router"s state changes.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.5 RFC 2328, s4.3 p43 Routing protocol packets

MUST Implementation Details

Each LSA is tagged with the ID of the originating router
and a checksum of its link state contents.
(This test is for Link-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 9 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.6 RFC 2328, s4.3 p43 Routing protocol packets

MUST Implementation Details

Each LSA is tagged with the ID of the originating router
and a checksum of its link state contents.
(This test is for Network-LSA)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.7 RFC 2328, s4.3 p43 Routing protocol packets

MUST Implementation Details

Each LSA is tagged with the ID of the originating router and a
checksum of its link state contents.
(This test is for Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 10 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.8 RFC 2328, s7.1 p52 The Hello Protocol

MUST Implementation Details

Bidirectional communication is indicated when the router sees
itself listed in the neighbor"s Hello Packet

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.9 RFC 2328, s7.1 p52 The Hello Protocol

MUST Implementation Details

On broadcast netPrefixes, each router advertises itself by
multicasting Hello Packets
(In IPv6, broadcasting has been incorporated into multicating
capability.)

Test Report created at 2022-03-22 13:39:59 UTC Page 11 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.10 RFC 2328, s7.1 p52 The Hello Protocol

MUST Implementation Details

On broadcast netPrefixes, each router advertises itself by
periodically multicasting Hello Packets
(In IPv6, broadcasting has been incorporated into multicating
capability.)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.11 RFC 2328, s7.2 p53 The Synchronization of Databases

MUST Implementation Details

Each router describes its database by sending a sequence
of Database Description packets to its neighbor.
(This is an indirect test which verifies that the DUT
recognizes the LSA headers contained in the Database
Description packets received from ANVL.)

Test Report created at 2022-03-22 13:39:59 UTC Page 12 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.12 RFC 2328, s7.2 p53 The Synchronization of Databases

MUST Implementation Details

When the neighbor sees an LSA that is more recent than its own
database copy, it makes a note that this newer LSA should be
requested.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.13 RFC 2328, s7.2 p53 The Synchronization of Databases

MUST Implementation Details

When the neighbor sees an LSA that is more recent than its own
database copy, it does make a note that this LSA (which is
newer) should be requested.
(This is a negative test)

Test Report created at 2022-03-22 13:39:59 UTC Page 13 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.14 RFC 2328, s7.2 p53 The Synchronization of Databases

MUST Implementation Details

Database Description Packets sent by the master (polls) are
acknowledged by the slave through echoing of the
sequence number

ANVL- NEGATIVE
OSPFV3-6.15 RFC 5340, s4 p13 Implementation details
RFC 2328, s7.2 p53 The Synchronization of Databases
MUST
Implementation Details
Database Description Packets sent by the master (polls) are
acknowledged by the slave through echoing of the sequence number

Test Report created at 2022-03-22 13:39:59 UTC Page 14 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.16 RFC 2328, s7.2 p54 The Synchronization of Databases

MUST Implementation Details

The master is the only one allowed to retransmit Database
Description Packets

ANVL- NEGATIVE
OSPFV3-6.17 RFC 5340, s4 p13 Implementation details
RFC 2328, s7.2 p54 The Synchronization of Databases
MUST
Implementation Details
The master is the only one allowed to retransmit Database
Description Packets

Test Report created at 2022-03-22 13:39:59 UTC Page 15 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.18 RFC 2328, s7.2 p54 The Synchronization of Databases

MUST Implementation Details

Each Database Description contains an indication that there are
more packets to follow --- the M-bit field.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.19 RFC 2328, s7.2 p54 The Synchronization of Databases

MUST Implementation Details

Database Exchange Process is over when a router has
received and sent Database Description Packets with
the M-bit off

Test Report created at 2022-03-22 13:39:59 UTC Page 16 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-6.20 RFC 5340, s4 p13 Implementation details
RFC 2328, s7.2 p54 The Synchronization of Databases
MUST
Implementation Details
Database Exchange Process is over when a router has
received and sent Database Description Packets with
the M-bit off

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.21 RFC 2328, s7.3 p54 The Designated Router

MUST Implementation Details

The Designated Router originates a network-LSA on behalf of the
network.

Test Report created at 2022-03-22 13:39:59 UTC Page 17 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.22 RFC 2328, s7.3 p54 The Designated Router

MUST Implementation Details

If a router is the DR, it does generate a network-LSA
for the network. (This test is with DUT as BDR.)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.23 RFC 2328, s7.3 p54 The Designated Router

MUST Implementation Details

If a router is the DR, it does generate a network-LSA
for the network.
(This test is with DUT as DR-Other)

Test Report created at 2022-03-22 13:39:59 UTC Page 18 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.24 RFC 2328, s7.4 p56 The Backup Designated Router

MUST Implementation Details

Backup Designated Router becomes Designated Router when
the previous Designated Router fails.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.25 RFC 2328, s7.4 p56 The Backup Designated Router

MUST Implementation Details

Each Hello Packet has a field that specifies the Backup
Designated Router for the network.

Test Report created at 2022-03-22 13:39:59 UTC Page 19 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.28 RFC 2328, s9.1 p69 Interface states

MUST Implementation Details

In DR Other state, the router itself has not been selected
Backup Designated Router either. The router forms adjacencies
to both the Designated Router and the Backup Designated Router
(if they exist).

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.29 RFC 2328, s9.1 p69 Interface states

MUST Implementation Details

In Backup state the router establishes adjacencies to all
other routers attached to the network.

Test Report created at 2022-03-22 13:39:59 UTC Page 20 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.30 RFC 2328, s9.1 p69 Interface states

MUST Implementation Details

In DR state Adjacencies are established to all other routers
attached to the network.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.31 RFC 2328, s9.3 p73 The Interface state machine

MUST Implementation Details

When router is in Waiting state, if BackupSeen event occurs
then router calculates the attached network"s Backup Designated
Router and Designated Router

Test Report created at 2022-03-22 13:39:59 UTC Page 21 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-6.32 RFC 2328, s9.3 p73 The Interface state machine

MUST Implementation Details

When router is in Waiting state, if WaitTimer event fires
then router calculates the attached network"s Backup
Designated Router and Designated Router

Ubuntu 16.04: Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu Ubuntu Ubuntu 16.04: Ubuntu Ubuntu Ubuntu Ubuntu
unpredict unpredict unpredict unpredict
16.04: pass 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: pass 16.04: FAIL 16.04: FAIL

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.1 RFC 2328, s9.3 p74 The Interface state machine

MUST More Implementation Details

When NbrChange event fires then router recalculates the
attached network"s Backup Designated Router and Designated
Router

Test Report created at 2022-03-22 13:39:59 UTC Page 22 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.2 RFC 2328, s9.3 p74 The Interface state machine

MUST More Implementation Details

When NbrChange event fires then router recalculates the
attached network"s Backup Designated Router and Designated
Router

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.3 RFC 2328, s9.4 p75 Electing the Designated Router

MUST More Implementation Details

If more than one routers have declared themselves as Backup
designated but not as Designated Router, the one having the
highest Router Priority is declared to be Backup Designated
Router.

Test Report created at 2022-03-22 13:39:59 UTC Page 23 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.4 RFC 2328, s9.4 p75 Electing the Designated Router

MUST More Implementation Details

When selecting a Backup Designated Router among more than one
Routers declaring themselves as Backup Designated Router, if
there is a tie in the Router Priority, the one having highest
Router ID is chosen.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.5 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

If no routers have declared themselves Backup Designated Router,
choose the router having highest Router Priority as Backup
Designated Router.

Test Report created at 2022-03-22 13:39:59 UTC Page 24 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.6 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

If no routers have declared themselves Backup Designated Router,
choose the router having highest Router Priority, again use the
Router ID to break ties. (Verify that Router ID is used to break
Ties).

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.7 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

If one or more of the routers have declared themselves
Designated Router the one having highest Router Priority
is declared to be Designated

Test Report created at 2022-03-22 13:39:59 UTC Page 25 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.8 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

In case of a tie in the router priority among routers
declaring themselves Designated Router, the one having
the highest Router ID is chosen.
(DUT loose the DR election)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.9 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

In case of a tie in the router priority among routers
declaring themselves Designated Router, the one having
the highest Router ID is chosen.
(DUT wins the DR election)

Test Report created at 2022-03-22 13:39:59 UTC Page 26 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.10 RFC 2328, s9.4 p76 Electing the Designated Router

MUST More Implementation Details

If no routers have declared themselves Designated Router,
assign the Designated Router to be the same as the newly
elected Backup Designated Router.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.11 RFC 2328, s10.1 p83 neighbor states

MUST More Implementation Details

After the two routers discover their master/slave status,
the state transitions to Exchange.
(This test checks the case when DUT eventually becomes
master)

Test Report created at 2022-03-22 13:39:59 UTC Page 27 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.12 RFC 2328, s10.1 p83 neighbor states

MUST More Implementation Details

After the two routers discover their master/slave status,
the state transitions to Exchange.
(This test checks the case when DUT eventually becomes
slave)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.13 RFC 2328, s10.1 p86 neighbor states

MUST More Implementation Details

Only one Database Description Packet is allowed outstanding
at any one time. (So when a router is slave it will always
send a Database Description packet with the DD sequence
number same as that of the Database Description packet
received from master.)

Test Report created at 2022-03-22 13:39:59 UTC Page 28 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.14 RFC 2328, s10.1 p86 neighbor states

MUST More Implementation Details

Only one Database Description Packet is allowed outstanding
at any one time. (So when a router is master it will
retransmit a Database Description packet unless slave sends
a Database Description packet echoing the DD sequence
number of the last sent Database Description packet.)

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.17 RFC 2328, s10.3 p91 The neighbor state machine

MUST More Implementation Details

AS-external-LSAs are omitted from the Database summary list if the
area has been configured as a stub area.

Test Report created at 2022-03-22 13:39:59 UTC Page 29 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-7.18 RFC 5340, s4 p13 Implementation details
RFC 2328, s10.3 p91 The neighbor state machine
MUST
More Implementation Details
AS-external-LSAs are omitted from the Database summary list if the
area has been configured as a stub area.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.19 RFC 2328, s10.3 p92 The neighbor state machine

MUST More Implementation Details

When in Exchange state if ExchangeDone event has fired
then if the neighbor Link state request list is not empty,
router transitions to Loading state and starts (or continues)
sending Link State Request packets to the neighbor.

Test Report created at 2022-03-22 13:39:59 UTC Page 30 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.20 RFC 2328, s10.3 p93 The neighbor state machine

MUST More Implementation Details

If the router is in Exchange or greater state and the
neighbor event SeqNumberMismatch has occurred then the
router increments the DD sequence number in the neighbor
data structure.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.21 RFC 2328, s10.3 p93 The neighbor state machine

MUST More Implementation Details

If the router is in Exchange or greater state and the
neighbor event SeqNumberMismatch has occurred then the
router increments the DD sequence number in the
neighbor data structure.
This test is for Loading State.

Test Report created at 2022-03-22 13:39:59 UTC Page 31 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.22 RFC 2328, s10.3 p94 The neighbor state machine

MUST More Implementation Details

The action for event BadLSReq is exactly the same as for the
neighbor event SeqNumberMismatch. The (possibly partially
formed)
adjacency is torn down, and then an attempt is made at
reestablishment.
This test is for Exchange State.

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.23 RFC 2328, s10.3 p94 The neighbor state machine

MUST More Implementation Details

The action for event BadLSReq is exactly the same as for the
neighbor event SeqNumberMismatch. The (possibly partially
formed) adjacency is torn down, and then an attempt is made at
reestablishment.
This test is for Loading State.

Test Report created at 2022-03-22 13:39:59 UTC Page 32 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4 p13 Implementation details

OSPFV3-7.24 RFC 2328, s10.4 p95 Whether to become adjacent

MUST More Implementation Details

On broadcast, all routers become adjacent to both the
Designated Router and the Backup Designated Router.

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.1 RFC 2328, s9 p66 The Interface Data Structure

MUST The Interface Data Structure

The Designated Router is initialized to 0.0.0.0, which
indicates the lack of a Designated Router.

Test Report created at 2022-03-22 13:39:59 UTC Page 33 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.2 RFC 2328, s9 p66 The Interface Data Structure

MUST The Interface Data Structure

The Backup Designated Router is initialized to 0.0.0.0,
indicating the lack of a Backup Designated Router

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.3 RFC 2328, s9 p66 The Interface Data Structure

MUST The Interface Data Structure

RxmtInterval is the number of seconds between Database
Description packet retransmissions.
This tests for Database Description packet retransmission
in ExStart state.

Test Report created at 2022-03-22 13:39:59 UTC Page 34 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.4 RFC 2328, s9 p66 The Interface Data Structure

MUST The Interface Data Structure

RxmtInterval is the number of seconds between Link State
Request packet retransmissions.
This tests for Database Description packet retransmission
in Loading state.

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.5 RFC 2328, s9 p66 The Interface Data Structure

MUST The Interface Data Structure

RxmtInterval is the number of seconds between LSA
retransmissions, for adjacencies belonging to this
interface.

Test Report created at 2022-03-22 13:39:59 UTC Page 35 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.6
The Interface Data Structure
MUST The Interface ID appears in Hello packets sent out the interface,
the link-local-LSA originated by router for the attached link

ANVL- RFC 5340, s4.1.2 p15 The Interface Data structure

OSPFV3-8.7
The Interface Data Structure
MUST The Interface ID appears in Hello packets sent out the interface,
the router-LSA originated by the router-LSA for the associated
area

Test Report created at 2022-03-22 13:39:59 UTC Page 36 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.1.2 p16 The Interface Data structure

OSPFV3-8.8
The Interface Data Structure
MUST A list of IPv6 prefixes can be configured for the attached link.
These will be advertised by the router in link-LSAs

ANVL- RFC 5340, s4.1.2 p16 The Interface Data structure

OSPFV3-8.9
The Interface Data Structure
MUST A list of IPv6 prefixes can be configured for the attached link.
These will be advertised by the router in link-LSAs, so that
they can be advertised by the link"s Designated Router in
intra-area-prefix-LSAs.
(Verify that DR sends intra-area-prefix-LSA).

Test Report created at 2022-03-22 13:39:59 UTC Page 37 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.1.3 p17 The Neighbor Data Structure

OSPFV3-9.2
The Neighbor Data Structure
MUST The neighbor"s choice of Designated Router is now encoded as a
Router ID, instead of as an IP address
(The test is for Designated Router)

ANVL- RFC 5340, s4.1.3 p17 The Neighbor Data Structure

OSPFV3-9.3
The Neighbor Data Structure
MUST The neighbor"s choice of Designated Router is now encoded as a
Router ID, instead of as an IP address
(The test is for Backup Designated Router)

Test Report created at 2022-03-22 13:39:59 UTC Page 38 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2 p17 Protocol Packet Processing

OSPFV3-10.1
Protocol Packet Processing
MUST The Next Header field of the immediately encapsulating IPv6 header
set to the value 89.

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.1
Sending Protocol Packets
MUST Packet lengtn
The length of the entire OSPF packet in bytes, including the
standard OSPF packet header

Test Report created at 2022-03-22 13:39:59 UTC Page 39 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-11.2 RFC 5340, s4.2.1 p18 Sending protocol packets

MUST Sending Protocol Packets

Packet length
The length of the entire OSPF packet in bytes, including the
standard OSPF packet header

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.3
Sending Protocol Packets
MUST Instance ID
The OSPF instance ID associated with the interface out of which the
packet is being sent

Test Report created at 2022-03-22 13:39:59 UTC Page 40 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.4
Sending Protocol Packets
MUST Checksum
The standard IPv6 Upper-Layer checksum covering the entire OSPF
packet and prepended IPv6 pseudo-header.

ANVL- NEGATIVE
OSPFV3-11.5 RFC 5340, s4.2.1 p18 Sending protocol packets

MUST Sending Protocol Packets

Checksum
The standard IPv6 Upper-Layer checksum covering the entire OSPF
packet and prepended IPv6 pseudo-header.

Test Report created at 2022-03-22 13:39:59 UTC Page 41 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.6 RFC 2328, s8.1 p59 Sending protocol packets

MUST Sending Protocol Packets

In OSPF protocol packet headers Router ID is set to the
identity of the router itself (who is originating
the packet).

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.7 RFC 2328, s8.1 p59 Sending protocol packets

MUST Sending Protocol Packets

Area ID in the OSPF packet header must be set to the ID
of the area that the packet is being sent into.
(This test checks Hello packet)

Test Report created at 2022-03-22 13:39:59 UTC Page 42 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.9 RFC 2328, s8.1 p60 Sending protocol packets

MUST Sending Protocol Packets

Retransmissions of Link State Update packets are ALWAYS sent
directly to the neighbor.

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.10 RFC 2328, s10.9 p105 Sending Link State Request Packets

MUST Sending Protocol Packets

When the neighbor responds to these requests (Link State Request)
with the proper Link State Update packet(s), the Link state
request list is truncated and a new Link State Request packet is
sent. This process continues until the Link state request list
becomes empty.

Test Report created at 2022-03-22 13:39:59 UTC Page 43 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.11 RFC 2328, s10.9 p105 Sending Link State Request Packets

MUST Sending Protocol Packets

Link state request list that have been requested, but
not yet received, are packaged into Link State Request
packets for retransmission at intervals of RxmtInterval.

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.12 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment
packets
MUST
Sending Protocol Packets
If the new LSA has been flooded back out receiving interface no
acknowledgment is sent.

Test Report created at 2022-03-22 13:39:59 UTC Page 44 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.13 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment
packets
MUST
Sending Protocol Packets
If the new LSA is more recent than database copy, but was not
flooded back out receiving interface and if the router is in
state Backup then delayed acknowledgment is sent if
advertisement
is received from Designated Router, otherwise nothing is done.

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu Ubuntu 16.04: Ubuntu
unpredict unpredict unpredict
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: pass 16.04: pass 16.04: FAIL

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.14 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is more recent than database copy, but was not
flooded back out receiving interface and if the receiving router
is not in state Backup then delayed acknowledgment is sent.
(This test checks the case when router state is DR Other)

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu 16.04: Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu Ubuntu
unpredict unpredict unpredict
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: pass 16.04: pass 16.04: FAIL

FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD FreeBSD FreeBSD 12.0: FreeBSD FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0:
untested untested untested untested unpredict untested untested untested
12.0: FAIL 12.0: FAIL 12.0: FAIL

Test Report created at 2022-03-22 13:39:59 UTC Page 45 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.15 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu
unpredict unpredict unpredict unpredict
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.16 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is a duplicate, and was treated as implied
acknowledgment and if the receiving router is in state Backup
then delayed acknowledgment is sent if advertisement is received
from Designated Router, otherwise nothing is done.

Test Report created at 2022-03-22 13:39:59 UTC Page 46 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.17 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is a duplicate, and was treated as implied
acknowledgment and if the receiving router is not in state
Backup then no acknowledgment is sent.
(This test checks the case when router state is DR Other)

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.18 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is a duplicate, and was treated as implied
acknowledgment and if the receiving router is not in state Backup
then no acknowledgment is sent.
(This test checks the case when router state is DR)

Test Report created at 2022-03-22 13:39:59 UTC Page 47 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.19 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is a duplicate, and was not treated as implied
acknowledgment and if the receiving router is in state Backup
then direct acknowledgment is sent.

ANVL- RFC 5340, s4.2.1 p18 Sending protocol packets

OSPFV3-11.20 RFC 2328, s13.5 p152-153 Sending Link State Acknowledgment packets

MUST Sending Protocol Packets

If the new LSA is a duplicate, and was not treated as implied
acknowledgment and if the receiving router is not in state Backup
then direct acknowledgment is sent.

Test Report created at 2022-03-22 13:39:59 UTC Page 48 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.1 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

The Hello Packet also indicates how often a neighbor must be
heard from to remain active (RouterDeadInterval)

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.2 RFC 2328, s9.5 p78 Sending Hello packets

SHOULD Sending Hello Packets

While sending a Hello packet into a stub area the E-bit of the
Options field should be clear.

Test Report created at 2022-03-22 13:39:59 UTC Page 49 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-12.3 RFC 5340, s4.2.1.1 p18 Sending Hello packets
RFC 2328, s9.5 p78 Sending Hello packets
SHOULD
Sending Hello Packets
While sending a Hello packet into a stub area the E-bit of the
Options field should be clear.

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.4 RFC 2328, s9.5 p78 Sending Hello packets

SHOULD Sending Hello Packets

While sending a Hello packet into a non-stub area the E-bit
of the Options field should be set.

Test Report created at 2022-03-22 13:39:59 UTC Page 50 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.5 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

In order to ensure two-way communication between adjacent
routers, the Hello packet contains the list of all routers
on the network from which Hello Packets have been seen
recently.

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.6 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

Hello packet also contains the router"s current choice for
Designated Router and Backup Designated Router.

Test Report created at 2022-03-22 13:39:59 UTC Page 51 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.7 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

On broadcast networks, Hello packets are sent to the IP
multicast address AllSPFRouters.

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.8 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

On broadcast networks, Hello packets are sent every
HelloInterval seconds.

Test Report created at 2022-03-22 13:39:59 UTC Page 52 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.11 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

On virtual links, Hello packets are sent as unicasts
(addressed directly) to the other end of the virtual
link

ANVL- RFC 5340, s4.2.1.1 p18 Sending Hello packets

OSPFV3-12.12 RFC 2328, s9.5 p78 Sending Hello packets

MUST Sending Hello Packets

On virtual links, Hello packets are sent every HelloInterval
seconds.

Test Report created at 2022-03-22 13:39:59 UTC Page 53 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-12.13 RFC 5340, s4.2.1.1 p19 Sending Hello packets

MUST Sending Hello Packets

the N-bit is set if and only if the interface attaches to an
NSSA area

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.1 RFC 2328, s10.8 p103 Sending Database Description Packets

SHOULD Sending Database Description Packets

Interface MTU should be set to 0 in Database Description
packets sent over virtual links.

Test Report created at 2022-03-22 13:39:59 UTC Page 54 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.2 RFC 2328, s10.8 p103 Sending Database Description Packets

SHOULD Sending Database Description Packets

In Database Description packet the unrecognized bits in the
Options field should be set to zero.

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.3 RFC 2328, s10.8 p103 Sending Database Description Packets

MUST Sending Database Description Packets

In state ExStart the router sends empty Database Description
packets, with the initialize (I), more (M) and master (MS)
bits set.

Test Report created at 2022-03-22 13:39:59 UTC Page 55 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.4 RFC 2328, s10.8 p103 Sending Database Description Packets

MUST Sending Database Description Packets

In state ExStart Database Description packets are
retransmitted every RxmtInterval seconds.

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.5 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Exchange, if the router is master, Database Description
packets are sent when slave acknowledges the previous Database
Description packet by echoing the DD sequence number.

Test Report created at 2022-03-22 13:39:59 UTC Page 56 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.6 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Exchange, if the router is slave, Database
Description packets are sent only in response to Database
Description packets received from the master.

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.7 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Exchange, if the router is slave, if the Database
Description packet received from the master is new, a new
Database Description packet is sent, otherwise the previous
Database Description packet is resent.

Test Report created at 2022-03-22 13:39:59 UTC Page 57 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.8 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Loading the slave must resend its last Database
Description packet in response to duplicate Database Description
packets received from the master.

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.9 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Full the slave must resend its last Database
Description packet in response to duplicate Database
Description packets received from the master.

Test Report created at 2022-03-22 13:39:59 UTC Page 58 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.10 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Loading reception of a Database Description packet from
the master after this interval (RouterDeadInterval) will generate
a SeqNumberMismatch neighbor event.

ANVL- RFC 5340, s4.2.1.2 p19 Sending Database Description Packets

OSPFV3-13.11 RFC 2328, s10.8 p104 Sending Database Description Packets

MUST Sending Database Description Packets

In state Full reception of a Database Description packet"
from the master after this interval (RouterDeadInterval)
will generate a SeqNumberMismatch neighbor event.

Test Report created at 2022-03-22 13:39:59 UTC Page 59 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p20 Receiving protocol packets

OSPFV3-14.1
Receiving Protocol Packets
SHOULD The fields specified in the header must match those configured
for the receiving OSPFv3 interface. If they do not, the packet should
be discarded:
o The version number field must specify protocol version 3

ANVL- RFC 5340, s4.2.2 p20 Receiving protocol packets

OSPFV3-14.2
Receiving Protocol Packets
SHOULD The fields specified ... for the receiving interface.
If they do not, the packet should be discarded:
The IPv6 Upper-Layer checksum, covering the entire OSPF
packet and prepended IPv6 pseudo-header, must be verified

Test Report created at 2022-03-22 13:39:59 UTC Page 60 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p20 Receiving Protocol Packets

OSPFV3-14.3
Receiving Protocol Packets
SHOULD The fields specified ... for the receiving interface.
If they do not, the packet should be discarded:
o The Area ID and Instance ID found in the OSPF header must be
verified.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.4
Receiving Protocol Packets
SHOULD The fields specified ... for the receiving interface.
If they do not, the packet should be discarded:
o Packets whose IPv6 destination is AllDRouters should only be
accepted if the state of the receiving OSPFv3 interface is
DR or Backup

Test Report created at 2022-03-22 13:39:59 UTC Page 61 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.5 RFC 2328, s10.6 p100 Receiving Database Description Packets

MUST Receiving Protocol Packets

In ExStart state if the received Database Description
packet has the I, M and MS-bit fields set, the packet is empty,
and the neighbor"s Router ID is larger than the router"s
own then the router is slave, and it sets the neighbor
data structure"s DD sequence number to that specified
by master.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.6 RFC 2328, s10.6 p100 Receiving Database Description Packets

MUST Receiving Protocol Packets

In ExStart state if the received Database Description
packet has the I and MS-bit fields off, the packet"s DD sequence
number equals the neighbor data structure"s DD sequence
number and the neighbor"s Router ID is smaller than the
router"s own then the router is Master.

Test Report created at 2022-03-22 13:39:59 UTC Page 62 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.7 RFC 2328, s10.6 p102 Receiving Database Description Packets

SHOULD Receiving Protocol Packets

When the router accepts a received Database Description Packet
as the next in sequence, if the router is master and the accepted
packet has more bit (M) set to 1, it should send a new Database
Description to the slave.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.8 RFC 2328, s10.6 p102 Receiving Database Description Packets

SHOULD Receiving Protocol Packets

When the router accepts a received Database Description
Packet as the next in sequence, if the router is master
and the router has not sent its entire sequence of Database
Description packets, it should send a new Database Description
to the slave.(This test is for DUT as Master)

Test Report created at 2022-03-22 13:39:59 UTC Page 63 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.9 RFC 2328, s10.6 p102 Receiving Database Description Packets

MUST Receiving Protocol Packets

When the router accepts a received Database Description
Packet as the next in sequence, if the router is master
it increments the DD sequence number in the neighbor data
structure.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.10 RFC 2328, s10.6 p102 Receiving Database Description Packets

MUST Receiving Protocol Packets

When the router accepts a received Database Description
Packet as the next in sequence, if the router is slave,
it sets the DD sequence number in the neighbor data
structure to the DD sequence number appearing in the
received packet and also it must send a Database
Description packet in response.

Test Report created at 2022-03-22 13:39:59 UTC Page 64 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.11 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be accepted when the neighbor is in
state Exchange.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.12 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be accepted when the
neighbor is in state Loading.

Test Report created at 2022-03-22 13:39:59 UTC Page 65 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.13 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be accepted when the
neighbor is in state Full.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.14 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be ignored when
neighbor is in ExStart state.

Test Report created at 2022-03-22 13:39:59 UTC Page 66 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.15 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be ignored when neighbor
is in Init state.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.16 RFC 2328, s10.7 p102 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

Link State Request Packets should be ignored when neighbor
is in Down state.

Test Report created at 2022-03-22 13:39:59 UTC Page 67 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.17 RFC 2328, s10.7 p103 Receiving Link State Request Packets

SHOULD Receiving Protocol Packets

If an LSA specified in the Link State Request packet cannot be
found in the database, something has gone wrong with the
Database Exchange process, and neighbor event BadLSReq should
be generated.

ANVL- RFC 5340, s4.2.2 p21 Receiving protocol packets

OSPFV3-14.18 RFC 2328, s13.7 p156 Receiving link state acknowledgments

MUST Receiving Protocol Packets

If the acknowledgment is for the same instance that is contained
on the Link state retransmission list, remove the item from
the list.

Test Report created at 2022-03-22 13:39:59 UTC Page 68 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2.1 p21 Receiving Hello packets

OSPFV3-15.1 RFC 2328, s10.5 p96 Receiving Hello Packets

MUST Receiving Hello Packets

The values of the HelloInterval field in the received Hello
packet must be checked against the values configured for the
receiving interface.Any mismatch causes processing to stop and
the packet to be dropped.

ANVL- RFC 5340, s4.2.2.1 p21 Receiving Hello packets

OSPFV3-15.2 RFC 2328, s10.5 p96 Receiving Hello Packets

MUST Receiving Hello Packets

The values of the RouterDeadInterval fields in the received
Hello packet must be checked against the values configured for
the receiving interface. Any mismatch causes processing to stop
and the packet to be dropped.

Test Report created at 2022-03-22 13:39:59 UTC Page 69 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.2.2.1 p21 Receiving Hello packets

OSPFV3-15.3 RFC 2328, s10.5 p96 Receiving Hello Packets

MUST Receiving Hello Packets

If the receiving interface is attached to a stub area the E-bit
must be clear in received Hello Packets and a mismatch causes
processing to stop and the packet to be dropped.

ANVL- RFC 5340, s4.2.2.1 p21 Receiving Hello packets

OSPFV3-15.4 RFC 2328, s10.5 p96 Receiving Hello Packets

MUST Receiving Hello Packets

If the receiving interface is attached to a non-stub area the E-bit
must be set in received Hello Packets and a mismatch causes processing
to stop and the packet to be dropped.

Test Report created at 2022-03-22 13:39:59 UTC Page 70 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.1 RFC 2328, s12.1.1 p116 LS age

MUST The LSA Header

LSAs are also aged as they are held in each router"s database.

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.2 RFC 2328, s12.1.1 p116 LS age

MUST The LSA Header

The age of an LSA is never incremented past MaxAge.

Test Report created at 2022-03-22 13:39:59 UTC Page 71 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.3 RFC 2328, s12.1.1 p116 LS age

MUST The LSA Header

When an LSA"s age first reaches MaxAge, it is reflooded.

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.4 RFC 2328, s12.1.1 p116 LS age

MUST The LSA Header

LSA of age MaxAge is finally flushed from the database when it
is no longer needed to ensure database synchronization.

Test Report created at 2022-03-22 13:39:59 UTC Page 72 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.5 RFC 2328, s12.1.1 p117 LS age

MUST The LSA Header

If the two instances of a LSA have identical LS sequence number
and LS checksum, an instance of age MaxAge is then always
accepted as most recent.

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.6 RFC 2328, s12.1.1 p117 LS age

MUST The LSA Header

If the two instances of a LSA have identical LS sequence number
and LS Checksum and none of them is of age MaxAge then if their
ages differ by more than MaxAgeDiff, the instance having the
smaller age is accepted as most recent.

Test Report created at 2022-03-22 13:39:59 UTC Page 73 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.7 RFC 2328, s12.1.5 p119 Advertising Router

MUST The LSA Header

The Advertising Router field specifies the OSPF Router ID of
the LSA"s originator.

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.8 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it
originates any LSA.
(This test checks for Router-LSAs)

Test Report created at 2022-03-22 13:39:59 UTC Page 74 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.9 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates any
LSA.
(This test checks for Network-LSAs)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.10 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates
any LSA.
(This test checks for Inter-Area-Prefix-LSAs)

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass

Test Report created at 2022-03-22 13:39:59 UTC Page 75 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.11 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates
any LSA.
(This test checks for Inter-Area-Router-LSAs)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.12 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it
originates any LSA. Afterwards, the LSA"s sequence number
is incremented each time the router originates a new
instance of the LSA.
(This test checks for Router-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 76 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.13 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates
any LSA. Afterwards, the LSA"s sequence number is incremented
each time the router originates a new instance of the LSA.
(This test checks for Network-LSA)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.14 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates
any LSA. Afterwards, the LSA"s sequence number is incremented
each time the router originates a new instance of the LSA.
(This test checks for Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 77 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.15 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

A router uses InitialSequenceNumber the first time it originates
any LSA. Afterwards, the LSA"s sequence number is incremented
each time the router originates a new instance of the LSA.
(This test checks for Inter-Area-Router-LSA)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.16 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

When an attempt is made to increment the sequence number past
the maximum value of N - 1 (0x7fffffff; also referred to as
MaxSequenceNumber), the current instance of the LSA must
first be flushed from the routing domain.

Test Report created at 2022-03-22 13:39:59 UTC Page 78 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.17 RFC 2328, s12.1.6 p120 LS sequence number

MUST The LSA Header

As soon as this flooding of a LSA with LS sequence number
MaxSequenceNumber has been acknowledged by all adjacent
neighbors, new instance can be originated with sequence
number of InitialSequenceNumber.

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.18 RFC 2328, s12.1.7 p121 LS checksum

MUST The LSA Header

The LSA header also contains the length of the LSA in
bytes; subtracting the size of the LS age field
(two bytes) yields the amount of data to checksum.
(This test checks for Router-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 79 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.19 RFC 2328, s12.1.7 p121 LS checksum

MUST The LSA Header

The LSA header also contains the length of the LSA in bytes;
subtracting the size of the LS age field (two bytes)
yields the amount of data to checksum.
(This test checks for Network-LSA)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.20 RFC 2328, s12.1.7 p121 LS checksum

MUST The LSA Header

The LSA header also contains the length of the LSA in bytes;
subtracting the size of the LS age field (two bytes) yields the
amount of data to checksum.
(This test checks for Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 80 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.21 RFC 2328, s12.1.7 p121 LS checksum

MUST The LSA Header

The LSA header also contains the length of the LSA in bytes;
subtracting the size of the LS age field (two bytes) yields the
amount of data to checksum.
(This test checks for Inter-Area-Router-LSA)

ANVL- RFC 5340, s4.4.1 p23 The LSA Header

OSPFV3-16.22 RFC 2328, s12.1.7 p121 LS checksum

SHOULD The LSA Header

The LS checksum field cannot take on the value of zero; the
occurrence of such a value should be considered a checksum
failure.

Test Report created at 2022-03-22 13:39:59 UTC Page 81 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.1 p24 The LSA Header

OSPFV3-16.23
The LSA Header
MUST Instead of the IPv4 behavior of encoding the network number
within the AS-external-LSA"s Link State ID, the IPv6
Link State ID simply serves as a way to differentiate multiple
LSAs originated by the same router

ANVL- RFC 5340, s4.4.1 p24 The LSA Header

OSPFV3-16.24
The LSA Header
MUST When a router originates a Link-LSA for a given link,
its Link State ID is set equal to the router"s Interface ID
on the link.

Test Report created at 2022-03-22 13:39:59 UTC Page 82 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.2 p24 The link-state database

OSPFV3-17.1 RFC 2328, s13.1 p145 Determining which LSA is newer

MUST The Link-State Database

The LSA having the newer LS sequence number is more recent.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.1 RFC 2328, s12.4 p123 Originating LSAs

MUST Originating LSAs

Destinations are advertised one at a time so that the change in
any single route can be flooded without reflooding the entire
collection of routes.
This test is for Inter-Area-Prefix-LSA.

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu
16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: pass 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL

Test Report created at 2022-03-22 13:39:59 UTC Page 83 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.2 RFC 2328, s12.4 p123 Originating LSAs

MUST Originating LSAs

During the flooding procedure, many LSAs can be carried by a
single Link State Update packet.
This test verifies whether the DUT recognizes multiple LSAs
residing in a single Link State Update packet.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.3 RFC 2328, s12.4 p124 Originating LSAs

MUST Originating LSAs

Whenever a new instance of an LSA is originated, its LS sequence
number is incremented, its LS age is set to 0.

Test Report created at 2022-03-22 13:39:59 UTC Page 84 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.4 RFC 2328, s12.4 p125 Originating LSAs

MAY Originating LSAs

A change in an interface"s state may mean that it is necessary to
produce a new instance of the router-LSA.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.5 RFC 2328, s12.4 p125 Originating LSAs

SHOULD Originating LSAs

If an attached network"s Designated Router gets changed a new
router-LSA should be originated.

Test Report created at 2022-03-22 13:39:59 UTC Page 85 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.6 RFC 2328, s12.4 p125 Originating LSAs

SHOULD Originating LSAs

When Designated Router changes and if the router itself is now the
Designated Router, a new network-LSA should be produced.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.7 RFC 2328, s12.4 p125 Originating LSAs

SHOULD Originating LSAs

If the router itself is no longer the Designated Router, any
network-LSA that it might have originated for the network should
be flushed from the routing domain.

Test Report created at 2022-03-22 13:39:59 UTC Page 86 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.8 RFC 2328, s12.4 p125 Originating LSAs

MAY Originating LSAs

If one of the neighboring routers changes to the FULL state then
this may mean that it is necessary to produce a new instance of
the router-LSA.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.9 RFC 2328, s12.4 p125 Originating LSAs

MAY Originating LSAs

If one of the neighboring routers changes from the FULL state
then this may mean that it is necessary to produce a new
instance of the router-LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 87 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.11
Originating LSAs
MAY The state or interface ID of one of the router"s interfaces changes. The router
may need to (re)originate or flush its Link-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
(This test is for (re)origination or flush of Router-LSA during
State change)

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.12
Originating LSAs
MAY The state or interface ID of one of the router"s interfaces changes. The router
may need to (re)originate or flush its Link-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
(This test is for (re)origination of Intra-Area-Prefix-LSA
during the state change.)

Test Report created at 2022-03-22 13:39:59 UTC Page 88 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.13
Originating LSAs
MAY The state or interface ID of one of the router"s interfaces changes. The router
may need to (re)originate or flush its Link-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
(This test is for flushing of Intra-Area-Prefix-LSA
during the state change.)

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.14
Originating LSAs
MAY The identity of a link"s Designated Router changes. The router
may need to (re)originate or flush the link"s network-LSA and
one or more router-LSAs and/or intra-area-prefix-LSAs.
(This test is for "(re)originate".)

Test Report created at 2022-03-22 13:39:59 UTC Page 89 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.15
Originating LSAs
MAY The identity of a link"s Designated Router changes. The router
may need to (re)originate or flush the link"s network-LSA and
one or more router-LSAs and/or intra-area-prefix-LSAs.
(This test is for "flush".)

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.16
Originating LSAs
MAY A neighbor transitions to/from "Full" state. The router may need
to (re)originate or flush the link"s network-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
This test is for "to Full state".

Test Report created at 2022-03-22 13:39:59 UTC Page 90 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.17
Originating LSAs
MAY A neighbor transitions to/from "Full" state. The router may need
to (re)originate or flush the link"s network-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
(This test is for "from Full state".)

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.18
Originating LSAs
MAY The Interface ID of a neighbor changes. This may cause a new
instance of a router-LSA to be originated for the associated area.

Test Report created at 2022-03-22 13:39:59 UTC Page 91 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.19
Originating LSAs
MUST A new prefix is added to an attached link (both through
configuration). This causes the router to
reoriginate its link-LSA for the link

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.20
Originating LSAs
MUST A new prefix is added to an attached link. If the router is the
only router attached to the link, causes the router to
reoriginate an intra-area-prefix-LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 92 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.21
Originating LSAs
MUST A prefix is deleted (both through configuration). This causes
the router to reoriginate its link-LSA for the link.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.22
Originating LSAs
MUST A prefix is deleted (both through configuration). If it is the
only router attached to the link, causes the router to
reoriginate an intra-area-prefix-LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 93 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.23
Originating LSAs
MUST A new link-LSA is received, causing the link"s collection of
prefixes to change. If the router is the Designated Router for the
link, it originates a new intra-area-prefix-LSA.

ANVL- RFC 5340, s4.4.3 p25 Originating LSAs

OSPFV3-18.24
Originating LSAs
MAY The state or interface ID of one of the router"s interfaces changes. The router
may need to (re)originate or flush its Link-LSA and one or more
router-LSAs and/or intra-area-prefix-LSAs.
(This test is for (re)origination or flush of Link-LSA during
State change)

Test Report created at 2022-03-22 13:39:59 UTC Page 94 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.1
Router-LSAs
MUST Router-LSAs have area flooding scope.

ANVL- RFC 5340, s4.4.3.1 p27 LSA Options

OSPFV3-19.2
Router-LSAs
SHOULD The V6-bit should be set unless the router will not participate
in transit IPv6 routing. The E-bit should be clear if and only
if the attached area is an OSPF stub or OSPF NSSA area.
(This is to test Router-LSA for stub area)

Test Report created at 2022-03-22 13:39:59 UTC Page 95 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.4 RFC 2328, s12.4.1 p127 Router-LSAs

MUST Router-LSAs
A router also indicates whether it is an area border router, by
setting the appropriate bits (bit B, respectively) in its
router-LSAs.

ANVL- NEGATIVE
OSPFV3-19.5 RFC 5340, s4.4.3.2 p27 Router-LSAs
RFC 2328, s12.4.1 p127 Router-LSAs
MUST
Router-LSAs
A router also indicates whether it is an area border router, by
setting the appropriate bits (bit B, respectively) in its
router-LSAs.

Test Report created at 2022-03-22 13:39:59 UTC Page 96 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.6 RFC 2328, s12.4.1 p127 Router-LSAs

SHOULD Router-LSAs
Bit B should be set whenever the router is actively attached to
two or more areas, even if the router is not currently attached
to the OSPF backbone area.
(This is for DUT attached to two non-backbone areas)

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.7 RFC 2328, s12.4.1 p128 Router-LSAs

MUST Router-LSAs
The router sets bit V in its router-LSA for Area A if and only
if the router is the endpoint of one or more fully adjacent
virtual links having Area A as their Transit area.

Test Report created at 2022-03-22 13:39:59 UTC Page 97 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.8 RFC 2328, s12.4.1 p129 Router-LSAs,

MUST Router-LSAs
If the router wishes to build a router-LSA for Area A then for
each interface if the attached network does not belong to
Area A, no links are added to the LSA.

ANVL- RFC 5340, s4.4.3.2 p27 Router-LSAs

OSPFV3-19.11
Router-LSAs
MUST Each of the router"s interfaces to the area are then described by
appending "link descriptions" to the router-LSA. Each link
description is 16 bytes long, consisting of five fields: (link) Type,
Metric, Interface ID, Neighbor Interface ID and Neighbor Router ID

Test Report created at 2022-03-22 13:39:59 UTC Page 98 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p28 Router-LSAs

OSPFV3-19.12
Router-LSAs
MUST Interfaces in state "Down" or "Loopback" are not described
(This test is for Down state)

ANVL- RFC 5340, s4.4.3.2 p28 Router-LSAs

OSPFV3-19.14
Router-LSAs
MUST Within each link description, the Metric field is
always set to the interface"s output cost, and the Interface ID
field is set to the interface"s OSPF Interface ID.

Test Report created at 2022-03-22 13:39:59 UTC Page 99 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.2 p28 Router-LSAs

OSPFV3-19.16
Router-LSAs
MUST If the router is fully adjacent to the link"s Designated Router,
or if the router itself is Designated Router and is fully adjacent
to at least one other router, add a single Type 2 link description
(transit network).

ANVL- RFC 5340, s4.4.3.2 p28 Router-LSAs

OSPFV3-19.17
Router-LSAs
MUST If the neighboring router is fully adjacent, add a Type 4 link
description (virtual). The Neighbor Interface ID field is set to
the Interface ID advertised by the neighbor in its Hello
packets, and the Neighbor Router ID field is set to the
neighbor"s Router ID

Test Report created at 2022-03-22 13:39:59 UTC Page 100 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.3 p29 Network-LSAs

OSPFV3-20.1
Network-LSAs
MUST Network-LSAs have area flooding scope.

ANVL- RFC 5340, s4.4.3.3 p29 Network-LSAs

OSPFV3-20.2
Network-LSAs
MUST A network-LSA is originated for every broadcast or NBMA link with
an elected Designated Router that is fully adjacent with at least
one other router on the link. The network-LSA is originated by the
link"s Designated Router and lists all routers on the link with
which it is fully adjacent.

Test Report created at 2022-03-22 13:39:59 UTC Page 101 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.3 p29 Network-LSAs

OSPFV3-20.3 RFC 2328, s12.4.2 p134 Network-LSAs

SHOULD Network-LSAs
A router that has formerly been the Designated Router for
a network, but is no longer, should flush the network-LSA that it
had previously originated.

ANVL- RFC 5340, s4.4.3.3 p29 Network-LSAs

OSPFV3-20.4 RFC 2328, s12.4.2 p134 Network-LSAs
(see also s13.4 p151 Receiving self-originated LSAs),
MUST
Network-LSAs
When a router"s Router ID has changed, any network-LSAs that were
originated with the router"s previous Router ID must be flushed.

Test Report created at 2022-03-22 13:39:59 UTC Page 102 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.3 p29 Network-LSAs

OSPFV3-20.5
Network-LSAs
MUST An IPv6 network-LSA"s Link State ID is set to the Interface ID of
the Designated Router on the link.

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.1
Inter-Area-Prefix-LSAs
MUST Inter-area-prefix-LSAs have area flooding scope.

Test Report created at 2022-03-22 13:39:59 UTC Page 103 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.2 RFC 2328, s12.4.3. p136 Summary-LSAs

MUST Inter-Area-Prefix-LSAs
If for a route the area associated with this set of paths is
the Area A itself, do not generate a summary-LSA for the route
for advertising into Area A.
(Type 3 Summary LSA has been renamed as Inter-Area-Prefix-LSA)

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.3 RFC 2328, s12.4.3. p136 Summary-LSAs

MUST Inter-Area-Prefix-LSAs
If for a route the area associated with the set of paths is not
Area A but the next hops associated with this set of paths
belong to Area A itself, do not generate a summary-LSA for the
route for advertising into Area A.
(Type 3 Summary LSA has been renamed as Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 104 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.4 RFC 2328, s12.4.3 p136 Summary-LSAs

MUST Inter-Area-Prefix-LSAs
If the destination of a route is an AS boundary router,
a summary-LSA should be originated if and only if the routing
table entry describes the preferred path to the AS boundary
router. If so, a Type 4 summary-LSA is originated for the destination.
(Type 4 Summary-LSA has been renamed as Inter-Area-Router-LSA.)

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.5 RFC 2328, s12.4.3. p136 Summary-LSAs

MUST Inter-Area-Prefix-LSAs
While originating summary-LSAs for networks reachable by
inter-area routes at most a single Type 3 summary-LSA is
originated for each area address range.
(Type 3 Summary-LSA has been renamed as Inter-Area-Prefix-LSA.)

Test Report created at 2022-03-22 13:39:59 UTC Page 105 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.4 p30 Inter-Area-Prefix-LSAs

OSPFV3-21.6
Inter-Area-Prefix-LSAs
MUST The Link State ID of an inter-area-prefix-LSA has lost all of
its addressing semantics, and simply serves to
distinguish multiple inter-area-prefix-LSAs that are
originated by the same router.

ANVL- RFC 5340, s4.4.3.5 p31 Inter-Area-Router-LSAs

OSPFV3-22.1
Inter-Area-Router-LSAs
MUST Inter-area-router-LSAs have area flooding scope.

Test Report created at 2022-03-22 13:39:59 UTC Page 106 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.5 p32 Inter-Area-Router-LSAs

OSPFV3-22.2
Inter-Area-Router-LSAs
SHOULD The Options field in an inter-area-router-LSA should be
set equal 1to the Options field contained in the destination
router"s own router-LSA.

ANVL- RFC 5340, s4.4.3.6 p32 AS-External-LSAs

OSPFV3-23.1
AS-External-LSAs
MUST AS-external-LSAs have AS flooding scope.

Test Report created at 2022-03-22 13:39:59 UTC Page 107 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.6 p32 AS-External-LSAs

OSPFV3-23.2
AS-External-LSAs
MUST The Link State ID of an AS-external-LSA has lost all of its
addressing semantics, and simply serves to distinguish
multiple AS-external-LSAs that are originated by the same
router.

ANVL- RFC 5340, s4.4.3.6 p32 AS-External-LSAs

OSPFV3-23.4
AS-External-LSAs
MUST The forwarding address is present in the AS-external-LSA if and
only if the AS-external-LSA"s bit F is set.

Test Report created at 2022-03-22 13:39:59 UTC Page 108 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.6 p33 AS-External-LSAs

OSPFV3-23.5
AS-External-LSAs
SHOULD Received non-zero values for Reference LS Type field should be
ignored.

ANVL- RFC 5340, s4.4.3.8 p34 Link-LSAs

OSPFV3-24.1
Link-LSAs
MUST Link-LSAs have link-local flooding scope.

Test Report created at 2022-03-22 13:39:59 UTC Page 109 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.8 p35 Link-LSAs

OSPFV3-24.2
Link-LSAs
MUST The Link State ID is set to the router"s Interface ID on Link L.

ANVL- RFC 5340, s4.4.3.8 p35 Link-LSAs

OSPFV3-24.3
Link-LSAs
MUST The Router Priority of the router"s interface to Link L is
inserted into the Link-LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 110 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.8 p35 Link-LSAs

OSPFV3-24.4
Link-LSAs
MUST The link-LSA"s Options field is set to reflect the router"s
capabilities. On multi-access links, the Designated Router will
logically OR the link-LSA Options fields for all fully adjacent
neighbors in Link L"s network-LSA.

ANVL- RFC 5340, s4.4.3.8 p35 Link-LSAs

OSPFV3-24.5
Link-LSAs
MUST The router inserts its link-local address on Link L into the
Link-LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 111 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.8 p35 Link-LSAs

OSPFV3-24.6
Link-LSAs
MUST Each IPv6 address prefix that has been configured on
Link L is added to the Link-LSA, by specifying
values for the PrefixLength, PrefixOptions, and Address Prefix
fields.

ANVL- RFC 5340, s4.4.3.9 p36 Intra-Area-Prefix-LSAs

OSPFV3-25.1
Intra-Area-Prefix-LSAs
MUST Intra-area-prefix-LSAs have area flooding scope.

Test Report created at 2022-03-22 13:39:59 UTC Page 112 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.9 p36 Intra-Area-Prefix-LSAs

OSPFV3-25.2
Intra-Area-Prefix-LSAs
MUST It either associates a list of IPv6 address prefixes with a transit
network link by referencing a network- LSA, or associates a
list of IPv6 address prefixes with a router by referencing
a router-LSA.

ANVL- RFC 5340, s4.4.3.9 p32, p37 Intra-Area-Prefix-LSAs

OSPFV3-25.3
Intra-Area-Prefix-LSAs
MUST If the link-LSA"s Advertising Router is fully adjacent to the Designated
Router and the Link State ID matches the neighbor"s interface ID,
the list of prefixes in the link-LSA is copied into the intra-
area-prefix-LSA that is being built.

Test Report created at 2022-03-22 13:39:59 UTC Page 113 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.9 p37 Intra-Area-Prefix-LSAs

OSPFV3-25.4
Intra-Area-Prefix-LSAs
MUST Multiple prefixes having the same PrefixLength and Address
Prefix are considered to be duplicates; .....
and a single instance of the duplicate prefix should be included
in the intra-area-prefix-LSA. The Metric field for all prefixes is
set to 0.

ANVL- RFC 5340, s4.4.3.9 p37 Intra-Area-Prefix-LSAs

OSPFV3-25.5
Intra-Area-Prefix-LSAs
MUST A router builds an intra-area-prefix-LSA to advertise prefixes for
its attached stub links.

Test Report created at 2022-03-22 13:39:59 UTC Page 114 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.4.3.9 p38 Intra-Area-Prefix-LSAs

OSPFV3-25.6
Intra-Area-Prefix-LSAs
MUST If RTX has one or more virtual links configured through
the area, it includes one of its global
scope IPv6 interface addresses in the LSA (if it hasn"t
already), setting the LA-bit in the PrefixOptions field,
the PrefixLength to 128 and
the Metric to 0.

ANVL- RFC 5340, s4.4.3.9 p39 Intra-Area-Prefix-LSAs

OSPFV3-25.7
Intra-Area-Prefix-LSAs
MAY When network conditions change, it may be necessary for a router
to move prefixes from one intra-area-prefix-LSA to another.

Test Report created at 2022-03-22 13:39:59 UTC Page 115 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.1 RFC 2328, s13 p143 The Flooding Procedure

MUST Flooding
To make the flooding procedure reliable, each LSA must be
acknowledged separately. Acknowledgments are transmitted in Link
State Acknowledgment packets.

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.2 RFC 2328, s13 p143 The Flooding Procedure

MUST Flooding
For each LSA contained in a Link State Update packet, validate the
LSA"s LS checksum. If the checksum turns out to be invalid,
discard the LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 116 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.3 RFC 2328, s13 p144 The Flooding Procedure,

MUST Flooding
If the LSA"s LS age is equal to MaxAge, and there is currently no
instance of the LSA in router"s link state database, and none of
router"s neighbors are in state Exchange or Loading send direct
Acknowledgment packet to the sending neighbor and discard the LSA.

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.4 RFC 2328, s13 p144 The Flooding Procedure

MUST Flooding
If there is already a database copy, and if the database copy
was received via flooding and installed less than MinLSArrival
seconds ago, discard the new LSA (without acknowledging it).

Test Report created at 2022-03-22 13:39:59 UTC Page 117 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.5 RFC 2328, s13 p144 The Flooding Procedure

MUST Flooding
If there is no database copy or the received LSA is more recent
than the database copy and the database copy was installed more
than MinLSArrival seconds ago, immediately flood the new LSA out
some subset of the router"s interfaces.

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.6 RFC 2328, s13 p144 The Flooding Procedure

MUST Flooding
When a new instance of a LSA is installed in database, a router
possibly acknowledges the receipt of the LSA by sending a Link
State Acknowledgment packet on the receiving interface.

Ubuntu Ubuntu Ubuntu Ubuntu Ubuntu 16.04: Ubuntu Ubuntu 16.04: Ubuntu 16.04: Ubuntu 16.04: Ubuntu 16.04: Ubuntu
unpredict unpredict unpredict unpredict unpredict
16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL 16.04: FAIL

Test Report created at 2022-03-22 13:39:59 UTC Page 118 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.7 RFC 2328, s13 p145 The Flooding Procedure

MUST Flooding
When the received LSA is at most as recent as the database copy of
that LSA then if there is an instance of the LSA on the sending
neighbor"s Link State Request list, generate the neighbor event
BadLSReq.

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.8 RFC 2328, s13 p145 The Flooding Procedure

SHOULD Flooding
If the received LSA is the same instance as the database copy
and is listed in the Link state retransmission list for the
receiving adjacency, the router itself is expecting an
acknowledgment for this LSA. The router should remove the LSA
from the Link state retransmission list.

Test Report created at 2022-03-22 13:39:59 UTC Page 119 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.9 RFC 2328, s13 p145 The Flooding Procedure

MUST Flooding
If the database copy has LS age equal to MaxAge and LS sequence
number equal to MaxSequenceNumber, simply discard the received
LSA without acknowledging it.

FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD 12.2: FreeBSD FreeBSD 12.2:
untested untested untested untested untested untested untested untested untested unpredict
12.2: pass

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.10 RFC 2328, s13.4 p151 Receiving self-originated LSAs

MUST Flooding
A self-originated LSA is detected when the LSA"s Advertising
Router is equal to the router"s own Router ID and in most cases
(....), the router must then advance the LSA"s LS sequence
number one past the received LS sequence number, and originate a
new instance of the LSA.

Test Report created at 2022-03-22 13:39:59 UTC Page 120 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.11 RFC 2328, s13.4 p151 Receiving self-originated LSAs

SHOULD Flooding
If the received self-originated LSA is a summary-LSA and the
router no longer has an (advertisable) route to the destination
instead of updating the LSA, the LSA should be flushed from the
routing domain by incrementing the received LSA"s LS age to
MaxAge and reflooding.
(Summary-LSA has been renamed as Inter-Area-Prefix/Router LSA.)

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.12 RFC 2328, s13.4 p151 Receiving self-originated LSAs

SHOULD Flooding
If the received self-originated LSA is an AS-external-LSA and
the router no longer has an (advertisable) route to the
destination instead of updating the LSA, the LSA should be
flushed from the routing domain by incrementing the received
LSA"s LS age to MaxAge and reflooding.

Test Report created at 2022-03-22 13:39:59 UTC Page 121 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5 p40 Flooding

OSPFV3-26.13 RFC 2328, s13.4 p151 Receiving self-originated LSAs

SHOULD Flooding
If the received self-originated LSA is a network-LSA but the
router is no longer Designated Router for the network, instead of
updating the LSA, the LSA should be flushed from the routing
domain by incrementing the received LSA"s LS age to MaxAge and
reflooding.

ANVL- RFC 5340, s4.5.1 p41 Receiving Link State Update packets
OSPFV3-27.1
Receiving Link State Update Packets
MUST Discard the LSA and get the next one from the Link State
Update packet if the interface area has been configured as
a stub or NSSA area and the LS type indicates "AS flooding scope"
(This is to test stub area)

Test Report created at 2022-03-22 13:39:59 UTC Page 122 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5.1 p41 Receiving Link State Update packets
OSPFV3-27.2
Receiving Link State Update Packets
MUST if the flooding scope of the LSA"s LS type is set to
"reserved", discard the LSA

ANVL- RFC 5340, s4.5.2 p41 Sending Link State Update packets
OSPFV3-28.1 RFC 2328, s13.3 p149 Next step in the Flooding Procedure

MUST Sending Link State Update Packets

If the adjacency is not yet full and there is an instance of
new LSA in Link State request list and if the new LSA is more
recent delete the LSA from the Link state request list.

Test Report created at 2022-03-22 13:39:59 UTC Page 123 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5.2 p41 Sending Link State Update packets
OSPFV3-28.2 RFC 2328, s13.3 p150 Sending protocol packets

MUST Sending Link State Update Packets

On broadcast network, the Link State Update packets are multicast
but Link State Update packets carrying retransmissions are
always sent directly to the neighbor.

ANVL- RFC 5340, s4.5.2 p42 Sending Link State Update packets
OSPFV3-28.3
Sending Link State Update Packets
MUST If the flooding scope is "AS flooding scope", the
eligible interfaces are all router interfaces excepting virtual
links.

Test Report created at 2022-03-22 13:39:59 UTC Page 124 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5.2 p42 Sending Link State Update packets
OSPFV3-28.4
Sending Link State Update Packets
MUST If the flooding scope is "area flooding scope", the
eligible interfaces are those interfaces connecting to the
LSA"s associated area.

ANVL- NEGATIVE
OSPFV3-28.5 RFC 5340, s4.5.2 p42 Sending Link State Update packets

MUST Sending Link State Update Packets

If the flooding scope is "area flooding scope", the
eligible interfaces are those interfaces connecting to the
LSA"s associated area.

Test Report created at 2022-03-22 13:39:59 UTC Page 125 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5.2 p42 Sending Link State Update packets
OSPFV3-28.6
Sending Link State Update Packets
MUST If the flooding scope is "link-local flooding scope", then there
is a single eligible interface, the one connecting to the LSA"s
associated link

ANVL- NEGATIVE
OSPFV3-28.7 RFC 5340, s4.5.2 p42 Sending Link State Update packets

MUST Sending Link State Update Packets

If the flooding scope is "link-local flooding scope", then there
is a single eligible interface, the one connecting to the LSA"s
associated link

Test Report created at 2022-03-22 13:39:59 UTC Page 126 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.5.2 p42 Sending Link State Update packets
OSPFV3-28.8
Sending Link State Update Packets
MUST The LS type is unrecognized, and the U-bit in the LS Type is set
to 1 (store and flood the LSA, as if type understood).......

ANVL- RFC 5340, s4.5.2 p42 Sending Link State Update packets
OSPFV3-28.9
Sending Link State Update Packets
MUST The LS type is unrecognized, and the U-bit in the LS Type is set
to 1 (store and flood the LSA, as if type understood).......

Test Report created at 2022-03-22 13:39:59 UTC Page 127 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.1 RFC 2328, s15 p158 Virtual Links

MUST Virtual Links

When an adjacency is established over a virtual link, then OSPF
packets pertaining to the backbone area will flow over the
adjacency.

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.2 RFC 2328, s15 p158 Virtual Links

MUST Virtual Links

AS-external-LSAs are NEVER flooded over virtual adjacencies.

Test Report created at 2022-03-22 13:39:59 UTC Page 128 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.3 RFC 2328, s15 p159 Virtual Links

MUST Virtual Links

The cost of a virtual link is NOT configured.It is defined to be
the cost of the intra-area path between the two defining area
border routers.

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.4 RFC 2328, s15 p159 Virtual Links

SHOULD Virtual Links

When the cost of a virtual link changes, a new router-LSA should
be originated for the backbone area.

Test Report created at 2022-03-22 13:39:59 UTC Page 129 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.5 RFC 2328, s15 p159 Virtual Links

MUST Virtual Links

The time between link state retransmissions, RxmtInterval, is
configured for a virtual link.

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.6
Virtual Links
MUST LSAs having AS flooding scope are never flooded over virtual
adjacencies, nor are LSAs with AS flooding scope summarized over
virtual adjacencies during the Database Exchange process.This is
a generalization of the IPv4 treatment of AS-external-LSAs.

Test Report created at 2022-03-22 13:39:59 UTC Page 130 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.7 p44 Virtual links

OSPFV3-30.7
Virtual Links
MUST Like all other IPv6 OSPF interfaces, virtual links are assigned
unique (within the router) Interface IDs.These are advertised in
Hellos sent over the virtual link and in the router"s
router-LSAs.

ANVL- RFC 5340, s4.8.3 p47 Calculating the Inter-Area Routes

OSPFV3-31.1 RFC 2328, s16.2 p168 Calculating the inter-area routes

MUST Calculating the Inter-Area Routes

If the router has active attachments to multiple areas, only
backbone summary-LSAs are examined.
(Type 3 Summary LSA has been renamed as Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 131 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, s4.8.3 p47 Calculating the Inter-Area Routes

OSPFV3-31.2
Calculating the Inter-Area Routes
SHOULD Prefixes having the NU-bit set in their Prefix Options field
should be ignored by the inter-area route calculation.

ANVL- RFC 5340, s4.8.5 p48 Calculating AS External and NSSA Routes
OSPFV3-32.1
Calculating AS External Routes
MUST The default route in AS-external-LSAs or NSSA-LSAs is advertised
by a zero-length prefix.
(This is to test AS-external-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 132 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.1 p57 Encapsulation of OSPF Packets

OSPFV3-33.1
Encapsulation of OSPF Packets
SHOULD As such, the multicast addresses have been chosen with
link-local scope, and packets sent to these addresses should have
their IPv6 Hop Limit set to 1.

ANVL- RFC 5340, sA.1 p57 Encapsulation of OSPF Packets

OSPFV3-33.2
Encapsulation of OSPF Packets
SHOULD As such, the multicast addresses have been chosen with
link-local scope, and packets sent to these addresses should have
their IPv6 Hop Limit set to 1.
(This test is for OSPF-DD> packet)

Test Report created at 2022-03-22 13:39:59 UTC Page 133 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-33.3 RFC 5340, sA.1 p57 Encapsulation of OSPF Packets

SHOULD Encapsulation of OSPF Packets

As such, the multicast addresses have been chosen with
link-local scope, and packets sent to these addresses should have
their IPv6 Hop Limit set to 1.
(This test is for OSPF-LSR> packet)

ANVL- RFC 5340, sA.1 p57 Encapsulation of OSPF Packets

OSPFV3-33.4
Encapsulation of OSPF Packets
SHOULD As such, the multicast addresses have been chosen with
link-local scope, and packets sent to these addresses should have
their IPv6 Hop Limit set to 1.
(This test is for OSPF-LSU> packet)

Test Report created at 2022-03-22 13:39:59 UTC Page 134 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-33.5 RFC 5340, sA.1 p57 Encapsulation of OSPF Packets

SHOULD Encapsulation of OSPF Packets

As such, the multicast addresses have been chosen with
link-local scope, and packets sent to these addresses should have
their IPv6 Hop Limit set to 1.
(This test is for OSPF-LSA> packet)

ANVL- RFC 5340, sA.1 p58 Encapsulation of OSPF Packets

OSPFV3-33.12
Encapsulation of OSPF Packets
SHOULD This multicast address has been assigned the value FF02::5. All
routers running OSPF should be prepared to receive packets
sent to this address.

Test Report created at 2022-03-22 13:39:59 UTC Page 135 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.1 p58 Encapsulation of OSPF Packets

OSPFV3-33.13
Encapsulation of OSPF Packets
MUST Hello packets are always sent to this destination
(AllSPFRouters).

ANVL- RFC 5340, sA.1 p58 Encapsulation of OSPF Packets

OSPFV3-33.14
Encapsulation of OSPF Packets
MUST This multicast address has been assigned the value FF02::6. Both
the Designated Router and Backup Designated Router must be
prepared to receive packets destined to this address.
(This test is for Designated Router.)

FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0: FreeBSD FreeBSD FreeBSD 12.0: FreeBSD 12.0: FreeBSD 12.0:
untested untested untested untested unpredict unpredict untested untested untested
12.0: pass 12.0: pass

Test Report created at 2022-03-22 13:39:59 UTC Page 136 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-33.15 RFC 5340, sA.1 p58 Encapsulation of OSPF Packets

MUST Encapsulation of OSPF Packets

This multicast address has been assigned the value FF02::6. Both
the Designated Router and Backup Designated Router must be
prepared to receive packets destined to this address.
(DUT is in state DROther)

ANVL- RFC 5340, sA.1 p58 Encapsulation of OSPF Packets

OSPFV3-33.16
Encapsulation of OSPF Packets
MUST This multicast address has been assigned the value FF02::6. Both
the Designated Router and Backup Designated Router must be
prepared to receive packets destined to this address.
(This test is for Backup Designated Router.)

Test Report created at 2022-03-22 13:39:59 UTC Page 137 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.1
The Options Field
SHOULD V6-bit
If this bit is clear, the router/link should be excluded from
IPv6 routing calculations.

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.2 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

The E-bit represents OSPF"s ExternalRoutingCapability. This bit
should be set in all LSAs associated with the backbone.

Test Report created at 2022-03-22 13:39:59 UTC Page 138 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.3 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

The E-bit represents OSPF"s ExternalRoutingCapability. This bit
should be set in all LSAs associated with (non-backbone)
non-stub areas.
(This test checks for Network-LSA)

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.4 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

The E-bit represents OSPF"s ExternalRoutingCapability. This bit
should be set in all LSAs associated with (non-backbone)
non-stub areas.
(This test checks for Inter-Area-Router-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 139 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.5 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

E-bit should be reset (set to 0) in all router-LSAs associated
with a stub area.

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.6 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

E-bit should be reset (set to 0) in all router-LSAs associated
with a stub area.

Test Report created at 2022-03-22 13:39:59 UTC Page 140 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.7 RFC 2328, s12.1.2 p117 Options

SHOULD The Options Field

E-bit should be reset (set to 0) in all network-LSAs associated
with a stub area.

ANVL- RFC 5340, sA.2 p59 The Options Field

OSPFV3-34.8
The Options Field
MUST R-bit This bit (the `Router" bit) indicates whether the originator
is an active router. ... Clearing the router bit would be
appropriate for a multi-homed host that wants to
participate in routing, but does not want to forward
non-locally addressed packets.

Test Report created at 2022-03-22 13:39:59 UTC Page 141 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.3.1 p61 The OSPF packet header

OSPFV3-35.1
The OSPF Packet Header
MUST Packets traversing a virtual link are labeled
with the backbone Area ID of 0.

ANVL- NEGATIVE
OSPFV3-35.2 RFC 5340, sA.3.1 p61 The OSPF packet header

MUST The OSPF Packet Header

Packets traversing a virtual link are labeled
with the backbone Area ID of 0.

Test Report created at 2022-03-22 13:39:59 UTC Page 142 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.3.1 p62 The OSPF packet header

OSPFV3-35.3
The OSPF Packet Header
MUST +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | Instance ID | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 These fields are reserved. They must be 0.
(NOTE: Here we are testing that the field following the
Instance ID field is set to 0 in the OSPFv3 Packet Header)

ANVL- RFC 5340, sA.3.2 p62 The Hello Packet

OSPFV3-36.1
The Hello Packet
MUST All routers connected to a common link must agree on certain
parameters (HelloInterval and RouterDeadInterval). Thes e
parameters are included in Hello packets allowing differences
can inhibit the forming of neighbor relationships.
(This test is for HelloInterval.)

Test Report created at 2022-03-22 13:39:59 UTC Page 143 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.3.2 p62 The Hello Packet

OSPFV3-36.2
The Hello Packet
MUST All routers connected to a common link must agree on certain
parameters (HelloInterval and RouterDeadInterval). These
parameters are included in Hello packets allowing differences
can inhibit the forming of neighbor relationships.
(This test is for RouterDeadInterval.)

ANVL- RFC 5340, sA.4.1.1 p70 Prefix Options

OSPFV3-37.1
Prefix Options
SHOULD NU-bit
The "no unicast" capability bit. If set, the prefix should be
excluded from IPv6 unicast calculations

Test Report created at 2022-03-22 13:39:59 UTC Page 144 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.4.3 p75 Router-LSAs

OSPFV3-38.1
Router-LSAs
MUST bit V
When set, the router is an endpoint of one or more fully
adjacent virtual links having the described area as Transit
area (V is for virtual link endpoint).

ANVL- RFC 5340, sA.4.5 p77 Inter-Area-Prefix-LSAs

OSPFV3-39.1
Inter-Area-Prefix-LSAs
MUST Default summary routes are used in stub areas instead of
flooding a complete set of external routes. When describing a
default summary route, the inter-area-prefix-LSA"s PrefixLength
is set to 0.

Test Report created at 2022-03-22 13:39:59 UTC Page 145 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.4.5 p78 Inter-Area-Prefix-LSAs

OSPFV3-39.2
Inter-Area-Prefix-LSAs
MUST When the Inter-Area-Prefix-LSA is describing a route to a range
of addresses (see Section C.2) the cost is set to the maximum
cost to any reachable component of the address range.
(Note: we are testing that the metric of nter-Area-Prefix-LSA
from DUT will be greater than the Advertised Value)

ANVL- RFC 5340, sA.4.10 p85 Intra-Area-Prefix-LSAs

OSPFV3-40.1
Intra-Area-Prefix-LSAs
SHOULD If Referenced LS type is 0x2001, the prefixes are associated with a
router-LSA, Referenced Link State ID should be 0 and Referenced
Advertising Router should be the originating router"s
Router ID.

Test Report created at 2022-03-22 13:39:59 UTC Page 146 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sA.4.10 p85 Intra-Area-Prefix-LSAs

OSPFV3-40.2
Intra-Area-Prefix-LSAs
SHOULD If Referenced LS type is 0x2002, the prefixes are associated with a
network-LSA, Referenced Link State ID should be the Interface ID
of the link"s Designated Router and Referenced Advertising
Router should be the Designated Router"s Router ID.

ANVL- RFC 5340, sB p86 Architectural Constants

OSPFV3-41.2 RFC 2328, sB p218 Architectural Constants

MUST Architectural Constants

LSInfinity is the metric value indicating that the destination
described by an LSA is unreachable. Used in summary-LSAs as an
alternative to premature aging. It is defined to be the 24-bit
binary value of all ones: 0xffffff.
(Type 3 Summary-LSA has been renamed as Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 147 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 5340, sB p86 Architectural Constants

OSPFV3-41.3 RFC 2328, sB p218 Architectural Constants

MUST Architectural Constants

LSInfinity is the metric value indicating that the destination
described by an LSA is unreachable. Used in AS-external-LSAs as an
alternative to premature aging. It is defined to be the 24-bit
binary value of all ones: 0xffffff.

ANVL- RFC 5340, sC.3 p89 Router Interface Parameters

OSPFV3-42.1
Router Interface Parameters
MUST Instance ID
The OSPF protocol instance associated with this OSPF interface.
Defaults to 0.

Test Report created at 2022-03-22 13:39:59 UTC Page 148 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, s2.3 p23 Use of external routing information

OSPFV3-43.1
RFC 2328 Compatibility
MUST External routing information is flooded unaltered throughout the
AS.

ANVL- RFC 2328, s10 p81 The neighbor Data Structure

OSPFV3-43.2
RFC 2328 Compatibility
MUST The initialize(I), more (M) and master(MS) bits, Options field,
and DD sequence number contained in the last Database
Description packet received from the neighbor are used to
determine whether the next Database Description packet received
from the neighbor is a duplicate.

Test Report created at 2022-03-22 13:39:59 UTC Page 149 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- NEGATIVE
OSPFV3-43.3 RFC 2328, s10 p81 The neighbor Data Structure

MUST RFC 2328 Compatibility

The initialize(I), more (M) and master(MS) bits, Options field,
and DD sequence number contained in the last Database
Description packet received from the neighbor are used to
determine whether the next Database Description packet received
from the neighbor is a duplicate.

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.4
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the router
originates a newer instance of one of its self-originated LSAs.
(This test checks for Router-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 150 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.5
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the router
originates a newer instance of one of its self-originated LSAs.
(This test checks for Network-LSA)

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.6
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the router
originates a newer instance of one of its self-originated LSAs.
(This test checks for Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 151 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.7
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the router
originates a newer instance of one of its self-originated LSAs.
(This test checks for Inter-Area-Router-LSA)

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.8
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the LSA ages out and
is flushed from the routing domain.
(This test is for Router-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 152 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.9
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the LSA ages
out and is flushed from the routing domain.
(This test is for Network-LSA)

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.10
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the LSA ages out and
is flushed from the routing domain.
(This test is for Inter-Area-Prefix-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 153 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.11
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the LSA
ages out and is flushed from the routing domain.
(This test is for Inter-Area-Router-LSA)

ANVL- RFC 2328, s12.2 p122 The link state database

OSPFV3-43.12
RFC 2328 Compatibility
MUST An LSA is deleted from a router"s database when the LSA
ages out and is flushed from the routing domain.
(This test is for AS-External-LSA)

Test Report created at 2022-03-22 13:39:59 UTC Page 154 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, sA.3.2 p194 The Hello packet

OSPFV3-43.13
RFC 2328 Compatibility
MUST If Router Priority set to 0, the router will be ineligible to
become Backup Designated Router.
(This test checks the case when router itself has Router
Priority 0)

ANVL- RFC 2328, sA.3.2 p194 The Hello packet

OSPFV3-43.14
RFC 2328 Compatibility
MUST If Router Priority set to 0, the router will be ineligible to
become Backup Designated Router
(This test checks the case when a neighbor has Router Priority 0)

Test Report created at 2022-03-22 13:39:59 UTC Page 155 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, sA.3.2 p194 The Hello packet

OSPFV3-43.15
RFC 2328 Compatibility
MUST If Router Priority set to 0, the router will be ineligible to
become Designated Router
(This test checks the case when router itself has Router
Priority 0)

ANVL- RFC 2328, sA.3.2 p194 The Hello packet

OSPFV3-43.16
RFC 2328 Compatibility
MUST If Router Priority set to 0, the router will be ineligible to
become Designated Router.
(This test checks the case when a neighbor has Router Priority 0)

Test Report created at 2022-03-22 13:39:59 UTC Page 156 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, sA.3.2 p194 The Hello packet

OSPFV3-43.17
RFC 2328 Compatibility
MUST If Router Priority set to 0, the router will be ineligible to
become Designated Router.
(This test checks the case when two router has Router Priority 0)

ANVL- RFC 2328, sA.3.6 p201 The Link State Acknowledgment packet
OSPFV3-43.18
RFC 2328 Compatibility
MUST A Link State Acknowledgment packet is sent either to the multicast
address AllSPFRouters, to the multicast address AllDRouters, or as
a unicast
(NOTE: This test is for multicast address AllSPFRouters)

Test Report created at 2022-03-22 13:39:59 UTC Page 157 of 158

RFC Compliance Test Report
OSPFV3 Results
Release Release Release Release Release Release Release Release Release Release Release
2.0.2 3.0.3 4.0 5.0.1 6.0.3 7.0.1 7.1 7.3 7.5 8.0 8.2.2

ANVL- RFC 2328, sA.3.6 p201 The Link State Acknowledgment packet
OSPFV3-43.19
RFC 2328 Compatibility
MUST A Link State Acknowledgment packet is sent either to the multicast
address AllSPFRouters, to the multicast address AllDRouters, or as
a unicast
(NOTE: This test is for multicast address AllDRouters)

ANVL- RFC 2328, sA.3.6 p201 The Link State Acknowledgment packet
OSPFV3-43.20
RFC 2328 Compatibility
MUST A Link State Acknowledgment packet is sent either to the multicast
address AllSPFRouters, to the multicast address AllDRouters, or as
a unicast
(NOTE: This test is for unicast address)

Test Report created at 2022-03-22 13:39:59 UTC Page 158 of 158

JNCIE SP v1.1 Technology Focused Workbook 2018
No ratings yet
JNCIE SP v1.1 Technology Focused Workbook 2018
28 pages
RIP Extended Results
No ratings yet
RIP Extended Results
18 pages
OSPF Extended Results
No ratings yet
OSPF Extended Results
93 pages
1 IPv6 Routing - Grundemann Hughes Sexton - FINAL1
No ratings yet
1 IPv6 Routing - Grundemann Hughes Sexton - FINAL1
128 pages
Ospf For Ipv6: Isp Workshops
No ratings yet
Ospf For Ipv6: Isp Workshops
28 pages
Net Topics
No ratings yet
Net Topics
42 pages
OSPFv 3
No ratings yet
OSPFv 3
22 pages
OSPF
No ratings yet
OSPF
10 pages
Exploring The Inner Workings of OSPF - BRKENT-1802
No ratings yet
Exploring The Inner Workings of OSPF - BRKENT-1802
58 pages
Brkipv 2418
100% (1)
Brkipv 2418
71 pages
IGP: Open Shortest Path First v3: Dr. Dimitrios Kalogeras Grnet
No ratings yet
IGP: Open Shortest Path First v3: Dr. Dimitrios Kalogeras Grnet
39 pages
Brkipv 2418
No ratings yet
Brkipv 2418
65 pages
Module 4 Protocols: Custom Training
No ratings yet
Module 4 Protocols: Custom Training
41 pages
Configure Juniper OSPF As The IGP
No ratings yet
Configure Juniper OSPF As The IGP
5 pages
BRKSPG-3612 Troubleshooting IOS-XR
No ratings yet
BRKSPG-3612 Troubleshooting IOS-XR
81 pages
Single Area OSPF Lab: Merida Vargas
No ratings yet
Single Area OSPF Lab: Merida Vargas
24 pages
Feature Guide Ospf v3 For Ipv6 TC
No ratings yet
Feature Guide Ospf v3 For Ipv6 TC
47 pages
Lab 8.3.3.6
No ratings yet
Lab 8.3.3.6
10 pages
BIRD Internet Routing Daemon: Introduction, Version 2.0.x
No ratings yet
BIRD Internet Routing Daemon: Introduction, Version 2.0.x
29 pages
IOS XR Basic Lab
No ratings yet
IOS XR Basic Lab
20 pages
Load Balanced Quangga
No ratings yet
Load Balanced Quangga
4 pages
Network Vulnerability
No ratings yet
Network Vulnerability
6 pages
7350 Wu
No ratings yet
7350 Wu
11 pages
R 2
No ratings yet
R 2
4 pages
Ospf
No ratings yet
Ospf
759 pages
Cis 185 CCNP Route Chapter 3: Implementing OSPF: Rick Graziani Cabrillo College Graziani@cabrillo - Edu Spring 2015
No ratings yet
Cis 185 CCNP Route Chapter 3: Implementing OSPF: Rick Graziani Cabrillo College Graziani@cabrillo - Edu Spring 2015
107 pages
CCNA
No ratings yet
CCNA
72 pages
Juniper OSPF
No ratings yet
Juniper OSPF
1,030 pages
HCIP Datacom Quick Notes
No ratings yet
HCIP Datacom Quick Notes
12 pages
Mini PC
No ratings yet
Mini PC
17 pages
RFC 2740
No ratings yet
RFC 2740
80 pages
Docs Frrouting Org Dev Guide en Latest
No ratings yet
Docs Frrouting Org Dev Guide en Latest
206 pages
9.2.2.9 Lab Configuring Multiarea OSPFv3
100% (1)
9.2.2.9 Lab Configuring Multiarea OSPFv3
13 pages
Filip BIRD Final N48
No ratings yet
Filip BIRD Final N48
28 pages
Eurobsdcon2024-Openbsd Vs Ipv6-Slides
No ratings yet
Eurobsdcon2024-Openbsd Vs Ipv6-Slides
33 pages
9.2.2.9 Lab - Configuring Multi-Area OSPFv3
No ratings yet
9.2.2.9 Lab - Configuring Multi-Area OSPFv3
8 pages
Open VSwitch Getting Started
No ratings yet
Open VSwitch Getting Started
6 pages
IOS Interior Routing Protocols
No ratings yet
IOS Interior Routing Protocols
1 page
Cis 185 CCNP Route Chapter 3: Implementing OSPF: Rick Graziani Cabrillo College Graziani@cabrillo - Edu Spring 2015
No ratings yet
Cis 185 CCNP Route Chapter 3: Implementing OSPF: Rick Graziani Cabrillo College Graziani@cabrillo - Edu Spring 2015
172 pages
Lesson 2 Quiz
No ratings yet
Lesson 2 Quiz
6 pages
RFC-1078 Network Wizards Inetd Inetd Inetd: TCPMUX - A Mostly Overlooked TCP Service
No ratings yet
RFC-1078 Network Wizards Inetd Inetd Inetd: TCPMUX - A Mostly Overlooked TCP Service
4 pages
02-Configuring Routing 2017
No ratings yet
02-Configuring Routing 2017
56 pages
OSPF
No ratings yet
OSPF
57 pages
LDonatoPTActivity 2.7.1
No ratings yet
LDonatoPTActivity 2.7.1
3 pages
Socket Prog With C
No ratings yet
Socket Prog With C
12 pages
Ospf GRE Ipsec
No ratings yet
Ospf GRE Ipsec
6 pages
6.2.3.9 Lab
No ratings yet
6.2.3.9 Lab
10 pages
Single Questions
No ratings yet
Single Questions
113 pages
BSCI Lab 13 PDF
No ratings yet
BSCI Lab 13 PDF
8 pages
Opensource Implementation of Ms Ris Server: Gianluigi Tiesi May 29, 2007
No ratings yet
Opensource Implementation of Ms Ris Server: Gianluigi Tiesi May 29, 2007
17 pages
Open Shortest Path First (OSPF) Protocol & Operation Overview
No ratings yet
Open Shortest Path First (OSPF) Protocol & Operation Overview
47 pages
CCNP Advanced Routing 4
No ratings yet
CCNP Advanced Routing 4
29 pages
Introduction To Netmiko
No ratings yet
Introduction To Netmiko
23 pages
Basic's of L2VPN and Its Features
No ratings yet
Basic's of L2VPN and Its Features
62 pages
Ethernet Datasheet 14pager V1
No ratings yet
Ethernet Datasheet 14pager V1
14 pages
Gcasr 9 Kvpls
No ratings yet
Gcasr 9 Kvpls
52 pages
The C Suite Report WSJ Forcepoint PDF
No ratings yet
The C Suite Report WSJ Forcepoint PDF
35 pages
Juniper Vpls Configuration Example
No ratings yet
Juniper Vpls Configuration Example
2 pages
VLan Some Basic Concepts PDF
No ratings yet
VLan Some Basic Concepts PDF
11 pages