On Mon, Feb 14, 2022 at 10:15 AM Adrian Farrel <adrian@xxxxxxxxxxxx> wrote:
[Beware: trumpet blowing]
Yes, I often take the time as document shepherd to chivvy the process along. Chasing ADs to review, issue IETF last call, put the document on an agenda; chasing authors to update the document after reviews; chasing ADs and authors to talk about Comments and Discusses; chasing ADs to clear Discusses when the document has been updated. Even chasing authors to do Auth48 sign-off (although the RPC is pretty good at that).
I did some shepherd ing both as a chair and as a WG member. To my knowledge, shepherd's job finishes after sending the document to IESG.
The rest just flows along, no need to keep checking everything at every step.
Actually it used to be the chair(s) who did the job, I think that was the correct procedure.
Behcet
Is that part of the shepherd's brief? By 4858, possibly. By my understanding of what is needed, definitely.
Cheers,
Adrian
-----Original Message-----
From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of Salz, Rich
Sent: 14 February 2022 16:03
To: tom petch <daedulus@xxxxxxxxxxxxx>; Eric Vyncke (evyncke) <evyncke=40cisco.com@xxxxxxxxxxxxxx>; Donald Eastlake <d3e3e3@xxxxxxxxx>
Cc: ietf@xxxxxxxx
Subject: Re: RFC 4858 on shepherding
My original note wasn't clear, sorry for the confusion.
RFC 4858 talk in detail about writing the shepherd document, and then working with the various parties to get the document through the AD, IESG, IETF LC, and IANA reviews. I was asking if the *everything but the document part* is obsolete. Does anyone have recent examples (use your own definition of recent; mine is like five years) where the *document shepherd* guided the draft through all of the other parts, as described in the RFC?
