IETF Logo Mail Archive

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

Dan York <york@isoc.org> Fri, 21 February 2020 12:19 UTC

Return-Path: <york@isoc.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 317CF120114 for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 04:19:06 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 LVW9zxZI5EzP for <dnsop@ietfa.amsl.com>; Fri, 21 Feb 2020 04:19:04 -0800 (PST)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2051.outbound.protection.outlook.com [40.107.244.51]) (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 38339120033 for <dnsop@ietf.org>; Fri, 21 Feb 2020 04:19:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K0ZV9W8CEqOXgcEQRVHebgqbexR8h2YUZPPRR9HEoQ/vNLXUsbcEBbD8wggDFG+KPyy0GHgnfZyt9yRIGyfXi7nPPj+Y5XosqD0aK0rCXHcXc+V8yDiyrS9zpZcTNyCVn2NE1Es2W3EjOYEus/iKFKAuckzazv6e3IjyZdw73qE0wsWIG4LiB93JBRIMZ91cIaP26kNsZ+yOMnbYZWSKGSf2P0yOXj7IxwygO17cg271qnqfnxsfJso3HLj89v89FgZ6yidKKJJAsMpbXC10CT2nepg4adIWS6TltrgQvPEKskAyN+4ojwvqEI5sjrMDLPFSEW31+Hz/rL3mTJGlwQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8u94he8F2UKnqinYJoczaMDBFETHTSwJZExa0t/zrxQ=; b=CDxJ3GMcPKEpB3HzfScN094QDeL9fmegLwvFo74m0YtCQ5WKOa51ce0LhlVX838zyD7dZalS0hPgxrRr/6jK60N4+VyCcqQelDOtNzXfJ0yVq0iaoOO0Sq+BscAOrOhq+4c46eGISldjYz/8VUzEVWuLpdBzgHoF2dB1PcUHP/8sGK/fqfXLiQYr8IGU69rrJv7d6zPVMJKRZqlpdcMzMLZB66S5UIqt2RNgk/IufUi2KwPMbWKOrns7oH54i8a8zckYb9jYZ2nszC18Zbjg4/kHh7zC4Sx1EplcK3pstca745yJ6A6PIOHefOwGoLNM/HSlXVty+8LMT9JWgEGCeA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isoc.org; dmarc=pass action=none header.from=isoc.org; dkim=pass header.d=isoc.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8u94he8F2UKnqinYJoczaMDBFETHTSwJZExa0t/zrxQ=; b=qBMLto1nwjsNs7pDdk7hGBVKhOith60f/iJY1qo6Kqy5RUbsp5SGLV8KLGpOLKwTSVkK4JhbZSIZIsFQWbRkZ/BhISvcNLP/BTZZb1SFvWygaa34Zr04HvlLgZUrVu/egs+Ursxd6IaSHjDUKAmD6U2psTgYH8FG/ipsDiThxpM=
Received: from BL0PR06MB4530.namprd06.prod.outlook.com (2603:10b6:208:5a::16) by BL0PR06MB4724.namprd06.prod.outlook.com (2603:10b6:208:59::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.22; Fri, 21 Feb 2020 12:19:01 +0000
Received: from BL0PR06MB4530.namprd06.prod.outlook.com ([fe80::4100:32c:5ad:2f3e]) by BL0PR06MB4530.namprd06.prod.outlook.com ([fe80::4100:32c:5ad:2f3e%4]) with mapi id 15.20.2729.033; Fri, 21 Feb 2020 12:19:01 +0000
From: Dan York <york@isoc.org>
To: "benno@nlnetlabs.nl" <benno@nlnetlabs.nl>
CC: Klaus Malorny <Klaus.Malorny@knipp.de>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] status of the aname and svcb/httpsvc drafts
Thread-Index: AQHV5m7e7YCCRUonqEqGr6ttc+T7G6ghIOUAgAKh/ICAABEyAIABjCCAgAA1IoA=
Date: Fri, 21 Feb 2020 12:19:01 +0000
Message-ID: <57505938-340A-4594-A283-EF670BD1B47E@isoc.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>
In-Reply-To: <041cf7a9-be2b-18bd-7f76-edbae5cd1e4b@NLnetLabs.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=york@isoc.org;
x-originating-ip: [2601:198:4100:84b0:2d3a:c5dc:e963:7e82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2f64ae3c-5fc1-4db5-6fd1-08d7b6c83c56
x-ms-traffictypediagnostic: BL0PR06MB4724:
x-ld-processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
x-microsoft-antispam-prvs: <BL0PR06MB472486FD3DEB36CDFBD85347B7120@BL0PR06MB4724.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0320B28BE1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(346002)(366004)(136003)(376002)(396003)(189003)(199004)(81156014)(8676002)(71200400001)(66446008)(81166006)(66616009)(8936002)(66476007)(66556008)(64756008)(36756003)(4326008)(2616005)(2906002)(186003)(5660300002)(6916009)(966005)(478600001)(76116006)(54906003)(33656002)(6486002)(66574012)(66946007)(86362001)(53546011)(6506007)(316002)(6512007); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR06MB4724; H:BL0PR06MB4530.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gF+73DA1QdMtdhjWfQNSpeg9VPhOxKNeWlHwrau1zAeovxtebsR5EWRVxJzONn6/KSbe5QkGoGsB2kHdpGWp7GViYADNv7/ux/aZTQWK2jD/mZhQCZ9wKAd59lTdHrjGRPVCQH2WZkLzDVnrq40WtxKJ69i83SERBgKE4VYJBAA/pec5LeYS+c0Ee5n9xXtmWgnBlF7bLnyFQeXASHiGNYesiXdmGc0CyeAWaABnp55RonUT7wSNlV9SiMrc9vNgeteJ2gCwv4Kb+J27r6p9g5waUP4any73fn0DuhBpxBMOi+eqWt5lxMvSG0q1QbPL1GStLjZBrg2+98Gb71Q+llLRvvbJ2fUCRZALNd6LnMgTLL+HLzaHoC1VMYmp2Aqt2u/EoYt3Z8GQswCnQgC300cTzB05gCzdPV+wsjq+FudP7B/xtpA/tkdcHLKhGLs7XvMWGXew3l87yxC9xVwSYI4OoLfBJEzDCz9sHQttPCLAlvRwiJlkLOAG/WM00DUU454IjE0HNG0Hk4YB2iDfyw==
x-ms-exchange-antispam-messagedata: ekbxs1BPdPw5h96xtAgGDEUcqPdPkNt/ShsfUmQEJkZfQWTvXrvT9z6PxWrEbJEwfE5hj+OiNfqq6do2t/xQyQF9Lr4h/Q7RVVCYuKby2/BQF0bbBsI7KRLLRbkXwaGzWGb9jk69JuxDXiEodQguoISn5LjqkMQYTyYdpR0FqxgK6kvi/1CJYUjLJa8F6Q93LjMS1KJ4QGk6bdFgwVmYnw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_004_57505938340A4594A283EF670BD1B47Eisocorg_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-Network-Message-Id: 2f64ae3c-5fc1-4db5-6fd1-08d7b6c83c56
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Feb 2020 12:19:01.6457 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DpEwvoQPUMmm1mfeIMP2QZMfkuQ0hCsbnip4AvcqGNJFvxSou1KTpHkqc0UKKmYV
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR06MB4724
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bWIwihP9HH9cESD2uMCGDM3f0UE>
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:19:06 -0000

Benno,

On Feb 21, 2020, at 4:08 AM, Benno Overeinder <benno@NLnetLabs.nl<mailto:benno@NLnetLabs.nl>> 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.

Similar to Karl’s customers, I want to use domains name without any subdomains to point to a CDN address and have the appropriate CDN edge node respond. I had outlined my perspective in a draft last year:

https://tools.ietf.org/html/draft-york-dnsop-cname-at-apex-publisher-view-01

What Evan says is true… it’s not so much that I “need” to have “CNAME at apex”. I just need some method that becomes widely available that allows web browsers (and other web endpoints) to go from “example.com<http://example.com>” to a CDN node.

If HTTPSVC can do that, and browser vendors will implement it [1], then that use case can be satisfied.

Dan

[1] And, of course, to get “the DNS infrastructure” to allow domain registrants to get the HTTPSVC records updated with their DNS hosting operator, which often means upgrading those DNS operators to support the new record. But that is an issue with ALL of the various “new DNS record” solutions we’ve come up with.

--
Dan York, Director, Web Strategy / Project Leader, Open Standards Everywhere<https://www.internetsociety.org/issues/open-standards-everywhere/> / Internet Society
york@isoc.org<mailto:york@isoc.org> | +1-603-439-0024 | @danyork<https://twitter.com/danyork>

[cid:image001.png@01D5D03B.DF736FF0]
internetsociety.org<https://www.internetsociety.org/> | @internetsociety<https://twitter.com/internetsociety>

v2.23.0 | Report a Bug | By Email