IETF Logo Mail Archive

Re: [regext] EPP Transport Service Discovery

Paul Ebersman <list-regext@dragon.net> Wed, 20 March 2024 03:00 UTC

Return-Path: <list-regext@dragon.net>
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 6CE1AC15108E for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 20:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dragon.net
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 L-VsdnVl_NuV for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 20:00:22 -0700 (PDT)
Received: from mail.dragon.net (mail.dragon.net [IPv6:2001:4f8:ffff::15]) (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 7ADA8C15106F for <regext@ietf.org>; Tue, 19 Mar 2024 20:00:22 -0700 (PDT)
Received: from fafnir.remote.dragon.net (localhost [127.0.0.1]) by mail.dragon.net (Postfix) with ESMTP id 4F4237A4672; Tue, 19 Mar 2024 20:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dragon.net; s=dnkey; t=1710903621; bh=caJ6mVZ7WmEL4NUjQP4qUSKGVihzptsaX5q+Ms3LL04=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=xb8o3CuYD4jmiM0+/g++CY7QyLEAOZvlpoJviWqHlcmUsm9tm0XzA2zI1VFk9xZJx hqLagLTXsspS967Dp1+icTZ5Zln/J57qnzAx0kDQKmFLav8rmcp0lkw3k0mBiQUeqZ JtolrkVyB7A4Omsrm7ZZal1pAoi1m87JKH3Yjr/enfgGZ6qgTTmmKSdHkYhv9U7GnG sBXzXyANeMkVTxAnwrfE5HfYHaMQoAM53hAv7Iq/9cJjhJmtDePOU6/x3TbmyoyxH3 9uAJ5eqGyICU8scsrnD+Q3sn7G86Bs61CB4Frz/flfj1z2cQWXINBFYMEHWh1d4XET csZFbAfDblEvw==
Received: by fafnir.remote.dragon.net (Postfix, from userid 501) id E024F550FBF9; Tue, 19 Mar 2024 21:00:20 -0600 (MDT)
Received: from fafnir.remote.dragon.net (localhost [127.0.0.1]) by fafnir.remote.dragon.net (Postfix) with ESMTP id DD05A550FBF6; Tue, 19 Mar 2024 21:00:20 -0600 (MDT)
From: Paul Ebersman <list-regext@dragon.net>
To: Jim Reid <jim@rfc1035.com>
cc: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
In-reply-to: <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com>
References: <c9fd4e5780f740dc9129e42a28a21813@verisign.com> <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com>
Comments: In-reply-to Jim Reid <jim@rfc1035.com> message dated "Wed, 20 Mar 2024 02:40:06 -0000."
X-Mailer: MH-E 7.4.2; nmh 1.7.1; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <91109.1710903620.1@fafnir.remote.dragon.net>
Date: Tue, 19 Mar 2024 21:00:20 -0600
Message-Id: <20240320030020.E024F550FBF9@fafnir.remote.dragon.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/LSzg8MHzr5z_PpbBZ7QN7jfZHOk>
Subject: Re: [regext] EPP Transport Service Discovery
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 20 Mar 2024 03:00:26 -0000

jim> Surely clients get told about the EPP server's supported transports
jim> as a result of signing the registry's contract? If so, do we
jim> *really* need something else?

My guess is that even though registry software updates aren't overly
nimble, registry contracts are probably even slower and harder to
update/change.

v2.23.0 | Report a Bug | By Email