Re: [DNSOP] Call for Adoption: draft-song-atr-large-resp

Mukund Sivaraman <muks@mukund.org> Wed, 06 February 2019 08:08 UTC

Return-Path: <muks@mukund.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 7F67C126C7E for <dnsop@ietfa.amsl.com>; Wed, 6 Feb 2019 00:08:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 g38RAss_cBJA for <dnsop@ietfa.amsl.com>; Wed, 6 Feb 2019 00:08:38 -0800 (PST)
Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:151:2016::99]) by ietfa.amsl.com (Postfix) with ESMTP id 245AF12426E for <dnsop@ietf.org>; Wed, 6 Feb 2019 00:08:38 -0800 (PST)
Received: from jurassic.lan.banu.com (unknown [27.5.209.222]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 7272F5A40748; Wed, 6 Feb 2019 08:08:36 +0000 (GMT)
Date: Wed, 06 Feb 2019 13:38:32 +0530
From: Mukund Sivaraman <muks@mukund.org>
To: Benno Overeinder <benno@nlnetlabs.nl>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <20190206080832.GA14062@jurassic.lan.banu.com>
References: <BCACF554-8BE6-49BC-B75A-BCED776F5189@NLnetLabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BCACF554-8BE6-49BC-B75A-BCED776F5189@NLnetLabs.nl>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cz3dqrFdzGoDNmyqmIWUW_cJ7HE>
Subject: Re: [DNSOP] Call for Adoption: draft-song-atr-large-resp
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: Wed, 06 Feb 2019 08:08:43 -0000

On Fri, Jan 18, 2019 at 06:55:16PM +0100, Benno Overeinder wrote:
> Please review this draft to see if you think it is suitable for
> adoption by DNSOP, and comments to the list, clearly stating your
> view.

Considering that the method is implementable without any changes at a
resolver, and that it doesn't require compatible behavior among DNS
implementations ("protocol" or best practice), I suppose it does not
matter if this draft is adopted or not as long as the idea has been
described somewhere.

		Mukund