<?xmlversion='1.0' encoding='utf-8'?>version="1.0" encoding="UTF-8"?> <!-- draft submitted in xml v3 --> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?><!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.17 (Ruby 3.1.3) --> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-shmoo-online-meeting-05" number="9400" submissionType="IETF" category="info" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" updates="" obsoletes="" xml:lang="en" version="3"> <!-- xml2rfc v2v3 conversion 3.15.3 --> <front> <title abbrev="Organization of Online Meetings">Guidelines for the Organization of Fully Online Meetings</title> <seriesInfoname="Internet-Draft" value="draft-ietf-shmoo-online-meeting-05"/>name="RFC" value="9400"/> <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind"> <organization>Ericsson</organization> <address> <email>mirja.kuehlewind@ericsson.com</email> </address> </author> <author initials="M." surname="Duke" fullname="Martin Duke"> <organization>Google</organization> <address> <email>martin.h.duke@gmail.com</email> </address> </author> <dateyear="2022" month="December" day="15"/> <keyword>Internet-Draft</keyword>year="2023" month="June"/> <area>gen</area> <workgroup>shmoo</workgroup> <abstract> <t>This document provides guidelines for the planning and organization of fully online meetings, regarding the number, length, and composition of sessions on the meeting agenda. These guidelines are based on the experiencewithgained by holding online meetings during the COVID-19 pandemic in 2020 and 2021.</t> </abstract><note removeInRFC="true"> <name>Discussion Venues</name> <t>Discussion of this document takes place on the Stay Home Meet Only Online Working Group mailing list (manycouches@ietf.org), which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/manycouches/"/>.</t> <t>Source for this draft and an issue tracker can be found at <eref target="https://github.com/mirjak/draft-shmoo-online-meeting"/>.</t> </note></front> <middle> <section anchor="introduction"> <name>Introduction</name> <t>In 2020, the COVID-19 pandemic forced the IETF to convert all its plenary meetings to online-only events. This document records the experience gained by holding plenary meetings fully online and proposes guidelines based on this experience. In general, participant surveys indicated satisfaction with the organization of these meetings.</t> <t>Although these guidelines reflect lessons learned in 2020 and 2021, the IETF is encouraged to continue to experiment with the format and agenda of fully online meetings, using this document as a baseline.</t> <t>Hybrid meetings (meaning meetings that have large remote participation but also onsite participation) are out of scope. However, some of the experience gained from fully online meetings might also provide input for decisions regarding the organization of hybrid meetings.</t> <section anchor="requirements-language"> <name>Requirements Language</name> <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t> <t>This document uses the term "plenary meeting" for the whole IETF meeting that covers the IETF meeting week; this term is used to distinguish the plenary meeting from other IETF meetings like "interim meetings". The term "administrative plenary" is used for the respective session during the IETF meeting week that is usually hosted on Wednesday.</t> </section> </section> <section anchor="some-history"> <name>Some History</name> <t>When the World Health Organization (WHO) declared aworld-wideworldwide pandemic in March 2020, the IETF canceled its plenary meeting and organized an online replacement in less thantwo2 weeks. For this first online-only meeting, the agenda was reduced to a set of sessions thatbenefittedbenefited most from cross-area participation, like BoFs, first-time meetings of new working groups, and dispatch sessions. It also included the administrative plenary to preserve the officialhand-overhandover procedures that occur attheMarchmeeting,IETF meetings, as described in <xref target="RFC8713"/>.</t> <t>With a reduced agenda, the meeting format was2two sessions (about 4 hours) per day with a maximum of two parallel tracks. Other working group meetings were scheduled as interims over the followingsix6 weeks. The IESG published a purely advisory recommended schedule <xref target="INTERIM-SCHEDULE"/> to reduce conflicts among those interims.</t> <t>While satisfaction was high right after themeetinngmeeting <xreftarget="_107-FEEDBACK"/>,target="IETF107-FEEDBACK"/>, some participants later indicated in mailing listdiscussiondiscussions that the period of intensive interims had a greater impact on their calendar than a single plenary meeting week, and in some meetings participation was reduced. Those interims tended to occur at times convenient for the bulk of participants, which was convenient for most but could exclude those in less common time zones.</t> <t>For the remainder of 2020 and 2021, the online schedule was switched back to be similar to an in-person meeting(1-2 hour(1- to 2-hour slots and8-9eight or nine parallel tracks). However, each day was limited to 5-6 hours in recognition that remote participation is more tiring.</t> <t>All fully online meetings followed the time zone of the planned in-person meeting location. As asix-hour6-hour agenda has some flexibility regarding the start time while still fitting within a previously used 8-hour in-person agenda, the start time was approximately noon, with adjustments of an hour or so to mitigate the impact of early morning hours in time zones with many participants. As selection of in-person meeting sites was consistent with the 1-1-1 guideline as documented in <xref target="RFC8719"/>, this approach was intended to share the burden across all common geographies roughly equally.</t> </section> <section anchor="guidelines-for-online-meeting-planning"> <name>Guidelines for Online Meeting Planning</name> <section anchor="time-zone-selection"> <name>Time Zone Selection</name> <t>The following algorithm was not used in 2020 or 2021, but it enables most participants to avoid late-night sessions in2two out of every3three fully online IETF plenary meetings. Basically, every fully online meeting is for two regions of the three regions described in <xreftarget="RFC8179"/>,target="RFC8719"/>, with one being roughly after sunrise and the other around sundown. This has thetradeofftrade-off that the third region is in the middle of night.</t> <t>The times are also seasonally adjusted to leverage differentials in Daylight Saving Time. These time slots are as follows, in UTC, based on the Daylight Saving Practices at the time of publication:</t> <table> <thead> <tr> <th align="left">Name</th> <th align="left">Times (Northern Summer)</th> <th align="left">Times (Northern Winter)</th> </tr> </thead> <tbody> <tr> <td align="left">North America Night</td> <td align="left">0500-1100 UTC</td> <td align="left">0600-1200 UTC</td> </tr> <tr> <td align="left">Asia Night</td> <td align="left">1300-1900 UTC</td> <td align="left">1400-2000 UTC</td> </tr> <tr> <td align="left">Europe Night</td> <td align="left">2200-0400 UTC</td> <td align="left">2200-0400 UTC</td> </tr> </tbody> </table> <t>Note that the"European"Europe Night" slot covers the"Early Morning""early morning" slot for Asia where most countries do not have Daylight Saving Time.</t> <t>If Daylight Saving Practiceschange, whichchange -- this change is under consideration in multiple countries at the time ofpublication,publication -- this table may need adjustment.</t> <t>The intent of rotating between these three slots is to scatter meetings throughout the course of the global day, to maximize the ease of participants so that no attendee has to be consistently inconvenienced, regardless of their location and what time of day is optimal for their schedule. However, as participation is distributed globally, it needs to be acknowledged that restricting the scheme to three regions observes the intent of <xreftarget="RFC8179"/>target="RFC8719"/> but does not achieve the goal of2two non-late-night sessions for all participants equally.</t> <section anchor="guidelines-for-selection"> <name>Guidelines forselection</name>Selection</name> <t>The IETF <bcp14>SHOULD</bcp14> select a start time from these three choices based on the prior three meetings. The following table covers all permutations of previous meetings heldin-personin person in Region A, B, orC;C or remotely in the nights of one of those regions.</t> <table> <thead> <tr> <thalign="left">3 meetings ago</th>align="left">Three Meetings Ago</th> <thalign="left">2 meetings ago</th>align="left">Two Meetings Ago</th> <th align="left">Last Meeting</th> <th align="left">Online Selection</th> </tr> </thead> <tbody> <tr> <td align="left">Any</td> <td align="left">Any</td> <td align="left">In-Person A</td> <td align="left">A Night</td> </tr> <tr> <td align="left">Any</td> <td align="left">Online A Night</td> <td align="left">Online B Night</td> <td align="left">C Night</td> </tr> <tr> <td align="left">Online A Night</td> <td align="left">In-Person B</td> <td align="left">Online B Night</td> <td align="left">C Night</td> </tr> <tr> <td align="left">In-Person A</td> <td align="left">In-Person B</td> <td align="left">Online B Night</td> <td align="left">A Night</td> </tr> <tr> <td align="left">In-Person A</td> <td align="left">In-Person A</td> <td align="left">Online A Night</td> <tdalign="left">seealign="left">See below</td> </tr> <tr> <td align="left">Online A Night</td> <td align="left">Online B Night</td> <td align="left">Online C Night</td> <td align="left">A Night</td> </tr> </tbody> </table> <t>This table follows two basicguidelines: 1) Wheneverguidelines:</t> <ol spacing="normal" type="%d)"> <li>Whenever a fully online meeting follows an in-person meeting, the online meeting time is used that most disadvantagesmostthe participants in the time zone where the in-person meeting washeld. 2) Ifheld.</li> <li>If multiple fully online meetings follow each other, the time zone selection should be rotated based on the most recent time zonesthatin which the in-person meetings wereheld in.</t>held.</li> </ol> <t>The final case occurs in the rare event that back-to-back in-person plenary meetings occur in the same region. In this case, find the most recent meeting that wasneitherin neither 'A' (ifin-person) norin'A' nightperson) nor 'A Night' (if fully online). If this meeting wasin-personin person in region 'B', then the next meeting should be in'B' Night.'B Night'. If it was remote in'B' Night,'B Night', the next meeting should be in'C' Night.</t>'C Night'.</t> </section> </section> <section anchor="number-of-days-and-total-hours-per-day"> <name>Number of Days and Total Hours per Day</name> <t>By 2021, fully online meetings were consistently held over 5 days with roughly 6-hour meeting days. The day with the administrative plenary, which concludes with multiple open mic sessions, sometimes exceeded this limit.</t> <t>Six hours of online meetings, with two 30-minute breaks, was a compromise between the physical limits of attending an online meeting in an inconvenient timezone,zone and the demand for many sessions with a manageable number of conflicts. The IETF 109 feedback <xreftarget="_109-SURVEY"/>target="IETF109-SURVEY"/> indicated broad satisfaction with a 5-day meeting but only medium satisfaction with the overall length of each day.</t> <t>The IETF did not seriously consider extending sessions into the weekend before or after the main meeting week, although at IETF 108 and subsequent meetings the Hackathon occupied the entire week before (see <xref target="RFC9311"/>).</t> </section> <section anchor="sessionbreak-length"> <name>Session/Break Length</name> <t>For fully onlinemeetingsmeetings, there are typically fewer sessions per day than for in-person meetings, to keep the overall meeting day to roughly 6 hours. With fewer sessions, chairs were offered only two options for session length (instead of three).</t><t>IETF-108,<t>IETF 108, based on an indicated preference of the community, scheduled 50- and 100-minute slots, with 10-minute breaks, in order to keep the overall day length at 5 hours. This resulted in many sessions going over time, which indicated that 10 minutes for breaks is not practical.</t> <t>The survey afterIETF-109IETF 109 <xreftarget="_109-SURVEY"/>target="IETF109-SURVEY"/> showed high satisfaction with 60/120-minute session lengths and 30-minute breaks, and a significant improvement in satisfaction overIETF-108.</t>IETF 108.</t> <t>The longer breaks, while extending the day, provided adequate time for meals, exercise, and "hallway" conversations using online tools.</t> </section> <section anchor="tracks"> <name>Number of Parallel Tracks</name> <t>In-person meetings are limited in the number of parallel tracks by the number of meeting rooms, but online meetings are not. However, more parallel tracksincreaseswould increase the number of possible agenda conflicts.</t> <t>If the total number of requested sessions exceeds the capacity of the usual8eight parallel tracks, it is possible for a fully online meeting to simply use more tracks. If the number and length of meeting daysisare seen as fixed, this decision is implicitly made by the working group chairs requesting a certain number of sessions and length.</t><t>IETF-111<t>IETF 111 used9nine parallel tracks for some of thesessions,sessions and experienced slightly more conflicts in theagenda schedulingagenda-scheduling process, though there was no statistically significant increase in dissatisfaction about conflicts in the survey <xreftarget="_111-SURVEY"/>.</t>target="IETF111-SURVEY"/>.</t> <t>The IESG encouraged working group chairs to limit their session requests and use interim meetings aggressively for focused work.</t> </section> </section> <section anchor="additional-considerations-and-recommendations"> <name>Additional Considerations and Recommendations</name> <section anchor="full-limited"> <name>Full vs. Limited Agenda (andinterim meetings)</name>Interim Meetings)</name> <t>TheIETF-108IETF 108 meeting survey <xreftarget="_108-SURVEY"/>target="IETF108-SURVEY"/> asked about the structure of that meeting (full meeting) compared to that of IETF 107, which hosted only a limited set of sessions followed by interims in the weeks after. The structure of IETF 108 was preferred by 82%. Respondents valued cross-participation and an intensive meeting week for maintaining project momentum.</t> <t>Furthermore, a well-defined meeting time, rather than spreading many interims over the whole year, can make deconflicting with other non-IETF meetings easier.</t> <t>However, interim meetings can also help to reduce scheduling conflicts during an IETF week and allow for a more optimal time slot for the key participants. While interim meetings are less likely to attract people with casual interest, they provide a good opportunity for the most active participants of a group to have detailed technical discussions and solve recorded issues efficiently.</t> </section> <section anchor="flexibility-of-time-usage"> <name>Flexibility of Time Usage</name> <t>This document recommends further experiments with reducing conflicts by leveraging the increased flexibility of the online format.</t> <t>An in-person meeting must fit all sessions into an acceptable length for international travel (usually roughly a week), but online meetings do not have that constraint.</t> <t>Therefore, it would be possible to keep most regular working group sessions within the usualfive5 main meeting days but have some of the more conflicted sessions in other dedicated time slots. As the Hackathon for fully online meetings is usually held in the week before the online plenary meeting <xref target="RFC9311"/>, that week is already a highly active week for many IETF participants and might provide an opportunity to schedule a few selected sessions.</t> <t>This might work especially well for sessions that are of high interest to a large part of the community, such as BoFs and dispatch meetings, and therefore hard to schedule during the main IETF week.</t> <t>At IETF 112, the IESG ran an experiment where the administrative plenary was scheduled on the Wednesday before the official session week. The experiment report <xreftarget="_112-EXPERIMENT"/>target="IETF112-EXPERIMENT"/> found that it led to a reduction in scheduling conflicts but also a slight drop in attendance of the administrative plenary, partly due to insufficient awareness.</t> </section> <section anchor="inclusivity-and-socializing"> <name>Inclusivity and Socializing</name> <t>Participation in the fully online meetings in 2021 was high and had a stable per-country distribution, even though time zones were rotated. This indicates that online meetings support a more consistent geographic distribution of participants than in-person meetings, where participation often fluctuates based on the location.</t> <t>However, online meetings do not provide an equivalent opportunity to socialize. Despite significant investment in tools to foster hallway conversations, many did not use those tools, whether due to ignorance of them, dislike of the tools, or a preference fortheother activities at home (including sleep and food) over hallway interactions.</t> <t>There was a decrease insubmissionsubmissions of new (-00)draftsInternet-Drafts during 2020 and 2021, although the overall number of draft submissions remainedstable, whichstable; this decrease in new submissions mightresulthave resulted from the loss of these interactions. Informal conversations might be important to inspire new work.</t> </section> <section anchor="experiments"> <name>Experiments</name> <t>This document recommends further experiments with the meeting structure. Often, only practical experience can answer open questions. A given meeting <bcp14>SHOULD</bcp14> only experiment with one major change at a time in order to be able to assess the outcome correctly. Furthermore, the IESG <bcp14>SHOULD</bcp14> announce any such experiment well in advance, so people can adjust to changes and potentially provide feedback.</t> </section> <section numbered="true" toc="default"> <name>IANA Considerations</name> <t>This document has no IANA actions.</t> </section> <sectionanchor="acknowledgments"> <name>Acknowledgments</name> <t>Thanks to Brian Carpenter, Lars Eggert, Toerless Eckert, Charles Eckel, Jason Livingood, Sanjeev Gupta, Dale Worley, and Mark Nottingham for their reviews and many from more for their input and suggestions on the time zone discussion!</t>numbered="true" toc="default"> <name>Security Considerations</name> <t>This document has no security considerations.</t> </section> </section> </middle> <back> <references> <name>References</name> <references> <name>Normative References</name><reference anchor="RFC2119"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <author fullname="S. Bradner" initials="S." surname="Bradner"> <organization/> </author> <date month="March" year="1997"/> <abstract> <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/> </reference> <reference anchor="RFC8174"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <author fullname="B. Leiba" initials="B." surname="Leiba"> <organization/> </author> <date month="May" year="2017"/> <abstract> <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="8174"/> <seriesInfo name="DOI" value="10.17487/RFC8174"/> </reference> <reference anchor="RFC8179"> <front> <title>Intellectual Property Rights in IETF Technology</title> <author fullname="S. Bradner" initials="S." surname="Bradner"> <organization/> </author> <author fullname="J. Contreras" initials="J." surname="Contreras"> <organization/> </author> <date month="May" year="2017"/> <abstract> <t>The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process. The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This document sets out the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026. This document also obsoletes RFCs 3979 and 4879.</t> </abstract> </front> <seriesInfo name="BCP" value="79"/> <seriesInfo name="RFC" value="8179"/> <seriesInfo name="DOI" value="10.17487/RFC8179"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8719.xml"/> </references> <references> <name>Informative References</name> <referenceanchor="_107-FEEDBACK"anchor="IETF107-FEEDBACK" target="https://www.ietf.org/media/documents/ietf-107-survey-results.pdf"> <front> <title>IETF 107 Virtual MeetingSurvey Report</title>Survey</title> <author initials="J." surname="Daley"> <organization/> </author> <date year="2020" month="April" day="17"/> </front> </reference> <referenceanchor="_108-SURVEY" target="https://www.ietf.org/blog/ietf-108-meeting-survey">anchor="IETF108-SURVEY" target="https://www.ietf.org/blog/ietf-108-meeting-survey/"> <front> <title>IETF 108 Meeting Survey</title> <author initials="J." surname="Daley"> <organization/> </author> <date year="2020" month="August" day="13"/> </front> </reference> <referenceanchor="_109-SURVEY"anchor="IETF109-SURVEY" target="https://www.ietf.org/blog/ietf-109-post-meeting-survey/"> <front> <title>IETF 109 Post-Meeting Survey</title> <author initials="J." surname="Daley"> <organization/> </author> <date year="2020" month="December" day="07"/> </front> </reference> <referenceanchor="_111-SURVEY"anchor="IETF111-SURVEY" target="https://www.ietf.org/blog/ietf-111-post-meeting-survey/"> <front> <title>IETF 111Post-Meeting Survey</title>post-meeting survey</title> <author initials="J." surname="Daley"> <organization/> </author> <date year="2021" month="August" day="23"/> </front> </reference> <referenceanchor="_112-EXPERIMENT"anchor="IETF112-EXPERIMENT" target="https://www.ietf.org/blog/ietf112-plenary-experiment-evaluation/"> <front> <title>IETF 112 Plenary Experiment Evaluation</title><author initials="" surname="IESG" fullname="IESG"> <organization/><author> <organization>IESG</organization> </author> <date year="2022" month="February" day="04"/> </front> </reference> <reference anchor="INTERIM-SCHEDULE" target="https://mailarchive.ietf.org/arch/msg/wgchairs/l382SqKVVHoTzFw9kIYl2boM6_c/"> <front><title>Post-IETF-107<title>Subject: Post-IETF-107 Recommended Virtual Interim Schedule</title> <author initials="A." surname="Cooper"> <organization/> </author> <date year="2020" month="March" day="13"/> </front></reference> <reference anchor="RFC8713"> <front> <title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title> <author fullname="M. Kucherawy" initials="M." role="editor" surname="Kucherawy"> <organization/> </author> <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden"> <organization/> </author> <author fullname="J. Livingood" initials="J." role="editor" surname="Livingood"> <organization/> </author> <date month="February" year="2020"/> <abstract> <t>The process by which the members of the IAB and IESG, some Trustees of the IETF Trust, and some Directors of the IETF Administration LLC (IETF LLC) are selected, confirmed, and recalled is specified in this document. This document is based on RFC 7437. Only those updates required<refcontent>message toreflectthechanges introduced by IETF Administrative Support Activity (IASA) 2.0 have been included. Any other changes will be addressed in future documents.</t> <t>This document obsoletes RFC 7437 and RFC 8318.</t> </abstract> </front> <seriesInfo name="BCP" value="10"/> <seriesInfo name="RFC" value="8713"/> <seriesInfo name="DOI" value="10.17487/RFC8713"/>Working Group Chairs mailing list</refcontent> </reference><reference anchor="RFC8719"> <front> <title>High-Level Guidance for the Meeting Policy of the IETF</title> <author fullname="S. Krishnan" initials="S." surname="Krishnan"> <organization/> </author> <date month="February" year="2020"/> <abstract> <t>This document describes a meeting location policy<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8713.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9311.xml"/> </references> </references> <section anchor="acknowledgments" numbered="false"> <name>Acknowledgments</name> <t>Thanks to <contact fullname="Brian Carpenter"/>, <contact fullname="Lars Eggert"/>, <contact fullname="Toerless Eckert"/>, <contact fullname="Charles Eckel"/>, <contact fullname="Jason Livingood"/>, <contact fullname="Sanjeev Gupta"/>, <contact fullname="Dale Worley"/>, and <contact fullname="Mark Nottingham"/> forthe IETFtheir reviews, andthe various stakeholders requiredthanks torealize this policy.</t> </abstract> </front> <seriesInfo name="BCP" value="226"/> <seriesInfo name="RFC" value="8719"/> <seriesInfo name="DOI" value="10.17487/RFC8719"/> </reference> <reference anchor="RFC9311"> <front> <title>Running an IETF Hackathon</title> <author fullname="C. Eckel" initials="C." surname="Eckel"> <organization/> </author> <date month="September" year="2022"/> <abstract> <t>IETF Hackathons encouragetheIETF community to collaborate on running code related to existing and evolving Internet standards. This document provides a set of practices that have been used for running IETF Hackathons. These practices apply to Hackathons in which both in-personmany other people who provided input andremote participation are possible, with adaptations for Hackathons that are online only.</t> </abstract> </front> <seriesInfo name="RFC" value="9311"/> <seriesInfo name="DOI" value="10.17487/RFC9311"/> </reference> </references> </references>suggestions on the time zone discussion!</t> </section> </back><!-- ##markdown-source: H4sIAAAAAAAAA61b63YbR3L+30/RS58ci3swEEFJtsjNSZaiKItr3SJSVpw9 e/Y0ZhrAmIMZuHuGECzrXfIg+ZW8WL6q6p4bIa13E18kYC7d1dVVX31VXUiS RNV5XdhT/V2TZ7bIS+v1onK6Xln92i1Nmf9i6rwqdbXQz5qi2OnXJT2lX1pb 5+XSKzOfO3t7Onx6/FBWpaVZY5rMmUWd5LZeJH61rqqk4ieTtTyZHD1Smant qUrx57Jyu1Odl4tKqXzjTnXtGl8fHx2dHB2rG7vbVi471ZdlbV1p6+Qpja2U r02Z/dUUVYn5dtarTX6q/+wrVzu78BPtd2v68BelTFOvKneqtE7wv8ZM/lS/ nOrv/+e/VoXd5mXGl0Xyl7n7yYxvVW55qi9cnnpflXzFrk1enOo1PT29aWx4 +o82PDRNq/WdCZ82N7Y/lXFQRneVZ/muqpaFHczBj01X0wwP/nFJF3l0pcrK rbERt9CjIvV137SeHX2bPLu4ePrk7Pz7Ux4uWMDB5cX1M7qtf8hd3Zgibp++ atyt3em3dgMlHvA7neron0RW8iesxBR2x1d5G/Xx0fFRcvQwmX0rUxm3tDXm WtX1xp/ev7/dbqdkDVOs8f7aZrm5D1tp1ras/X02E5LXswCJs74paj/dZIsD Wcrj5Ord2x8ufty7kMejBfwjkj9OZg9+g+TzolpGcR+3xuzDtCzqyZdEPdFv Kl8n/2d5Z8fJ0W/RdF/ek2RDcw+Fvi9Sz2ZfkHo2+3+RekZaPv47tQzBviD1 cXLx728u3l6+vHh1vVfyY/2msKVxO33xYQPXJHvTF7emaBi/9q9BnPPy4uq7 4QKgc/z38O9ZAIm4EQkS20qQ2FYCWcnlq2taRXJ1/vzi6bsXF8O1sPJpQeQj 8E74PkbJbNY6MENjvtZX6cpmTWG/sDf6bKrPqwqi3PGBB5/1AYIc49IVsKVb JF24v/bL+9tlujK58/eLB4+Pr37+/ocfnlfXvzzbntxc/lgcz6uX3/w1pXWq JEm0mfvamRT4fb3KvY4goDeuukVk8np5N0BtClOWZHkAfALJQbRaULRSEl50 MBOgv7NL4zJ6iUYom/XcuonGVizr1YQHghphWnkcx1vv8dFrADy9EobSZgld m6m+Xllv+9IZZ/XceGwDBqA3ZINtmVq9zeuVFplUlElnjYvynL/+4fJpMjvR G0hi13mKzeFdYMnIWaairnWeZYgG6ivaY1dlTUryKnUpj08+Mxo0l0Iwusme UFdYbnlrXa1NUei89jqYZasyhWdCkMZfO21vCZtp3f1tcrA+l/nxepcG72V6 vtOrqiCtq/Hwsk9hBl4ldhz6H+54T5+YtZtgSgvGRlhnigmWiYCY5lhtrQUQ PPSX5cQlMu1hGn5hWFGyESTsyGxoi31nL9D2WQFvaZb89HCjwSIKm9YwHgrs Hn8bR6sdb9mk03fuFcSuGgfryYL2MVFj6XMHBJ14Ert5KDG41rTHZjTRjRcz 6u+LgT2y9uhZrOb5bu7yrNP+vbU17ELtlXqF+Vbm1uqC3B2rXFe17XTLipo3 ZDC+gn/BU0Z3D9kFKjxC7pMCU6b6ebWF4cDTfLW2dH2voaiFq9ZDi2jlWufL lUwaMQGK3mASQoPMprl46cC/1RgUVsPlQyFffQXk/LnJsUyya/3ClMsGqiYc shokU2/ZsA9evru6PpjI3/rVa/789uLf3l2+vXhKn6+en7140X5Q4Ymr56/f vXjaferePH/9EuHpqbyMq3pwSR28PPvxQADp4PWb68vXr85eHJBpjfbXsenM SRnA+o2zZOoGjNv61OVzMccn52/++z9nD/XHj797++z8eDY7+fQpfHk8+/Yh vmxXtpTZ2MnlKzS4U2azgV3TKIQQqdnkNTZhQpblV9W21CvryLJ+/2fSzF9O 9T/P083s4b+EC7TgwcWos8FF1tndK3deFiXuubRnmlabg+sjTQ/lPftx8D3q vXdxHJ4aAiqyZSh/rQ9G6HbQhqot8C9gQAwg5GgqreAVvgOIeHNr7c0fZK95 ZPzdeIGMLPf0SJP7VYiCgznFhyrccYMhgU/5jdUHeeAE8fLBlC1d5DfZOi9z isSUL8ShD9rp43LAxDeAPnomxEfVi2J3ViKgwoOAlhQUDXwtgP7eZsDSzOzI F/UVocNzCIDMT6n3sEIe8H3likw/twZYPEw0771//vqQ3B9gRYZP3lpkyZbg IUY9pECUUqWrXmhkEVMD6CnIRWo/Dkx9TkEDlxGQnAXtSBktyCkI/Gl5EHRb 8WIRG59VTvHeLUB/6kH4DMOLFAHSt4ZwCzFcNthAp/WAerCpzBHmFnlNeltD fZr3OXWV9wnWboYYPJHdflI9g6uyFEmN0NIZA0Jdabekrhta7dJVzcYLAsDA MAjUFeef6suAvHmZFk0WGMTQWFoF1gTQCJWIvxJhFwuIBTYKJWUJ2TsBONba OBvCTZWmjdP4QM/zVqlWT9DNAMs+fvxXgq1vZw8+fYLNvKdIaVr1iUZFu3En QwwlLR93Or1n5hSiHsIWG+cPNUIRWO9ObWXAtfmQr5s1hypsLJQLw7WFJpJK W/yaHWygvk65W0Ci8oF0Exzr4HXQO61fIntRVFt62ecfouFcs2lefac3zbyA g9PLagNFwXJMdpt7+AVzrcj04yRQyzhZAKpjK0QxxDMWRZ7Czs26YjcFxWql Ij2ucowy5EiQe4Woq52E3kUdRJd1YpSPH/vVhE+fQnjv8TCvCkOvdTQMW0hp Ay0cK6zJ2tKG90RsgSENUlUZ6Z4kBMW47WSFGZFSljB5Hni9gbiBaucOPl2Q BTjxSbgSJirugCTrW6wd8pDQHR0fMp2eb9L29LUGzOQ9IILcGjCczAunLnOC iIiY86a4UVhQXzcThIUcfkZzjF5hDyeWBbII6LMf2O/abWPYUWQGtHBy7F8q wCj28VmL0NAyxHOkxT10NKBZaz8kg4ft03cQxvRGaIXy+ZpyPMalEjMn2Buw 3VaR92bJMbuQ9kUF/kSzPE5Oxg5zOFUtBbQGa4ar8ZwFxq9FiY+Sb8QZaYFk 5MtSsjC2C+Gharg7gNh1RRQop+DDbL34DH8UfwvQ1aosUlFOJdk6wwKjPeii SnmuqT7zbE8fEl5uwO4V6Y2MHrnAh3wOw653oyTTI2+uFU+5FS+rcxITWM6m CMAhdkWoeZtXjYfwHGwfy0Sdzvvg1h+USP4GmArEgk/g9bKiCCBIlv3U+Fq4 LdaKPeRBYSWAcygd2s+XeIvpcnSmBfbIUbCqHCcH7a50piajr025G5g0awnZ hpV8lD14bDKUMfho9B4YMMh4Zgn+7dIsxv/AtpAg9APACQEOh1levQmexJAR /NKvmCCz/7kMbMJwwBQqy96jlrZaOrNZ5ZTRUaJHOe7PTFOYkowK48PKtn4T ShCcSFyTdv6DrOqq1QCTqw7rTbGsHJa6ZlHLqpatjikjJhAXJdcHYs3h54wF qq9kdsbbCokMgWtSMjy3gY3GitkXOdxOPxi6BHGfO3n4VD8xHhCN5ybhtX1+ RB7HkLal0LKUwgi7EAiPs7a9OIrZIdXgLQtFEOyJpRGj0iW++KZ0ubeKcIRx iuOswUO4gJsZUo5QfCDXY2d2JrNgGV38gFG4LIhCEuehdMNFE5KXVTaVzRHI JjthiuOtgbEySxXfEUsqSCdwQMSrxQLhHWk7HqfFPTW7goZTV+aW1kNWEMtC 7C8BGB3bspgCoB9vvrs+nwxLReOx3lBJLE9JvroDLgojxA8EmE6V+lW/Mrj+ K88NavOqcqS2Ul81IArucM+d9xzFcAcvJ1RRkr/2/POlOzQzjajP1nTAYfQr tsVf9dGjo6NkNjs6okXS92/o+3H8jvfOfN49PntAt0/ax2cP8R1Pd49fNK7a 2PaFY9xMjh62L4y+K/WqYkwLajuQ14F+PMAB74nuJV8HFwx4LwXwwn0ydBZz Szmu4piMeFzWjsAiq9h/uVQS9033bUCpy8WdO92OpiAoSxs5ACVHHK4ZE/Eh BDjAZlPUOdy1m1p93hgCINaEHEBnhAJLHLINAsHmGSMZIVxVG3bsua1BispQ 5hJnFsvNGXA8JiAH7eqCK/ZcQhoShqpavo2ny6Kag/Ijyk84yhCbRiIlZR8j zw1oIkUj2q0S0FYzgFtxcGYhXaDAJiEJiWQJrCyWdDkRk9lBA2PUZj6yXQVm RveJeOReVRtcgISBn+GVSIV6xSozZoOU+lPGkwOfoVdZJRBT5TVrOsiLMHNT Vltwfy7zCX2h19K6JQWYbc21mwFuqmrOmZNYZbdNfQTl4JBVVuIHwl5uJdVS yworIr6HO2WyLzjQcin4DcJJL9x9dSfg+WEo48Q51FzkFpEiIiOiYc5K+zaU rio29wHObcDvXYgYXQQahkqx4eCjLLN166bmjeCdjnypo+4rW/QoHDnPW4kB ZxP9ZELR9fwP9KdwSTYlOQYgJXFO3FJC4tlhT6YEsA86JmmWFSHO+MILA3iI vODXSBRaJtAi7ReQdXRhD/IKdIJ0xT8vy+SNrPaMrkWAbJ8KYrQ34oUn7YXz 3jt3nu6Gf/K33h1K8jdePPsNL57tE99b4g0wkf3y3pkoXDjfM7OU8sTMQlhm XjMnItQr9J+q2aGmWhSBAqx9Ly+KA+xLkvoZV5tXsLe0ZT2CCI4vgBck+nBL cA2hfuIwfX8NVtuSccXxKSDGmG1zFg+/mKrjQ42A1IaTL6VJkqMx95qMEqYO D/yKc1PAHQcRzht7Ps6yI40jBOvlDW1MvpNqSd0kOnGIVIscXAxZPYUMSrLb 1TsiVHwYJUNSzprUVcK5a6eGO8dZkqqHQTzRJnHzKSxPgidNRkWzwED76+jX bkmzqrQ5E1SM9/XZ1/pe3kt4DoHC7R3BYbrf1/vhlLaEZ43lW0lhehAWaOzX T77mrQiIZT900nQbkfNzYuE8dF4rqWDwIU7/9uRvjXMex+Hc5hWflBI2gtFI mn+NXS8QLGlTqHqGG0o92YUMZr958Q4PojlvN1fFHlFsDollTAq+4Ry4dRp6 QOIE1w9izri/bB2pFabj6okMrVoHACGEm8DVY3SU8pXkA/ZDinjOrpmHKgUU cZV/CMkwFHHnbFnkAYI8OEogECiCnjtrbugWH8TR0TLiI+U3PbqlN6sdp14y jeTpzIGkDn0nBSsFZbqSkWr9S2paNGhm1/SRi0mUpbcUoC1wloAYBr8y7q1q y4SxFBm6UxbQBTsWVfxiJwuYSFfWmyMBH56xxkrqo4T2KgpP3CUUwrO8WX/u VJaSLYR8OZcnyWLRaNqjIRkyYKJAnsqFXDeJ5BnbF/XXy4uZbFmu/eEm7BzK oTPCfmnT5OW4SNg7ANbPoQSD7yWj0SYP9SRKB52MrGRYfY8ildQqTh7MZp8+ HYojXYk895+QZegXvEAp2+33mJqxncsYu40k6NiOLaXKcWWhdC0lT0yu7kQB zyz8xtrNQL09t+JacXQ6sfGpFNeHk020NHWIJ1ecC4dDQ7J8otWRZ4ZXwiaq e3kJnzeZ8CswP1JIaF953MuD2bajWYHjcbadtpkFlW2aMq/h3l2F/dFRQoav kHBGz+PcJfjk7I4/YpcrR4ayTy2kjiA0YP5R0IYUHaQHLdax+361rEiVUt+H O7aJXbsWPsWZHWkRRXQk8hAPIEPeSHJoimDl0sQQzDOo6mTsg3QKi9G5Un/X m745uo+0OyxfDbdEYPwuWHG3gfb5sswXkIYOugi3buOhlxpMwyuO+xgELyqk tq5DPy57dj5ZC4BP4kk+ZaiUhNSBaDBoWTpmVvaDdWnuA7AdrLA/W7M7CG0r PmQD0voQXKeuqsKPo9abWI++5nq0/viVFKY/Uc/M2FvY3WJlOuYI7VCj0jZ1 twweaKOVq6q1n0TIG3g1TYAd7+WaXMceDQ1HTh2ly34sQoV9JOgOVegOt7no wIyNo3P3ioOCLVezWouVGCdjp2ZjUqpdBzfjk1r9WI0kgufwQW4rACeU+ykx FQ1gOFLO5vWpeHoWZAzS0c62SN8HJXYMT2GSKmf5B8r2pf8h9HsoKu5hClBj 4hJrmFHcjuHRXACtoASOqzq1ria47zau1UwnUYtRs5lQ9TtHG4J1vbaWDipp mK7JJVOeS0FSWO+dyUUTC5sZYI2E5INST+jdhiBnQ+mYGp1r6gWQmDBw12A2 NDASioG7yrHneG4VoAbY0vZ88vlqeyLZ61vaq1qqkZLHxGpKQJqgcVEpFKjG /QdY9dLRw7eUkJMuF1XKmqZpuAR/lmV8EASDPO9Xx2TQtvFRrrHfU6u6voWh vQhOfCaqvScnfkMJDgEGZMBJ8PhPHcUgSOvocauitu8Y8Gv8DeHXPNbBwEKb tG5cMAdAfntURpPE0Q6ZDHLTQh1KX3g+tmDH4NH2SVA1OiKSGrcHtEdb8113 OBlsig+WJYIIpxvIx0cBtEYyKYm1TsZ5fPxPU6jWb6oy48Mjak3FLWk4GFbF OF6UqjurHfR+CAPFTfwfbPonKhutKwonzZoOLRuuSpNXTKiHw2IzMrvg3sF+ vjxB1sfpFjMdD4ENxxMOxHHlqj1il6abnTWAV/gFHrshXhxtPx6+hTMGKpkN G2bgQjnUprqjyzvGS8PysQHSmE3vvL3nw52rhRYZqIrnYe2w7jjlFiRlZIjF yfb4oD1Gpoa04XkbH9zv8SqKYFQSpT6QgukdcgriF6CLFaU/vHTkuoTz/Drc NPR8xQY7A1JD5/Abavxn0tUKwlmxkRagQXGCkpeADJiTquMqs9h7omm1TVcl Zzrdqb84sa+KWxu6SCnmet9QEsatI5wnSjx/1jtkxUR84PbOh3a9cT8qgwI1 mLJx9dorY45JWzXcoflOhYOeSFMilGaDA96A9CHgSYMJnT7vOyFfN9Ssk0uH 7TAbIeNJU7uRGlQIgULg6TctJoAetg3gqO/F7qn2xIxN6HA/w+gdTyiGF8qN MFIeDwEc5ykc0Lcx72/DeqTFofixbKgHYIj7cSkqHGB3rGHBGNDPpDiWk5R8 WtIPloNIyNjWHWOKX8IeIoFuT9P4mHmYjy1GGVRXVer3nUltqUXGkAP2N3Pc TvfxY5vBTULdh16kU+eC8Ie2gbg37Ye4Qw/1AEty2tr3ELJ36WZt/awc+Bif toS+DEP5Vyi69dQzDQYv49DGaG7Jy3mZBKD9FCxU3YyAPmcK0eMZGJS0+pKU 9EA/xWoQhRAbqJFs2BzWZZah4iD2hB12meqvoNcYyDbRYh85TK3jLzJiXx6o hjOcBfb7odsC5/5SD9fiunQwVCDb3sLBNsd2tMhQWBQOjd2EyvFvnZgO9X9M gni/4JNoaWik3u/QssdgEo/sOvRXPWwJPdOUWsmRYOaqDVdzuNhjeknu5wpa tEPFTmXSMI6EuokIqc0W24vlhsznkmpeCMZkT7RBVxUtOv+FexXeDA+1RFv7 yw/SmTDrmsFoMG7BolMfQIWCzhI5mtx1h2N8FEnV2Za59jpHaC9DyThk1TFJ 9gJVYyF8w94Rw2OvbaTt3kgHcxOZH3ZMrPYV5jk1tW7c3V6BLQFQCuJJJJTU JlSwqrYhqMcLPgO+Pf+mHvNb6k2r77h62Bk7VU/hw9ROP+Tyt1bObnmjKLel txbEDJ0O+fAwHZ4w8qhYHmt8bBzjt3nNgqzBjJZl5XrWt56QLrl/tIq5JL3H lbJ+RSZygdCjQegHni7NCivC+HvSL8rkuaBwIhXJKjsUkhalZzCS/MTH4BRK pqBrbSrjm/k6F6elHg7g4r3k6OhQflTa0qvY7KakDj0o38UKT5cW87u9kX3o nKM8me07UHElSCvln/aUE8bQnjrHzsC4DrggE4NiVKvggRQV2ddkB7TH4ssb KiHGplzx4u7Xaf4fYTh1rwu25f1T/Zrse6I4q2hLTv1fYzCrLT3V/bhILkkz L+pML3Ny6zhsOAqmsdT4Byx0XLQ2P8FKpNeB7MKEg69e/Y3OywPnMN5LPzX/ fiQlGwIjxFKZAQ7ShDZaBAlMWQKEUnK2nYStvjgUEAlp6WgttVToDzRY8Vq5 P4J/j8OCSqjbVLW0+bCaxJNjIVzy0vaUv90hU96wez5xOcY9N25DfWtAiBcG OfLFcmkdSPZ1ZR2T84v0hi+cI2pSqxd9Lyb6T9SCpF7k1DECb5noK1P+ZO2t /q4BV5zwryi5Kd7uJPy+NCAArypuKFyZddfVoOiM3G4D6SDVsOkyjHatD/JD GubhDUT04Yh9dMzYI+2/U/8L2lcByTs+AAA= --></rfc>