Re: [DNSOP] status of the aname and svcb/httpsvc drafts

Klaus Malorny <Klaus.Malorny@knipp.de> Fri, 21 February 2020 12:04 UTC

Return-Path: <Klaus.Malorny@knipp.de>
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 C65D6120033 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 04:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 HOQozRSp_8ra for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 04:04:49 -0800 (PST)
Received: from kmx5a.knipp.de (kmx5a.knipp.de [IPv6:2a01:5b0:0:29::63]) (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 B06FD120227 for <dnsop@ietf.org>; Fri, 21 Feb 2020 04:04:49 -0800 (PST)
X-Original-Recipient: dnsop@ietf.org
X-Original-Recipient: klaus.malorny@knipp.de
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx5a.knipp.de (Postfix) with ESMTP id 48P9B65HBSz4vh8; Fri, 21 Feb 2020 13:04:46 +0100 (CET)
Received: from [195.253.2.27] (mclane.do.knipp.de [195.253.2.27]) by hp9000.do.knipp.de (Postfix) with ESMTP id 4A79472399; Fri, 21 Feb 2020 13:04:16 +0100 (MEZ)
To: dnsop@ietf.org
References: <b34f1b0d-fa65-23d4-1b2b-761b965a2aae@knipp.de> <CAG8jCEzO7zrfL5G5CzdJ=c5wipJgqqHfyeA-a3-QjquoyPYgvg@mail.gmail.com> <3ead518d-f166-1c36-c3e9-18aeb355d160@pletterpet.nl> <57323a0d-6d33-ceef-1e99-58d61eff16dd@knipp.de> <041cf7a9-be2b-18bd-7f76-edbae5cd1e4b@NLnetLabs.nl>
From: Klaus Malorny <Klaus.Malorny@knipp.de>
Message-ID: <24c3f4de-463d-1317-b4b7-40c0529116a6@knipp.de>
Date: Fri, 21 Feb 2020 13:04:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Thunderbird/75.0a1
MIME-Version: 1.0
In-Reply-To: <041cf7a9-be2b-18bd-7f76-edbae5cd1e4b@NLnetLabs.nl>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spamd-Bar: /
Authentication-Results: kmx5a.knipp.de; none
X-Rspamd-Server: v1117
X-Rspamd-Queue-Id: 48P9B65HBSz4vh8
X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:8391, ipnet:195.253.0.0/16, country:DE]; LOCAL_WL_IP(0.00)[195.253.2.54]
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_YW5I0_-aNk8ubOtujNAF5c_sSw>
Subject: Re: [DNSOP] status of the aname and svcb/httpsvc drafts
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, 21 Feb 2020 12:04:52 -0000

On 21.02.20 10:08, Benno Overeinder wrote:
> I am interested to learn what the problem is that the customer wants to
> solve.  Quoting from the email from Evan Hunt in this thread: "CNAME at
> the apex wasn't really the problem.  Getting browsers to display
> content from the right CDN server was the problem."
> 
> If there is a specific use case for CNAME in the APEX (ANAME), I am
> really interested to learn from this.
> 
> Thanks,
> 
> -- Benno
> 

Hi Benno,

according to my colleagues, who are in contact with the customers, the use case 
is mostly in the context of CDNs. Some of them maintain a larger set of domains 
with alternate spellings of their product names, with different ccTLDs, some for 
promotions etc. The content for these domains are hosted by CDNs and not by us 
(we are not in that business right now). They want their domains to work also 
without a "www." prefix, and for now we use a web redirection service. This has 
some disadvantages, e.g. a "heavy" extra roundtrip to an HTTP server and in 
respect with HTTPS support. So our problem is exactly the "CNAME in the apex" 
problem. HTH.

Regard,

Klaus