IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Joe Abley <jabley@hopcount.ca> Tue, 09 July 2019 15:07 UTC

Return-Path: <jabley@hopcount.ca>
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 B78631205EA for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 pZ0RPTlQ1Pma for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:07:31 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF41D120241 for <dnsop@ietf.org>; Tue, 9 Jul 2019 08:07:24 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id i10so43796239iol.13 for <dnsop@ietf.org>; Tue, 09 Jul 2019 08:07:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nJPsrxouPzB/QMbU6cO0dCKVUvQDP9Z7qQobV98raoo=; b=I0c804F7sYtvCJiBtl/qpahh1HAU7NuC9h8R8+E7KYLfPILY02ODUtgnMblwraZQRI J35QVTGXmDYU0blJXU48AatNJjUCW2xj59Hlj4zAJl/BzAeaiEfYUeOdXuBSfJBu26Ma 0m5LBBoqq00vQl78bi5X5Qc0Z0goQZ1Se9akc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nJPsrxouPzB/QMbU6cO0dCKVUvQDP9Z7qQobV98raoo=; b=HszsJPLmQ45cXOM+IujMYSNrmm0t+ICWPTci4iLOIzhFpSOAscqXIqJCQy+gKNPC7X YXJHr6C9z5lYVprAXaAkUUjrd1tJj5Ho+XIhXOfHv5N2R+taDCrlGFChMut2nFrIklHH 5TR6Ra1xxLewX3MXWS8AWqNg92NzKKSkJEVjbSXrfRRWRHX2ohCuqPcg2SPYZ+OoVqCj rAiQ3Bmd14mqQKGaugmlroZkbIW5CrIrCJCobGeyK1mFzISd7vmL4qcwagwYNoHbMg6f SmsiTD5sc8X6eSFRFT9Sq10Mc/pDZZysnzvDaShN+NPQ1xkM/C/Bv/rbCvHHL51O2pnl 7GkQ==
X-Gm-Message-State: APjAAAXyIKEFWj0X1CFBk6t87At0LeCn+OMV1rJVIy3Lb6quau6zSsCO /5QYVhRPIxjbpGtpuyewIBNwJg==
X-Google-Smtp-Source: APXvYqy09PwFyr0F4Hz10XthHea3yoMDjt2RaIwFpw4QuPCIqCOZxS2tj3srnBLuhWRvcMKAysLQAA==
X-Received: by 2002:a6b:6d07:: with SMTP id a7mr694673iod.254.1562684843913; Tue, 09 Jul 2019 08:07:23 -0700 (PDT)
Received: from [192.168.1.50] (24-246-23-138.cable.teksavvy.com. [24.246.23.138]) by smtp.gmail.com with ESMTPSA id r24sm16584088ioc.76.2019.07.09.08.07.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jul 2019 08:07:22 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Message-Id: <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_72731CD0-41F7-48E0-8ADD-E7FBB77EEA1F"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 09 Jul 2019 11:07:15 -0400
In-Reply-To: <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com>
Cc: Jim Reid <jim@rfc1035.com>, dnsop@ietf.org
To: John Bambenek <jcb@bambenekconsulting.com>
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>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CHp5obT144C-qRWA2ziAoEUBAEg>
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:07:37 -0000

Hi John,

On 9 Jul 2019, at 10:36, John Bambenek <jcb@bambenekconsulting.com> wrote:

> If the proposal is to create a standard by which to put contact
> information into DNS records, what venue would you suggest?

I think that the protocol aspects of this are the least difficult ones. If this is fundamentally the data governance issue that I think it is, I think it would make a lot more sense to align exactly with what is happening in RDAP, treating self-publication as a new profile and DNS as a possible transport. If there's data to publish, thinking about transport afterwards seems far more sensible than inventing a transport and hoping that the data will follow.

RDAP profiles are not being discussed in the IETF. I think this is a feature.

>> I also agree that without any widespread incentive to implement, test and maintain, the data is going to be noisy and sparse to the point where it's useless for any practical use anyway.
> 
> You could say the same for SPF.

There's an operational incentive to publish SPF records: the need for recipients to accept legitimate mail that is being sent. I don't know what the operational incentive is to publish "whois" data in zone files.


Joe

v2.23.0 | Report a Bug | By Email