IETF Logo Mail Archive

Re: [weirds] Ted Lemon's Discuss on draft-ietf-weirds-rdap-query-16: (with DISCUSS and COMMENT)

Ted Lemon <Ted.Lemon@nominum.com> Wed, 29 October 2014 23:50 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBEC1ACD49; Wed, 29 Oct 2014 16:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 G800fbZz-zi9; Wed, 29 Oct 2014 16:50:30 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 19FD01ACD50; Wed, 29 Oct 2014 16:50:30 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id F1BB0DA021E; Wed, 29 Oct 2014 23:53:44 +0000 (UTC)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id AA4CE53E084; Wed, 29 Oct 2014 16:49:59 -0700 (PDT)
Received: from [10.0.20.107] (71.233.43.215) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 29 Oct 2014 16:49:59 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <7EEC5E39-E7B7-4407-9634-9D13F4EE8075@arin.net>
Date: Wed, 29 Oct 2014 19:49:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <83C9269A-D476-4C64-ACFE-7D20DAE2BD25@nominum.com>
References: <20141029184749.10576.92440.idtracker@ietfa.amsl.com> <8CD1C8CB-38B4-44AF-A90D-9792FE62EBA3@arin.net> <18AD51DF-27E5-4E8E-85A2-FAB95A5B8EA2@nominum.com> <7EEC5E39-E7B7-4407-9634-9D13F4EE8075@arin.net>
To: Andy Newton <andy@arin.net>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/FdiAGJSKdJpuY3r0qjzE57v4Gdc
Cc: "weirds-chairs@tools.ietf.org" <weirds-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-weirds-rdap-query@tools.ietf.org" <draft-ietf-weirds-rdap-query@tools.ietf.org>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Ted Lemon's Discuss on draft-ietf-weirds-rdap-query-16: (with DISCUSS and COMMENT)
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 29 Oct 2014 23:50:31 -0000

On Oct 29, 2014, at 7:24 PM, Andy Newton <andy@arin.net> wrote:
> Not necessarily. How a nameserver object is mapped in a registry is not a detail needed to configure a nameserver to accept queries for a domain.

OK, that use case does make some sense.  My concern is that it will be used for data mining by people other than owners of nameservers.   I don't think there's much that can be done to mitigate this, though, so I'll take it out of the DISCUSS.   It wouldn't hurt to mention it specifically in the security considerations section, but I'll leave that up to you.

v2.23.0 | Report a Bug | By Email