Re: [DNSOP] WGLC for draft-ietf-dnsop-tcp-requirements

John Kristoff <jtk@dataplane.org> Mon, 19 April 2021 11:57 UTC

Return-Path: <jtk@dataplane.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684183A2EB0 for <dnsop@ietfa.amsl.com>; Mon, 19 Apr 2021 04:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnPIwcszbIFN for <dnsop@ietfa.amsl.com>; Mon, 19 Apr 2021 04:57:38 -0700 (PDT)
Received: from dataplane.org (dataplane.org [IPv6:2001:49f0:d0c4:3::2]) by ietfa.amsl.com (Postfix) with ESMTP id EB1A23A2EAD for <dnsop@ietf.org>; Mon, 19 Apr 2021 04:57:37 -0700 (PDT)
Received: from p50.localdomain (localhost [127.0.0.1]) by dataplane.org (Postfix) with ESMTP id 4A8AA688001A; Mon, 19 Apr 2021 11:57:36 +0000 (UTC)
Date: Mon, 19 Apr 2021 06:57:35 -0500
From: John Kristoff <jtk@dataplane.org>
To: Joe Abley <jabley@hopcount.ca>
Cc: Suzanne Woolf <suzworldwide@gmail.com>, dnsop@ietf.org
Message-ID: <20210419065736.664af5c2@p50.localdomain>
In-Reply-To: <9FDEDB22-997A-479A-9EC8-818988BC1A79@hopcount.ca>
References: <93D82731-7B33-4E39-8DEF-FF6C14803191@gmail.com> <9FDEDB22-997A-479A-9EC8-818988BC1A79@hopcount.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1D6ZGyKwW4SYPTthuiYSJouTjzQ>
Subject: Re: [DNSOP] WGLC for draft-ietf-dnsop-tcp-requirements
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2021 11:57:42 -0000

On Mon, 19 Apr 2021 07:31:49 -0400
Joe Abley <jabley@hopcount.ca> wrote:

> NEW:
> 
>    The specification of the DNS allows both UDP and TCP to be used 
>    as transport protocols for exchanging unencrypted DNS messages.
>    However, for various reasons, the availability of TCP transport
>    has sometimes been interpreted as being optional.  This document 
>    clarifies the need to provide TCP transport for both clients and
>    servers and strengthens the requirement of DNS implementations
>    to support both.

Hi Joe,

Thanks for your careful read and thoughtful comments.  I would just
point out that there is already a document that specifically requires
this of the implementations, IETF RFC 7766.  This draft was
specifically aimed at operators, which have that document had
sidestepped "this document makes no specific requirements for
operators".  So maybe a simple "implementations" to "operators" change
of your text would work?

John