Re: [DNSOP] Proposal: Whois over DNS

George Michaelson <ggm@algebras.org> Tue, 09 July 2019 22:27 UTC

Return-Path: <ggm@algebras.org>
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 E1E4E120141 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 15:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.604
X-Spam-Level:
X-Spam-Status: No, score=-0.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 Zd5CxRrDgf9Y for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 15:27:02 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 D795212006D for <dnsop@ietf.org>; Tue, 9 Jul 2019 15:27:01 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id s7so371214iob.11 for <dnsop@ietf.org>; Tue, 09 Jul 2019 15:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=1bMACsVmpi94/EawA3x4ABxMhRh59jU3T+TXE32TLAs=; b=WyOSOsOM/7V2lOwR1FVFy5zRKNNniCupEFgOh0K0pgGPizrdl6HnDdlnMD1vYlm2Y9 Bxf2tUt9kpJo/6n5vao5v/qkoQJSHm1fTap+SsGylZfSkUSDb3aSqFL0ENyjaihwsgYk +EZOnT64SnHGRg/Gfy/npvnY7bEAX2YNwFohqg72fbJMfKmQXXI9TxmVciU72oyJMFlv gpEqYjkth1tiVqIpxW/aFYOCepfT5soAkwTs3ZH9mk5JZW5y5bjzwMFIv+5RBP/GZro3 FJLdAbibFBx+0rBPcFiFH+9RmkQMvyzdRXjU5f+XHHM6WZwTOQGJBZHpSZJCP7VNmqGm 8qUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=1bMACsVmpi94/EawA3x4ABxMhRh59jU3T+TXE32TLAs=; b=eOPvbJ+odAcRiisik+qIFnbe08Am5K2+QgBvuIwDMv7VCMRFNJ0ZF+mHlijZRToS4t p36iZIloK2v5uYTmG4iOxQGjXwMIS8BwcKHau005OmpbTKNOGQojz6zwpGjsHLZ0dS2O 0Gbjp2JbNUpySD6WxZOuftdkgBMDesqQDGOkrcKM7vpxnmcm+ilPCfQgOwNFtH6CMWlH 1q1z6HnL9GGCstOy0MB7LrMYDurQEIJFMTXAoU9Nu0aLUrhGRr/IuR6yCv067D5oGiG9 c9/lPsi8eRArav1QdV0DDTbQkjG97IghDMTzaKeGhVP9QlKjg9xI2k5NgI4YrdRgbIvH Dj+A==
X-Gm-Message-State: APjAAAX9aObXxiW7zWjsuJiw4RpIary78/QmBRHWndfCqnj8ha/TlGHL xrZE983jh3Jbn8MCLSf+7ZLyVI9SNU5oieLATwV+Eg==
X-Google-Smtp-Source: APXvYqwzF1HZB12UTwC//8jqTLvl++sDeffu1p+sr1wAxwHTdwmeQF4EK7mlsEg+tUrOpYBE58IojQLO0vFq65DugcU=
X-Received: by 2002:a02:bca:: with SMTP id 193mr31233478jad.46.1562711221043; Tue, 09 Jul 2019 15:27:01 -0700 (PDT)
MIME-Version: 1.0
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> <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca>
In-Reply-To: <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 10 Jul 2019 08:26:48 +1000
Message-ID: <CAKr6gn1_v5ZxubyaKOQ1f2nbhPYcyGJ=PR=MeMms3kSQ0r41MA@mail.gmail.com>
To: Joe Abley <jabley@hopcount.ca>
Cc: John Bambenek <jcb@bambenekconsulting.com>, dnsop WG <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/keYUmHBXO3FWhP19bpOcbFLxIBM>
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 22:27:06 -0000

On Wed, Jul 10, 2019 at 1:07 AM Joe Abley <jabley@hopcount.ca> wrote:
>
> 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.
>

Wrong: https://tools.ietf.org/html/draft-harrison-regext-rdap-jcard-profile-00

(admittedly it's the profile for JCARD in RDAP, but in any case there
is a convergeance/profile/conformance discussion happening amongst the
RIR at least, regarding RDAP data. We're fully deployed)

-G