IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Mon, 19 April 2021 12:20 UTC

Return-Path: <jabley@hopcount.ca>
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 5F7CE3A2F4E for <dnsop@ietfa.amsl.com>; Mon, 19 Apr 2021 05:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 LKgmG5JfERVC for <dnsop@ietfa.amsl.com>; Mon, 19 Apr 2021 05:19:57 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F6973A2F6F for <dnsop@ietf.org>; Mon, 19 Apr 2021 05:19:50 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id f12so25853185qtf.2 for <dnsop@ietf.org>; Mon, 19 Apr 2021 05:19:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vtu5tHv5+DPN4098Mj1I59J4do26N/uMw7wC1bzuWbQ=; b=V0cp7IZdBbO0j3PbFsiFLuGXHZ4zLWT/WqYautQ63rlN1ys52GEvO7MlhGePSUaEGe bZNqIb35fyAmOKcPKT6t5l4G+4W/Qe+dBp4IytOOuTsCn7DLplQUYmc/mHsQcffhDagt wIAa7YGihck0Oh1GVIK/PQHaEI9FYFWCpwGwE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vtu5tHv5+DPN4098Mj1I59J4do26N/uMw7wC1bzuWbQ=; b=lDfFS5EYyDGS+3RuV9ipUGflwY2un8PaXeWej82gPJGkDTTJmR87Tj5D2SFqUxKULI lbtZuYbbKMCiyzvxBBxYWUbkFy4SQft2PQbhxbrh4VpHvbML9U2iaO9ORZ9A3KfMP5W8 bAFAczHGuyGP6ixEsysCJicMZot3sbcIyz+hwPEyGapxSByOxGfaB5tapmJjwF0a2gzB maev3tSOJNUWiaNSQQHGvIK15z3fUd90MSp97KSeA+uTP4vPaNfilO6ZQ0I9Jh8yM2yI KwZByRzk+kMZl9sB3PEBUM/M4dQ2nMdzL5V7DM0cUp6FqHs0j8C0f+KIuhUVh+yJtwQ9 Ffgw==
X-Gm-Message-State: AOAM533dzMiJ29MQFmFKY8O5abKlxlWgtHEgBt5JwKFzqXPd37BpAicy IPwEkoHlbGaXwGMo0E36DQJrXw==
X-Google-Smtp-Source: ABdhPJweB+b9n4nnYl2o6HoJzlHu/6PxhchBw5Ua2BeiU+kgHhOxiM46Oq9+53nCWWPqzm8bMppn0w==
X-Received: by 2002:ac8:7c56:: with SMTP id o22mr11461782qtv.80.1618834788230; Mon, 19 Apr 2021 05:19:48 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:e784:c7:a9e3:9dcf:2c3e:cd4c? ([2607:f2c0:e784:c7:a9e3:9dcf:2c3e:cd4c]) by smtp.gmail.com with ESMTPSA id m3sm10032813qkn.65.2021.04.19.05.19.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Apr 2021 05:19:47 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20210419065736.664af5c2@p50.localdomain>
Date: Mon, 19 Apr 2021 08:19:45 -0400
Cc: Suzanne Woolf <suzworldwide@gmail.com>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <39E30C82-A6DA-43CF-B7BC-4989F07E20F5@hopcount.ca>
References: <93D82731-7B33-4E39-8DEF-FF6C14803191@gmail.com> <9FDEDB22-997A-479A-9EC8-818988BC1A79@hopcount.ca> <20210419065736.664af5c2@p50.localdomain>
To: John Kristoff <jtk@dataplane.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/azjs05vkEePNGyTezIYYtRL-P2k>
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 12:20:02 -0000

Hi John,

On 19 Apr 2021, at 07:57, John Kristoff <jtk@dataplane.org> wrote:

> 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.
> 
> 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?

Oh, I missed that, sorry. Yes, I agree, "operators" makes sense.

Someone is going to ask whether this document, as a BCP, can update 1123 which pre-dates such designations as standard track. That person is not going to be me, however.


Joe

v2.23.0 | Report a Bug | By Email