IETF Logo Mail Archive

[DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Mon, 08 July 2019 21:39 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 15382120041 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.297
X-Spam-Level:
X-Spam-Status: No, score=-4.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 zt6u8Cw97V5S for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:39:01 -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 26E08120075 for <dnsop@ietf.org>; Mon, 8 Jul 2019 14:39:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=To:Message-Id:Subject:Date: Mime-Version:Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4KBsUvjA/ZxBsEwmcciqlK75oiBCVCIg0a2Am5bye9Q=; b=HH+YygDE2UyHfPRYYQWmCeknZ tn6WdBxWKEx2kVfm9B5/2rJZMIdgMVdV+CB+vMeWwFg6MVztUKsBx8IVeh4B9SUXtbLIFwe2neKHo aAYVUoLwf9LJdXRM3r1UzFO+tZxcx80iIZh3IDNC5uTUnj8Cq7ob8dbIgUlPa4TP69CyA=;
Received: from [216.169.1.210] (port=5294 helo=[192.168.11.116]) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hkbLe-000357-DB for dnsop@ietf.org; Mon, 08 Jul 2019 17:38:58 -0400
From: John Bambenek <jcb@bambenekconsulting.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-698B4EBA-C65B-4F52-925D-3CCF0EEFAACC"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Mon, 08 Jul 2019 16:38:58 -0500
Message-Id: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com>
To: dnsop@ietf.org
X-Mailer: iPhone Mail (16F203)
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/BQVudaOErde3DrVSZ7dLFmiGvuE>
Subject: [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: Mon, 08 Jul 2019 21:39:04 -0000

All-

In response to ICANN essentially removing most of the fields in WHOIS for domain records, Richard Porter and myself created a draft of an implementation putting these records into DNS TXT records. It would require self-disclosure which mitigates the sticky issues of GDPR et al. Would love to get feedback. 

Name:        draft-bambenek-porter-dnsop-whois-over-dns
Revision:    01
Title:        Domain Contact Information (WHOIS) over DNS
Document date:    2019-06-30
Group:        Individual Submission
Pages:        13
URL:            https://www.ietf.org/internet-drafts/draft-bambenek-porter-dnsop-whois-over-dns-01.txt
Status:         https://datatracker.ietf.org/doc/draft-bambenek-porter-dnsop-whois-over-dns/
Htmlized:       https://tools.ietf.org/html/draft-bambenek-porter-dnsop-whois-over-dns-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-bambenek-porter-dnsop-whois-over-dns
Diff:           https://www.ietf.org/rfcdiff?url2=draft-bambenek-porter-dnsop-whois-over-dns-01

Abstract:
  Domain contact information over DNS provides a vehicle for
  exchanging contact information in a programmatic and reliable
  manner. DNS has a ubiquitous presence within the internet
  infrastructure and will act as a reliable publication method for
  contact information exchange. This RFC provides an agreed upon
  structure, voluntarily, to publish points of contact for domains.

  This document outlines the methodology for utilizing DNS TXT records
  for voluntary publication of various forms of contact. The intended
  purpose is to provide a faster means of reliable contact for
  professionals, cyber-defense of domains.






—
John Bambenek

On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license which means commercial use will require a license. Contact sales@bambenekconsulting.com for details

v2.23.0 | Report a Bug | By Email