Re: [regext] I-D Action: draft-ietf-regext-simple-registration-reporting-06.txt

2022-03-25 Thread Gould, James
Hi, I did a detailed review of draft-ietf-regext-simple-registration-reporting-06 and below is my feedback: 1. Introduction * I’m not sure whether there have been “a number of best practice reports that have evolved”, but I do agree that there have been “a number of best practice

[regext] Comments to the feedback about epp-over-http

2022-03-25 Thread Mario Loffredo
Hi folks, here are in the following some comments grouped by subject to last meeting's feedback about EPP-over-HTTP: *1) Draft title* Ulrich suggested to call the document EPP-over-HTTPS. I replied that the name was assigned to be consistent with RFC5734, i.e. EPP-over-TCP. SImilarly to

[regext] draft-ietf-regext-rdap-redacted Support for Redaction by Replacement Value Method

2022-03-25 Thread Gould, James
There was discussion in the ICANN RDAP working group associated with the requirement for the “Registrar MUST publish an email address or a link to a web form for the email value to facilitate email communication with the relevant contact, but MUST NOT identify the contact email address”, based o

Re: [regext] Comments to the feedback about epp-over-http

2022-03-25 Thread Gould, James
Mario, For #4 “Cookie vs. HTTP Connection”, you asked the question “can you further clarify why we should opt for establishing the cookie at setup of the connection and how should it be possible? For example, what kind of request should be used to start the HTTP connection?”. I implemented plu

Re: [regext] draft-ietf-regext-rdap-redacted Support for Redaction by Replacement Value Method

2022-03-25 Thread Hollenbeck, Scott
Sorry to be pedantic, but the requirement doesn’t describe a form of redaction. It describes replacement. “Redaction by Replacement” is commonly implemented by obscuring sensitive information with a phrase like “[sensitive information removed]”. As long as the draft makes it clear that text bein