IETF Logo Mail Archive

Re: [regext] EPP Transport Service Discovery

Bill Woodcock <woody@pch.net> Wed, 20 March 2024 08:09 UTC

Return-Path: <woody@pch.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 E187BC1DA1CB for <regext@ietfa.amsl.com>; Wed, 20 Mar 2024 01:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.707
X-Spam-Level:
X-Spam-Status: No, score=-6.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=neutral reason="invalid (public key: not available)" header.d=pch.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 prXFE8PcBMAz for <regext@ietfa.amsl.com>; Wed, 20 Mar 2024 01:09:42 -0700 (PDT)
Received: from secmail.pch.net (secmail.pch.net [206.220.231.87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C8A3C1DA1C2 for <regext@ietf.org>; Wed, 20 Mar 2024 01:09:41 -0700 (PDT)
Received: from secmail.pch.net (localhost [127.0.0.1]) by secmail.pch.net (Postfix) with ESMTP id 4V01Td3jgkz4xR8d for <regext@ietf.org>; Wed, 20 Mar 2024 01:09:41 -0700 (PDT)
Authentication-Results: secmail.pch.net (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=pch.net
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pch.net; h= x-mailer:to:references:message-id:date:in-reply-to:from:subject :mime-version:content-type; s=secmail_dkim; t=1710922179; x= 1713514180; bh=tgNSdnsvU8d01P5EPQhG6XutK6GrOCEctGupjIQx2ok=; b=3 1dU3Iw0l1ghsu0zsw3ayeJz529H/DlXy2mf4sL14hlGMHR/12l4B+4yi9SUZOiur gcLawyT1X2fPuOCg+WGAJRXEslAQaXJsnFG3vhFu1cazsr5hRHoVKpEB05IGlG98 oUI+99JctW67Ek33FQgdclR3WlHcAx0HaYbFSVYNMHOuqOY4kSrP9cJFdL5syS6e vBkWY/VDltc7TlZ8kNptZ74HM7BH6we1pdeI4CcznMnROBtV5B4Pj8GLulupLwn8 JNWMlV9v7gQq/5hBnpmfkG5mpq6hoGFZ7o3EupoMloNuAEQ/ES+8+7a4ObVwJCvR j+EhRrJcKVMdN1fScPV7g==
X-Virus-Scanned: amavisd-new at secmail.pch.net
Received: from secmail.pch.net ([127.0.0.1]) by secmail.pch.net (secmail.pch.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SJUHyCaHMRK0 for <regext@ietf.org>; Wed, 20 Mar 2024 01:09:39 -0700 (PDT)
Received: from smtpclient.apple (itv-02 [69.166.14.6]) by secmail.pch.net (Postfix) with ESMTPSA id 4V01TZ5mPpz4xJNH; Wed, 20 Mar 2024 01:09:38 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_65030F5D-2929-4931-8B55-97381229FB62"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Bill Woodcock <woody@pch.net>
In-Reply-To: <C805E6EE-7101-467F-9954-6B0AC0943512@rfc1035.com>
Date: Wed, 20 Mar 2024 09:09:32 +0100
Cc: regext@ietf.org
Message-Id: <07FAADCE-E5CA-49FF-B0BC-A55DECCC43AC@pch.net>
References: <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com> <1FD8435C-9DEC-4007-807C-29EAE0B94A06@pch.net> <C805E6EE-7101-467F-9954-6B0AC0943512@rfc1035.com>
To: Jim Reid <jim@rfc1035.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/JFjzzbsgBhdc1vB1RtiQZ6DBN2U>
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 08:09:46 -0000


> On Mar 20, 2024, at 08:50, Jim Reid <jim@rfc1035.com> wrote:
>> On 20 Mar 2024, at 07:04, Bill Woodcock <woody@pch.net> wrote:
>> Yes, because the registry can improve over time, and the registrars can update their software over time. If we don’t give updated client-side software a mechanism to discover that the server now supports improved transport, we get gridlock.
> Bill, I somehow doubt a registry would introduce an updated/new transport and not tell anyone about that. 

So?  “Telling people about it” doesn’t get them to upgrade.  If we want to improve things, we actually need to improve things, not just talk about it.

                                -Bill

v2.23.0 | Report a Bug | By Email