Re: IETF 114 - Working Group/BOF/IRTF Scheduling
Robert Sparks <rjsparks@nostrum.com> Tue, 26 April 2022 21:59 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9896FC206751 for <wgchairs@ietfa.amsl.com>; Tue, 26 Apr 2022 14:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level:
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lznR_AYWnOZs for <wgchairs@ietfa.amsl.com>; Tue, 26 Apr 2022 14:58:58 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C283BC20674C for <wgchairs@ietf.org>; Tue, 26 Apr 2022 14:58:58 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 23QLwvDw015875 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <wgchairs@ietf.org>; Tue, 26 Apr 2022 16:58:57 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1651010337; bh=rz9di+XcpUuL0u7zlYpru0Dhqf3e8VsJYtNc6zKWRNk=; h=Date:Subject:From:To:References:In-Reply-To; b=STAMJPBTtCatn7gLxL6i19LJ02GPphxs6p0J0Ss7sOLV04YvKzbnw05bLssGJalJH WlEZ29KQQw4YdAVryrAop1a1LcrdncQztupZwEU/IgqRIB9fPPS42vqUhW8HCraU9U CXjDC+pQsAJDlAYn/HyjgJoC717PuMpurs9bkOYI=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <e8561c16-a730-38b2-7dd1-427270ecfb9a@nostrum.com>
Date: Tue, 26 Apr 2022 16:58:52 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Subject: Re: IETF 114 - Working Group/BOF/IRTF Scheduling
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
To: wgchairs@ietf.org
References: <165099131006.2413.18420729450963190676@ietfa.amsl.com> <db6e3b6e-d4a8-3e67-6871-1fb8371f5c35@nostrum.com>
In-Reply-To: <db6e3b6e-d4a8-3e67-6871-1fb8371f5c35@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/iAJ5erV1kRrwnGofIB4Q2APZlUI>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2022 21:59:02 -0000
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 support@ietf.org. If you are unable to >> use the tool, then you may send your request via email to >> support@ietf.org, 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 support@ietf.org. >> >> =============================================================== >> Area Director Contact Information >> >> IETF Chair >> Lars Eggert <lars@eggert.org> >> >> Applications and Real-Time Area (art) >> Murray Kucherawy <superuser@gmail.com> >> Francesca Palombini <francesca.palombini@ericsson.com> >> >> Internet Area (int) >> Erik Kline <ek.ietf@gmail.com> >> Éric Vyncke <evyncke@cisco.com> >> >> >> Operations & Management Area (ops) >> Warren Kumari <warren@kumari.net> >> Robert Wilton <rwilton@cisco.com> >> >> >> Routing Area (rtg) >> Andrew Alston <andrew-ietf@liquid.tech> >> John Scudder <jgs@juniper.net> >> Alvaro Retana <aretana.ietf@gmail.com> >> >> >> Security Area (sec) >> Roman Danyliw <rdd@cert.org> >> Paul Wouters <paul.wouters@aiven.io> >> >> Transport Area (tsv) >> Martin Duke <martin.h.duke@gmail.com> >> Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com> >> >
- IETF 114 - Working Group/BOF/IRTF Scheduling IETF Agenda
- Re: IETF 114 - Working Group/BOF/IRTF Scheduling Robert Sparks
- Re: IETF 114 - Working Group/BOF/IRTF Scheduling Robert Sparks
- Re: IETF 114 - Working Group/BOF/IRTF Scheduling Robert Sparks
- Re: IETF 114 - Working Group/BOF/IRTF Scheduling Barry Leiba
- Re: IETF 114 - Working Group/BOF/IRTF Scheduling Christian Hopps
- Re: [irsg] IETF 114 - Working Group/BOF/IRTF Sche… Carsten Bormann
- Re: [irsg] IETF 114 - Working Group/BOF/IRTF Sche… Robert Sparks
- Re: [irsg] IETF 114 - Working Group/BOF/IRTF Sche… Michael Richardson
- Re: [irsg] IETF 114 - Working Group/BOF/IRTF Sche… Carsten Bormann