> -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 ori
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
From: Andrew Newton (andy)
Sent: Wednesday, October 9, 2024 11:47 AM
To: regext@ietf.org
Subject: [EXTERNAL] [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open attachments unless
On 10/8/24 11:12, Jasdip Singh wrote:
[SAH] Yes, that's what I'm advocating for. I'd rather change the
non-conforming Proposed Standard extensions than update an Internet
Standard to validate them. Updating the Proposed Standard will be far
more disruptive than updating the optional extensio
20190
Verisign.com <http://verisigninc.com/>
*From: *Jasdip Singh
*Date: *Tuesday, October 8, 2024 at 2:49 PM
*To: *James Gould , "regext@ietf.org"
*Subject: *[EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
*Caution:*This email origin
James Gould , "regext@ietf.org"
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
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
, 2024 at 11:41 AM
To: Jasdip Singh , regext@ietf.org
Subject: Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Jasdip,
The use of sub-paths was not an envisioned form of extension in the base RFCs
as is the case for the other forms of extension that I included in my prior
s , regext@ietf.org
Subject: RE: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
From: Jasdip Singh
Sent: Monday, October 7, 2024 4:52 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extens
From: Hollenbeck, Scott
Date: Tuesday, October 8, 2024 at 7:48 AM
To: Jasdip Singh , a...@hxr.us , regext@ietf.org
Subject: RE: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
From: Jasdip Singh
Sent: Monday, October 7, 2024 4:52 PM
To: Hollenbeck, Scott ; a...@hxr.us; rege
From: Jasdip Singh
Sent: Monday, October 7, 2024 4:52 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or
"
Subject: [EXTERNAL] [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
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.
On 10/3/24 10:57, Holle
Scott,
From: Hollenbeck, Scott
Date: Monday, October 7, 2024 at 4:15 PM
To: Jasdip Singh , a...@hxr.us , regext@ietf.org
Subject: RE: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
…
I've read draft-ietf-regext-rdap-extensions-04 completely and have several
commen
From: Jasdip Singh
Sent: Monday, October 7, 2024 3:53 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or
Hi.
Please see my comments, marked [JS].
Jasdip
From: Hollenbeck, Scott
Date: Monday, October 7, 2024 at 11:42 AM
To: a...@hxr.us , regext@ietf.org
Subject: [regext] Re: Comments Regarding draft-ietf-regext-rdap-extensions-04
From: Andrew Newton (andy)
Sent: Monday, October 7, 2024 6:41 AM
From: Andrew Newton (andy)
Sent: Monday, October 7, 2024 6:41 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open attachme
Verisign.com<http://verisigninc.com/>
From: "Andrew Newton (andy)"
Date: Monday, October 7, 2024 at 7:04 AM
To: James Gould ,
"shollenbeck=40verisign@dmarc.ietf.org"
, "regext@ietf.org"
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regex
On 10/3/24 08:26, Gould, James wrote:
Andy,
I view updating the base RFCs as being a material change that would
trigger the need for signaling for interoperability via use of
“rdap_level_1”. If what is defined maintains backward compatibility
with what is defined in the base RFCs, then can
On 10/3/24 10:57, Hollenbeck, Scott wrote:
On 10/2/24 11:06, Hollenbeck, Scott wrote:
I've read draft-ietf-regext-rdap-extensions-04 completely and have several comments
to share. An overarching comment is that any update to Standard 95 responses means that
the modified responses will not
Il 04/10/2024 01:12, Tom Harrison ha scritto:
On Thu, Oct 03, 2024 at 02:51:47PM +, Jasdip Singh wrote:
On Thu, Oct 03, 2024 at 08:19:22AM -0400, Andy Newton wrote:
On Wed, Oct 02, 2024 at 03:06:26PM +, Hollenbeck, Scott wrote:
2.4.6:
"A strict interpretation of this wording where "c
On Thu, Oct 03, 2024 at 02:51:47PM +, Jasdip Singh wrote:
> On Thu, Oct 03, 2024 at 08:19:22AM -0400, Andy Newton wrote:
>> On Wed, Oct 02, 2024 at 03:06:26PM +, Hollenbeck, Scott wrote:
>>> 2.4.6:
>>>
>>> "A strict interpretation of this wording where "construction of
>>> the response" re
From: Andrew Newton (andy)
Sent: Thursday, October 3, 2024 8:19 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open attachme
From: Andrew Newton (andy)
Date: Thursday, October 3, 2024 at 8:19 AM
To: Hollenbeck, Scott ,
regext@ietf.org
Subject: [regext] Re: Comments Regarding draft-ietf-regext-rdap-extensions-04
2.4.6:
"A strict interpretation of this wording where "construction of the response&q
Way
Reston, VA 20190
Verisign.com<http://verisigninc.com/>
From: "Andrew Newton (andy)"
Date: Thursday, October 3, 2024 at 8:19 AM
To: "Hollenbeck, Scott" ,
"regext@ietf.org"
Subject: [EXTERNAL] [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensio
On 10/2/24 11:06, Hollenbeck, Scott wrote:
I've read draft-ietf-regext-rdap-extensions-04 completely and have several comments to
share. An overarching comment is that any update to Standard 95 responses means that the
modified responses will not be consistent with "rdap_level_0". A new identi
24 matches
Mail list logo
