IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Jim Reid <jim@rfc1035.com> Tue, 09 July 2019 15:05 UTC

Return-Path: <jim@rfc1035.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 01B04120493 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 Ytbe4A8BTpDt for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:05:54 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E56B11204DC for <dnsop@ietf.org>; Tue, 9 Jul 2019 08:05:39 -0700 (PDT)
Received: from wallace.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 84D11242109D; Tue, 9 Jul 2019 15:05:37 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <934c20d0-3da0-9ccc-2d52-dbab946c0f61@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 16:05:36 +0100
Cc: dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <669010D1-7B30-413F-8052-96248769492E@rfc1035.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <3A0433E0-7A69-4655-A799-DB3A6A8AE8F2@nic.br> <934c20d0-3da0-9ccc-2d52-dbab946c0f61@bambenekconsulting.com>
To: John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FoibpVKH9D7a84ASzfrfa0BSmAM>
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 15:05:55 -0000


> On 9 Jul 2019, at 15:50, John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org> wrote:
> 
> I'm not married to any name, I chose WHOIS for historical reasons. We can call it _hamsandwich if it builds consensus.

The concern here isn't what the label is called. Prepending a label won't work with absurdly long domain names because the maximum length of a domain name will be exceeded. That gives bad actors another way of not complying. Not that they would ever provide accurate contact data anyway.

v2.23.0 | Report a Bug | By Email