v6onbydefault =============
semi-editorial --------------
Fixing the destination address selection mechanism by adding such a
rule is only a mitigating factor if applications use standard name
resolution API's that implement this mechanism, and these
applications try addresses in the order returned. This may not be an
acceptable assumption in some cases, as there are applications that
use hard coded addresses and address search orders (DNS resolver is
one example), and/or literal addresses passed in from the user. [...]
==> I think this, still, needs more explicit text. That is, this paragraph
is describing e.g., DNS resolvers which implement their own version of the
name resolution, and are not fixed by modifying the standard name
resolution. Unless I misunderstand this completely, maybe reword the
beginning to something like:
Fixing the destination address selection mechanism by adding such a
rule is only a mitigating factor if applications use their own versions
of name resolution APIs which do not implement the same functionality
as the standard name resolution APIs.