IETF Logo Mail Archive

Re: [DNSOP] Minimum viable ANAME

Matthijs Mekking <matthijs@pletterpet.nl> Tue, 06 November 2018 09:15 UTC

Return-Path: <matthijs@pletterpet.nl>
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 4D64D12D4F1 for <dnsop@ietfa.amsl.com>; Tue, 6 Nov 2018 01:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 7C8EzNtYzH-g for <dnsop@ietfa.amsl.com>; Tue, 6 Nov 2018 01:15:48 -0800 (PST)
Received: from aserp2120.oracle.com (aserp2120.oracle.com [141.146.126.78]) (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 D1F5D1277C8 for <dnsop@ietf.org>; Tue, 6 Nov 2018 01:15:47 -0800 (PST)
Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wA6997ek059028 for <dnsop@ietf.org>; Tue, 6 Nov 2018 09:15:46 GMT
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp2120.oracle.com with ESMTP id 2nh3mpkua3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <dnsop@ietf.org>; Tue, 06 Nov 2018 09:15:46 +0000
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id wA69Fkc3023831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <dnsop@ietf.org>; Tue, 6 Nov 2018 09:15:46 GMT
Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id wA69FjOg016283 for <dnsop@ietf.org>; Tue, 6 Nov 2018 09:15:46 GMT
Received: from [172.19.129.214] (/216.146.45.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 06 Nov 2018 01:15:45 -0800
To: dnsop@ietf.org
References: <20180919201401.8E0C220051382A@ary.qy> <08C8A740-D09B-4577-AF2A-79225EDB526B@dotat.at> <20180920061343.GA754@jurassic> <E944887D-51ED-41A0-AC5A-3076743620D8@isoc.org> <acef1f69-8e4f-52cc-dca5-3ada9446e0ee@bellis.me.uk>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <683ea769-094a-4f06-5a43-d5cb557f285a@pletterpet.nl>
Date: Tue, 06 Nov 2018 10:15:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <acef1f69-8e4f-52cc-dca5-3ada9446e0ee@bellis.me.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9068 signatures=668683
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811060081
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9Uhxk0qTUDuXeTFYUhXEdVUVjBY>
Subject: Re: [DNSOP] Minimum viable ANAME
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: Tue, 06 Nov 2018 09:15:50 -0000

As nice and clean the HTTP record draft is, without specifying how to do 
expansion of the record into address records it is not going to solve 
the CNAME-at-the-apex problem that DNS providers have, and we will stick 
with the proprietary solutions (this may solve a different use case though).

Best regards,

Matthijs

On 03-11-18 18:04, Ray Bellis wrote:
> 
> 
> On 21/09/2018 20:12, Dan York wrote:
> 
>> I do think this is a path we need to go.  We need *something* like 
>> CNAME at the apex.  Either CNAME itself or something that works in the 
>> same way but might have a different name.
> 
> I agree, and earlier today (well, yesterday, now) I wrote it up:
> 
> A new version of I-D, draft-bellis-dnsop-http-record-00.txt
> has been successfully submitted by Ray Bellis and posted to the
> IETF repository.
> 
> Name:        draft-bellis-dnsop-http-record
> Revision:    00
> Title:        A DNS Resource Record for HTTP
> Document date:    2018-11-04
> Group:        Individual Submission
> Pages:        5
> URL: 
> https://www.ietf.org/internet-drafts/draft-bellis-dnsop-http-record-00.txt
> Status: https://datatracker.ietf.org/doc/draft-bellis-dnsop-http-record/
> Htmlized: https://tools.ietf.org/html/draft-bellis-dnsop-http-record-00
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-bellis-dnsop-http-record
> 
> 
> Abstract:
>     This document specifies an "HTTP" resource record type for the DNS to
>     facilitate the lookup of the server hostname of HTTP(s) URIs.  It is
>     intended to replace the use of CNAME records for this purpose, and in
>     the process provides a solution for the inability of the DNS to allow
>     a CNAME to be placed at the apex of a domain name.
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email