Re: [dhcwg] Bulk Leasequery for DHCPv6

["Marcus Goller" <mgoller at gmail.com>]

Er, in a protocol sense, existing implementations already know what
to do with UnknownQueryType; if you add a new status code, they need
to know what to do with it as well.   Probably the behavior is the
same: fail.   So presumably you mean that the implementor might find
this confusing.   I guess I can see your point, but as long as the
protocol is well-specified, it really shouldn't be a problem.

Ok, just wanted to get my point across and get some opinions on it. ;-)

Yes, new implementations would need to be able to to know what to do with the new status code. But the new functionality needs some changes anyway, existing implementations, not supporting these new query types, would not see this new status code.
Is it required to make it work? No, I agree with you there. 
Different status codes could only make it easier to take the appropriate action on the requestor side and therefor minimize failed query attempts.

_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg