RE: 2hr sessions and agendas

[Susan Hares <[e-mail]>]

Michael: 

IDR is one of the WG that requests 2 meetings (normally 1 meeting with 2
hours and 1 meeting with 1 hour).    

In the past with in person meetings, we ran discussions during the IDR
meetings in the IETF.  Also, we ran small group discussions within the week.
We also ran interims if they were needed. 

During the periods of online IETF meetings,  we try to updates on draft and
new work into the 2 meetings.  Often times status reports come from the
wiki.  
During the period of online IETF meetings,  have run 2-3 interims between
the meetings with lengthy discussions (time period 2-2.5 hours).    Our work
is schedule against large items (BGP-LS, SR-Routing, Flow Specification v2,
CAR/DT, Auto-configuration) with the ability to fit emerging work needed for
BGP. 

We are continual communication with our AD about how to best use our time. 

May I suggest that we are adhering to the spirit of your idea, but the form.
One of the best things IETF is that different areas and different ADs is
that we can take the spirit of the idea, and not get tied down to specific
forms. 

Sue 

-----Original Message-----
From: WGChairs [mailto:[e-mail]] On Behalf Of Michael
Richardson
Sent: Saturday, January 15, 2022 6:06 PM
To: Working Group Chairs; [e-mail]
Subject: 2hr sessions and agendas


IETF Agenda <[e-mail]> wrote:
    > Requests for more than two hours of total meeting time are unlikely to
    > succeed. In special cases, you may request more than two hours of
    > meeting time, but the IESG will likely request a rationale, and
    > scheduling pressure may still make it impossible to grant any
    > additional meeting slots. Please see this email from the IESG [2] for
    > more detailed guidance on how to structure your session requests.

I want to start by thanking the IESG for being more rigorous here.

I would like the IESG to encourage any WG asking for 2hr (or more) present a
clear agenda for the time usage, and that no more than 50% that time be for
presentations and/or status updates.
The bulk of the time should be for discussion, ideally relating to
identified issues.  I don't think that this is a new request, I just think
it's worth repeating.

I'd like to suggest that we have no 2hr slots (like we did on Thursday at
IETF112), and that all requests for 2hrs be turned into two requests for
1hr.

Even if I don't get to travel in the end, I'm excited for 113.