Hi Greg.
- It performs address resolution on the solicitation's sender, creates a new Neighbor Cache entry, installs the link-layer address, sets its reachability state to STALE as specified in Section 7.3.3, and responds with a unicast Router Advertisement directed to the solicitation's sender.
I'm not sure if I get this. Why would the NCE be stale if there's been an NA response for the Router's NS?
It should be REACHABLE, using existing techniques.
Sorry, my mistake. You are absolutely right.
The new text suggested a couple of hours back no longer explicitly mentions the state, because the usual address-resolution procedure is used anyway and the state should therefore be clear.
- Christian
Greg Daley schrieb:
Hi Christian,
Christian Vogt wrote:
Hi Hesham,
hope this is not too late.
Not sure but the text may suggest to create NC state even if the RS did not contain a SLLAO. In this case, it's actually not necessary to create NC state, especially if the router chooses to respond with a multicast RA. If you agree, you could change the text from this...
[...] If there is no existing Neighbor Cache entry for the solicitation's sender, the router creates one, installs the link- layer address and sets its reachability state to STALE as specified in Section 7.3.3. If there is no existing Neighbor Cache entry and no Source Link-Layer Address option was present in the solicitation, [...]
...to this...
[...] If there is no existing Neighbor Cache entry for the solicitation's sender and a Source Link-Layer Address option was present in the solicitation, the router creates a new Neighbor Cache entry, installs the link-layer address and sets its reachability state to STALE as specified in Section 7.3.3. If there is no existing Neighbor Cache entry and no Source Link-Layer Address option was present in the solicitation, the router does either one of the following:
- It performs address resolution on the solicitation's sender, creates a new Neighbor Cache entry, installs the link-layer address, sets its reachability state to STALE as specified in Section 7.3.3, and responds with a unicast Router Advertisement directed to the solicitation's sender.
I'm not sure if I get this. Why would the NCE be stale if there's been an NA response for the Router's NS?
It should be REACHABLE, using existing techniques.
You could precis this to:
- It elects to perform unicast delivery, performs address resolution on Router Solicitation's sender, creating a new neighbour cache
entry. It delivers a unicast Router Advertisement when neighbour discovery completes.
- It responds with a multicast Router Advertisement.
Whether or not a Source Link-Layer Address option is provided in the solicitation, [...]
The rest is perfect, IMO.
Oh, just a nit: s/link- layer/link-layer/.
- Christian
Whether we need it, is another matter (to be discussed with Jinmei and others).
Greg
-- Christian Vogt, Institute of Telematics, University of Karlsruhe www.tm.uka.de/~chvogt/pubkey/
"No great genius has ever existed without some touch of madness." (Aristotle)
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
