[regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search

2024-10-10 Thread Mario Loffredo
Hi Scott, sorry  but didn't undenstand your example about collisions. From a conceptual perspective, any path "/domains/" is a subpath (we can consider it as an extension) of "/domains" but, programmatically, they are different as AFAIK a full path is parsed and processed altogheter. Fo

[regext] Re: [Ext] Secdir last call review of draft-ietf-regext-epp-ttl-15

2024-10-10 Thread Wes Hardaker
Apologies for the delay in responding Gavin, I was sure I had already sent this (but have been proven very wrong): > That was not discussed explicitly. The document describes a policy > discovery mechanism (see Section 2.1.1.2) which allows clients to learnt > the min/default/max values, but it d

[regext] Re: Comments Regarding draft-ietf-regext-rdap-extensions-04

2024-10-10 Thread Andrew Newton (andy)
On 10/9/24 12:02, Hollenbeck, Scott wrote: Are you suggesting we acknowledge this was done in the past, but bar it from the future? What harm do you think is being done here? */[SAH] If we allow every extension to create it’s own rules about how that extension is identified, we’re adding un

[regext] Re: Comments Regarding draft-ietf-regext-rdap-extensions-04

2024-10-10 Thread Hollenbeck, Scott
> -Original Message- > From: Andrew Newton (andy) > Sent: Thursday, October 10, 2024 3:24 PM > To: Hollenbeck, Scott ; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding draft-ietf-regext- > rdap-extensions-04 > > Caution: This email originated from outside the organ