Hello all, This is the revamped ANAME draft that I have been talking about at the DNS-OARC and RIPE meetings. It's basically rewritten to remove ANAME processing from authoritative query handling and instead describe it as part of the zone provisioning / maintenance process.
There is an "as if" clause which is intended to allow a wide variety of implementations; the view is that an auth server that does dynamic answer generation is actually a weird kind of primary master (since it controls the zone contents) however much it tries to work like a secondary. This is difficult to explain well, so comments and questions are encouraged! There is still ANAME processing in resolvers, as an optimization for ANAME targets that are dynamic based on the client's address. ANAME works without this extra feature, so no forklift upgrade is needed. DNSSEC compatibility is handled by never altering records if the client might be validating, and assumung that the client will do so itself if it cares. There are some pending edits to the draft which might make it into a -03 before the submission deadline, but I wanted to get this out for discussion sooner rather than later. The draft's git repo is still https://github.com/each/draft-aname My phone's autocorrect rechristened this effort "ANAME minimization" when I was trying to write a note to myself about QNAME minimization and NSEC negative answer synthesis and IPv6 reverse DNS... Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ an equitable and peaceful international order ---------- Forwarded message ---------- Date: Fri, 19 Oct 2018 06:24:36 -0700 From: internet-dra...@ietf.org To: Tony Finch <d...@dotat.at>, Evan Hunt <e...@isc.org>, Peter van Dijk <peter.van.d...@powerdns.com>, Anthony Eden <anthony.e...@dnsimple.com> Subject: New Version Notification for draft-ietf-dnsop-aname-02.txt A new version of I-D, draft-ietf-dnsop-aname-02.txt has been successfully submitted by Tony Finch and posted to the IETF repository. Name: draft-ietf-dnsop-aname Revision: 02 Title: Address-specific DNS aliases (ANAME) Document date: 2018-10-19 Group: dnsop Pages: 17 URL: https://www.ietf.org/internet-drafts/draft-ietf-dnsop-aname-02.txt Status: https://datatracker.ietf.org/doc/draft-ietf-dnsop-aname/ Htmlized: https://tools.ietf.org/html/draft-ietf-dnsop-aname-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-aname Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-aname-02 Abstract: This document defines the "ANAME" DNS RR type, to provide similar functionality to CNAME, but only for type A and AAAA queries. Unlike CNAME, an ANAME can coexist with other record types. The ANAME RR allows zone owners to make an apex domain name into an alias in a standards compliant manner. 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 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
