> >> The problem is we can't rely on it since it is not widely supported by >> clients. > Chicken and egg. If you put it in hnetd, the clients will come. Well, the thing is. Homenet is not really chartered for host changes and many believe that IPv4 support is sort of deprecated anyway.
> Yes there is, option 51; it's the time at which you unconditionally > discard a lease even if you didn't manage to rebind it. I think there > are some tradeoffs between decreasing T2 and decreasing the lease time, > and I'm not sure I fully understand what they are. OK, Good to know. > >> "The requirement L-9 is modified, in that the M flag MUST be set >> if and only if a router connected to the respective Common Link >> is advertising a non-zero H-capability. The O flag SHOULD >> always be set." > If I'm reading this correctly, you're saying that a Homenet router SHOULD > implement stateless DHCPv6. That seems like a somewhat arbitrary > requirement -- could you please explain the rationale? I think we discussed this already: https://mailarchive.ietf.org/arch/search/?email_list=homenet&gbt=1&index=4PT0dEjoh_rSVbxoqT8vHZho5_A ;) Cheers, Steven _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
