On Tue, Oct 16, 2007 at 06:57:40PM +0200, Marcus Goller wrote: > Hence my suggestion to introduce a new status code, to tell the requestor > "Hey, we know that query type, but using it here is not supported. So go and Some protocols that extend from UDP->TCP like this create a status code or flag that indicates the question should be made via TCP. In those cases they simply answer the question to the extent that can be made to fit in the reply packet...something we can't (or shouldn't) do in DHCPv6's case. No one should think it is reasonable to attempt these queries over UDP and fall back to TCP. You try TCP first and last, no 'upgrade mechanism' is efficient here. So since any such status code is never going to be used assuming that implementations comply with the spec...I'd suggest just treating a UDP query with one of these types like it was garbage. Drop and (maybe) log. No reply, no new status code. -- Ash bugud-gul durbatuluk agh burzum-ishi krimpatul. -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins
Attachment:
pgpBkNefNwRee.pgp
Description: PGP signature
_______________________________________________ dhcwg mailing list dhcwg at ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg