Re: [DNSOP] dns interface to whois? (Re: Taking Back the DNS )
"John L. Crain" <john.crain@icann.org> Sun, 21 November 2010 17:50 UTC
Return-Path: <john.crain@icann.org>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A53C33A6A5D for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 09:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level:
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmaJEiOEoqNC for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 09:50:55 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 75FE93A6836 for <dnsop@ietf.org>; Sun, 21 Nov 2010 09:50:55 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Sun, 21 Nov 2010 09:51:49 -0800
From: "John L. Crain" <john.crain@icann.org>
To: Paul Vixie <vixie@isc.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Date: Sun, 21 Nov 2010 09:51:45 -0800
Thread-Topic: [DNSOP] dns interface to whois? (Re: Taking Back the DNS )
Thread-Index: AcuJpMUaZg5BQDobRjWrgk+L0aaeOw==
Message-ID: <C90E9A1D.AD4E%john.crain@icann.org>
In-Reply-To: <41856.1290360792@nsa.vix.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.1.0.101012
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [DNSOP] dns interface to whois? (Re: Taking Back the DNS )
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 21 Nov 2010 17:50:56 -0000
Hi Paul, On 11/21/10 9:33 AM, "Paul Vixie" <vixie@isc.org> wrote: >here's something interesting. > >> You have just received a comment for: >> >> Taking Back the DNS >> http://www.circleid.com/posts/20100728_taking_back_the_dns/#7331 >> By Marc Perkel >> ... >> Also - I would like to see some sort of DNS lookup to determine the >> age of a domain and the expiration date through DNS (high speed) as >> opposed to whois. That way domains that are very new can be >> distinguished for those who are established. > >how would the registry system implement something like this? could we >define another SRV-like schema like: Why would we do this, who gains by adding this? I don't see the benefit. As a registrant, registrar or registry I have access to that data. As a person (or client) resolving a name at a specific point in time I don't see how this data would be relevant. Even as a third party if I want the expiration data then there are existing protocols for doing that. Was the use case outlined? John > >vix._domain._whois._registry.com TXT "admin-c:pv15" > TXT "tech-c:pv15" > TXT "updated:25-Feb-2009" > TXT "created:20-Jun-1995" > TXT "expires:19-Jun-2011" > TXT "registrar:http://tucowsdomains.com" > >pv15._contact._whois._registry.com TXT "name:Vixie, Paul" > TXT "email:paul@vix.com" > TXT "postal:Star Route Box 159A, \ > Woodside, CA 94062, US" > TXT "pstn:+1.6504231383" > >...and then leave it up to each registry (and maybe icann if they are a >regulated registry) to decide whether to implement it and to decide what >kind of rate limiting to perform? > >i know there are a lot of related proposals in XML. that's another topic. >_______________________________________________ >DNSOP mailing list >DNSOP@ietf.org >https://www.ietf.org/mailman/listinfo/dnsop
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Andrew Sullivan
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Lawrence Conroy
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Paul Vixie
- Re: [DNSOP] dns interface to whois? (Re: Taking B… David Conrad
- [DNSOP] dns interface to whois? (Re: Taking Back … Paul Vixie
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Andrew Sullivan
- Re: [DNSOP] dns interface to whois? (Re: Taking B… John L. Crain
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Eric Brunner-Williams
- Re: [DNSOP] dns interface to whois? (Re: Taking B… David Conrad
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Patrik Fältström
- [DNSOP] whois: the protocol that can't be killed … Jim Reid
- Re: [DNSOP] whois: the protocol that can't be kil… Eric Brunner-Williams
- Re: [DNSOP] whois: the protocol that can't be kil… Joe Abley
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Tony Finch
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Tony Finch
- Re: [DNSOP] dns interface to whois? (Re: Taking B… bmanning
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Paul Vixie
- Re: [DNSOP] dns interface to whois? (Re: Taking B… bmanning
- Re: [DNSOP] dns interface to whois? (Re: Taking B… Paul Vixie