Thank you, Warren, for your replies on the 3 related I-Ds, I will proceed 
shortly with the IETF Last Call.

About deprecating an already historic RFC, I am unsure as well as those 2 terms 
are not really well defined. Let’s see what the IESG/RFC Editor say indeed, 
smart idea to add this note in the text.

-éric


From: Warren Kumari <[email protected]>
Date: Tuesday, 18 February 2025 at 23:39
To: Eric Vyncke (evyncke) <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [DNSOP] AD review of draft-ietf-dnsop-must-not-ecc-gost-02




On Mon, Feb 17, 2025 at 11:15 AM, Eric Vyncke 
<[email protected]<mailto:[email protected]>> 
wrote:
Dear all,

Thanks for your patience as I was on vacations when the publication of this I-D 
was requested. As the DNSOP responsible AD is also an author, I was selected as 
the acting responsible AD for this I-D. Hence, here are some comments that I 
want to be addressed (either by replying to this email or by a revised I-D) 
before proceeding to the IETF Last Call.


1.     The shepherd write-up is very terse , so far so good, but does not 
include a justification for the intended status (PS is the correct one of 
course) and is unclear whether authors have accepted to be cited as authors 
(even if I guess so)

2.     Even if RFC 5933 is already marked historic, let’s be clear and add 
meta-data and text in abstract/introduction/and shepherd write-up that this I-D 
deprecates RFC 5933

Done, but I'm not convinced this is a good idea. I added a note:


[RFC Editor: please remove this before publication: It is unclear if updating

RFC5933 (a Historic document) is the correct thing to do or not. We did it

so that it shows up in Datatracker and similar, but this may be a

mistake. We are happy to change this if the RFC Editor / IESG / whoever thinks

this is a bad idea.]

3.     Section 4, even if the “should” are not in uppercase, adding the 
consequences of not following the “should” should be explained

Thank you, done.



4.     RFC 9499 appears as a reference but is not cited, please remove it

Thanks, done.


Once the above points are addressed, I am proceeding with the publication of 
this important document.

Regards,

-éric



_______________________________________________
DNSOP mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to 
[email protected]<mailto:[email protected]>

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to