IETF Logo Mail Archive

Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.txt

Patrick Mevzek <mevzek@uniregistry.com> Thu, 13 June 2019 17:09 UTC

Return-Path: <mevzek@uniregistry.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 B9F4A12012D for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 10:09:25 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniregistry.com
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 QYLjKJ4nVnnm for <dnsop@ietfa.amsl.com>; Thu, 13 Jun 2019 10:09:23 -0700 (PDT)
Received: from a.mx.uniregistry.net (a.mx.uniregistry.net [64.96.177.8]) (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 650D712011C for <dnsop@ietf.org>; Thu, 13 Jun 2019 10:09:23 -0700 (PDT)
Abuse: Forward to abuse@uniregistry.com with full headers
X-Virus-Scanned: Content filter at a.mx.uniregistry.net
Powered-By: https://www.uniregistry.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniregistry.com; s=bravo; t=1560445761; bh=MOoco95kmcbsnDvdQTSoPgPYBXIu9SgDKwQ4YtPWAVA=; h=Subject:To:References:From:Date:In-Reply-To; b=HxvJ2xDdKmoE8bkkJjWkEhWg76oT/6QhYgtT0MLs8bZQQavDgLnWni6KInDqBNYQf 777OyBIDowz0S0/p+Cc/qebREJVv0YQ2ley93AsH6KHdzO7cgdaHozfrRqEg3l4Abc PvrpV8CRng3yhWVBEVjE075cvfHssMttltf9kgdGWyNdL5QKH7V5xZiRAkiL/4KLhL ln9Vg48SFLTAAGuMvur6yJg6jMXK+9+LgwCaacTnuX/0tvI3yKYx5D9dgwQb6E7tiJ lH9IdjU7mn0pgwbIsrdbLOeNQRsTaFRBcYp9cfaV4stETvmKJrjkIapa+BUXpuw+DX zYMiYHZ6n0Ecw==
Received: from PatrickM.local ([66.54.123.66]) (authenticated bits=0) by a.mx.uniregistry.net (8.15.2/8.15.2/Debian-8) with ESMTPSA id x5DH9KjM046460 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 13 Jun 2019 17:09:21 GMT
To: dnsop WG <dnsop@ietf.org>
References: <155771990790.31813.2767356343632633845.idtracker@ietfa.amsl.com> <7023B4C5-5207-4183-A945-244E65F00302@isc.org> <4C3E3ADC-16FE-467B-B0D4-26AEE698A153@rfc1035.com>
From: Patrick Mevzek <mevzek@uniregistry.com>
Organization: Uniregistry
Message-ID: <4d267b43-f127-de9b-8047-1e52cb912a63@uniregistry.com>
Date: Thu, 13 Jun 2019 12:09:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <4C3E3ADC-16FE-467B-B0D4-26AEE698A153@rfc1035.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FRs7KktB2yrEZWcK_u0oWp5m9GY>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.txt
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: Thu, 13 Jun 2019 17:09:26 -0000




On 2019-05-12 23:51 -0500, Jim Reid <jim@rfc1035.com> wrote:
> [Unless Telnic's T&Cs have changed, registrants can't delegate these names to arbitrary name servers.]

This has changed.

As written on frontpage of registry website:
"Now also available as a generic anything-you-want-it-to-be top-level 
domain"

The non-technical announcement:
https://www.do.tel/news/2017/05/meet-the-new-tel/

"You can build, create or design your website in whatever way you dream 
up – using any hosting or website services provider that you choose."

and also in the FAQ at https://www.do.tel/faqs/
" If you do not wish to use the free Telhosting service, that is fine as 
you can use your .tel for any purpose of your choosing e.g. hosting your 
own website."

and https://www.do.tel/news/2017/03/do-tel-with-tel/ :
"As of March 13, 2017, .tel registrants now have the freedom of choice 
with respect to their hosting provider and use of the .tel web address. 
This means you can use hosting or website services for your .tel domain 
name provided by your current Retailer or any web hosting provider you 
choose."

HTH,
-- 
Patrick Mevzek

v2.23.0 | Report a Bug | By Email