Re: [regext] creating invalid RDAP with redaction

On Wed, Apr 26, 2023 at 3:16 PM Gould, James wrote: > > Andy, > > Yes, JCard certainly added complexity to the draft __. I believe a statement > can be broader than RFC 9083 to state something like the following at the > start of Section 3: > > "Redaction in RDAP can be handled in multiple

Re: [regext] creating invalid RDAP with redaction

Andy, Yes, JCard certainly added complexity to the draft __. I believe a statement can be broader than RFC 9083 to state something like the following at the start of Section 3: "Redaction in RDAP can be handled in multiple ways. The resulting redacted RDAP response MUST comply with the

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

I don't believe we're using advanced features of JSONPath in draft-ietf-regext-rdap-redacted and jsonpath.com has been used to validate the included examples. If there is a better tool to use, please let me know and I'll validate the examples with it. Otherwise, I believe we can continue to

[regext] creating invalid RDAP with redaction

On Mon, Apr 17, 2023 at 9:27 AM Antoin Verschuren wrote: > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). I'd like to see this published, but have one issue. Perhaps this is in the

Re: [regext] [EXTERNAL] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

+1 for adoption From: regext on behalf of Antoin Verschuren Date: Tuesday, April 25, 2023 at 4:54 PM To: regext Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl CAUTION: This email came from outside your organization. Don’t trust emails, links, or attachments from

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

Hi Andy, Il 26/04/2023 17:55, Andrew Newton ha scritto: I see in the implementation section of the draft there is a test server that lists the redactions. However, has anybody taken any real output from a DNR and INR server and run some JSONPath expressions on them? Doing so would help to prove

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

Sorry, that didn't come out in a usable form. I used jsonpath.com to validate the expressions against the pre-redacted response in the draft. -- JG James Gould Fellow Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

Andy, I used https://jsonpath.com to validate the expressions against the pre-redacted response in the draft. -- JG James Gould Fellow Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 4/26/23, 11:56 AM,

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

I see in the implementation section of the draft there is a test server that lists the redactions. However, has anybody taken any real output from a DNR and INR server and run some JSONPath expressions on them? Doing so would help to prove out this spec. -andy On Wed, Apr 26, 2023 at 7:39 AM

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

+1 to adopt Jothan Frakes Tel: +1.206-355-0230 On Wed, Apr 26, 2023 at 8:25 AM Hollenbeck, Scott wrote: > > -Original Message- > > From: regext On Behalf Of Antoin Verschuren > > Sent: Tuesday, April 25, 2023 4:54 PM > > To: regext > > Subject: [EXTERNAL] [regext] CALL FOR

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

> -Original Message- > From: regext On Behalf Of Antoin Verschuren > Sent: Tuesday, April 25, 2023 4:54 PM > To: regext > Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl > > Caution: This email originated from outside the organization. Do not click > links >

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

On 22:54 25/04, Antoin Verschuren wrote: > This is a formal adoption request for Extensible Provisioning Protocol (EPP) > mapping for DNS Time-To-Live (TTL) values: > > https://datatracker.ietf.org/doc/draft-regext-brown-epp-ttl/ > > Please review this draft to see if you think it is

[regext] FW: ROW12 -> Call for Proposals & Registration

FYI, folks. Scott From: row-commit...@googlegroups.com On Behalf Of nicoleta munteanu Sent: Wednesday, April 26, 2023 8:41 AM Subject: [EXTERNAL] ROW12 -> Call for Proposals & Registration Caution: This email originated from outside the organization. Do not click links or open

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

+1 to adopt. -Original Message- From: regext On Behalf Of Antoin Verschuren Sent: Tuesday, April 25, 2023 3:54 PM To: regext Subject: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl Caution: This email is from an external sender. Please do not click links or open attachments

Re: [regext] WGLC: draft-ietf-regext-rdap-redacted-11

Il 26/04/2023 02:16, Tom Harrison ha scritto: On Mon, Apr 17, 2023 at 03:27:23PM +0200, Antoin Verschuren wrote: The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: Redacted Fields in the

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

+1 to adopt it Best, Tobias > On 25. Apr 2023, at 22:54, Antoin Verschuren > wrote: > > This is a formal adoption request for Extensible Provisioning Protocol (EPP) > mapping for DNS Time-To-Live (TTL) values: > > https://datatracker.ietf.org/doc/draft-regext-brown-epp-ttl/ > >