IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-ietf-dnsop-aname-01.txt

Stefan Bühler <ietf-dnsop@stbuehler.de> Fri, 26 January 2018 11:55 UTC

Return-Path: <ietf-dnsop@stbuehler.de>
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 A82EC12DA05 for <dnsop@ietfa.amsl.com>; Fri, 26 Jan 2018 03:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=stbuehler.de
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 9a7OJk-sEl7F for <dnsop@ietfa.amsl.com>; Fri, 26 Jan 2018 03:55:02 -0800 (PST)
Received: from mail.stbuehler.de (stbuehler.de [IPv6:2a01:4f8:a0:2276::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C02B12D960 for <dnsop@ietf.org>; Fri, 26 Jan 2018 03:55:02 -0800 (PST)
Received: from [IPv6:2a02:8070:a29c:5000:4d45:5ee8:71bb:2e67] (unknown [IPv6:2a02:8070:a29c:5000:4d45:5ee8:71bb:2e67]) by mail.stbuehler.de (Postfix) with ESMTPSA id A0FEAB80102 for <dnsop@ietf.org>; Fri, 26 Jan 2018 11:54:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stbuehler.de; s=stbuehler1; t=1516967699; bh=+cqfGZqxCLDJpuSHnGbreG2QBHYKpJx60wNYcylCkcc=; h=From:Subject:References:To:Date:In-Reply-To:From; b=zBAFI3E5NVpXdvDkYuecD5Caa4WlfK11GajoQHHL51sM/qk8BzrQeOqBJJK/mT60X EXTOKbKP7uk/6J4+7jHGsCLq6at0FmKtefXrkX9mbn0IPTFiALnvpIkovm9lbEPCdY ywuesSQL7hlB2cTMHddTRslOzXl2TsWIu212y0xo=
From: Stefan Bühler <ietf-dnsop@stbuehler.de>
References: <151573473976.18703.16142464801623244164@ietfa.amsl.com>
To: dnsop@ietf.org
Message-ID: <102bc41e-d2cf-e184-4bec-b1fdf945ae3e@stbuehler.de>
Date: Fri, 26 Jan 2018 12:54:59 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <151573473976.18703.16142464801623244164@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LzQ74WLIbGMZBztK4YxQqHjDtPk>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-aname-01.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: Fri, 26 Jan 2018 12:08:03 -0000

Hi!

I have concerns about the resolver replacing A/AAAA records in signed
zones as it breaks validation.

If a resolver understanding ANAME is queried using the DO=1 flag it
shouldn't touch the A/AAAA records, because it already knows the
requestor would through them away.

This also means a caching resolver should store the original A/AAAA
records (and not the ones resolved through ANAME) in the cache.

With this change I don't think it makes sense to say "a resolver MUST
re-query", I'd use "a resolver SHOULD re-query if it didn't use ECS and
the query didn't use DO=1".  But I'd add "a resolver MUST include ANAME
RRset in respones to queries for A/AAAA".

cheers,
Stefan

v2.23.0 | Report a Bug | By Email