Comments about the test

No. Title Result Log Script Packet Dump
(bin)
Dump
(txt)
21 R flag vs. IsRouter flag WARN X X X Link0 Link0

Category

Commentaries

*** Test Summary: NA vs. IsRouter flag ***
P/FPTNEXPRESULTJDG

unicast rso NA w/o TLLexp:updatedresult:updatedPASS

unicast rsO NA w/o TLLexp:updatedresult:updatedPASS

unicast rSo NA w/o TLLexp:updatedresult:updatedPASS

unicast rSO NA w/o TLLexp:updatedresult:updatedPASS

unicast rso NA w/ TLLexp:updatedresult:updatedPASS

unicast rsO NA w/ TLLexp:updatedresult:updatedPASS

unicast rSo NA w/ TLLexp:updatedresult:updatedPASS

unicast rSO NA w/ TLLexp:updatedresult:updatedPASS
*multicast rso NA w/o TLL (INVALID)exp:unchangedresult:updatedWARN
*multicast rsO NA w/o TLL (INVALID)exp:unchangedresult:updatedWARN

multicast rSo NA w/o TLL (INVALID)exp:unchangedresult:unchangedPASS

multicast rSO NA w/o TLL (INVALID)exp:unchangedresult:unchangedPASS

multicast rso NA w/ TLLexp:updatedresult:updatedPASS

multicast rsO NA w/ TLLexp:updatedresult:updatedPASS

multicast rSo NA w/ TLL (INVALID)exp:unchangedresult:unchangedPASS

multicast rSO NA w/ TLL (INVALID)exp:unchangedresult:unchangedPASS

unicast rso NA w/ TLL, diff. LLAexp:unchangedresult:unchangedPASS

unicast rsO NA w/ TLL, diff. LLAexp:updatedresult:updatedPASS

unicast rSo NA w/ TLL, diff. LLAexp:unchangedresult:unchangedPASS

unicast rSO NA w/ TLL, diff. LLAexp:updatedresult:updatedPASS

multicast rso NA w/ TLL, diff. LLAexp:unchangedresult:unchangedPASS

multicast rsO NA w/ TLL, diff. LLAexp:updatedresult:updatedPASS

multicast rSo NA w/ TLL (INVALID), diff. LLAexp:unchangedresult:unchangedPASS

multicast rSO NA w/ TLL (INVALID), diff. LLAexp:unchangedresult:unchangedPASS

An implementation may update Rflag of an NCE when receiving an multicast NA w/o TLL. The NA is not invalid as a receiver side, whereas it is invalid as a sender side (please see the following). In such case, this test judges "WARN" that never means the implementation is wrong. The test intends to inform such behavior.

Sender side: 

4.4. Neighbor Advertisement Message Format Possible options: Target link-layer address The link-layer address for the target, i.e., the sender of the advertisement. This option MUST be included on link layers that have addresses when responding to multicast solicitations. When responding to a unicast Neighbor Solicitation this option SHOULD be included.
Receiver side:
7.1.2. Validation of Neighbor Advertisements A node MUST silently discard any received Neighbor Advertisement messages that do not satisfy all of the following validity checks: - The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router. - If the message includes an IP Authentication Header, the message authenticates correctly. - ICMP Checksum is valid. - ICMP Code is 0. - ICMP length (derived from the IP length) is 24 or more octets. - Target Address is not a multicast address. - If the IP Destination Address is a multicast address the Solicited flag is zero. - All included options have a length that is greater than zero.

References

Notes

Implementors information


[email protected]