During the IESG-only portion of the retreat we discussed several process-related issues.
Understanding and navigating IETF processes can be difficult for individuals without previous experience working through them. We spent a significant portion of our time discussing various proposals to help new work flourish in the IETF and to help identify and support new participants. You'll be seeing some changes as a result: more advance notice to remind the community about the Birds of a Feather (BoF) deadline, encouragement embedded in our Important Dates to those thinking about proposing a BoF to alert the IESG about such proposals as soon as possible, and updated material on the IETF web site to make it easier for newcomers to understand the pathways by which new work can begin in the IETF.
We also spent some time on our own and with the IAB talking about a collection of topics related to the RFC series and document processing. We discussed some of the confusion that is caused by our current process for issuing document status changes, and a number of people in the leadership agreed to go think about ways to better combine the arguably mutable elements of our documents (errata, status changes, bis-style updates) with our current concept of immutable RFCs. The IESG also discussed some confusion we have noticed about the relationship between the status of informational RFCs and IETF consensus, and as a result a few ADs signed up to think further about how this could be clarified within the IETF document stream or the RFC series as a whole. We reviewed an upcoming experiment involving a few authors' use of Github to process changes during AUTH48. And we adopted a new procedure for scheduling documents on IESG telechats, such that under normal circumstances documents will be placed on telechats in the order in which their ballots were issued.
As always, feedback on topics that you think the IESG should be tackling is welcome at firstname.lastname@example.org.