[regext] Re: RESTful EPP Charter side meeting Thursday 13:00

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 25 July 2024 18:13 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 49A54C14F695 for <regext@ietfa.amsl.com>; Thu, 25 Jul 2024 11:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOcDnvjtwciy for <regext@ietfa.amsl.com>; Thu, 25 Jul 2024 11:13:32 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32BF7C14F5F6 for <regext@ietf.org>; Thu, 25 Jul 2024 11:13:31 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 5B643C0052; Thu, 25 Jul 2024 19:13:29 +0100 (IST)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=pass smtp.mailfrom=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1721931209; bh=OUDBuRCI9qLWHWAW3w5OE8waYOOJJqI89ME/sG9DEqY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XdcD4N0ADHEFs8dPRNXciLitYUpegC24kC5QYCwXCdQ/q+jDD7m6AC9jE1RXsPyvH Cho38G8dKHzreeJzC5BJvMaeYS3gpUR+tDkkDpeCvQaZodwJMcOzibxjxdrc4iaozC NlVN8GCXtevP/fe1Ru1RU8HAH/EDVC6A2uO7dMpg=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1721931208-15238-15210/9/4646; Thu, 25 Jul 2024 18:13:28 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: regext@ietf.org
Date: Thu, 25 Jul 2024 20:13:25 +0200
Mime-Version: 1.0
Message-Id: <53f95a88-c0cd-4fc1-87da-bf5c8c79815c@gulbrandsen.priv.no>
In-Reply-To: <a5f9c82e-a050-4df2-ae48-135c1a5c17fb@denic.de>
References: <603C6F0D-CED2-4624-8F2E-6A9F4BEB6083@sidn.nl> <CAN8C-_KWKxJ47CkL31UNPCgs0wqi6zce=j4aFPvDY4e4cnXn7g@mail.gmail.com> <780DCB74-893A-4D32-8DAA-35BC91FD3AC7@verisign.com> <a5f9c82e-a050-4df2-ae48-135c1a5c17fb@denic.de>
User-Agent: Trojita/v0.7-599-gbe0cf694; Qt/5.15.8; wayland; Linux; Devuan GNU/Linux 5 (daedalus)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: JJJXOMXMAAFTPC7GZ7C3TEAWE334SDWP
X-Message-ID-Hash: JJJXOMXMAAFTPC7GZ7C3TEAWE334SDWP
X-MailFrom: arnt@gulbrandsen.priv.no
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: RESTful EPP Charter side meeting Thursday 13:00
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/gh0mGg-PkBn9wlFba8buuJPr0wI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

Hi,

I've attended the meetings since Prague but am not an EPP person. Permit me 
to offer a different perspective, based on what you've been saying about 
the other topics of discussion.

When you've talked about EPP during those meetings, you talked about the 
data model, the commands, but you hardly ever mentioned XML. XML didn't 
sound like a core part of the EPP that exists in your minds. I heard many 
arguments against or in favour of one proposal or another, but noone stood 
up and the mike to say "because … XML", see? XML seems about as central as 
TCP.

On this view, REPP might be called an unanticipated extension. If the data 
model and commands don't change at all, then this isn't the kind of 
extension that 5730-3 define, but it does extend that which you talk about 
as being EPP.

On the other hand, if the data model or commands do change… so I suggest 
that a separate WG makes sense if and only if REPP is permitted to change 
the data model or commands.

Arnt