Re: [regext] FW: I-D Action: draft-hollenbeck-regext-rfc7482bis-00.txt

Patrick Mevzek <pm@dotandco.com> Mon, 27 April 2020 15:48 UTC

Return-Path: <pm@dotandco.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0CAD3A0DFB for <regext@ietfa.amsl.com>; Mon, 27 Apr 2020 08:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=C2eNAINy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=4RJRqEaq
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 UVbP7mEkhLXb for <regext@ietfa.amsl.com>; Mon, 27 Apr 2020 08:48:13 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0CDD3A0DD2 for <regext@ietf.org>; Mon, 27 Apr 2020 08:47:45 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E1FD15C01A8 for <regext@ietf.org>; Mon, 27 Apr 2020 11:47:44 -0400 (EDT)
Received: from imap22 ([10.202.2.72]) by compute3.internal (MEProxy); Mon, 27 Apr 2020 11:47:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=vujlqKMc9dmFcx54AE3ko+/qeeXLbDx 6vzaB+E2+aPQ=; b=C2eNAINyKARfxE4xJHNSsA9VS4apDwEYn3jinjWK1NQu9yS ciB3zlaeBIq/f29tnGVtUEZJzjY+pNfqEOhETvP1QbEsOssurHCT5/v6riwJqzDQ YrdRDjf1TUXePF3TRDETHnDPZn9YVO+G24I6TzjPbjS14Hj15ZILiijpSxoo31Yx HmvqisB6LVaj1shezn5gh5lSh7c0GkF2L7W4G+9mc+Y4dCiot4GzWk8Rjy9Wj3Vc KhefCm6mZ10suGS/a3uHuPLs/PJUMdjEV2EFSiu6ep/CyysFNMlstw/TC3MqLxkB 4vkd2VaBpGDwQcFUjjO8UVMJEa0jm4rxi3O+asQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=vujlqK Mc9dmFcx54AE3ko+/qeeXLbDx6vzaB+E2+aPQ=; b=4RJRqEaqOUmhrEJIwUM8wu Z+BlXr8ZOJXjLaXWWPalEnLBAKMTwZ5LnO62d570716Gs3GLpIaXZzBkfKYJsDUj gsAjkCZNWh+q+JusbN/GQPQlxnL3u94jLvuWaehhk4LBWXag9lBCLHDWhfcvEe9k U4k5s/K/JEVmQW5mw+sfFCcveH3/L6hjTlh0lqBVjIhBcMGKhd7aBKHDMXypK56q LcHTJn8x1SH0QjDA8NsPtIhOEHnP68MTMB4i2rW+AZcG+sYTX+WL8RdWTl8bp7zQ nGkGLjExCfmfA5Pp6mbZoEBkMv5F7LvYKH2e2BD8CvG5KHb3BqwYATYDqETc87gA ==
X-ME-Sender: <xms:oP6mXkRkJ0xcfcGj9qBWzfcTY_rOOoFU03RUbTVnw3HmVdLu-BpXwKDHgMI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrheelgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreerjeenucfhrhhomhepfdfrrghtrhhitghkucfovghviigvkhdfuceophhmseguohht rghnuggtohdrtghomheqnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphhmseguohhtrghnuggtohdrtghomh
X-ME-Proxy: <xmx:oP6mXjXFkQAyAaTmYJxibYHHi_X2hHh1NIDvIh4tWteIomtp7wn3qA> <xmx:oP6mXoJ85m9dN8kClX53uevvApfOVGy3bMI3Kejf5VlbefQRq21E4Q> <xmx:oP6mXj0IfrCkIE7ejKzYuBN66gt7c5iNnwIvLG2N0MUjNk_5UgDtnQ> <xmx:oP6mXg5IpLkPHOWnmCVfnaP_5xhDWoH44m-xI3KLi_lXyum5EhdMQw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9C9D26680073; Mon, 27 Apr 2020 11:47:44 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-351-g9981f4f-fmstable-20200421v1
Mime-Version: 1.0
Message-Id: <1187b76a-485e-4276-a17f-d9febda152f9@www.fastmail.com>
In-Reply-To: <88c2c3d3cf764a27b35e70960805749f@verisign.com>
References: <157978263830.22814.10753224081346165172@ietfa.amsl.com> <1a23b173513a40568e5fa6da66df9686@verisign.com> <a51395d3-137f-40b9-bab0-a6f636188a10@www.fastmail.com> <88c2c3d3cf764a27b35e70960805749f@verisign.com>
Date: Mon, 27 Apr 2020 10:47:24 -0500
From: "Patrick Mevzek" <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/rXimh9QPwph2srox1_NW2exp3o4>
Subject: Re: [regext] =?utf-8?q?FW=3A_I-D_Action=3A_draft-hollenbeck-regext-r?= =?utf-8?q?fc7482bis-00=2Etxt?=
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2020 15:48:21 -0000

On Mon, Apr 27, 2020, at 06:27, Hollenbeck, Scott wrote:
> > -----Original Message-----
> > From: regext <regext-bounces@ietf.org> On Behalf Of Patrick Mevzek
> > Sent: Monday, April 27, 2020 4:06 AM
> > To: regext@ietf.org
> > Subject: [EXTERNAL] Re: [regext] FW: I-D Action: draft-hollenbeck-regext-
> > rfc7482bis-00.txt
> >
> >
> >
> > On Thu, Jan 23, 2020, at 07:35, Hollenbeck, Scott wrote:
> > > FYI, folks. I just submitted the first version of 7482bis. I've
> > > addressed the known errata, but I also have some clarification
> > > suggestions queued up for discussion. I'll start a thread for each of
> > > those shortly.
> >
> >
> > See my previous email on RFC7483bis the same caveat (on the breadth of
> > changes called for) applies here.
> 
> The goal of the update is to only address necessary editorial 
> corrections and clarifications. No protocol changes. Some of what you 
> describe below has already come up in on-list discussion, so it will be 
> addressed. Anything that changes the protocol itself will be out of 
> scope for now. I'll take a look at everything below as I work on the 
> next version of the document.

Thanks Scott for your explanation and hence sorry for my two emails.

There may be a few things and nitpicks that could still be viewed as "corrections
and clarifications" and hence be useful, but indeed some other points are really
like protocol enhancements (based on what I see on the field today, trying to use
RDAP servers in gTLDs right now is really a minefield...) and hence sadly will
need to be jettisoned for now.

-- 
  Patrick Mevzek
  pm@dotandco.com