Hi Joe, all,
On 2/17/23 21:48, Joe Abley wrote:
On Fri, Feb 17, 2023 at 15:03, Peter Thomassen <pe...@desec.io
<mailto:pe...@desec.io>> wrote:
I am not sure whether draft expiry impacts the WG document handling process in
any way.
I would not worry. You can always reset the timer by bumping the version and
the date and resubmitting, if it bothers you. The particular lifetime of an I-D
is somewhat arbitrary; the main thing is that it is finite.
Thank you for explaining! I wasn't sure whether expiry would imply that a draft
would have to be (e.g.) re-adopted etc.pp. I'm relieved to know that's not the
case.
I nevertheless pushed a new revision (-03) to reflect the implementation
updates that have happened since -02.
Regardless, I had thought that the WG would generally process adopted drafts
within their expiration window (which is why a process hiccup had come to my
mind). I'm not sure if there is some policy about this or not.
I obviously do not speak for the chairs. However, in my experience are all
volunteers here, and we all do our best. Sometimes things take longer than we
expect and life goes on.
Yes, and it's indeed a great gift to the community that the chairs (and other
leadership, for that matter), are putting in their time volunteering. (Thank
you!)
I had no intentions to be pushy, and was simply concerned that expiration may
have undesirable consequences. I'd like to apologize in case anything I wrote
came across in any other way. Obviously, if there's no adverse consequences,
then there's no rush. :-)
Best,
Peter
--
https://desec.io/
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
