Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt

Tony Finch <dot@dotat.at> Tue, 18 April 2017 12:55 UTC

Return-Path: <dot@dotat.at>
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 66C4212EB9E for <dnsop@ietfa.amsl.com>; Tue, 18 Apr 2017 05:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_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 LpXfwiaP2q3v for <dnsop@ietfa.amsl.com>; Tue, 18 Apr 2017 05:55:01 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) (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 EA8E01205F0 for <dnsop@ietf.org>; Tue, 18 Apr 2017 05:55:00 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:60206) by ppsw-41.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1d0Sek-00030u-Qb (Exim 4.89) (return-path <dot@dotat.at>); Tue, 18 Apr 2017 13:54:54 +0100
Date: Tue, 18 Apr 2017 13:54:54 +0100
From: Tony Finch <dot@dotat.at>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
cc: Evan Hunt <each@isc.org>, dnsop <dnsop@ietf.org>
In-Reply-To: <CAJE_bqd03qfTs+9gXbwJJp5TJOiJG+mUDp8CxFfwmBWRq+2aOg@mail.gmail.com>
Message-ID: <alpine.DEB.2.11.1704181339350.4393@grey.csi.cam.ac.uk>
References: <20170407181139.GB66383@isc.org> <CAJE_bqd03qfTs+9gXbwJJp5TJOiJG+mUDp8CxFfwmBWRq+2aOg@mail.gmail.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1870870841-984481265-1492520094=:4393"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yKxtMgAQ-jL36mzowH1GKduqS2E>
Subject: Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.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: Tue, 18 Apr 2017 12:55:02 -0000

神明達哉 <jinmei@wide.ad.jp> wrote:
>
> I also wonder whether it's okay to allow 'AAAA or A' and ANAME to
> coexist for the same owner name.  Shouldn't it be prohibited similar
> to that CNAME and other types can't coexist?

From the point of view of a provisioning-side implementation of ANAME, the
A and AAAA records are pre-populated answers from the target name.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Sole: East or northeast 4 or 5. Slight or moderate. Fair. Good.