Re: [regext] Adoption of draft-gould-regext-rdap-redacted Document

2021-08-11 Thread Mario Loffredo

I support adoption

Mario

Il 06/08/2021 22:02, Jody Kolker ha scritto:


Hello RegExt Group Members,

Thank you for the feedback received on the mailing list and at 
IETF-111 RegExt meeting regarding draft-gould-regext-rdap-redacted.  
Based on this feedback and an action item at the meeting, we are 
asking the working group to adopt the draft-gould-regext-rdap-redacted 
document.  We have identified a document shepherd if the draft is adopted.


Please let me know if you have any questions.

Thanks,

Jody Kolker

GoDaddy


___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] Adoption of draft-gould-regext-rdap-redacted Document

2021-08-11 Thread Jasdip Singh
+1

Jasdip

From: regext  on behalf of Jody Kolker 

Date: Friday, August 6, 2021 at 4:03 PM
To: regext 
Subject: [regext] Adoption of draft-gould-regext-rdap-redacted Document

Hello RegExt Group Members,

Thank you for the feedback received on the mailing list and at IETF-111 RegExt 
meeting regarding draft-gould-regext-rdap-redacted.  Based on this feedback and 
an action item at the meeting, we are asking the working group to adopt the 
draft-gould-regext-rdap-redacted document.  We have identified a document 
shepherd if the draft is adopted.

Please let me know if you have any questions.

Thanks,
Jody Kolker
GoDaddy

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] Secdir last call review of draft-ietf-regext-epp-registry-maintenance-16

2021-08-11 Thread Jody Kolker
Hi Melinda,

Thanks for the detailed review of the document.  We have made the suggested 
updates below and incorporated the changes into the document at 
https://github.com/seitsu/registry-epp-maintenance/blob/master/draft-ietf-regext-epp-registry-maintenance.txt
 with an added reference to RFC 5730 regarding security considerations.  

We will publish the document with additional changes after our AD requests 
publication.

Please let us know if anything else is needed.

Thanks,
Jody Kolker.

-Original Message-
From: Melinda Shore via Datatracker  
Sent: Sunday, August 8, 2021 10:29 PM
To: sec...@ietf.org
Cc: draft-ietf-regext-epp-registry-maintenance@ietf.org; 
last-c...@ietf.org; regext@ietf.org
Subject: Secdir last call review of 
draft-ietf-regext-epp-registry-maintenance-16

Caution: This email is from an external sender. Please do not click links or 
open attachments unless you recognize the sender and know the content is safe. 
Forward suspicious emails to isitbad@.



Reviewer: Melinda Shore
Review result: Has Issues

The security considerations section is scanty - transport security is not 
described at all, nor is the question of defense against a malicious actor 
spoofing a server.  It may be the case that there are, in fact, mitigations in 
common use but they are not spelled out in this draft nor in RFC 5730 (and I’ll 
be the first to admit that I may have missed something).  Because of this I do 
have reservations about progressing the document towards publication.

Section 3.3: Is it the case that if an element is not explicitly identified as 
optional, it’s mandatory?  If that’s the case you may want to mention that in 
the first paragraph of this section

Nits:

There’s occasionally some unidiomatic English (for example, “The command 
mappings described here are specifically for the use to notify [ … ]” rather 
than, for example, “The command mappings described here are specifically used 
to notify [ … ]”, “The information on a [ … ]” rather than “The information 
about a [ … ], etc.),

Section 1, first paragraph:  It’s actually not very clear about what registries 
are informing registrars.  It may be clearer to start with something along the 
lines of “Registries usually inform registrars of maintenance activities in 
different ways.”


___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext