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

Joe Abley <jabley@hopcount.ca> Mon, 05 March 2018 19:28 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DA41812E040 for <dnsop@ietfa.amsl.com>; Mon, 5 Mar 2018 11:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bM4GSNjPbvHq for <dnsop@ietfa.amsl.com>; Mon, 5 Mar 2018 11:28:42 -0800 (PST)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 1140312D93E for <dnsop@ietf.org>; Mon, 5 Mar 2018 11:28:41 -0800 (PST)
Received: by mail-io0-x22b.google.com with SMTP id u84so19224920iod.9 for <dnsop@ietf.org>; Mon, 05 Mar 2018 11:28:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:subject:message-id:references:to:date; bh=MXe2uQpVJ9RNF8MEjeczqijqRqwWBJy7Qy2LekzKYuc=; b=lsNBjEV8zhwqqyp3d6fBzqUaviiTdN/Sv/sxipe1nXDALhlCqJl9YamyZodBxk09mL DTVFsHwiCKPAYNr8jDD1mc60UuMAYInjPlWcQ+STiB+N2fctWq0JYj8nNgTrqmmb+5K/ Li7af4L6otzdo0i9TLJfhw6rUSXs47JDCdJmw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:references :to:date; bh=MXe2uQpVJ9RNF8MEjeczqijqRqwWBJy7Qy2LekzKYuc=; b=fyof3nEBbfDV6l1/p8+vWSn5Scx9/cAyuQI162tzuPgxP0KzG/0v4BnOjbFRAo9iMg OxVnsn0BEBwCRzs7Cs7TAS/7w/DfnZxnZNk5Ixo5ps08iV+84svVDcPuBFKlsA2yuBQp i/8khmLm2WdI2aRgA3r9coeaC3DiePMHqMIRgT3rw8jNdbHbRaMsFOa+3RBsTLSMyOAJ pw8nrECbNYiTKtYS4YbUhOPujeDIzah2Zmc7L0ZTbge6UFev010mKtvOHUXGnpGk74+Y X+EucuPIa6l8Jv9zRlVZbtXsoNUsprtOdz6mkfXoR+Pm0li0Lerb3VB2b3UsaofbBhQ+ n2oQ==
X-Gm-Message-State: APf1xPDvpXLfFhMtEjjl3JZeYrTOhcEzvIRNMmuh/9pMlT75uqZPoekj 3uZk821/EibKrvRx01/d33jHyrOToGg=
X-Google-Smtp-Source: AG47ELvl3dlGVYh4Q/hfoltEE8g0cSjzGfCEEZX3ZWn5HthNjDfRVd7A21OzgNuE/XwkkQx+1KWzAg==
X-Received: by with SMTP id z20mr18641119ioi.274.1520278120137; Mon, 05 Mar 2018 11:28:40 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:203:5d7d:5d8d:4cd8:9f6? ([2607:f2c0:101:203:5d7d:5d8d:4cd8:9f6]) by smtp.gmail.com with ESMTPSA id x72sm5086907ite.26.2018. for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 11:28:39 -0800 (PST)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_671BD321-32DB-4531-AB38-32ED95F97D96"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <E9AB4737-2BD9-40BC-8194-6AA771C3E994@hopcount.ca>
References: <152027747064.31710.8843129799069187895.idtracker@ietfa.amsl.com>
To: dnsop <dnsop@ietf.org>
Date: Mon, 5 Mar 2018 14:28:37 -0500
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/chJQ5gn6UUkuh0R8Y6DHUPP92_A>
Subject: [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 19:28:47 -0000

Hi all,

Per subject, see below, etc. I apologise for the ludicrous amount of time it has taken for me to do these final edits. Fortunately the beatings continued until the morale improved.

I believe the -05 represents a reasonable facsimile of the consensus of suggestions that came up at the working group last call, which some of you may recall (others are no doubt too young). Apart from language changes, the principal change from the -04 is a softening of the language regarding RRSIG, basically punting any such specification to future work whilst observing the potential for alignment in approach. This seemed like a reasonable compromise and arguably better than specifying behaviour without the benefit of real-world experience or detailed RRSIG-specific thinking.


> Begin forwarded message:
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-dnsop-refuse-any-05.txt
> Date: 5 March 2018 at 14:17:50 EST
> To: "Joe Abley" <jabley@afilias.info>fo>, "Marek Majkowski" <marek@cloudflare.com>om>, "Olafur Gudmundsson" <olafur+ietf@cloudflare.com>
> A new version of I-D, draft-ietf-dnsop-refuse-any-05.txt
> has been successfully submitted by Joe Abley and posted to the
> IETF repository.
> Name:		draft-ietf-dnsop-refuse-any
> Revision:	05
> Title:		Providing Minimal-Sized Responses to DNS Queries that have QTYPE=ANY
> Document date:	2018-03-05
> Group:		dnsop
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-dnsop-refuse-any-05.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-dnsop-refuse-any/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-dnsop-refuse-any-05
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-refuse-any-05
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-refuse-any-05
> 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