Re: [regext] REGEXT Interim Meeting (2019JUN11) Notes

Patrick Mevzek <mevzek@uniregistry.com> Tue, 09 July 2019 17:39 UTC

Return-Path: <mevzek@uniregistry.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 AC9B01200F7 for <regext@ietfa.amsl.com>; Tue, 9 Jul 2019 10:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.336
X-Spam-Level: *
X-Spam-Status: No, score=1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniregistry.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 vNl0SWfIM9Qv for <regext@ietfa.amsl.com>; Tue, 9 Jul 2019 10:39:37 -0700 (PDT)
Received: from a-mx.uniregistry.com (a.mx.uniregistry.net [64.96.177.8]) (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 63DBD12004E for <regext@ietf.org>; Tue, 9 Jul 2019 10:39:37 -0700 (PDT)
Abuse: Forward to abuse@uniregistry.com with full headers
X-Virus-Scanned: Content filter at a-mx.uniregistry.net
Powered-By: https://www.uniregistry.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniregistry.com; s=bravo; t=1562693976; bh=f4CQMEFRIpQgBbxpXzCy85tSm+u7oUhWTp56b9tkmcw=; h=Subject:To:References:From:Date:In-Reply-To; b=D8K35tU9j1OFgkdA5/FuchUvfY8bXsPzxtjusaHpsHIHp3VK29b3DTHz/jfbLpVML EMQaWXtDLKnKxqFMumAQwX8e4D5nyUhqePuj0Ao2fEX3KizwUDiFE0NFw4nf7H3v3j T1k0AlCc7iMOy5hYgI/fw9UIAZtJnD9pNTRuZd30W7g6JRlHeP0CTedJw43l94cP2V HtQXFLNapga9dOyttRkjUmdHm0VABdiiLOCzDTYT/SuLC+Ovjlo8NmGgoK4qjYaE+I SQx+wkedJPqEbmd3Zdtl0fptSx4U5e6V4DsbfPjDtGmAhpTiRUYMEWO0aFhlu07mmE LoGt+abKASTRg==
Received: from PatrickM.local ([66.54.123.66]) (authenticated bits=0) by a-mx.uniregistry.com (8.15.2/8.15.2/Debian-8) with ESMTPSA id x69HdYvE003354 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 9 Jul 2019 17:39:35 GMT
To: "regext@ietf.org" <regext@ietf.org>
References: <4AC76D0F-F0F4-42B9-9A0F-29C37D5EA2F1@dnsbelgium.be>
From: Patrick Mevzek <mevzek@uniregistry.com>
Organization: Uniregistry
Message-ID: <d0b298cb-1d19-38f3-1943-63c5f0325a2d@uniregistry.com>
Date: Tue, 09 Jul 2019 12:39:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <4AC76D0F-F0F4-42B9-9A0F-29C37D5EA2F1@dnsbelgium.be>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/LJ5-bui7OylXIndUuTrCuDFQv_w>
Subject: Re: [regext] REGEXT Interim Meeting (2019JUN11) Notes
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: Tue, 09 Jul 2019 17:39:39 -0000

  On 2019-07-03 09:45 -0500, Pieter Vandepitte 
<pieter.vandepitte@dnsbelgium.be> wrote:> The current EPP specifications 
do not prevent a client to perform “bulk > updates”, it’s just the 
clients that are not smart enough. If clients > would operate 
asynchronously (not waiting for a server response), the

(except that sometimes updates may be linked in the sense of one should 
stop if one is giving out errors; using pipelining is explicitly allowed 
by the RFC, may or may not be allowed by registries - so it is not just 
a matter of clients being not smart enough - and will certainly not 
solve the problem of conditionally continuing the batch or not)

> only overhead is the verbosity of XML (vs. message RTT when operating 
> synchronously). I doubt that this is a real issue (except if you’re 
> provisioning billions of objects/updates)...

There is (at least) one (existing[1]) use case that is absolutely not 
covered:
in some registry, some names are "bundled" together.

If you transfer/update one name from the bundle, you need to apply the 
same operation to others.
Currently it is done in a fashion where the first command is put in 
pending state until all other commands are done, at which point all are 
released as done.

In situations like that, you would need a way to send multiple commands 
in the same "batch", like a logical unit, or a DB transaction.
Or an EPP extension clearly describing bundles, identifying them, and 
being then able to send commands not on a domain but on a bundle of 
domains, and I do not think this extension exists anywhere.

EPP does not provide that and I am not sure it should provide that anyway.
I will try to read the underlying proposal at some time, but I wanted to 
react to add a use case that may not be known.

[1] upon checking, that specific behavior I described existed but ceased 
to recently when the registry changed its backend (now any single 
operation on a domain in a bundle does the same operation for all other 
domains in the bundle - that clearly solves the "batch" problem but then 
exposes to many other pitfalls)
-- 
Patrick Mevzek