Re: [DNSOP] ANAME high-level benefit question

Dave Lawrence <tale@dd.org> Sat, 11 May 2019 08:54 UTC

Return-Path: <tale@dd.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 2F05C1200E0 for <dnsop@ietfa.amsl.com>; Sat, 11 May 2019 01:54:50 -0700 (PDT)
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 dFPYLXxexksM for <dnsop@ietfa.amsl.com>; Sat, 11 May 2019 01:54:48 -0700 (PDT)
Received: from gro.dd.org (host2.dlawren-3-gw.cust.sover.net [207.136.201.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B837C1200DE for <dnsop@ietf.org>; Sat, 11 May 2019 01:54:47 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id 377FAA60D; Sat, 11 May 2019 04:54:46 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <23766.36310.203310.826557@gro.dd.org>
Date: Sat, 11 May 2019 04:54:46 -0400
From: Dave Lawrence <tale@dd.org>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
In-Reply-To: <CAH1iCiqSYKxRTySvkRksw9x-LqaP3QELwrG9+ikzqQ5ykiYOkA@mail.gmail.com>
References: <CAH1iCiqSYKxRTySvkRksw9x-LqaP3QELwrG9+ikzqQ5ykiYOkA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jOMu4TXsY0c_lhqmmY-TxOgqjm4>
Subject: Re: [DNSOP] ANAME high-level benefit question
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, 11 May 2019 08:54:50 -0000

Brian Dickson writes:
> Have any "closed system" implementations of non-standard apex-CNAME
> hacks, committed publicly to neutral ANAME operations, presuming
> ANAME as currently envisioned?  I.e. If each such provider will
> ONLY support ANAME with targets on their own infrastructure, I don't
> think the standardization effort will have any real value.

I have a related question ... is allowing only targets on their own
infrastructure currently a limitation most such providers have?

I can't speak to Akamai's plans for implementing ANAME, but can say
that one of their apex-CNAME features allows any name to be used as a
target.  Their other feature allows only a subset of names on their
platform to be a target but that's an efficiency issue, not a policy
one, and I would expect their handling of ANAME to use that method
when appropriate or fall back to the general case otherwise.