Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt

Byron Ellacott <bje@apnic.net> Tue, 01 May 2012 23:36 UTC

Return-Path: <bje@apnic.net>
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 2B08F21E808F for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 16:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[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 fXJL7vCVRUMG for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 16:36:53 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2535621E8086 for <weirds@ietf.org>; Tue, 1 May 2012 16:36:53 -0700 (PDT)
Received: from [IPv6:2001:dc0:a000:4:1d43:6800:17a9:240a] (unknown [IPv6:2001:dc0:a000:4:1d43:6800:17a9:240a]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 8FD2FB6869; Wed, 2 May 2012 09:36:51 +1000 (EST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/signed; boundary="Apple-Mail=_8FCB2CD7-C7D3-4DD0-BAAD-DF9FB80913A4"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Byron Ellacott <bje@apnic.net>
In-Reply-To: <9452079D1A51524AA5749AD23E003928108588@exch-mbx901.corp.cloudmark.com>
Date: Wed, 02 May 2012 09:36:47 +1000
Message-Id: <CC2E6A60-A767-4A14-84E3-7775989D2C43@apnic.net>
References: <20120501024631.97808.qmail@joyce.lan> <6DAAECD8-30D3-4195-BE44-C95D0EE3ECE3@icann.org> <AC14FC70-A653-4204-9A78-E40AB68B3228@hxr.us> <B1466110-5ED2-49E9-90A3-7041D4AB3405@icann.org> <7A3EC36C-31DB-47F9-8BEB-DA8D655C5FCE@hxr.us> <DE4B6FDC-FCF0-49DC-987A-95622E9AC209@lacnic.net> <2E0495B1-34E1-47F4-BF04-49FCAE33F15A@icann.org> <9452079D1A51524AA5749AD23E003928108588@exch-mbx901.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1257)
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-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: Tue, 01 May 2012 23:36:54 -0000

Given this case could be generalised to a reverse lookup search function based on arbitrary attributes, including name server IP address, I would support an approach around an individual submission for a search API extension.  I could see this as generic across names and numbers, if it is merely asking, essentially, for all <x> type records where attribute <x->a> is some value <v>.

Privacy concerns about whether this function should be provided for a particular attribute, or at all, with or without authorisation, should remain a local operator decision - the draft should follow the rir-response aim of minimising policy decisions taken within a technical protocol specification.

  Byron

On 02/05/2012, at 2:56 AM, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of Dave Piscitello
>> Sent: Tuesday, May 01, 2012 9:23 AM
>> To: Arturo Servin
>> Cc: weirds@ietf.org
>> Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt
>> 
>> So we're clear, this increases the likelihood that other
>> implementations than registry/registrar might extend the protocol in
>> non-uniform manners. Would be nice to avoid but I'm not going to fall
>> on my sword on this issue in this working group.
> 
> Such could be developed as individual submissions until this group finishes its first set of deliverables, and then we could re-charter to take on the extensions.
> 
> Just one possible path forward.
> 
> -MSK
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds