Re: [weirds] draft-newton-et-al-weirds-rir-query-00

Alessandro Vesely <vesely@tana.it> Sat, 24 September 2011 17:22 UTC

Return-Path: <vesely@tana.it>
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 7254121F8ADE for <weirds@ietfa.amsl.com>; Sat, 24 Sep 2011 10:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.63
X-Spam-Level:
X-Spam-Status: No, score=-4.63 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 8dIKCK0hnB50 for <weirds@ietfa.amsl.com>; Sat, 24 Sep 2011 10:22:25 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8C321F8ACA for <weirds@ietf.org>; Sat, 24 Sep 2011 10:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1316885102; bh=agxXP+pyoMSAmulzHsTX73Y+Ly2JAVvULZGvRmWUjN8=; l=2216; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=W2Kv8U29nU0xrv+U7Z36XSIlBAI7Z1gUYHKhjpeZJzYhYwkYFdwRzzMku1Ds3Omio L7I3edObzyGc44+Mn0GSD3LZUD+SCCojTE0B1L4ctvKTuV/R8W+nckxxAlg1tGW8Zv k5KgIC4aIDyDgKuSyG8MXJQiYBde74tzkOf//u1Y=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sat, 24 Sep 2011 19:25:02 +0200 id 00000000005DC039.000000004E7E126E.00004E27
Message-ID: <4E7E126D.40503@tana.it>
Date: Sat, 24 Sep 2011 19:25:01 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: weirds@ietf.org
References: <20110923003612.64561.qmail@joyce.lan> <904CE8EE-D61F-48BE-9DE0-8A66B80428E7@lacnic.net> <CA+z-_EXv8JGB6jVv8nzNFsCfts13+pybmVU+4EnXquLA_FhtkQ@mail.gmail.com> <BBF69B08-E0CE-429B-B2CD-26C123B02DC5@arin.net> <4E7DFA13.1070709@tana.it> <21EB16B9-8194-4A34-9F12-F8E09CBA4CC8@arin.net>
In-Reply-To: <21EB16B9-8194-4A34-9F12-F8E09CBA4CC8@arin.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] draft-newton-et-al-weirds-rir-query-00
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: Sat, 24 Sep 2011 17:22:26 -0000

On 24/Sep/11 17:45, Andy Newton wrote:
> On Sep 24, 2011, at 11:41 AM, Alessandro Vesely wrote:
> 
>> However, the zero-or-one rule can be path-specific.  Another kind of
>> query, namely rdns, can return a list without compromising overall
>> consistency.  BTW, I don't think it is necessary for rdns' argument
>> and results to be in in-addr.arpa format: that only introduces a
>> difficulty when clients have to compare or generate such values.
> 
> Can you provide examples of what you are talking about here?

Sure.  To get the delegation chain I'd use

   get http://restwhois.net/rdns/192.0.2.87

instead of the "in-addr.arpa format"

   get http://restwhois.net/rdns/87.2.0.192.in-addr.arpa

I'd imagine the answer --in plain text, for simplicity-- can be
something like this:

   192.0.2.87
   192.0.2.80/26
   192.0.2.0/24

Now I can take any element from the list, for example the second, and
use it as a link to an operator query

   get http://restwhois.net/ip/192.0.2.80/26/operator

The other way around, I start with, say,

   get http://restwhois.net/ip/192.0.2.87/contacts/abuse

and get

   inetnum: 192.0.2.80/26
   email: abuse@example.org

Assume I'm not satisfied with this, e.g. because abuse@example.org
bounces.  To get it's next-level-up contact I can use the inetnum from
the result, or the same IP I started with.  That is, I'd query
respectively

   get http://restwhois.net/rdns/192.0.2.80/26

(which I'd imagine returns just two items), or

   get http://restwhois.net/rdns/192.0.2.87

In the latter case I can reckon that the sought item must be the
third, but may still want to check that the second item compares equal
to the inetnum returned on the previous query.  If the other format is
used, both comparison and argument passing require an extra variable
where the bytes are reversed and ".in-addr.arpa" appended, a a
function that is cumbersome and error-prone to write if it's not
provided in the environment.

>> We should target web and mail usage on equal terms, though.
> 
> What do you mean by that?

If we assume that clients operate in typical web environments, we may
come up with solutions that are hard to deploy for mail filters.