Stuart and Ted,

With all due respect for your $dayjob workload, I keep wondering why these 2 
RFC-to-be take so long (approved in April 2024 and in AUTH48 since September 
2024!) to get moving.

If the authors want to remove these two RFC-to-be from the publication queue, 
i.e., do not publish them as they are, please let me know and I will 
investigate how they could be removed.

“Perfect is the enemy of the good”  and I would hate to abuse my AD power when 
actioning 
https://datatracker.ietf.org/doc/statement-iesg-iesg-statement-on-auth48-state-20060105/

Your documents are useful, in good shape, and well written, so let’s get them 
out.

Regards

-éric

From: Stuart Cheshire <chesh...@apple.com>
Date: Wednesday, 21 May 2025 at 02:27
To: Sarah Tarrant <starr...@staff.rfc-editor.org>
Cc: Ted Lemon <mel...@fugue.com>, Eric Vyncke (evyncke) <evyn...@cisco.com>, 
Chris Box <chris.box.i...@gmail.com>, dnssd-...@ietf.org <dnssd-...@ietf.org>, 
dnssd-cha...@ietf.org <dnssd-cha...@ietf.org>, auth48archive 
<auth48archive@rfc-editor.org>, RFC Editor <rfc-edi...@rfc-editor.org>
Subject: Re: [AD] AUTH48: RFC-to-be 9664 <draft-ietf-dnssd-update-lease-08> for 
your review
I reviewed the latest draft yesterday. I will confer with Ted tomorrow morning 
and then send my email reply.

Stuart Cheshire
-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to