Subject: [scim] Timing of administrative actions related to chartering

From: Roman Danyliw <[email-masked]>
Date: Wed, 1 Sep 2021 21:18:47 +0000

Hi!

All of the regular and active discussion about the charter and deliverables is exactly what is needed as the next step to a working group.  Thanks for continuing the conversation.  While this technical scoping discussion is happening, I wanted to share a bit of detail around the timing of the administrative process of chartering.  

==[ BLUF

To get a WG chartered by IETF 112, a full charter needs to be produced and shared on the mailing list NLT Sept 20-ish.

==[ Details

The WG chartering process typically consists of the following rough steps:

(1) Discuss and produce a v1 of the charter based on mailing list and BOF conversations <== we are here now
-- duration = as long as it takes
-- output = initial charter

(2) Do a call on the mailing list to elicit support for this v1 charter.  I'll be looking for active support and volunteers to produce, review and implement the documents.  If there is dissent or additional recommended finesse, this should be adjudicated or assessed as being in the rough.
-- input = initial charter
-- duration: minimum 1-2 weeks
-- output = possibly revised charter (call it v2)

(3) Bring the v2 charter to the IESG during a telechat for concurrence that it is ready for "external review".  Comments from the IESG should be adjudicated. 
-- input = v2 charter
-- timing = has to be scheduled on the agenda of an IESG telechat with rough a week's notice
-- output = possibly revised charter (call it v3)

(4) Charter is sent for "IETF Review" where feedback and comments are elicited from the community.  Feedback should be discussed and changes to the charter may be made.
-- input = v3 charter
-- duration = 2 weeks
-- output = possibly revised charter (call it v4)

(5) Bring the v4 charter to the IESG again during a telechat for approval.  Final comments from the IESG should be adjudicated.
-- input = v4 charter 
-- timing = has to be scheduled on the agenda of an IESG telechat
-- output = approved WG

Future IESG telechats before IETF 112 are:
-- Thursday, Sept 9
-- Thursday, Sept 23
-- Thursday, October 7
-- Thursday, October 21

Therefore, working backwards, step (5) has to happen at the latest at the Oct-21 telechat meeting.  This means that step (3) has to happen at the Oct-7 meeting (with something final ready by Sept 30, one week before).  Thus, step (3) has to begin NLT Sept 20-ish (to provide for 1 - 2 weeks of review time on the scim mailing list).

In the worst case where these steps do not conclude on the notional schedule, another BOF could be convened at IETF 112.  Practically, since the a WG can't be chartered before agenda slots are defined for IETF 112, a SCIM/SINS meeting will be scheduled as a BOF to reserve agenda time regardless.  If a WG is chartered by the meeting date, this BOF slot turns into a normal WG meeting slot.

Regards,
Roman