IETF Logo Mail Archive

Re: [DNSOP] Any website publishers who use CDNs on the list?

Joel Jaeggli <joelja@bogus.com> Fri, 02 November 2018 23:06 UTC

Return-Path: <joelja@bogus.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 CB1E6130DFC for <dnsop@ietfa.amsl.com>; Fri, 2 Nov 2018 16:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=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 GmK5X6CXuFyg for <dnsop@ietfa.amsl.com>; Fri, 2 Nov 2018 16:06:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 0D52B130DC5 for <dnsop@ietf.org>; Fri, 2 Nov 2018 16:06:45 -0700 (PDT)
Received: from [172.20.5.232] (110-170-235-6.static.asianet.co.th [110.170.235.6]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id wA2N6cI0039352; Fri, 2 Nov 2018 23:06:43 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host 110-170-235-6.static.asianet.co.th [110.170.235.6] claimed to be [172.20.5.232]
From: Joel Jaeggli <joelja@bogus.com>
Message-Id: <8EBFB9C8-8F99-4128-A0F2-3D87DD8619F1@bogus.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F353790B-0115-4075-81FF-730746536575"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Sat, 03 Nov 2018 06:06:37 +0700
In-Reply-To: <CCEEBCEF-FE91-49A6-96FE-122A5E025159@isoc.org>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
To: Dan York <york@isoc.org>
References: <CCEEBCEF-FE91-49A6-96FE-122A5E025159@isoc.org>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sQxcYHQ1trAuJqvxWydPQvVrVjY>
Subject: Re: [DNSOP] Any website publishers who use CDNs on the list?
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: Fri, 02 Nov 2018 23:06:47 -0000


> On Nov 2, 2018, at 17:57, Dan York <york@isoc.org> wrote:
> 
> Are there any other publishers of websites on this list who use CDNs in front of their sites - and who are interested in the whole “CNAME at apex” issue?
> 
> Given the ANAME discussions and other continuing “CNAME at apex” discussions, I started putting together a short draft clearly stating the problem statement of why we who publish websites want something like CNAME at apex (and why we aren’t happy being locked into proprietary solutions).  
> 
> The issue has been stated multiple times in different email threads (including by Paul Vixie just yesterday) … but I thought it would be useful / helpful to formally write it down in a draft during these discussions.

$employer hosts apex domains on an anycast service. Like all of the work-arounds it is a bodge, albeit one that is not explicitly incompatible with existing DNS practice.

v2.23.0 | Report a Bug | By Email