Re: [regext] WG LAST CALL: draft-ietf-regext-tmch-func-spec

"James Galvin" <galvin@elistx.com> Fri, 21 February 2020 21:27 UTC

Return-Path: <galvin@elistx.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 819A51200B8 for <regext@ietfa.amsl.com>; Fri, 21 Feb 2020 13:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level:
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=elistx-com.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 Sgke8hG8ZznN for <regext@ietfa.amsl.com>; Fri, 21 Feb 2020 13:27:51 -0800 (PST)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 C245012008A for <regext@ietf.org>; Fri, 21 Feb 2020 13:27:50 -0800 (PST)
Received: by mail-qv1-xf34.google.com with SMTP id y8so1625594qvk.6 for <regext@ietf.org>; Fri, 21 Feb 2020 13:27:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:embedded-html; bh=fNbJ222xM8oC5xIUkWehIP21mCpihdWYeV8bXY6yRe8=; b=JsY786wnkD76s9FMfX7QCz3uWGPCa0hdARjHUAWH4SyzEgpLPIOkSIGECiIa6MIKSf adUI9KJcLyLKZjUhgJ7UiLSpEGCLbTcStz8UTBWCrNE1GObUXLWuFl/TjiRAZCkXPMV8 dYWga4a/n0MUUBfrQ4jPLEfrd/m8/7v2t3+FQh1YmFZEnuZsDlTZsx23twLuFGe3i24I TMagVtgB5ova+nLTdm8XJwIghvQ8jka+kzK66uEMyWwZM/w933szG/6VuPW6eJMLiDK/ WM/11exrGBvpqAn0UeXVBbNWm/L/6zffQw2n1S+uS4jKH1HlEUJwV/4ehYUJNDU3G0id 5pyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding:embedded-html; bh=fNbJ222xM8oC5xIUkWehIP21mCpihdWYeV8bXY6yRe8=; b=SX7DS04yPN02YIJFFX6uuGd1RomtWTkWXxJT46JeJ8FAmTdb7RUjeDOzeSINnmq+K1 WqeR9tgQn5wY8EOAKAGZ0bANHx87yCY5Thfln4T9CYAJpJTZy8eVXcIfEqcHSt0J2vXt 2hgTKXX3DfAYZW9FEMei5xwAnObHSMsO5MvUZjSLCsE3KPtl/2CdA54l5q/mY7TcNc4C beQiahNeCaiIjA1yLQggjqhZeSO0NYTJ3OOdnc5VW69BYsgU1qaipmoMSj8b51HQvl12 PaUwoXFP6j1qe2dgasMLdRJU1Oijsad2xkKer2GT+owWQVRGNCb0mzqG5giPpkVM78AE Dy7A==
X-Gm-Message-State: APjAAAV+a9LeBDo/GMyPTVwvzgEJ168vK+f9ApiBnA+p3zy4p1DmTDGH FFX+MGKvBu/sHZ5OzJBY8/3yHQ==
X-Google-Smtp-Source: APXvYqyWbZ8Gt1eSBp25hAR241MljnyFryWr4l5KQn9QaKb5lgwkfYZOdsEGOSVc01VkmGHsM5PxCg==
X-Received: by 2002:a0c:e408:: with SMTP id o8mr32687711qvl.236.1582320469789; Fri, 21 Feb 2020 13:27:49 -0800 (PST)
Received: from [169.254.239.91] ([2601:154:c202:9d20:5c25:fb4f:dfe5:91c8]) by smtp.googlemail.com with ESMTPSA id r1sm2106596qtu.83.2020.02.21.13.27.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Feb 2020 13:27:48 -0800 (PST)
From: "James Galvin" <galvin@elistx.com>
To: "Roger D Carney" <rcarney@godaddy.com>
Cc: regext <regext@ietf.org>
Date: Fri, 21 Feb 2020 16:27:50 -0500
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <3B6DB671-A36B-4592-9E27-6863C167343C@elistx.com>
In-Reply-To: <CY4PR02MB2663F7FB81E40F8B6B2F1D00B1150@CY4PR02MB2663.namprd02.prod.outlook.com>
References: <D92DC51A-DAD8-4517-86C8-4A1D0EAE75D6@antoin.nl> <CY4PR02MB2663F7FB81E40F8B6B2F1D00B1150@CY4PR02MB2663.namprd02.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_9D5DEFAA-A76B-4E42-91E9-CAE54B69984B_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[661, 3905], "plain":[377, 2050], "uuid":"08981F6B-0760-4218-A730-EF244D21FB44"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/JFOuHWNgmwPAc-aadm0S8f_jt8E>
Subject: Re: [regext] WG LAST CALL: draft-ietf-regext-tmch-func-spec
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: Fri, 21 Feb 2020 21:27:53 -0000

Roger,

Would you be willing to highlight this document and the concern you have 
on the ICANN TechOps list?  It would be good to see if there are 
registry and registrars (albeit gTLDs) that share the concern.

Also a good opportunity to remind folks to join this mailing list to 
express their views directly.

Thanks!

Jim



On 14 Feb 2020, at 14:06, Roger D Carney wrote:

> Good Afternoon,
>
>
>
> As I have mentioned previously, this informational draft has quite a 
> few policy dependencies built into it that are currently being 
> reviewed and will be changed by ICANN. The authors have addressed 
> several of these potential policy issues but there are some that still 
> exist (e.g. TCNIDs generated twice daily; use and definition of 
> <tmNotice:notBefore> and <tmNotice:notAfter>).
>
>
>
> I do support sending this to the IESG as this draft does depict the 
> current operating environment, but due to these dependent policy 
> items, I do believe this will need to be revisited and corrected once 
> these policy decisions are made/changed, I would guess, at ICANN 
> speed, in the next 2-3 years.
>
>
>
> There are a few wording/grammatical issues that a good read should 
> resolve (e.g. section 5.2.2, second paragraph, I believe “effective 
> allocate” is meant to be “effectively allocate”, copyright dates 
> should be updated).
>
>
>
>
>
> Thanks
>
> Roger
>
>
>
>
>
> -----Original Message-----
> From: regext <regext-bounces@ietf.org> On Behalf Of Antoin Verschuren
> Sent: Friday, February 14, 2020 9:01 AM
> To: regext <regext@ietf.org>
> Subject: [regext] WG LAST CALL: draft-ietf-regext-tmch-func-spec
>
>
>
> Notice: This email is from an external sender.
>
>
>
>
>
>
>
> The following working group document is believed to be ready for 
> submission to the IESG for publication as an Informational document:
>
>
>
> https://datatracker.ietf.org/doc/draft-ietf-regext-tmch-func-spec/
>
>
>
> This WG last call will end at close of business, Friday, 28 February 
> 2020.
>
>
>
> Please review this document and indicate your support (a simple 
> “+1” is sufficient) or concerns with the publication of this 
> document by replying to this message on the list.
>
>
>
> The document shepherd for this document is Ulrich Wisser.
>
>
>
> Thanks!
>
>
>
> Jim and Antoin
>
> _______________________________________________
>
> regext mailing list
>
> regext@ietf.org<mailto:regext@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/regext


> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext