Re: [weirds] I-D Action: draft-blanchet-weirds-bootstrap-ianaregistries-00.txt

"John R Levine" <johnl@taugh.com> Mon, 24 June 2013 01:47 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A064321E8088 for <weirds@ietfa.amsl.com>; Sun, 23 Jun 2013 18:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPsFPXTgFy3x for <weirds@ietfa.amsl.com>; Sun, 23 Jun 2013 18:47:21 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7994F21E804C for <weirds@ietf.org>; Sun, 23 Jun 2013 18:47:20 -0700 (PDT)
Received: (qmail 73333 invoked from network); 24 Jun 2013 01:47:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=11e74.51c7a521.k1306; bh=BPgi4Qh0NKQ95cmQJnyn1o5cbfPO+kNMrukPZg6WlsA=; b=oAV2o6QjOFUTcuS+Vdx9ty306JbYamuIIhgzwMmbilUnjeRVzjDUwV2or9Rd8L9rOgEWTLICdfXQEskDp6JReuNhK/Ph+xwm/J1nKpIrtsTpR5K4ju1WZj9wyBOUdCJ4LehKzYDqS+9MGdOb60WqvKcTS+3FKmKn9qhDWuzE3OSEcKUiJbFcrx8GfNJ5w/G/x5pPqompsVen5+UtoI3v3fvGCtEmyf2uEhBn/suA/aWELFG7t214CfDqpC6a+184
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=11e74.51c7a521.k1306; bh=BPgi4Qh0NKQ95cmQJnyn1o5cbfPO+kNMrukPZg6WlsA=; b=t3zldO2CFFH5UbTx0/ZYeqS4YeRmUqJNXMMZ6rn1JJ/MkxSh62UhyHUyMhK4h32fGc/zKwiw8eL7sDSiGZiKYI5AbdvxPLedD8D+0cB5UcDEDfxUX/EURhqOCWsZVdg4Wk1Zk10jFFWWgMP0p2tg0Z3typr3T2vnKC+qw+dLmpryT6p4PeFCr6iis82vPxg31W49YQceBOLzMbiFJ7N/3h0pQrx8NZh4NNZTN9pU0URkp2YF8pwKV+U5XIDJOizj
Received: (ofmipd 127.0.0.1); 24 Jun 2013 01:46:51 -0000
Date: Sun, 23 Jun 2013 21:47:13 -0400
Message-ID: <alpine.BSF.2.00.1306232140340.16280@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Byron Ellacott <bje@apnic.net>
In-Reply-To: <CDEDDDA4.2784D%bje@apnic.net>
References: <CDEDDDA4.2784D%bje@apnic.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg="sha1"; BOUNDARY="3825401791-727333866-1372038433=:16280"
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] I-D Action: draft-blanchet-weirds-bootstrap-ianaregistries-00.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 01:47:21 -0000

>>> How would a client bootstrap a query for 29.12.202.in-addr.arpa ?
>>
>> It would look at arpa.domains.rdap.arpa to get the name of the RDAP
>> server for .arpa, if there were one.  I expect that's not the answer
>> to the question you meant to ask.
>
> Presumably, the server for .arpa is then going to redirect the client to
> the appropriate RDAP server for the specific resource associated with the
> reverse domain being queried.

Uh, no.  Since arpa is a TLD, it'll find you the RDAP server for the .arpa 
TLD, which will tell you something about the people at IANA who manage it. 
As I said, this is probably not the question you meant to ask.  It's worth 
noting somewhere that asking about the rDNS name associated with an IP 
address is not the same as asking about that IP address.  Name and number 
queries are different, different question syntax and different answer 
syntax.

>> If you're asking how to bootstrap a query for 202.12.29.0/24, or
>> 2001:0400::/22, my proposal is that the numbers bootstraps are built
>> into the clients, with informal advice to update them every year or
>> two, sort of like the root zone hints in a DNS cache. ...

> I don't mind this approach; is there suitable RFC wording that would allow
> clients to have confidence that asking one of the numbers bootstrap
> servers will get you to the right place for the answer you seek?

This is the IETF, so we can't force anyone to do anything.  But assuming 
the RIRs are willing, we could put in language along the lines of what I 
suggested a couple of messages ago.

R's,
John