RE: draft-ietf-6man-slaac-renum: Text for the heuristics (Section 4.5)

[Vasilenko Eduard <[e-mail]>]

Hi Fernando,
I still do not agree.
The list of cases (when to send RS) looks comprehensive.

But it is not a big problem - I am arguing now just for document clarity.
It would not affect your solution if people would agree to send RSes at different times.
Hence, you could ignore me in this case.
Eduard
-----Original Message-----
From: Fernando Gont [mailto:[e-mail]] 
Sent: Tuesday, August 16, 2022 11:47 AM
To: Vasilenko Eduard <[e-mail]>; [e-mail]
Subject: Re: draft-ietf-6man-slaac-renum: Text for the heuristics (Section 4.5)

Hi, Eduard,

On 16/8/22 05:08, Vasilenko Eduard wrote:
> I do not agree. Section 6.7.3 has a very clear name "Sending Router 
> Solicitations" (assuming all cases) And the list of permitted cases is very strict:

The corresponding section does not provide a list of "permitted cases", but rather a recommendation on when to send Router Solicitations ("To obtain Router Advertisements quickly, a host SHOULD transmit up to...").


Additionally, Section 6.3.7 of RFC4861 says:

 >    When an interface becomes enabled, a host may be unwilling to wait
 >    for the next unsolicited Router Advertisement to locate default
 >    routers or learn prefixes.

That clearly refers to multicasted RSes.


Indeed, the same Section subsequently says:

 >    A host sends Router Solicitations to the all-routers multicast
 >    address.

Thanks,
--
Fernando Gont
SI6 Networks
e-mail: [e-mail]
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494