[regext] Re: Dnsdir early review of draft-ietf-regext-epp-ttl-09

2024-05-16 Thread Jim Reid
Many thanks for the timely review Anthony - much appreciated.

___
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org


Re: [regext] EPP evolution and the REGEXT charter

2024-03-21 Thread Jim Reid


> On 21 Mar 2024, at 23:49, Gould, James  
> wrote:
> 
> I don’t believe that there is a need to revise the REGEXT charter to support 
> the additional of new EPP transports. 

+1

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] EPP Transport Service Discovery

2024-03-20 Thread Jim Reid


> On 20 Mar 2024, at 08:09, Bill Woodcock  wrote:
> 
> “Telling people about it” doesn’t get them to upgrade.

Neither would publishing some discovery info (presumably in the DNS).

> If we want to improve things, we actually need to improve things, not just 
> talk about it.

I agree. What I was trying to say is a discovery mechanism shouldn’t be the 
only tool in that toolbox.

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] EPP Transport Service Discovery

2024-03-20 Thread Jim Reid


> On 20 Mar 2024, at 07:04, Bill Woodcock  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. Other than changing some not-yet-defined discovery 
RRtype. YMMV.

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] EPP Transport Service Discovery

2024-03-19 Thread Jim Reid


> On 20 Mar 2024, at 02:11, Hollenbeck, Scott 
>  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