[DNSOP] Re: Fwd: New Version Notification for draft-tojens-dnsop-do-not-accommodate-udp53-00.txt

Sun, 06 Jul 2025 11:37:24 -0700


“ These complications can be avoided by assuming Classic DNS over TCP is the only form of Classic DNS that new protocols need to accommodate.”

This is not how protocols using DNS work. You can’t say “new” protocols must use only a specific flavour of DNS transport as it’s mostly not up to the new protocol or application how DNS is resolved.

This is at least 10 years too soon.

Paul



Sent using a virtual keyboard on a phone

On Jul 6, 2025, at 14:30, Tommy Jensen <[email protected]> wrote:

 Happy Second to Last I-D Submission Day!

This draft is short and to the point: it's time to stop accommodating Classic DNS over UDP when writing new protocols that can use encrypted DNS or Classic DNS over TCP instead. This draft is super short, so please see it for my arguments.

Thoughts?

Thanks,
Tommy


-------- Forwarded Message --------
Subject: New Version Notification for draft-tojens-dnsop-do-not-accommodate-udp53-00.txt
Date: Sun, 06 Jul 2025 11:16:40 -0700
From: [email protected]
To: Tommy Jensen <[email protected]>


A new version of Internet-Draft
draft-tojens-dnsop-do-not-accommodate-udp53-00.txt has been successfully
submitted by Tommy Jensen and posted to the
IETF repository.

Name: draft-tojens-dnsop-do-not-accommodate-udp53
Revision: 00
Title: Do Not Accommodate Classic DNS over UDP
Date: 2025-07-06
Group: Individual Submission
Pages: 5
URL: https://www.ietf.org/archive/id/draft-tojens-dnsop-do-not-accommodate-udp53-00.txt
Status: https://datatracker.ietf.org/doc/draft-tojens-dnsop-do-not-accommodate-udp53/
HTML: https://www.ietf.org/archive/id/draft-tojens-dnsop-do-not-accommodate-udp53-00.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-tojens-dnsop-do-not-accommodate-udp53


Abstract:

Protocols that rely on Classic DNS have to account for considerations
that only apply to UDP, such as message fragmentation. However, DNS
implementations are already required to support both TCP and UDP, and
using TCP would alleviate these considerations. This document
specifies that new protocols with a dependency on Classic DNS do not
need to account for the limitations of Classic DNS over UDP and can
instead expect implementations to use Classic DNS over TCP.



The IETF Secretariat


_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to