all, short and sweet document; a few comments if I may.
- this new behaviour is supposed to be implemented by all hosts, right?
shouldn't this document then update rfc4861?
- "AP" isn't defined section 1.
- section 1 bullet b. couldn't you argue that turning off periodic RAs is a
configuration error?
- section 1 bullet c. If a link isn't multicast capable, you couldn't send RS
in the general case either.
ISATAP has special provisions for that. could you
make c) more general?
- section 2.1. "…results in a default route". is awkward. this is the function
we call "router discovery" in rfc4861,
where the host discovers a "default router". perhaps just
copy or reference rfc4861 verbatim:
"Once the host sends a Router Solicitation, and receives a valid
Router Advertisement with a non-zero Router Lifetime, the host MUST
desist from sending additional solicitations on that interface, until
the next time one of the above events occurs. Moreover, a host
SHOULD send at least one solicitation in the case where an
advertisement is received prior to having sent a solicitation.
Responses to solicited advertisements may contain more information
than unsolicited advertisements."
Best regards,
Ole
signature.asc
Description: Message signed with OpenPGP using GPGMail
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
