IETF Logo Mail Archive

Re: [regext] EPP Transport Service Discovery

Bill Woodcock <woody@pch.net> Wed, 20 March 2024 07:05 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 10CD9C180B6A for <regext@ietfa.amsl.com>; Wed, 20 Mar 2024 00:05:13 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 SrHrQAs7U64B for <regext@ietfa.amsl.com>; Wed, 20 Mar 2024 00:05:09 -0700 (PDT)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66071C17A743 for <regext@ietf.org>; Wed, 20 Mar 2024 00:05:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pch.net; s=mail; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=jxQq48mE6AIzUavCOr0wQshOnYn1iOS4y25OoSdgo3I=; b=Fws4uvsDGIWiprahd0nzrFQiz81IwmxFKQ1zSVtPSEBItYROc76XL5luPxRoKiW/yahwAoGJ2XBI7 COfMMublxK+o/Stfbqyy3xIccCxKZoKolq3QCZ9/CYK82tipYdg93nVcqY82ZCydErutfOSXMg5OFO 6R7rqvi4OGF4FZ6qncwRvCyTtnEeuTmtjzU1gPC6e93G1v9Pid3CzBlPpSCQYdIFoWxvoEA22MaHdE zzGCibIQiHFtHhA6q4ScBP8en999eYvA/S6wy5o3KeFRx8wMgHw39tbzZutg12bZcjy1nBk/xZJqys SHVrODa3/76q40gECwaXhtyf2r+BjGA==
X-Footer: cGNoLm5ldA==
Received: from smtpclient.apple ([69.166.14.6]) by mail.pch.net (Kerio Connect 9.2.7 patch 3) with ESMTPS (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Wed, 20 Mar 2024 00:05:07 -0700
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Bill Woodcock <woody@pch.net>
In-Reply-To: <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com>
Date: Wed, 20 Mar 2024 08:04:42 +0100
Cc: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, regext@ietf.org
Message-Id: <1FD8435C-9DEC-4007-807C-29EAE0B94A06@pch.net>
References: <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com>
To: Jim Reid <jim@rfc1035.com>
X-Mailer: iPhone Mail (21E219)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/GK5PORpFfPSl5Yr0AG4CNy5IN5I>
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 07:05:13 -0000

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


> On Mar 20, 2024, at 3:40 AM, Jim Reid <jim@rfc1035.com> wrote:
> 
> 
> 
>> On 20 Mar 2024, at 02:11, Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org> wrote:
>> 
>> we need to consider how a client can discover the transport services provided by an EPP server.
> 
> I’m sceptical about that. Though I don’t object to the idea.
> 
> Surely clients get told about the EPP server’s supported transports as a result of signing the registry’s contract? If so, do we *really* need something else?
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

v2.23.0 | Report a Bug | By Email