IETF Logo Mail Archive

[DNSOP] dictionary of registration data elements

Jim Reid <jim@rfc1035.com> Tue, 09 July 2019 20:57 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 0860B1200B5 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 13:57:44 -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=ham 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 YkzebD3gvtSY for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 13:57:42 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5974A12015C for <DNSOP@ietf.org>; Tue, 9 Jul 2019 13:57:42 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (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 AF396242109D; Tue, 9 Jul 2019 20:57:39 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CABf5zvLvicDeSEfgkBotwRp=UYpKf3ryp-Cz-T+SjSBA6d8GNg@mail.gmail.com>
Date: Tue, 09 Jul 2019 21:57:38 +0100
Cc: dnsop <DNSOP@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F64C2EF0-48F3-4A9C-AEC2-538D7B6C257D@rfc1035.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <233E0AD8-97FE-466C-9B6C-D7A376031C3B@rfc1035.com> <93244821-6C22-457F-BA06-CF43CA9FD12B@bambenekconsulting.com> <F45666C7-181A-4853-897E-40D5C0EA972B@fugue.com> <37daa562-c8a0-ec11-8a3f-ffebfb464d16@bambenekconsulting.com> <CABf5zvKtkVX+1WLoNcjwmff6-KoOxjVxh9cwZYS0YVO4PAVq4w@mail.gmail.com> <CABf5zvLvicDeSEfgkBotwRp=UYpKf3ryp-Cz-T+SjSBA6d8GNg@mail.gmail.com>
To: Steve Crocker <steve@shinkuro.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jBec7k7K_qIvsZ7m5Blw6R_6YkM>
Subject: [DNSOP] dictionary of registration data elements
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 20:57:46 -0000


> On 9 Jul 2019, at 17:26, Steve Crocker <steve@shinkuro.com> wrote:
> 
> I would strongly support an effort within the IETF to create and maintain a dictionary of registration data elements.  This would probably be in the form of an IANA-maintained registry, with oversight from DNSOP.

Hmmm. That might be a better fit for regext where the EPP people gather since those data elements are more likely to figure in EPP transactions than in DNS traffic. I’m not sure dnsop is a suitable place to discuss stuff that goes in domain name registry databased and whois servers.

v2.23.0 | Report a Bug | By Email