-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patch applied, with a comment to explain the logging stuff.
Cheers,
Simon.
On 19/04/15 22:16, Vladislav Grishenko wrote:
Simon, thanks As for reasons, I guess, Steven thought it departs
from ordinal meaning of RFC and prevents his odhcp6c to
Simon, thanks
As for reasons, I guess, Steven thought it departs from ordinal meaning of
RFC and prevents his odhcp6c to work normally.
p.s in my previous mail was a typo, RFC 2119, of course, not 2219. sorry
Best Regards, Vladislav Grishenko
-Original Message-
From: Simon Kelley
Well, the general issue here is that indication of M- and O-Flags in the
RA is not a 100% clear indicator of what the DHCPv6 support on the link
is. Especially in the ISP-case O in practice does also mean: do stateful
DHCPv6, but only ask for IA_PD and not IA_NA. Since this is all so
ambiguous
Hi,
Per RFC 3315 17.2.1 the server MAY discard the Solicit message, but per
17.2.2, if the server will not assign any addresses to any IAs in a
subsequent Request from the client, the server MUST send an Advertise
message to client. Also, per RFC 2219 MAY is truly optional item, and MUST
be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My first reaction to this was to apply it, but then I went and looked
at RFC3315, and found this:
If the server will not assign any addresses to any IAs in a
subsequent Request from the client, the server MUST send an Advertise
message to
