Re: [DNSOP] Genart last call review of draft-ietf-dnsop-terminology-bis-11

Joe Abley <jabley@hopcount.ca> Fri, 10 August 2018 16:50 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 053F1130F90 for <dnsop@ietfa.amsl.com>; Fri, 10 Aug 2018 09:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 A3IoqQ3U57gT for <dnsop@ietfa.amsl.com>; Fri, 10 Aug 2018 09:50:03 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 B666B130F12 for <dnsop@ietf.org>; Fri, 10 Aug 2018 09:50:03 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id u24-v6so4772795pfn.13 for <dnsop@ietf.org>; Fri, 10 Aug 2018 09:50:03 -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=O6wpI77SqOClQ215C1vRai8P+45kYWe+MPO8ARLFfyY=; b=D9tDYpIIGABzu0h7j3PQKeLhPBy0784kvlFEFRGuJp92MPT3Drmp5Uzzb3J+DvOdLx XlqJ2tTEpre9gRUUNQ+DlZDOl+4i+avciQe6pRYvhBmAAX0MzaqtJs/d0pTi64kRMptJ sLd0jr4pJ12jVGwKZFNDPntx2yCvKNrLldqaI=
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=O6wpI77SqOClQ215C1vRai8P+45kYWe+MPO8ARLFfyY=; b=cJO55n1KeuxADOwFVmB+WSSrTgdXvkCyh6uamGW70kS4bltP5ATkQW4nAv0SWB/oP6 xWZ4rWiGh3+TbYHmkByUh/HJgWZFXBKfcRmHtuSZZNfOjJErl0mbdGwfwz1vzvWxKh5S kuFKrrhM5SWX/oj+UFffzS+R402iammBK7BXdvvxZBhLrfOSAtmpqMPclFh766AxlHMk yksr5fO+d/yBbIdYX36VGWi1UNIUz7xfn0/x7V4yqBWIx9J8+gLU5x0/XnVyJ1TiDEXR CdG5rxELktknG2I6GVYot2vLoTKpLUsugppkWGwzaOp5j6llwvBcuoixkpU2EOCe2IY6 pkcA==
X-Gm-Message-State: AOUpUlHayyBkTHL2V3lXcWFeB9QUGHhusKNmcT9gq2e7NN/1KyTn6hBz GjGPwG2qS2e+SZv4iJyFQbWfzPwZwdg=
X-Google-Smtp-Source: AA+uWPzqNWDWLLYU1HU3nKdCEWK8rQYaNg0YqQgR/EK43aaxJ3mz5GaI3oI6AWeaajOB94+mFF/S3Q==
X-Received: by 2002:a63:1360:: with SMTP id 32-v6mr7324944pgt.159.1533919802884; Fri, 10 Aug 2018 09:50:02 -0700 (PDT)
Received: from [199.212.90.42] (23-233-21-69.cpe.pppoe.ca. [23.233.21.69]) by smtp.gmail.com with ESMTPSA id g28-v6sm20039519pfe.41.2018.08.10.09.50.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Aug 2018 09:50:01 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (15G77)
In-Reply-To: <802f2da7-9f05-6cc7-18b2-72d1e993a3d0@oracle.com>
Date: Fri, 10 Aug 2018 12:49:58 -0400
Cc: "Giovane C. M. Moura" <giovane.moura@sidn.nl>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6C35730-A840-4373-AB6B-E7B8B5B48006@hopcount.ca>
References: <153373205122.6368.16143820330220001109@ietfa.amsl.com> <C8F7BE0B-07B2-43F7-9710-06C0C05EDDAC@icann.org> <6E58094ECC8D8344914996DAD28F1CCD8BB306@DGGEMM506-MBX.china.huawei.com> <1c46806e-9e80-a14f-4f6b-44239e27e31d@sidn.nl> <E6DE5965-4390-4C0A-86E9-B5B7A333EA04@vpnc.org> <efc71dce-2ca8-33c9-4d78-77488d213b0b@sidn.nl> <802f2da7-9f05-6cc7-18b2-72d1e993a3d0@oracle.com>
To: Richard Gibson <richard.j.gibson@oracle.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Iys6Vxv1_4kVCSZAiOgtadgZkF4>
Subject: Re: [DNSOP] Genart last call review of draft-ietf-dnsop-terminology-bis-11
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 10 Aug 2018 16:50:11 -0000

Hi Richard,

I'd suggest that the unqualified nouns "question" and "answer" are sufficiently ambiguous as to be dead to us at this point.

I agree with the idea that a "response" is a DNS message generated in response to a query. Both "query" and "response" can be defined as DNS messages with particular values of QR observed in their respective headers.

I think "question" and "answer" can only usefully be used in other definitions as "question section" and "answer section". The document can certainly provide suggestions as to the set of meanings that other documents have previously ascribed to the bare nouns, but I think there ought to be a recommendation that they not be used in that way.


Joe

> On Aug 10, 2018, at 12:36, Richard Gibson <richard.j.gibson@oracle.com> wrote:
> 
> On 08/10/2018 11:51 AM, Giovane C. M. Moura wrote:
>>> The response is the entire DNS message that is sent in reply to a
>>> question.
>> Great. Do you plan to define it in the document as well?
> Analogous to a "response" DNS message containing an "answer" (presumably consisting of zero or more records), I'd be equally precise about a "query" DNS message containing a "question" (consisting of zero or more entries, but with any count other than 1 being essentially meaningless) and avoid conflating those terms.
> 
> https://tools.ietf.org/html/rfc1035#section-4.1.2 :
> > The question section is used to carry the "question" in most queries, i.e., the parameters that define what is being asked.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop