On Mon, May 4, 2020 at 2:20 AM IETF Executive Director <exec-director@xxxxxxxx> wrote:
The IETF Administration LLC has prepared its Draft Strategic Plan 2020 [1].
I think this drfat should be an ID best practice to become updated if needed, but there may be reasons why it was not. If there was a reason, then this plan should follow with all IETF RFC best practices. Therefore, IMO this draft needs to refer to some best practices documents (ex, RFC8711).
This is a significant expansion on the previous IETF LLC strategy and is intended to provide a comprehensive strategy both for the 2020 fiscal year and the long term.
The strategic plan is made up of the following elements, all of which are being presented for comment:
how review or comment become productive if the plan was not input as ID or within IETF process? however, I think this strategy plan is the responsibility of LLC board as RFC8711-sec5.2.
1. **Mission**. This is a literal definition of what the IETF LLC does. The mission rarely changes in the lifetime of the company.
2. **Values**. These define how the company behaves as it follows its mission. These may change over time to reflect broader social changes.
3. **Strategic Goals**. The highest priority goals of the IETF LLC. These may be short-, medium- or long-term goals or a mix. These are the big picture of what the IETF LLC is aiming to do in the next 3-5 years and so are the key setting that the board expects the company to follow.
4. **Strategic Transformations**. These detail the changes that need to be made in order to achieve the strategic goals. Each transformation details the current state and the desired state to transform into. These transformations should be achievable within 1-3 years.
The strategy mostly depends on IETF community Needs, as mentioned in RFC8711:
he role of the Board is to ensure that the strategy and conduct of the IETF LLC is consistent with the IETF's needs -- both its concrete needs and its needs for transparency and accountability. The Board is not intended to directly define the IETF's needs; to the extent that is required, the IETF community should document its needs in consensus-based RFCs (e.g., as the community did in [RFC8718]) and provide more detailed input via consultations with the Board (such as
takes place on email discussion lists or at IETF meetings).
So IMHO, the IETF community should create an RFC for year 2020 to include the IETF community Needs, so then this strategy plan can be more focused and more productive. Therefore, this plan draft must reference the IETF community Needs document (i.e. I was not sure if we have one or not, but if we have one then please add it so we can comment while seeing the needs).
Best Wishes,
AB
This email now begins a two week consultation on this Draft Strategic Plan 2020, closing on Monday 18 May.
If you have any comments or questions then you can submit those by any of the following methods:
* Raising an issue on the Github repository
* Direct to me at exec-director@xxxxxxxx
* Direct to the IETF LLC Board (not including me) at llc-board-only@xxxxxxxx
* To the ietf@xxxxxxxx list
[1] https://github.com/ietf-llc/strategy-2020-consultation/blob/master/DRAFT%20Strategic%20Plan%202020.md
--
Jay Daley
IETF Executive Director
exec-director@xxxxxxxx
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
