IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 16:44 UTC

Return-Path: <jcb@bambenekconsulting.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 522B0120026 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bambenekconsulting.com
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 ODhGCCuLgTnX for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:43:57 -0700 (PDT)
Received: from chicago.bambenekconsulting.com (chicago.bambenekconsulting.com [99.198.96.122]) (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 ECF0412072D for <dnsop@ietf.org>; Tue, 9 Jul 2019 09:43:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=Content-Transfer-Encoding:Content-Type :In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Zvp4S5FDtkIdH4SAZauokJ2HV9zj+/veVheXx+t1e1Y=; b=OCEczPDv1jMoeQj9I3Vnz6tNwM 8yV3MBzVxogAASC2yRGxOa53u6EaX0qJTqx4mN2Q7Q9ddl4QOFH8eqREKB8pns4bwxZ6t9ndN7eCe JASKqLOZEtQxLdCSdw3LDbfe0lpi62umIc8I5+ZqLLzwX9Kp/rmB7TgaNTHh03WTF664=;
Received: from [216.169.1.210] (port=24943 helo=jcb.local) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hktDU-0002mp-UO for dnsop@ietf.org; Tue, 09 Jul 2019 12:43:45 -0400
To: dnsop@ietf.org
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <233E0AD8-97FE-466C-9B6C-D7A376031C3B@rfc1035.com> <93244821-6C22-457F-BA06-CF43CA9FD12B@bambenekconsulting.com> <EDE98437-E0B8-4B2E-8AA5-2F6B0079CE8B@hopcount.ca> <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com> <866041097.2378.1562689637240@appsuite-gw1.open-xchange.com>
From: John Bambenek <jcb@bambenekconsulting.com>
Openpgp: preference=signencrypt
Message-ID: <23e86618-610f-8b49-a3bc-4417ebc28efd@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 11:43:44 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <866041097.2378.1562689637240@appsuite-gw1.open-xchange.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chicago.bambenekconsulting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bambenekconsulting.com
X-Get-Message-Sender-Via: chicago.bambenekconsulting.com: authenticated_id: jcb@bambenekconsulting.com
X-Authenticated-Sender: chicago.bambenekconsulting.com: jcb@bambenekconsulting.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QUDhgBxiKWzU3b9-nOD5_uEOdik>
Subject: Re: [DNSOP] Proposal: Whois over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 09 Jul 2019 16:44:00 -0000

I'll look at ETSI.

But is the risk to self-identification as present when role-based
accounts could be used as opposed to PII? I guess I'm not understanding
the risks of people accidentally disclosing what they don't intend to.

On 7/9/19 11:27 AM, Vittorio Bertola wrote:
>> Il 9 luglio 2019 16:36 John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org> ha scritto:
>>
>>> I agree with pretty much everything else Jim said, but really this seems like the core issue: this seems like a proposal in the wrong venue.
>> If the proposal is to create a standard by which to put contact
>> information into DNS records, what venue would you suggest?
> You could try with ETSI... Seriously, the IETF in the past has already decided not to standardize certain technologies, as they could easily have been used to gain access to personal information and identify/track people on a mass scale, even with the blessing of law enforcement authorities and with the purpose of legitimate investigation activities. It would be weird now to work on a mechanism that could easily be used to coerce people to self-identify themselves in a global, public, automatically scrapable database to facilitate similar investigations.
>

v2.23.0 | Report a Bug | By Email