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

2024-11-01 Thread Tom Harrison
Hi Pawel, On Tue, Oct 22, 2024 at 08:51:32AM +0200, kowa...@denic.de wrote: > On 21.10.24 23:57, Tom Harrison wrote: >> [...] In the absence of any text permitting partial implementation, >> this text requires implementers to implement the whole document >> ("the functionality specified in this do

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

2024-10-22 Thread Jasdip Singh
Hi Pawel, Beside the discussion with Tom, want to highlight one other point you made. Thanks, Jasdip From: kowa...@denic.de Date: Monday, October 21, 2024 at 3:30 AM To: regext@ietf.org Subject: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search Also 2.3.1 of draft

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

2024-10-21 Thread kowalik
Hi Tom, On 21.10.24 23:57, Tom Harrison wrote: Hi Pawel, On Mon, Oct 21, 2024 at 09:29:49AM +0200,kowa...@denic.de wrote: [...] In the absence of any text permitting partial implementation, this text requires implementers to implement the whole document ("the functionality specified in this doc

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

2024-10-21 Thread Tom Harrison
Hi Pawel, On Mon, Oct 21, 2024 at 09:29:49AM +0200, kowa...@denic.de wrote: > The ambiguity seems to be also there because /domains path segment > is used the same in both context of RIR and domain name registry. > The draft puts however RIR in focus. This poses an interesting > question - if a do

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

2024-10-21 Thread kowalik
e=CID-40*&role=technical”. Jasdip *From: *Hollenbeck, Scott *Date: *Friday, October 11, 2024 at 8:19 AM *To: *mario.loffredo=40iit.cnr...@dmarc.ietf.org , Jasdip Singh , a...@hxr.us , regext@ietf.org *Subject: *RE: Re: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-ri

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

2024-10-13 Thread Tom Harrison
Hi Scott, On Wed, Oct 09, 2024 at 11:57:09AM +, Hollenbeck, Scott wrote: > In another thread focused on the extensions draft, I was asked > "Would you like regext to revisit Reverse Search?" That prompted me > to take another look at the draft. It currently defines five > extension identifiers

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

2024-10-11 Thread Jasdip Singh
beck, Scott Date: Friday, October 11, 2024 at 8:19 AM To: mario.loffredo=40iit.cnr...@dmarc.ietf.org , Jasdip Singh , a...@hxr.us , regext@ietf.org Subject: RE: Re: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search From: Mario Loffredo Sent: Friday, October 11, 2024 2:44 A

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

2024-10-11 Thread Hollenbeck, Scott
From: Mario Loffredo Sent: Friday, October 11, 2024 2:44 AM To: Hollenbeck, Scott ; jasd...@arin.net; a...@hxr.us; regext@ietf.org Subject: [EXTERNAL] Re: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search Caution: This email originated from outside the organization. Do

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

2024-10-10 Thread Mario Loffredo
tt ; a...@hxr.us; regext@ietf.org *Subject:* [EXTERNAL] Re: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search *Caution:*This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. We

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

2024-10-09 Thread Jasdip Singh
@ietf.org Cc: mario.loffr...@iit.cnr.it Subject: RE: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search Yes, we do, but I would still like to request that the shepherd writeup include a description of the situation with respect to the extension identifiers and non

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

2024-10-09 Thread Hollenbeck, Scott
: Wednesday, October 9, 2024 at 12:30 PM To: Jasdip Singh mailto:jasd...@arin.net>>, a...@hxr.us<mailto:a...@hxr.us> mailto:a...@hxr.us>>, regext@ietf.org<mailto:regext@ietf.org> mailto:regext@ietf.org>> Subject: RE: [regext] Re: Extension Identifiers in draft-

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

2024-10-09 Thread Jasdip Singh
We agree. :) Jasdip From: Hollenbeck, Scott Date: Wednesday, October 9, 2024 at 12:30 PM To: Jasdip Singh , a...@hxr.us , regext@ietf.org Subject: RE: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search From: Jasdip Singh Sent: Wednesday, October 9, 2024 11:54 AM To

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

2024-10-09 Thread Hollenbeck, Scott
From: Jasdip Singh Sent: Wednesday, October 9, 2024 11:54 AM To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org Subject: [EXTERNAL] Re: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search Caution: This email originated from outside the organization. Do not click links

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

2024-10-09 Thread Jasdip Singh
issue. One can define new child segments under it. Jasdip From: Hollenbeck, Scott Date: Wednesday, October 9, 2024 at 11:48 AM To: a...@hxr.us , regext@ietf.org Subject: [regext] Re: Extension Identifiers in draft-ietf-regext-rdap-rir-search From: Andrew Newton (andy) Sent: Wednesday, October 9

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

2024-10-09 Thread Hollenbeck, Scott
From: Andrew Newton (andy) Sent: Wednesday, October 9, 2024 11:41 AM To: Hollenbeck, Scott ; regext@ietf.org Subject: [EXTERNAL] Re: [regext] Extension Identifiers in draft-ietf-regext-rdap-rir-search Caution: This email originated from outside the organization. Do not click links or open a

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

2024-10-09 Thread Andrew Newton (andy)
Scott, This was discussed in this working group on this list by me and others. I even proposed something similar. However, absent some functional deficiency or harm, I do not favor re-opening this issue post WGLC. It may not have been the way I would have done it, but to my knowledge it works