Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-aname-02.txt

Tim Wicinski <tjw.ietf@gmail.com> Sat, 20 October 2018 09:42 UTC

Return-Path: <tjw.ietf@gmail.com>
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 36925128CFD for <dnsop@ietfa.amsl.com>; Sat, 20 Oct 2018 02:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dspIZYAiASYC for <dnsop@ietfa.amsl.com>; Sat, 20 Oct 2018 02:42:22 -0700 (PDT)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 624E7126BED for <dnsop@ietf.org>; Sat, 20 Oct 2018 02:42:22 -0700 (PDT)
Received: by mail-it1-x135.google.com with SMTP id h6-v6so5984128ith.0 for <dnsop@ietf.org>; Sat, 20 Oct 2018 02:42:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=11PYicFaw09u261NKQiwNNwf+6j4gKRf8Vj9UcMxkyw=; b=g0Qjj1IchFuB4wGcDo8OiV5yhqzfGuqYGMKHR9ge89+T54WM9WsPCPi9FpzdPx2xc5 dV5rY+M8dE/d59ay4neAjT/1eDUAePX4juZLberNeOuCW7dZDn3XRheQkgbwjFMZ/q3n AIqlBkIltAI+XC5Iv+Gn4z4Oi2GYRMQS+ZAqY6zLt3XVkHFB5FJHwyQS2q01U3Rq+fFs PSo+vBeYLVqMBsT5LUySDZJpiTnGScTMyaukyRXfhkaT9cKO5Qv5AqwCKFuqwpmSH2NQ Mid06iO96fdtikWAfSArnR2vSLjFwzHhpqORjzm8X02Y4lShZZBwkn2TZp23UwRWvzzc PLSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=11PYicFaw09u261NKQiwNNwf+6j4gKRf8Vj9UcMxkyw=; b=P2IUnKxHvKUHZ3AqYTiDbMCbElWID9l1omqqHw4JGREASokOLGPaOPa/Z0OxzXkr0F mdObN5QpurcSQdTOUvAq2bJCC151HEbaYjUAhoxVNS39tsrcJ5qb+3PqNfwWM4b/JIZd 7a6zS+iUqFdusAL0cjxU1cEa/uPMsyInt1PljopppkwiU+9/IVAMB9agnaiySHPFOEYW ZOpj/r/IpIthIihpAWSE+lqu/FWDDAMQ7SvHhFzwpFgGo+RxH0Rpd0p57i+pXttiV6wo iwBu89tpkVPyv9jWnIVmmQUkAttoTPI7tQvcjoyjYtJTorptTMIG/PvPYrgsWBRpYjJj bKDw==
X-Gm-Message-State: ABuFfogEfa16Ou0mKWg0MDV3JXyJl9WnVYzLB17UfheLBxu0GfjdrB2q SVaeJetxLFDR5n9pKILWM+tljmbJeGMRcf1iAEZL2u+i
X-Google-Smtp-Source: ACcGV61ogzx43wJXlxcZEuBDsbr5C8CKnAKjHHvE/eBvLvHcV5ubNZWmcJjaQXVbz8WrLeEIRx5jZLOm8IzO2X7FPeU=
X-Received: by 2002:a02:844c:: with SMTP id l12-v6mr29864236jah.137.1540028541508; Sat, 20 Oct 2018 02:42:21 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.DEB.2.20.1810191639120.2662@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.20.1810191639120.2662@grey.csi.cam.ac.uk>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sat, 20 Oct 2018 05:42:12 -0400
Message-ID: <CADyWQ+E7xzn11PNuTeq8DN1QMU+yZRZeKMVMEfXyeL9Acfts-g@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002923cb0578a5d614"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gcnEDbqPq7hZ9Xicu3g2xKhQUgI>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-aname-02.txt
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: Sat, 20 Oct 2018 09:42:25 -0000

Working Group

I spent some time this evening reading over the updated draft, and there
has been significant work to help move this forward.
I would encourage others to review it also.

The Chairs are going to put this on the schedule for Bangkok.  We should be
able to walk through the changes and listen for the complaints.

thanks
Tim


On Fri, Oct 19, 2018 at 12:14 PM Tony Finch <dot@dotat.at> wrote:

> 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  <dot@dotat.at>  http://dotat.at/
> an equitable and peaceful international order
>
> ---------- Forwarded message ----------
> Date: Fri, 19 Oct 2018 06:24:36 -0700
> From: internet-drafts@ietf.org
> To: Tony Finch <dot@dotat.at>at>, Evan Hunt <each@isc.org>rg>,
>     Peter van Dijk <peter.van.dijk@powerdns.com>om>,
>     Anthony Eden <anthony.eden@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
>