Re: [regext] 2nd WG LAST CALL: draft-ietf-regext-epp-registry-maintenance

Marcel Parodi <marcel.parodi@switch.ch> Mon, 12 April 2021 16:40 UTC

Return-Path: <marcel.parodi@switch.ch>
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 74E0C3A08E4 for <regext@ietfa.amsl.com>; Mon, 12 Apr 2021 09:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=switch.ch
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 68fw5IuZO8Tt for <regext@ietfa.amsl.com>; Mon, 12 Apr 2021 09:40:33 -0700 (PDT)
Received: from mx1.switch.ch (mx1.switch.ch [84.254.110.100]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E7F3A0963 for <regext@ietf.org>; Mon, 12 Apr 2021 09:40:33 -0700 (PDT)
X-Virus-Scanned: by SpamTitan at switch.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=switch.ch; s=selector1; t=1618245629; bh=FxszVjDvZVWfD//T2pNLEVrr2TqffaEMp2tB8IcG+BE=; h=From:To:Subject:Date:References:In-Reply-To; b=cGg3r62Weqf/xVMu8x7GFbqd5JYePLmLayJpvMbI8hAdqP3toPvR96/3Y8Z4e2bZ5 oomBpgujaEe2mmIGm43vgkAEXF5UN9g8vj8tGgD3pI8qpAEpdUwcFfvIm8Zp3NF4kF CV3yHjsSxR8WU/1aHxVo6yOuAckx3uuiDxX7N1GG0GWgoDc1BcCk5HydUS+t1NoFPd fVejFBcGrKKOPJ4aJPOoGxpfb1LKBKiwoXbflIEy7dvzAClb7mFHa9AVRLeA4WrpQF aFeFdKGW9Yq7tybZ5syPyCgtXVwueD+8nLPvXFZoCdFgT6ze0IAfP0LG137JusrviA +UqOPY3YtcvyA==
Authentication-Results: mx1.switch.ch; x-trusted-ip=pass
Received: from SWH-S04-EXC2.swd.switch.ch ([fe80::85f9:d35f:5007:ca92]) by SWH-S04-EXC2.swd.switch.ch ([fe80::85f9:d35f:5007:ca92%15]) with mapi id 15.02.0792.010; Mon, 12 Apr 2021 18:40:29 +0200
From: Marcel Parodi <marcel.parodi@switch.ch>
To: Antoin Verschuren <ietf@antoin.nl>, regext <regext@ietf.org>
Thread-Topic: [regext] 2nd WG LAST CALL: draft-ietf-regext-epp-registry-maintenance
Thread-Index: AQHXJJn/ZSL3jD03zEWIdpwbY2ApI6qw2k6AgABRloA=
Date: Mon, 12 Apr 2021 16:40:29 +0000
Message-ID: <7B717D4C-D409-4B35-BEDD-2655611C7F28@switch.ch>
References: <08C180EC-A760-4A13-B4DA-C2AD21BB8E91@antoin.nl> <8EA696FF-3700-4BCB-A346-AC33F058C2D9@antoin.nl>
In-Reply-To: <8EA696FF-3700-4BCB-A346-AC33F058C2D9@antoin.nl>
Accept-Language: en-CH, de-CH, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.47.21031401
x-originating-ip: [172.16.60.41]
Content-Type: multipart/alternative; boundary="_000_7B717D4CD4094B35BEDD2655611C7F28switchch_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/oFMJNGPT6p9Ew38XtF-JC4QxydU>
Subject: Re: [regext] 2nd WG LAST CALL: draft-ietf-regext-epp-registry-maintenance
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, 12 Apr 2021 16:40:38 -0000

For some time now, I’ve been wondering whether it’s a good idea to choose the EPP service as a channel to provide information about maintenance windows of an unspecified set of services.
After reading last weeks discussion here on the mailing list, it seems rather unrealistic to me, that this proposed EPP extension will ever help a registrar to significantly simplify its job of juggling with the services of hundreds of registries. In my view, the semantics of several fields are not defined precise enough to be of much help. And during the last week it got even worse (by declaring <system:host> as optional).

A “system” (what I usually call a service) is specified by two free form strings (<system:id>, <system:name>) and an (meanwhile) optional <system:host>. The value of <system:name> can be updated by the registry at discretion. How can an EPP client make sense out of these strings?

In my opinion, the proposed extension can only be used to communicate the beginning and end of some maintenance windows in machine readable form. Information about the affected services can be provided only as free form text (or as a URI whose content can be changed at any time).
Or is it indended, that the missing semantics will be specified outside IETF? Will some other group need to specify an “EPP maintenance profile”?

Regards,
Marcel.

On 12.04.21, 15:49, "regext on behalf of Antoin Verschuren" <regext-bounces@ietf.org<mailto:regext-bounces@ietf.org> on behalf of ietf@antoin.nl<mailto:ietf@antoin.nl>> wrote:

Hi all,

This is a reminder that this 2nd WGLC will end tonight!
We still don’t seem to have enough consensus, so please state your support. Also if you have responded to the first WGLC.

Regards,

Jim and Antoin





Op 29 mrt. 2021, om 14:49 heeft Antoin Verschuren <ietf@antoin.nl<mailto:ietf@antoin.nl>> het volgende geschreven:

The following working group document is believed to be ready for submission to the IESG for publication as a standards track document:

https://datatracker.ietf.org/doc/draft-ietf-regext-epp-registry-maintenance/

EXTRA ATTENTION: This is the second WGLC for this document. During the first WGLC, there were still some substantial comments to be addressed, and there was not enough positive feedback to declare consensus on this document. Let’s do better this time and please take the time to 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. Since we have 3 authors, we need more reviewers to state support!

This WG last call will end at close of business, Monday, 12 April 2021.


The document shepherd for this document is James Galvin.

Regards,

Antoin and Jim



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