On Thu, 29 Jul 2021, Jared Mauch wrote:
I think calling out that it’s possible people will create situations where a
name won’t resolve, is similar to what happens with routing that isn’t
deterministic as well. We should be defining how to determinsticly resolve a
name and highlight that it’s flexible enough you can configure it so it won’t
work.
Sounds reasonable. I'd also like us to keep in mind what our capitalized
words mean. MUST means "do this to interoperate". The only MUST I've
seen in this document is that servers MUST return all in-bailiwick glue.
I don't think there's anything harmful about returning sibling glue, but
it is 100% optional. Ignoring NS loops, anything you can get with sibling
glue you can get by another query, which makes it a MAY. Maybe two
queries are slower, maybe the single response with extra glue needed a
retry with TCP while the two simpler responses could each use UDP, so
maybe not.
Conflating it with in-bailiwick glue is 100% confusing, which I why I
think we should drop it and stick to the important point about all the
in-bailiwick glue.
Regards,
John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
