IETF Logo Mail Archive

Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-refuse-any-05.txt

Joe Abley <jabley@hopcount.ca> Mon, 05 March 2018 21:47 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 225DD12E059 for <dnsop@ietfa.amsl.com>; Mon, 5 Mar 2018 13:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 H4PgVmPFCDgA for <dnsop@ietfa.amsl.com>; Mon, 5 Mar 2018 13:47:33 -0800 (PST)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 E0B8412E034 for <dnsop@ietf.org>; Mon, 5 Mar 2018 13:47:32 -0800 (PST)
Received: by mail-it0-x22f.google.com with SMTP id k79so12100662ita.2 for <dnsop@ietf.org>; Mon, 05 Mar 2018 13:47:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=aOGi2SA5d+v5fJD+6LmVskQuaIqtMCPdz7156TcK0fk=; b=iOjNvY39+SIlwJNb8iasiMih7qppek36qFy3+u6thFrApSRc7hUd/3QBZ7s+MwaY6K pF+/epRIHkC55zMaiXG2k2yF9DelVAmi3fhvQwxg3VzJu1cjDjcbPB6sF/TfBk8U8Fq+ e80TPHkLxD5s5knQZfdhBudCHOkt4CLVTlXo0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=aOGi2SA5d+v5fJD+6LmVskQuaIqtMCPdz7156TcK0fk=; b=XPM5tKwtDlDYnr/1yo0LOH1NSTorHC5Jca8LqlfUORE/IYE2NFSSixXiCQxK3gJU3y TgMmxnnOXHHzIXO2XeCenZtkYvTXKNhVUBjQ6nCXH44Ppy7fayndv4Zu6Av3GD/HVBWG CbrTBt4et7lmi/ZxOIPVuwd4FjbBuZAPrbBeGPSFWENylUI8MGgNNFpIcI4eOIqba6Ti C0A1q/d3JlWqX6C14IA+Nv0bnSS2Mw1uEKsHDUfTaUT5sBVTpxoqGc6xA85RZsuVdqIn n5xjry40fbVHeyEB6lkTPdybtCcUETBl/3fHKv+1AAZBRTOpOBQEqvDtNicRNWlgOL1+ mMdg==
X-Gm-Message-State: AElRT7H7J8jhFF0dzSkGqtj6imGrr33sooSoqqD1eeyCPrd6j8lTx8r/ M0JfEHg9oFBk7OSEkD2O+hBlxA==
X-Google-Smtp-Source: AG47ELswnmXNSyKHmrHE+nCojb5oDYDEiFORUfKbO4+z+YlhgZcCei50axfU/9p4dIBrs39N/4Y24A==
X-Received: by 10.36.151.148 with SMTP id k142mr15947601ite.40.1520286452049; Mon, 05 Mar 2018 13:47:32 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:3:961:afdc:4a56:f253? ([2607:f2c0:101:3:961:afdc:4a56:f253]) by smtp.gmail.com with ESMTPSA id f69sm8986111iod.2.2018.03.05.13.47.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 13:47:30 -0800 (PST)
From: Joe Abley <jabley@hopcount.ca>
Message-Id: <A4996C28-8D61-4A36-9643-D0DB90A8E35B@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_9F443FE4-44B4-4972-9110-81096D3B8698"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 05 Mar 2018 16:47:29 -0500
In-Reply-To: <507d1fb7-8607-91d2-00b3-2e2aac5b98da@oracle.com>
Cc: dnsop <dnsop@ietf.org>
To: Richard Gibson <richard.j.gibson@oracle.com>
References: <152027747064.31710.8843129799069187895.idtracker@ietfa.amsl.com> <E9AB4737-2BD9-40BC-8194-6AA771C3E994@hopcount.ca> <507d1fb7-8607-91d2-00b3-2e2aac5b98da@oracle.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yVspVRfz2GpG1yPAZagLUefidkY>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-refuse-any-05.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 05 Mar 2018 21:47:39 -0000

On 5 Mar 2018, at 15:00, Richard Gibson <richard.j.gibson@oracle.com> wrote:

> To re-raise my unaddressed points:
> 
> 	• The document should include planned text you mentioned acknowledging lack of a signal to indicate "partial response" for section 4.1/section 4.3 subset responses ([1]).
> 	• "Conventional [ANY] response" is used but not defined ([2]).
> 	• The document needs to identify itself as updating RFC 1034 (specifically, section 4.3.2).
> 	• In section 7, "ANY does not mean ALL" is misleading—[RFC 1035 section 3.2.3] is clear about QTYPE=255 being "a request for **all** records" (emphasis mine). That said, the proposed response behavior is consistent with that RFC.
> [1]: https://www.ietf.org/mail-archive/web/dnsop/current/msg20629.html
> [2]: https://www.ietf.org/mail-archive/web/dnsop/current/msg20628.html
> [RFC 1035 section 3.2.3]: https://tools.ietf.org/html/rfc1035#section-3.2.3

Many apologies for missing those. Fortunately I had spare minutes before the cut-off. With luck the following will address those issues; if not, you can look forward to another rev in a couple of weeks.

Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-dnsop-refuse-any-06.txt
> Date: 5 March 2018 at 16:44:49 EST
> To: "Joe Abley" <jabley@afilias.info>, "Marek Majkowski" <marek@cloudflare.com>, "Olafur Gudmundsson" <olafur+ietf@cloudflare.com>
> 
> 
> A new version of I-D, draft-ietf-dnsop-refuse-any-06.txt
> has been successfully submitted by Joe Abley and posted to the
> IETF repository.
> 
> Name:		draft-ietf-dnsop-refuse-any
> Revision:	06
> Title:		Providing Minimal-Sized Responses to DNS Queries that have QTYPE=ANY
> Document date:	2018-03-05
> Group:		dnsop
> Pages:		11
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-dnsop-refuse-any-06.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-dnsop-refuse-any/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-dnsop-refuse-any-06
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-refuse-any-06
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-refuse-any-06
> 
> Abstract:
>   The Domain Name System (DNS) specifies a query type (QTYPE) "ANY".
>   The operator of an authoritative DNS server might choose not to
>   respond to such queries for reasons of local policy, motivated by
>   security, performance or other reasons.
> 
>   The DNS specification does not include specific guidance for the
>   behaviour of DNS servers or clients in this situation.  This document
>   aims to provide such guidance.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>

v2.23.0 | Report a Bug | By Email