Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

[Job Snijders <[e-mail]>]

On Fri, Oct 19, 2018 at 15:48 Mikael Abrahamsson <[e-mail]> wrote:

> On Fri, 19 Oct 2018, Job Snijders wrote:
>
> > Operating system implementers will be able to provide valuable feedback
> > to the working group on how to mitigate risk for some of the suspected
> > attack vectors - and it’ll be educational to see how this works in
> > practice. I think running code will improve this specification.
>
> I don't see how it would, since it doesn't mandate the hosts to do
> anything.


>
> "Dual stack hosts that have a good reason to use IPv4, for example for
>     a specific IPv4 link-local service, can attempt to do so.  Therefore
>     respect of the IPv6-Only flag is recommended, not mandatory, for
>     hosts."
>
> So this is just one more input into whatever heuristics a host might have
> to decide how to behave. For instance do more agressive exponential
> backoff for IPv4 operations but not turn it off completely.



I’m suggesting that two or three operating systems do something with the
flag. Demonstrate how the flag can be used and observe if there are any
gotchas.

If running code isn’t possible, I don’t think the document needs to be
published at all.

Kind regards,

Job