Re: WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023

Michael Richardson <[email protected]> Tue, 09 Jan 2024 09:16:17 -0500

Newsgroups	gmane.ietf.dhc
Message-ID	<[email protected]>

Jen Linkova <[email protected]> wrote:
    >> I'm not claiming a new security issue, I'm claiming that finding these kinds
    >> of things is exactly the problem we are trying to diagnose.

    > I do not think the primary use case here is "finding rogue DHCP
    > servers", to be honest.

No, its finding broken things on the network :-)

    >> But, I see your point, one could just observe the latest announcement.
    >>
    >> Well, I don't know then, the simpler solution is appealing.

    > By the simplest you mean "once the client starts sending, it doesn't stop"?
    > Are you (and the group) OK with 'cons' (such as 'if the administrator
    > wants to turn it off, it might need to
    > bounce the client's connection.')?

I'm rather okay with this.

    >> Is this the ADDR-REG-INFORM message, or another information request?

    > I'm not sure I understand the question. The client sent a packet (e.g.
    > Information request) which includes OPTION REQUEST OPTION containing
    > OPTION_ADDR_REG_ENABLE code and got a response w/o
    > OPTION_ADDR_REG_ENABLE option back.
    > What's now?
    > Stop? Continue sending?

If it was the first such message, then it didn't start.
If it was running before, I think that continuing is preferrable to
oscilating.  I think that oscillating will be worse for diagnostics.

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

_______________________________________________
dhcwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dhcwg

signature.asc (application/pgp-signature, 515 B)