On Mon, 1 Jul 2019, Petr Špaček wrote: [broken record on]
I would only add reference to https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/ + DNS Flag Day 2020, which is going to effectivelly kill UDP fragmentation in DNS and thus require TCP for perfect operation.
The internet does not do "flag days". Please stop calling it flag days. We recommend, via SHOULD's or MUST's what implementers should implement. Obsolete things gradually fade out over time. Please read these RFCs on how to obsolete things in protocols or software without using "flag days": - RFC 8624 - RFC 8247 - RFC 8221 These RFC's obsolete a number of things, gradually. It changes items for implementors from MUST to SHOULD to SHOULD NOT to MUST NOT. You can tell implementors MUST NOT. It's nice if you coordinate this with a number of leading opensource implementers to release on a specific date, but that's unrelated to the RFC being published. Please stop the misleading phrase of "flag day". There is no flag day for internet users nor internet implementors. That's not how any of the internet works.
Maybe we could add something along these lines around end of section-2.4: Problems caused by IP fragmentation are described at length in document https://tools.ietf.org/html/draft-ietf-intarea-frag-fragile . One of possible approaches to workaround this problem is lowering EDNS buffer size to values which do not cause IP fragmentation. In fact, such coordinated change is planned for year 2020 [http://dnsflagday.net/2020/].
Definitely not include a url with "dnsflagday" in the name. (in general, RFC's do not reference external URL's unless strictly needed, because RFCs tend to outlive ephemeral websites, so even without 'flagday' I would not recommend the URL for inclusion in the draft) Paul _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
