Re: [irsg] IETF 114 - Working Group/BOF/IRTF Scheduling

[Carsten Bormann <[e-mail]>]

And since the damage from not recording an AD “be there” can be significant, I’m not happy that we are asked to rely on a mechanism that we can’t see whether it’s doing its work.

Grüße, Carsten


> On 2022-04-28, at 09:33, Christian Hopps <[e-mail]> wrote:
> 
> 
> I wondered the same thing. I removed the chairs and the AD. The visual feedback I got was that it now says:
> 
>   People who must be present:          None
> 
> which to be honest seems a lot more confusing that if it showed the AD and chairs. Not sure what visual noise we're avoiding here.
> 
> Thanks,
> Chris.
> 
> Barry Leiba <[e-mail]> writes:
> 
>> The chairs, too, I presume, yes?
>> 
>> Barry
>> 
>> On Wed, Apr 27, 2022 at 10:10 AM Robert Sparks <[e-mail]> wrote:
>>> 
>>> The session request tool issue has been resolved. Please resume
>>> requesting sessions.
>>> 
>>> NOTE: An upcoming release will make it clear that you should not include
>>> your AD in the "must be present" list. The scheduling tool already knows
>>> that a Working Group's AD needs to be present, and including them in the
>>> must-be-present list introduces unnecessary visual noise. Please remove
>>> the AD from the list as you're making your session requests this time.
>>> 
>>> RjS
>>> 
>>> On 4/26/22 4:58 PM, Robert Sparks wrote:
>>> > Update: We expect to put a release into production tomorrow that will
>>> > address this issue.
>>> >
>>> > RjS
>>> >
>>> > On 4/26/22 1:06 PM, Robert Sparks wrote:
>>> >> There is an issue with session requests at the moment (all are
>>> >> failing). See https://github.com/ietf-tools/datatracker/issues/3889
>>> >> for status. I'll send another note here when the issue is resolved.
>>> >>
>>> >> RjS
>>> >>
>>> >> On 4/26/22 11:41 AM, IETF Agenda wrote:
>>> >>> -----------------------------------------------------------------
>>> >>> IETF 114 – Philadelphia, PA, USA
>>> >>> Meeting Dates: July 23-29, 2022
>>> >>> -----------------------------------------------------------------
>>> >>>
>>> >>> We are now accepting scheduling requests for all Working Groups and
>>> >>> Research Groups until Friday, June 10, 2022 and BOF requests until
>>> >>> Friday, May 27, 2022.
>>> >>>
>>> >>>
>>> >>> ===========================================================
>>> >>> What’s New for IETF 114
>>> >>>
>>> >>> The session request form will ask you to estimate the number of
>>> >>> people attending. Please make your best guess as to the total number
>>> >>> of participants, based on your last several online sessions and
>>> >>> in-person at IETF 113 if applicable. When we assign conference rooms
>>> >>> at the meeting, we will make room size estimates based on the
>>> >>> proportion of in-person registrations.
>>> >>>
>>> >>> 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 [1]
>>> >>> for more detailed guidance on how to structure your session requests.
>>> >>>
>>> >>> As of IETF 112, BOFs are now requested via the Datatracker instead
>>> >>> of the wiki. Please see the BoF section of this email below for more
>>> >>> details.
>>> >>>
>>> >>> [1]
>>> >>> https://mailarchive.ietf.org/arch/msg/wgchairs/_x2nc9Xqa5i1U4SuEFs3eggTCyk/
>>> >>>
>>> >>> ===========================================================
>>> >>> How to Request a WG or RG Session
>>> >>>
>>> >>> Requests to schedule Working Group or Research Group sessions should
>>> >>> be submitted using the "IETF Meeting Session Request Tool." The URL
>>> >>> for the tool is:
>>> >>>
>>> >>> https://datatracker.ietf.org/secr/sreq/
>>> >>>
>>> >>> If you require an account on this tool, or assistance in using it,
>>> >>> then please send a message to [e-mail].  If you are unable
>>> >>> to use the tool, then you may send your request via email to
>>> >>> [e-mail], with a copy to the appropriate Area Director(s).
>>> >>>
>>> >>> As a reminder, the conflict list options are:
>>> >>>
>>> >>> - Chair Conflict: to indicate other WGs the Chairs also lead, or
>>> >>> will be active participants in the upcoming meeting
>>> >>>
>>> >>> - Technology Overlap: to indicate WGs with a related technology or a
>>> >>> closely related charter
>>> >>>
>>> >>> - Key Participant Conflict (e.g., presenter, Secretary, etc.): to
>>> >>> indicate WGs with which key participation may overlap in the
>>> >>> upcoming meeting
>>> >>>
>>> >>> The Special Request field will continue to be available for more
>>> >>> specific needs, and Responsible AD conflicts are already taken into
>>> >>> consideration. Please make sure you take a few minutes to check your
>>> >>> conflict lists carefully!
>>> >>>
>>> >>> ===========================================================
>>> >>> How to Request a BOF
>>> >>>
>>> >>>
>>> >>> The BOF deadline is on May 27. The intent of this earlier deadline
>>> >>> is to allow BOF proponents time to work more closely with the IESG
>>> >>> and IAB to develop their proposal before final approval
>>> >>> determinations. If your initial proposal needs further work you may
>>> >>> revise and resubmit before final decisions must be made.
>>> >>>
>>> >>> BOFs will NOT be scheduled unless the Area Director approves the
>>> >>> BOF. The proponents behind a BOF need to contact a relevant Area
>>> >>> Director, preferably well in advance of the BOF approval deadline
>>> >>> date. The AD needs to have the full name of the BOF, its acronym,
>>> >>> suggested names of chairs, an agenda, full description of the BOF
>>> >>> and the information below. Please refer to
>>> >>> https://datatracker.ietf.org/doc/bof-requests/new/ for more
>>> >>> information about planning a BOF. You will need a Datatracker
>>> >>> account to submit a BOF request.
>>> >>>
>>> >>> You MUST provide the following information before a BOF session will
>>> >>> be scheduled:
>>> >>>
>>> >>> a. BOF full name with acronym in brackets
>>> >>> b. AREA under which the BOF appears
>>> >>> c. CONFLICTS you wish to avoid, please be as specific as possible
>>> >>> d. Special requests
>>> >>> e. Number of sessions
>>> >>> f. Length of session: 60 minutes or 120 minutes
>>> >>>
>>> >>>
>>> >>> ===========================================================
>>> >>> Deadlines
>>> >>> Cut-off dates are subject to change.
>>> >>>
>>> >>> • 2022-04-26 (Tuesday): Working Group and BOF scheduling begins.
>>> >>> • 2022-05-27 (Friday): Cut-off date for BOF proposal requests.
>>> >>> • 2022-06-10 (Friday): Cut-off date for requests to schedule Working
>>> >>> Group meetings at UTC 23:59.
>>> >>> • 2022-06-17 (Friday): Cut-off date for Area Directors to approve
>>> >>> BOFs at UTC 23:59.
>>> >>> • 2022-06-24 (Friday): Preliminary agenda published for comment.
>>> >>> • 2022-06-29 (Wednesday): Cut-off date for requests to reschedule
>>> >>> Working Group and BOF meetings UTC 23:59.
>>> >>> • 2022-07-01 (Friday): Final agenda to be published.
>>> >>> • 2022-07-13 (Wednesday): Draft Working Group agendas due by UTC 23:59.
>>> >>> • 2022-07-18 (Monday): Revised Working Group agendas due by UTC 23:59.
>>> >>>
>>> >>>
>>> >>> ===========================================================
>>> >>>
>>> >>> Submitting Session Agendas
>>> >>>
>>> >>> Please submit the agendas for your sessions as early as possible
>>> >>> using the "IETF Meeting Materials Management Tool," a Web-based tool
>>> >>> for making your meeting agenda, minutes, and presentation slides
>>> >>> available to the community before, during, and after an IETF
>>> >>> meeting.  If you are a BOF chair, then you may use the tool to
>>> >>> submit a revised agenda as well as other materials for your BOF once
>>> >>> the BOF has been approved.
>>> >>>
>>> >>> The URL for the tool is:
>>> >>>
>>> >>> https://datatracker.ietf.org/secr/proceedings/
>>> >>>
>>> >>> Agendas submitted via the tool will be available to the public on
>>> >>> the "IETF Meeting Materials" webpage as soon as they are submitted.
>>> >>>
>>> >>> The URL for the "IETF 114 Meeting Materials" Web page is:
>>> >>>
>>> >>> https://datatracker.ietf.org/meeting/114/materials.html
>>> >>>
>>> >>> If you are a Working Group chair, then you already have accounts on
>>> >>> the "IETF Meeting Session Request Tool" and the "IETF Meeting
>>> >>> Materials Management Tool."  The same User ID and password will work
>>> >>> for both tools.  If you are a BOF chair who is not also a Working
>>> >>> Group chair, then you will be given an account on the "IETF Meeting
>>> >>> Materials Management Tool" when your BOF has been approved.  If you
>>> >>> require assistance in using either tool, or wish to report a bug,
>>> >>> then please send a message to [e-mail].
>>> >>>
>>> >>> ===============================================================
>>> >>> Area Director Contact Information
>>> >>>
>>> >>> IETF Chair
>>> >>> Lars Eggert <[e-mail]>
>>> >>>
>>> >>>   Applications and Real-Time Area (art)
>>> >>> Murray Kucherawy <[e-mail]>
>>> >>> Francesca Palombini <[e-mail]>
>>> >>>
>>> >>>   Internet Area (int)
>>> >>> Erik Kline <[e-mail]>
>>> >>> Éric Vyncke <[e-mail]>
>>> >>>
>>> >>>
>>> >>> Operations & Management Area (ops)
>>> >>> Warren Kumari <[e-mail]>
>>> >>> Robert Wilton <[e-mail]>
>>> >>>
>>> >>>
>>> >>> Routing Area (rtg)
>>> >>> Andrew Alston <[e-mail]>
>>> >>> John Scudder <[e-mail]>
>>> >>> Alvaro Retana <[e-mail]>
>>> >>>
>>> >>>
>>> >>> Security Area (sec)
>>> >>> Roman Danyliw <[e-mail]>
>>> >>> Paul Wouters <[e-mail]>
>>> >>>
>>> >>>   Transport Area (tsv)
>>> >>> Martin Duke <[e-mail]>
>>> >>> Zaheduzzaman Sarker <[e-mail]>
>>> >>>
>>> >>
>>> >
>>> 
>