> Good point; I changed the language here to refer to name server > sets for referral, and now explicitly state what you suggested: > > A resolver that tries to look up a name starts out at the root, > and follows referrals until it is referred to a name server set > that is authoritative for the name. If it is referred to a name > server set that is, based on the referral, only contains name > servers that are exclusively reachable via an IP address family > the resolver doe snot support, the resolver is unable to continue > DNS resolution. > > Does this work for you?
Two tiny changes. When starting from the root, there are in general multiple referrals. Any of them could cause a failure. This text makes the last referral special, which is not needed, but I don't object. However, then the text says: "based on the referral," and that should be "based on a referral," There is also "doe snot support". Otherwise perfectly fine. > I selected RECOMMENDED here, as it is, essentially, a straight > forward extension of the RFC9715 recommendations for TCP. However, > I also see your point and will change RECOMMENDED to MAY: I'd like to note here that I'm very curious if setting TCP MSS would reduce PMTU blackholes. In theory it should help. But it would require careful research to see how big the problem is today. And if setting the MSS at either end would improve the situation. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
