IETF Logo Mail Archive

Re: [regext] EPP Transport Service Discovery

Jim Reid <jim@rfc1035.com> Wed, 20 March 2024 02:40 UTC

Return-Path: <jim@rfc1035.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 BBF0DC180B7E for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 19:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=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 qi7e3Iu0JmZg for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 19:40:12 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32C7EC1519BA for <regext@ietf.org>; Tue, 19 Mar 2024 19:40:12 -0700 (PDT)
Received: from smtpclient.apple (dhcp-8280.meeting.ietf.org [31.133.130.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 1B46A2420E4A; Wed, 20 Mar 2024 02:40:09 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <c9fd4e5780f740dc9129e42a28a21813@verisign.com>
Date: Wed, 20 Mar 2024 02:40:06 +0000
Cc: "regext@ietf.org" <regext@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AEBB003-A5EC-4F7A-AF53-486EC6866EEB@rfc1035.com>
References: <c9fd4e5780f740dc9129e42a28a21813@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/91IW0de1V--qhRbAEPI7zr8NF1Q>
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 02:40:16 -0000


> 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?

v2.23.0 | Report a Bug | By Email