<?xml version='1.0' encoding='utf-8'?> version="1.0" encoding="UTF-8"?>
<!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.10 (Ruby 2.6.8) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-shmoo-hackathon-08" number="9311" submissionType="IETF" category="info" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" updates="" obsoletes="" xml:lang="en" version="3">
<!-- xml2rfc v2v3 conversion 3.12.8 -->
<front>
<title abbrev="ietf-hackathon">Running abbrev="IETF Hackathon">Running an IETF Hackathon</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-shmoo-hackathon-08"/> name="RFC" value="9311"/>
<author initials="C." surname="Eckel" fullname="Charles Eckel">
<organization>Cisco Systems</organization>
<address>
<postal>
<country>United States of America</country>
</postal>
<email>eckelcu@cisco.com</email>
</address>
</author>
<date year="2022" month="July" day="23"/>
<area>General</area>
<workgroup>Stay Home Meet Occasionally Online</workgroup>
<keyword>Internet-Draft</keyword> month="September"/>
<area>gen</area>
<workgroup>shmoo</workgroup>
<abstract>
<t>IETF Hackathons encourage the IETF 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-person and remote participation are possible possible, with adaptations for Hackathons that are online only.</t>
</abstract>
<note removeInRFC="true">
<name>Discussion Venues</name>
<t>Discussion of this document takes place on the
Stay Home Meet Occasionally 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/eckelcu/draft-ietf-shmoo-hackathon"/>.</t>
</note>
</front>
<middle>
<section anchor="introduction">
<name>Introduction</name>
<t>IETF Hackathons encourage the IETF community to collaborate on running code related to existing and evolving Internet standards. IETF Hackathons aim to:</t>
<ul spacing="normal">
<li>Advance
<li>advance the pace and relevance of IETF standards activities by bringing the speed and collaborative spirit of open source development into the IETF</li>
<li>Bring
<li>bring developers and early career professionals into the IETF and get them exposed to and interested in the IETF</li>
</ul>
<t>IETF Hackathons are free to attend and open to everyone. Software developers are the primary audience, but participation by subject-matter experts who are not necessarily developers is encouraged and very important as well. Similarly, while the Hackathon is meant to attract newcomers and people who do not typically attend standards meetings, long time long-time IETF contributors, including Internet-Draft authors, working group chairs, and subject-matter experts, are key participants as well. Collaboration and blending of skill sets and perspectives are extremely valuable aspects of IETF Hackathons.</t>
<t>In addition to the running code created and improved as a result of each Hackathon, the exchange of ideas, extensions of human networks, and establishment of trust, respect, and friendships are some of the most valuable outputs of each Hackathon. Code written in a programming language is often more illustrative and constructive than opinions expressed during a meeting or in an email. Working together to find common understanding of proposals, concerns, and solutions that result in improvements to evolving Internet standards is as important as the development of running code that implements or validates the correctness of these same proposals.</t>
<t>Consequently, IETF Hackathons are collaborative events, not competitions. Any competitiveness among participants is friendly and in the spirit of advancing the pace and relevance of new and evolving Internet standards. IETF Hackathons are inclusive, not only in terms of who can participate but also in terms of the projects included in each Hackathon. All projects should be related to existing or proposed Internet standards in some way. Examples include, but are not limited to, interoperability of implementations, proof of concepts, and tools that help implement, monitor, or deploy network protocols.</t>
<t>IETF Hackathons foster an open environment, with much of the code being open source and projects results of projects typically shared publicly. The Hackathon operates under the <xref target="NOTE-WELL"/>; however, the rules and terms around code are those of the license associated with the code. Although code is often and preferably open source, it may be proprietary as well.</t>
<t>This document provides a set of practices that have been used for running IETF Hackathons.</t>
</section>
<section anchor="timing">
<name>Timing</name>
<t>The first IETF Hackathon was held the weekend before the start of the IETF 92 meeting. The rationale was to avoid conflicts yet make it relatively convenient for those attending the IETF meeting to participate in the Hackathon as well. Holding the Hackathon on the weekend was also viewed as making it more accessible to non those who are not IETF meeting participants, including students and working professionals who would have other commitments during the week. The weekend before was viewed as better than the weekend after so that things learned during the Hackathon could be shared and discussed with the rest of the IETF community during working group sessions and the like. This worked well at IETF 92, was repeated at IETF 93, and quickly became an established norm with the IETF meeting being officially extended to include the Hackathon at the start. An additional benefit of this timing noted and appreciated by participants is that it serves as a more informal and social way to physically and mentally acclimate to changes in time zones and surroundings.</t>
<section anchor="agenda">
<name>Agenda</name>
<t>The IETF Hackathon is a strenuous event. Though not a competition, participants want to make the most of their time together, much as with the IETF meeting in general. Competitive Hackathons typically run non-stop nonstop for on the order of 40 hours. There is a strict deadline and deadline, teams are judged judged, and winners are declared at the end. Afterward, participants are wiped out and head off to briefly celebrate or commiserate, commiserate but mainly to recuperate. As the IETF Hackathon serves as the start of the overall IETF meeting, we aim to strike a compromise that provides time to get valuable work accomplished without exhausting everyone before the main IETF meeting even starts. While some people participate in the Hackathon only, the majority of people remain and plan to be actively engaged in the rest of the IETF meeting.</t>
<t>The typical agenda is as follows:</t>
<artwork><![CDATA[
Saturday before IETF meeting week
08:30: Room open for setup by project champions
09:00: Room open for all - Pastries pastries and coffee provided
09:30: Hackathon kickoff
09:45: Form Teams teams
12:30: Lunch provided
15:30: Afternoon break - Snacks snacks provided
19:00: Dinner provided
22:00: Room closes
Sunday before IETF meeting week
08:30: Room opens - Pastries pastries and coffee provided
12:30: Lunch provided
13:30: Hacking stops, stops; prepare brief presentation of project
results
14:00: Project Present project results presentations to other participants
15:45: Closing remarks and opportunities for next time
16:00: Hackathon ends
17:00: Tear down complete
]]></artwork>
<t>The time on Saturday morning provides the opportunity for team champions time for setup to set up and participants time to socialize and learn more about projects and teams they might want to join. The kickoff presentation and formalities are kept to a minimum to leave as much time as possible for teams to work together on their projects. The proximity of teams to each other fosters communication and collaboration across teams between them as well.</t>
<t>Lunch and dinner are provided as a convenience and an incentive to remain at the Hackathon. Participants are free to come and go as they like. It is well understood and accepted that there are other things vying for time and that meeting with friends and colleagues outside of the Hackathon is an entirely reasonable thing to do.</t>
<t>The room closes Saturday evening to give hotel staff unfettered access to the room and to encourage people to pace and take care of themselves. There are no rules against continuing work on projects outside of the Hackathon room. Similarly, working on projects long before and after the Hackathon is allowed and encouraged.</t>
<t>The end of the Hackathon on Sunday is driven by other IETF meeting events. There typically Typically, there are Newcomer events that start at 16:00. The IETF Hackathon typically includes many newcomers in its list of participants participants, and it is important to provide them time to participate in the Newcomer events. The opening reception for the IETF typically start starts at 17:00, and we want to make it easy for all Hackathon participants to join that as well.</t>
<t><xref target="hackdemo-happy-hour">Hackdemo Happy Hour</xref> and the <xref target="code-lounge">Code Lounge</xref> exist to facilitate ongoing discussion and work on projects beyond the official end of the Hackathon weekend.</t>
</section>
<section anchor="hackdemo-happy-hour">
<name>Hackdemo Happy Hour</name>
<t>Hackdemo Happy Hour provides an opportunity for more in depth in-depth sharing and discussion than is possible within the time constraints of the result results presentations that occur at the end of the Hackathon. This opportunity is made available to all teams. As with the results presentations, participation is optional.</t>
<t>Initially, something similar was done as part of <xref target="BITS-N-BITES"/>. This worked well for the Hackathon Hackathon, but the Bits-N-Bites event was eventually abandoned for other reasons. Hackdemo Happy Hour was created as a low cost, low-cost, informal event to provide a venue for the IETF community to engage with the Hackathon teams in more in depth in-depth discussions related to their projects.</t>
<t>Hackdemo Happy Hour is typically Monday evening, roughly from 18:00 - 19:30, often overlapping a bit with the last working group session of the day but continuing long enough to allow everyone an opportunity to join. The goal is to make it convenient to attend by not conflicting with other meetings but and also no by not running too late into the night.</t>
<t>Light snacks and beverages are provided, and a cash bar is available to align with the spirit of a happy hour.</t>
</section>
<section anchor="code-lounge">
<name>Code Lounge</name>
<t>The Code Lounge provides space for groups to gather and continue to collaborate on running code after the Hackathon. It is typically in the IETF Lounge and open the same hours as the IETF Lounge. Champions are encouraged to look at the final agenda and determine which time slots are best suited to ensure attendance of Code Lounge sessions sessions, as well as any related working group sessions. It is okay for multiple teams to sign up for the same time slots. This is in fact encouraged for work that spans multiple working groups or projects.</t>
</section>
<section anchor="code-sprint">
<name>Code Sprint</name>
<t>The <xref target="CODE-SPRINT"/> develops tools that support the work of the IETF. The Code Sprint existed long before the Hackathon and benefitted benefited from being a focused event in a quiet space with few interruptions. However, there is a great deal of synergy between the Code Sprint and the Hackathon, and they attract some of the same participants. For example, some Hackathon projects, such as those related to YANG model validation, involve the creation or modification of IETF tools. It is therefore advantageous to co-locate these two events when practical, and practical and, when separate space is deemed helpful, to allocate spaces that are physically close to each other to make it easy for participants to switch back and forth between the two events.</t>
</section>
<section anchor="online-only">
<name>Online Only</name>
<t>The IETF 107 Hackathon was originally scheduled to be the weekend at the start of the IETF meeting in Vancouver. When COVID-19 hit and it became clear the IETF meeting could not occur in person, the Hackathon already had 23 projects and 176 registrations. With only 10 days until the anticipated start of the Hackathon, a <xref target="SURVEY"/> went out to the Hackathon community, including all project champions and registered participants, to see if they wanted to participate in the Hackathon exactly as planned except with everyone participating remotely rather than in person. A relatively small number of people expressed interest in participating, with even fewer wanting to continue to champion their projects. The fact that the Hackathon was planned for the weekend before the IETF meeting and in the local time zone, both of which were historically very convenient and attractive to Hackathon participants, suddenly became huge obstacles. Consequently, the IETF 107 Hackathon was cancelled.</t> canceled.</t>
<t>We knew more in advance that IETF 108 would be an online only online-only meeting. We moved and expanded the schedule to run the entire work week before the rest of the IETF meeting. The Hackathon kickoff was set for Monday, Monday and the closing set for Friday, with all the time in between left for individual project teams to arrange to meet how and when was most convenient for them. The kickoff and closing sessions were scheduled to align with the time frame established for the IETF 108 meeting. All of this was, of course, not ideal, and it worked much better for some people than for others, but at least everyone knew the plan and corresponding time commitment well in advance and had the ability to plan accordingly.</t>
<t>We ultimately had 19 projects and almost 300 registrations. It is hard to say how many people actually participated and for how long, but many projects were able to get substantial work done. done on their projects. For the closing, 10 teams produced and shared presentations summarizing their findings and achievements. All results presentations presentations, as well as the agenda and a recording of the closing session session, are available via the <xref target="IETF-108-HACKATHON-WIKI"/>. This level of participation was strong enough to be considered a success and justify justifies including the Hackathon in future online only online-only IETF meetings.</t>
<t>Hackdemo Happy Hour and the Code Lounge are not applicable for online only online-only Hackathons.</t>
</section>
</section>
<section anchor="funding">
<name>Funding</name>
<t>The Hackathon requires funding, and that funding increases with the number of participants. Participating has always been free; therefore, funding from other sources other than participant fees is required.</t>
<section anchor="sponsorship">
<name>Sponsorship</name>
<t>The initial funding model was to have Hackathon sponsors sign up to sponsor and fund the Hackathon for one year. As part of starting the Hackathon, Cisco volunteered to sponsor and fund the Hackathon it for its the first year (i.e., three Hackathons, one at each IETF meeting during a calendar year). This sponsorship was to rotate. Huawei volunteered to sponsor the second year of the Hackathon. After the second year, a sponsor for the 3rd third year was not found. However, the Hackathon had become a proven success. Consequently, the IETF decided to fund the Hackathon as part of the IETF meeting, with Hackathon sponsorship being on a best effort best-effort basis.</t>
<t>Online only
<t>Online-only Hackathons in response to the COVID-19 pandemic, pandemic and increased remote participating in general, general result in increased cloud infrastructure requirements that make Hackathon sponsorship more attractive to cloud infrastructure providers.</t>
<t>Hackathon sponsorship is available at different levels as part of being an IETF <xref target="IETF-RUNNING-CODE-SPONSOR"/>.</t> target="RUNNING-CODE-SPONSOR"/>.</t>
</section>
<section anchor="expenses">
<name>Expenses</name>
<t>The primary expenses associated with the Hackathon are those for hosting an in-person event, e.g., meeting space, food and beverage, etc. It is often challenging to quantify the portion what portions of this are associated with the Hackathon from that versus what is incurred for the IETF meeting overall.</t>
<section anchor="in-person-event-expenses">
<name>In-person
<name>In-Person Event Expenses</name>
<t>The following expenses are associated with in-person participation in a Hackathon. When the IETF meeting is online only, these expenses are eliminated.</t>
<section anchor="meeting-space">
<name>Meeting Space</name>
<t>The meeting space for the Hackathon is sometimes included as part of the overall contract for the IETF meeting. Other times, an additional expense is incurred to secure a large enough space earlier than would otherwise have been required. Typically, the space is needed for setup from Friday afternoon before the start of the IETF meeting until Sunday afternoon. After the Hackathon, the space is typically repurposed for the IETF Lounge. If the size of the Hackathon continues to increase, it might be necessary to use the same space as is later used for the IETF plenary.</t>
</section>
<section anchor="food-and-beverage">
<name>Food and Beverage</name>
<t>Some portion of the food and beverage expense is often included as part of a minimum spend the IETF is obligated to make. When a Hackathon sponsor is identified, funds resulting from this sponsorship are typically used to offset food and beverage expenses, expenses or to increase the food and beverage budget.</t>
<t>The minimum food and beverage requirements for the Hackathon has been,</t> have been:</t>
<ul spacing="normal">
<li>coffee, tea, and water Saturday and Sunday morning</li>
<li>lunch Saturday and Sunday</li>
</ul>
<t>Additional items, in order of importance, include,</t> include:</t>
<ul spacing="normal">
<li>beer Saturday evening</li>
<li>dinner Saturday evening</li>
<li>continental breakfast Saturday and Sunday</li>
<li>afternoon snacks Saturday and Sunday</li>
</ul>
</section>
<section anchor="t-shirts">
<name>T-shirts</name>
<name>T-Shirts</name>
<t>Hackathon t-shirts T-shirts are an important part of the Hackathon. They have been provided for all in-person Hackathons and greatly appreciated by many participants. They also serve as great advertising for the IETF, the Hackathon, and sponsors. Cisco or other event sponsors have often covered expenses associated with t-shirts. T-shirts. The current model is that the secretariat Secretariat covers the expenses using whatever funding is available.</t>
<t>The number of size distribution of t-shirts T-shirts for IETF 107 is provided here as an example.</t>
<ul spacing="normal">
<li>
<t>380 t-shirts T-shirts at a cost of roughly $10 USD / t-shirt each, with shipping to the Secretariat included included:
</t>
<ul spacing="normal">
<li>50 Small</li>
<li>120 Medium </li> Medium</li>
<li>110 Large</li>
<li>75 XL</li>
<li>25 XXL</li>
</ul>
</li>
</ul>
<t>The t-shirts T-shirts are all standard cut. We previously tried providing fitted cut t-shirts T-shirts as an option for Hackathon participants, but these were not well received.</t>
</section>
<section anchor="stickers">
<name>Stickers</name>
<t>Laptop stickers are popular with developers. Stickers have been made available at the Hackathon for those that want them. Expenses have been covered by the IETF LLC, Director of Communications which oversees the communications and Operations.</t> operations budget.</t>
</section>
</section>
<section anchor="remote-participation-expenses">
<name>Remote Participation Expenses</name>
<t>The following expenses are associated things done primarily to facilitate remote participation in a Hackathon. This includes participation when the Hackathon is online only only, as well as remote participation when the Hackathon is in-person.</t> in person.</t>
<ul spacing="normal">
<li>Meetecho: cost associated with the Hackathon kickoff and closing</li>
<li>Gather: costs associated with premium service, required to enable more than 25 concurrent users. This has not been necessary, necessary but will almost certainly be if Gather becomes a valuable way for Hackathon participants to meet within and across teams.</li>
<li>Webex: IETF Webex accounts are made available to champions for the duration of the Hackathon and some period beyond that encompasses at least the rest of the IETF meeting. These accounts are presently available at no additional cost to the IETF at present</li> IETF.</li>
<li>Network: setup and support of the IETF network, network and remote access to it</li>
</ul>
<t>The change in timing and extended duration of the Hackathon at an online only online-only IETF meeting increases the duration and use of remote participation facilities from 7 days to 12 days. This may result in increases to the cost of providing these facilities.</t>
</section>
</section>
</section>
<section anchor="project-presentations">
<name>Project Presentations</name>
<t>Project presentations are an important mechanism for capturing what each team intends to accomplish, capturing what they actually accomplished, and sharing the results and findings with the IETF community.</t>
<t>For the first few Hackathons, we had two very distinct types of presentations:</t>
<ol spacing="normal" type="1"><li>Presentations type="1">
<li>presentations that served as project pitches at the start of the Hackathon</li>
<li>Presentations
<li>presentations that summarized results at the end of the Hackathon.</li> Hackathon</li>
</ol>
<section anchor="project-pitches">
<name>Project Pitches</name>
<t>The project pitches were 5-10 minute presentations by a champion of a project describing what they wanted to do and how they proposed to accomplish it. This gave everyone in the room a better understanding of all the projects and helped participants match themselves with appropriate projects. This worked well when we had few projects, but it became unwieldy as the number of projects increased. As knowledge of the Hackathon grew and advanced planning became more common, many participants knew exactly which team they planned to join and wanted to get to work as quickly as possible rather than spend time listening to presentations. Project pitches were dropped from the Hackathon. Champions are encouraged to share this type of information in advance via the <xref target="meeting-wiki">Meeting target="meeting-wiki">IETF Meeting Wiki</xref> instead.</t>
</section>
<section anchor="project-results-presentations">
<name>Project Results Presentations</name>
<t>The project results presentations were brief presentations by each team of what problem they tried to solve, what they achieved, and highlights that included lessons learned, feedback to associated working groups, and collaboration with open source communities and other standards organizations. They also highlight individuals who participated in their first IETF Hackathon or first IETF event, which helps facilitate the introduction of such individuals to the IETF community. The production and presentation of results summaries of results is optional. Fortunately, despite the lack of awards and prizes, most teams participate.</t>
<t>As with the project pitches, project results presentations can become unwieldy as the number of projects increases. With this in mind, the total time for all results presentations is limited to 2 hours. The maximum duration of each presentation is calculated based on the number of teams that indicate the desire to present. This maximum is strictly enforced to ensure all teams have the opportunity to present their results. Maximum durations of 3-5 minutes are typical.</t>
<section anchor="templates">
<name>Templates</name>
<t>Project results presentation templates provides guidance on what to cover. The use of these templates is optional. They are made available in various formats in a GitHub repo created specifically for the presentations for each IETF Hackathon, e.g., <xref target="RESULTS-PRESENTATIONS"/>.</t>
<section anchor="pptx">
<name>PPTX</name>
<name>Microsoft PowerPoint Open XML (PPTX)</name>
<t>For portability, presentations that use this the PPTX template should be made exported into a PDF format as well.</t>
</section>
<section anchor="html-format">
<name>HTML format</name>
<t>This Format</name>
<t>The HTML format template should render within any browser. It can be rendered as a slideshow using <xref target="REMARK"/>.</t>
</section>
</section>
</section>
<section anchor="upload-to-github">
<name>Upload to GitHub</name>
<t>All project results presentations are uploaded to the GitHub repo created for the Hackathon, e.g., <xref target="RESULTS-PRESENTATIONS"/>. The contents of this repo are used as the source for all results presentations at the end of the Hackathon and remain as a reference after the Hackathon.</t>
<t>One must be a member of the <xref target="IETF-HACKATHON-GITHUB"/> organization to upload a new presentation or update/replace an existing presentation.</t>
<t>To be added as a member, presenters are asked to:</t>
<ul spacing="normal">
<li>include the name by which they are known in their GitHub profile</li>
<li>enable two-factor 2-factor authentication (2FA)</li>
<li>send your their GitHub username to the Hackathon Chair(s)</li>
</ul>
<t>Presenters are asked to do this at their earliest convenience convenience, as the Chair(s) typically get gets very busy as the start of presentations approaches.</t>
</section>
<section anchor="presenting-in-person">
<name>Presenting in Person</name>
<t>Presentations are run from a shared Chromebook at the front of the Hackathon room. This Chromebook is provided by the Secretariat.</t>
</section>
<section anchor="presenting-remotely">
<name>Presenting Remotely</name>
<t>Remote presenters are welcome to run their own presentations using the screen sharing screen-sharing functionality in Meetecho. Alternatively, the Hackathon Chairs Chair(s) can share the presentation and advance slides for the presenter.</t>
</section>
</section>
<section anchor="tooling">
<name>Tooling</name>
<t>The IETF Hackathon uses the same tooling used by the IETF community for its work and meetings.</t>
<section anchor="datatracker">
<name>Datatracker</name>
<t>The <xref target="DATATRACKER"/> supports the notion of Teams teams that are not part of the standards development process. The Hackathon exists as one such Team. team. From the Datatracker menu, navigate to "Groups" -> "Other" -> "Active Teams" -> "hackathon". Here exists a Datatracker space for the Hackathon similar to what is available for working groups, including meeting materials, agendas, etc. Initially, there was some attempt to copy materials hosted in the <xref target="IETF-HACKATHON-GITHUB"/> to the Datatracker. Now Now, this is done only when required for integration with other IETF tooling, including to:</t> including:</t>
<ul spacing="normal">
<li>
<xref target="REQUEST-SESSIONS"/>
<li>requesting sessions for the Hackathon kickoff and closing, closing and for Hackdemo Happy Hour</li>
<li>post Hour, e.g., <xref target="AGENDAS"/></li> target="REQUEST-SESSIONS"/></li>
<li>posting agendas (e.g., see <xref target="AGENDAS"/>)</li>
</ul>
</section>
<section anchor="ietf-website">
<name>IETF Website</name>
<section anchor="hackathon-website">
<name>Hackathon Website</name>
<t>The IETF website includes a <xref target="HACKATHON-WEBSITE"/>. This website contains information about the Hackathon in general general, as well as links to past, present, and future Hackathons. The relevant links are updated after each IETF meeting. Other content on the website is updated on a more ad hoc basis.</t>
</section>
<section anchor="meeting-website">
<name>Meeting Website</name>
<t>Each IETF <xref target="MEETING-WEBSITE"/> contains information about the corresponding Hackathon, including the dates of the Hackathon in the header and a link to the Hackathon website in the "Additional Events" section.</t>
</section>
</section>
<section anchor="registration">
<name>Registration</name>
<t>Registration for the Hackathon is through the IETF meeting <xref target="REGISTRATION-SYSTEM"/>. Participant registration for the Hackathon is:</t>
<ul spacing="normal">
<li>independent of participation registration for the meeting</li>
<li>free</li>
<li>required</li>
</ul>
<t>As with meeting registration, registrants for the Hackathon acknowledge the <xref target="NOTE-WELL"/> during the registration process.</t>
<section anchor="participant-list">
<name>Participant List</name>
<t>An active list of all registered participants, e.g., <xref target="PARTICIPANTS"/>, is maintained by the Secretariat. Important information displayed for each registrant includes the set of projects and technologies in which each participant is interested and an email address. This information is optional at the time of registration and may be updated or removed by editing one's registration.</t>
</section>
<section anchor="caps-on-registrations">
<name>Caps on Registrations</name>
<t>Registrations were capped for the first several Hackathons. This was done both for both space and costs considerations. The cap was hit multiple times, each time resulting in temporary confusion and frustration among would be would-be registrants, followed by which led to the cap being increased. Currently, there are no caps enforced by the registration system. In the event the number of participants exceeds the capacity of the main Hackathon room, designated overflow areas within the meeting venue are made available.</t>
</section>
</section>
<section anchor="meeting-wiki">
<name>Meeting Wiki</name>
<t>The <xref target="MEETING-WIKI"/> serves as the primary source of information for each Hackathon.</t>
<section anchor="hackathon">
<name>Hackathon</name>
<t>A page within the meeting wiki, e.g., <xref target="IETF-110-HACKATHON-WIKI"/>, is created by the Secretariat for each Hackathon and initialized with information that is based largely on the information from the previous Hackathon. Once created, the Hackathon Chairs update Chair(s) updates and moderate moderates this page.
Champions are requested and are responsible for adding information about projects for which they are a champion.</t>
<t>Anyone can edit the wiki by logging in using their Datatracker login credentials. Credentials can be obtained by creating a <xref target="DATATRACKER-ACCOUNT"/>.</t>
</section>
<section anchor="lost-and-found">
<name>Lost and Found</name>
<t>A Lost and Found wiki page, e.g., <xref target="LOST-AND-FOUND"/>, is created by the Chairs Chair(s) for each Hackathon. Participants looking for a team are encouraged to add themselves to the "Skills to Offer" table, providing some information about their skills and interests. This will help others with matching needs and/or interests find them. Champions wanting help on their projects are encouraged to add their teams to the "Skills Needed" table, providing some information about the skills they seek.</t>
</section>
<section anchor="results-presentation-schedule">
<name>Results Presentation Schedule</name>
<t>A Results Presentation Schedule wiki page, e.g., <xref target="RESULTS-PRESENTATION-SCHEDULE"/>, is created by the Chairs Chair(s) for each Hackathon. Hackathon teams are welcome and encouraged to present their results during the Hackathon Closing. closing. Hackathon teams add the name of their project and the name of the presenter to the table at the bottom of this page.</t>
</section>
<section anchor="in-person-only">
<name>In Person Only</name>
<t>The following wiki pages are applicable for in-person Hackathons only.</t>
<section anchor="hackdemo-happy-hour-1">
<name>Hackdemo Happy Hour</name>
<t>A Hackdemo Happy Hour wiki page, e.g., <xref target="HACKDEMO"/>, is created by the Chairs Chair(s) for each Hackathon. Champions are welcome and encouraged to add their project by entering the project name/acronym and a contact name and email address in the table displayed on the page.</t>
</section>
<section anchor="code-lounge-1">
<name>Code Lounge</name>
<t>A Code Lounge wiki page, e.g., <xref target="CODE-LOUNGE"/>, is created by the Chairs Chair(s) for each Hackathon. Champions are welcome and encouraged to add their project by entering the project name/acronym and a contact name and email address in the table displayed on the page.</t>
</section>
</section>
<section anchor="online-only-1">
<name>Online Only</name>
<t>The following wiki pages are applicable for online Hackathons only.</t> online-only Hackathons.</t>
<section anchor="team-schedule">
<name>Team Schedule</name>
<t>A Team Schedule wiki page, e.g., <xref target="TEAM-SCHEDULE"/>, is created by the Chairs Chair(s) for each online only online-only Hackathon. Online only Online-only Hackathons take place globally for an entire week. It is up to individual project teams to determine the preferred dates, times, and ways to meet to work on their project within the context of that week (e.g., Zoom, Webex, or Slack). This page is meant to help facilitate coordination of schedules within and across teams.</t>
</section>
</section>
</section>
<section anchor="email-list">
<name>Email List</name>
<t>The Hackathon email list, <xref target="EMAIL-LIST"/>, target="EMAIL-LIST"/> is used for all email communication and announcements related to the Hackathon. All registrants are given the option to subscribe to the list. Anyone interested in staying up to date on the Hackathon is able to subscribe at any time. Once subscribed, anyone can send and respond to emails to via the list. The same list is used for each Hackathon. Anyone wishing to receive email emails for a specific Hackathon only can unsubscribe after that Hackathon has concluded.</t>
<section anchor="hackathon-chairs-email-alias">
<name>Hackathon Chairs Email Alias</name>
<name>Email Alias for Hackathon Chairs</name>
<t>The email alias, <xref target="EMAIL-ALIAS"/>, alias <hackathon-chairs@ietf.org> was created and is maintained by the Secretariat. It is used on Hackathon webpages web pages and wiki pages to provide a single point of contact for the Hackathon.</t>
</section>
</section>
<section anchor="github">
<name>GitHub</name>
<t>The <xref target="IETF-HACKATHON-GITHUB"/> is used to share code, presentations, and other artifacts at IETF Hackathons. The Hackathon Chairs are Chair(s) is responsible for administering the GitHub organization.</t>
<t>Code for Hackathon projects often exist elsewhere, which is perfectly fine. Anyone needing a place to host code for the Hackathon can request the creation of a repository for their project.</t>
<t>A repository is created and maintained by the Chairs Chair(s) for each Hackathon, e.g., <xref target="RESULTS-PRESENTATIONS"/>. This repo is for participants to upload project results presentations. The contents of this repo are used as the source for all presentations at the end of the Hackathon and remain as a reference after the Hackathon.</t>
</section>
<section anchor="meetecho">
<name>Meetecho</name>
<t><xref target="MEETECHO"/> is used for the kickoff and closing sessions of the Hackathon. This provides many capabilities, including the following:</t>
<ul spacing="normal">
<li>allows participants to join Hackathon sessions in person or remotely</li>
<li>validates the registration of participants at the time of joining Hackathon sessions</li>
<li>enables remote presenters of project results presentations</li>
<li>captures recording recordings of the Hackathon kickoff and closing</li>
</ul>
</section>
<section anchor="network">
<name>Network</name>
<t>Access to the IETF network is an important aspect of the Hackathon. The IETF network provides unfettered Internet access that is not typical within many residential, corporate, and university environments. For many of IETF participants and projects, access to the Internet and each other via wireless access to the IETF network is sufficient. However, due to the nature of the work done in the IETF, wired access and special networking capabilities are often required.</t>
<t>The NOC Network Operations Center (NOC) has graciously met the needs of the Hackathon since its inception and continues to add more capabilities over time. Champions In advance, champions are able to request in advance wired access and special networking functionality, including static IPv4 and IPv6 addresses, IPv6 only IPv6-only networking, a closed user group, NAT64, Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64), and IPv6 Prefix Delegation. All of this, and the IETF network in general, is made available by the start of the Hackathon and in advance for setup to the extent possible.</t>
<section anchor="remote-networking">
<name>Remote Networking</name>
<t>Online only
<t>Online-only meetings present both a personal networking personal-networking challenge and a computer networking computer-networking challenge. The NOC came to the rescue for the latter with an experimental mechanism that was used to join the IETF network while attending a meeting remotely. This evolved into what is now known as "HackNet" <xref target="HACKNET"/>, a global Layer 2 VPN designed to support IETF protocol development across teams within the IETF Hackathon. A limited set of devices for connecting to HackNet are supported. In addition to layer Layer 2 connectivity, a subset of the networking capabilities available at in-person meetings are available. Both the set of devices and the set of networking capabilities are expected to expand and evolve over time. However, it is important to note that HackNet is still an experiment and not a production service. Best effort Best-effort support is available via email to <xref target="TICKET"/>.</t> <support@ietf.org>.</t>
</section>
</section>
<section anchor="webex">
<name>Webex</name>
<t>Champions can request a <xref target="WEBEX-ACCOUNT"/> they can use to schedule meetings for their team. These are similar to the Webex accounts that are allocated to and used by the working group chairs to be used for virtual interim meetings. An account can be requested by a team champion at any time. Accounts remain active and available throughout the duration of the Hackathon and the associated IETF meeting. A project name may be used in place of "Working Group Name" in the request form.</t>
</section>
<section anchor="gather">
<name>Gather</name>
<t><xref target="GATHER"/> facilitates virtual hallway interaction during IETF meetings. A dedicated area within the overall space is created by the Secretariat for the Hackathon. The area includes tables, identified by letters of the alphabet, that teams are free to self assign self-assign and use as and when they like. Eight to ten seats around each table facilitate group discussions within the team.
A whiteboard dry erase board or shared notes tablet, e.g., <xref target="HEDGEDOC"/>, at tables facilitates sharing of information within the team. The tables also facilitate collaboration across teams. One cautionary note, note: Gather has relative high network high-network bandwidth and CPU requirements, and requirements and, as such such, may not be well suited for some Hackathon participants.</t>
<t>The Gather space remains available between IETF meetings, with incremental improvements and additions made during this time. The space is cleaned about a month prior to the start of the next meeting, removing anything left over from the previous meeting. Hackathon teams are encouraged to make a copy of anything they want to retain within a week of the end of the IETF meeting.</t>
</section>
</section>
<section anchor="statistics-and-metrics">
<name>Statistics and Metrics</name>
<t>Statistics for the Hackathon have been gathered informally from the first Hackathon, at IETF 92, and more formally since IETF 101. Registration is required required, but it is also free, which can lead to misleading statistics. Starting with IETF 101, an effort has been made by the Secretariat to validate registrations for all in-person participants by checking registrations at the main entrance to the Hackathon room. Badges similar to those issued for the rest of the IETF meeting are now issued for the Hackathon as well. There is still no good mechanism for determining the number of remote participants.</t>
<t>Hackathon participation has grown from 45 participants at IETF 92 to a maximum of 406 participants at IETF 104. Participation tends to be slightly higher when the IETF meeting is located in Europe. Recent in-person Hackathons have had roughly 30-40% as many participants as the corresponding IETF meeting. For roughly 20-30% of Hackathon participants, the Hackathon is their first experience at any IETF event.</t>
<section anchor="ietf-survey-results">
<name>IETF Survey Results</name>
<t>For each IETF meeting, there is a post event post-event survey that often includes a question or two about the Hackathon, e.g., <xref target="IETF-106-SURVEY"/></t> target="IETF-106-SURVEY"/>.</t>
</section>
<section anchor="hackathon-survey-results">
<name>Hackathon Survey Results</name>
<t>Hackathon specific
<t>Hackathon-specific surveys have been used on some occasions to obtain more detailed feedback about the Hackathon from the IETF community. This has been especially useful for feedback on online only online-only Hackathons. Survey Surveys have been short with most questions being optional, e.g., <xref target="IETF-110-SURVEY"/>.</t>
</section>
</section>
<section anchor="roles-and-responsibilities">
<name>Roles and Responsibilities</name>
<t>This section provides a summary of the roles and responsibilities of individuals and groups involved in a successful IETF Hackathon. The summary provided here is not meant to be exhaustive. Some responsibilities are described entirely or in more detail throughout the rest of the document.</t>
<section anchor="hackathon-chairs">
<name>Hackathon Chair(s)</name>
<t>The role of a Hackathon chair Chair is similar to that of a working group chair. As with working groups, it is typically best to have co-chairs share responsibilities and the workload. The Chairs work Hackathon Chair(s) works very closely with the Secretariat on all responsibilities. Key responsibilities include:</t> include the following:</t>
<ul spacing="normal">
<li>Organize and deliver a Hackathon at each IETF meeting, which involves soliciting help from all other roles to do much of the heavy lifting</li>
<li>Encourage and provide guidance to champions who volunteer to lead projects</li>
<li>Maintain the Hackathon wiki, e.g., <xref target="IETF-110-HACKATHON-WIKI"/>, and all of its child pages.</li>
<li>Moderate the <xref target="email-list">Hackathon email list</xref></li>
<li>
<xref target="REQUEST-SESSIONS"/>
<li>request sessions for the Hackathon opening and closing in the IETF meeting</li> meeting, e.g., <xref target="REQUEST-SESSIONS"/></li>
<li>Emcee the Hackathon, including the opening and closing sessions and announcements in between</li>
<li>Create and manage the GitHub repository used for each Hackathon, e.g.,<xref target="RESULTS-PRESENTATIONS"/></li>
<li>Serve as the main point of contact for all Hackathon questions and concerns</li>
</ul>
</section>
<section anchor="secretariat">
<name>Secretariat</name>
<t>Key responsibilities include:</t> include the following:</t>
<ul spacing="normal">
<li>Configure and manage the Hackathon <xref target="registration">registration system</xref></li>
<li>Maintain the Hackathon <xref target="hackathon-website">website</xref></li>
<li>Create and maintain the web page for each Hackathon, e.g., <xref target="IETF-110-HACKATHON-WEBSITE"/></li>
<li>Create a wiki page for each Hackathon, e.g., <xref target="IETF-110-HACKATHON-WIKI"/>. This is initialized and updated at times by the Secretariat, but the Chair(s) are is ultimately responsible for maintaining it.</li>
<li>Handle venue logistics for the Hackathon, Hackdemo Happy Hour, and the Code Lounge (e.g., reserve room, food and beverages, AV, etc.)</li>
<li>Internal
<li>Handle internal IETF promotion (e.g., via email messages to the IETF community)</li>
<li>Assist with external outreach, as needed, including finding sponsors</li>
<li>Validate Hackathon registrations for in-person participants, including issuing badges and <xref target="t-shirts">Hackathon t-shirts</xref> T-shirts</xref> when available</li>
</ul>
</section>
<section anchor="sponsor">
<name>Sponsor</name>
<t>Key responsibilities include:</t> include the following:</t>
<ul spacing="normal">
<li>Provide some funding to help offset costs of the Hackathon (either per meeting or per year, depending on the model)</li>
<li>Optionally provide t-shirts T-shirts or other giveaways</li>
<li>Optionally provide support staff to assist with the Hackathon</li>
</ul>
<t>Key benefits include:</t> include the following:</t>
<ul spacing="normal">
<li>Sponsor logo on Hackathon t-shirts</li> T-shirts</li>
<li>Sponsor logo on Hackathon signage</li>
<li>Sponsor logo on the Hackathon webpage web page and wiki</li>
<li>Sponsor logo and call out in the Hackathon kickoff and closing presentation</li> presentations</li>
<li>Sponsor logo and call out in the IETF Plenary plenary presentation</li>
<li>Sponsor logo and call out in the Hackathon recap on <xref target="IETF-BLOG"/></li>
<li>Recognition in the IETF community for helping the IETF Hackathon remain free and open to everyone</li>
</ul>
</section>
<section anchor="champions-of-projects">
<name>Champions of Projects</name>
<t>Champions of projects are the key to a successful Hackathon. Key responsibilities for champions include:</t> include the following:</t>
<ul spacing="normal">
<li>Volunteer to lead a project at the Hackathon</li>
<li>Serve as the primary contact for the project</li>
<li>Add and manage information on the Hackathon wiki for the project, including the <xref target="hackdemo-happy-hour">Hackdemo Happy Hour</xref>, <xref target="code-lounge">Code Lounge</xref>, and <xref target="team-schedule">Team Schedule</xref> pages</li>
<li>Promote the project to appropriate groups inside the IETF and outside as well</li>
<li>Welcome and organize members of the team</li>
<li>Provide focus, guidance, and leadership for the project</li>
</ul>
</section>
<section anchor="ietf-llc-director-of-communications-and-operations-was-isoc">
<name>IETF LLC, Director of Communications and Operations (was ISOC)</name>
<t>Key responsibilities include:</t> include the following:</t>
<ul spacing="normal">
<li>Promotion
<li>Promote the Hackathon outside of the IETF, including web search engine ad words, social media posts, and listing on external event calendars calendars, such as <xref target="RIPE-CALENDAR"/> and <xref target="NSRC-CALENDAR"/>.</li>
<li>Outreach target="NSRC-CALENDAR"/></li>
<li>Handle outreach to local universities</li>
<li>Provide a photographer, including optional team photos and candid photos of collaborating during in-person events</li>
<li>
<li>Provide <xref target="stickers">Laptop target="stickers">laptop stickers</xref> at in-person events</li>
</ul>
</section>
<section anchor="judges">
<name>Judges</name>
<t>The first several Hackathon Hackathons involved judges who listened to project results presentations by teams at the closing of each Hackathon and identified winning teams for an arbitrary number of project categories. Prizes were made available to members of winning teams. This was done as an incentive to participate in the Hackathon and present results, results and to provide a fun yet informative end to the Hackathon that could be appreciated by the entire IETF community. Judging and the awarding of prizes led to confusion regarding the nature of the Hackathon, making it appear to some overly competitive. competitive to some. Procurement of appropriate prizes was financially and logistically challenging. Arrangement The arrangement of judges, determination of winners, and awarding of prizes all became more time consuming, especially as the number of projects and participants grew. Ultimately, it was deemed best to eliminate judging, awards, and prizes entirely. Apparently Apparently, the IETF community has an innate incentive to participate and present results in the Hackathon.</t>
</section>
</section>
<section anchor="implementation-status">
<name>Implementation Status</name>
<t>The practices described in this document have been established, used, and refined over the course of running numerous IETF Hackathons, including several at online only online-only IETF meetings. The <xref target="GITHUB-REPO"/> GitHub repository target="GITHUB-REPO">GitHub repository</xref> has been used to collaborate on this document. The <xref target="github">IETF-Hackathon GitHub</xref> contains code associated with IETF Hackathons.</t>
</section>
<section anchor="security-considerations">
<name>Security Considerations</name>
<t><xref target="remote-networking">HackNet</xref> enables Hackathon participants to join the IETF network while attending a meeting remotely. The intent is for those connecting remotely to have as open a network as possible, just like those connecting to the IETF network at an in person in-person meeting. A user must have a Datatracker account to access HackNet and is expected to respect it it, just as they are expected to respect the IETF network at an in person in-person meeting. If HackNet is exploited, it is addressed in the same manner as an exploitation of the IETF network would be at an in person in-person meeting.</t>
<section anchor="privacy-considerations">
<name>Privacy Considerations</name>
<t>The Hackathon complies with the IETF/IRTF/IAB <xref target="IETF-IRTF-IAB-PRIVACY-STATEMENT"/>.</t> target="PRIVACY-STATEMENT"/>.</t>
<t>Participant names are displayed publicly in the <xref target="participant-list">Participant List</xref>. As part of their registration, participants may opt in to display their email address as well.</t>
<t>The email addresses of individual champions are often shared publicly by the champions on the wiki. This is done voluntarily by individual champions to make it easier for others to contact them.</t>
<t>Photos taken during the Hackathon, and during the IETF meeting in general, are sometimes included in blog posts or on social media. Red lanyards are made availale available to Hackathon participants to wear to indicate that they do not wish to be photographed individually or in small groups.</t>
</section>
</section>
<section anchor="iana-considerations">
<name>IANA Considerations</name>
<t>This document has no IANA actions.</t>
</section>
</middle>
<back>
<references>
<name>Informative References</name>
<reference anchor="SURVEY" target="https://www.surveymonkey.com/results/SM-9HLRXN8M7/">
<front>
<title>IETF 107 Hackathon Results: Participant Survey</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-108-HACKATHON-WIKI" target="https://trac.ietf.org/trac/ietf/meeting/wiki/108hackathon/">
<front>
<title>IETF 108 Hackathon Wiki</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-RUNNING-CODE-SPONSOR" anchor="RUNNING-CODE-SPONSOR" target="https://www.ietf.org/support-us/sponsorship/#running-code">
<front>
<title>IETF Meeting Sponsorship: Running Code Sponsor</title> Sponsors</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="REMARK" target="https://github.com/gnab/remark/">
<front>
<title>remark GitHub Repository</title>
<title>remark: A simple, in-browser, markdown-driven slideshow tool</title>
<author>
<organization/>
</author>
<date>n.d.</date>
<date month="May" year="2022"/>
</front>
<refcontent>commit 1bbce13</refcontent>
</reference>
<reference anchor="DATATRACKER" target="https://datatracker.ietf.org/">
<front>
<title>IETF Datatracker</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-HACKATHON-GITHUB" target="https://github.com/ietf-hackathon/">
<front>
<title>IETF-Hackathon GitHub</title> Repositories</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="REQUEST-SESSIONS" target="https://datatracker.ietf.org/secr/sreq/">
<front>
<title>IETF Session Request</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="AGENDAS" target="https://datatracker.ietf.org/meeting/agenda/">
<front>
<title>IETF Meeting Agenda</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="HACKATHON-WEBSITE" target="https://www.ietf.org/how/runningcode/hackathons/">
<front>
<title>IETF Hackathon Website</title> Hackathons</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="MEETING-WEBSITE" target="https://www.ietf.org/how/meetings/">
<front>
<title>IETF Meeting Website</title>
<title>Meetings and events</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="REGISTRATION-SYSTEM" target="https://registration.ietf.org/">
<front>
<title>IETF Meeting Registration System</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="NOTE-WELL" target="https://ietf.org/about/note-well/">
<front>
<title>IETF Note
<title>Note Well</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="DATATRACKER-ACCOUNT" target="https://datatracker.ietf.org/accounts/create/">
<front>
<title>IETF Datatracker Account Creation</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="EMAIL-LIST" target="https://www.ietf.org/mailman/listinfo/Hackathon/">
<front>
<title>IETF Hackathon Email Mailing List</title>
<author>
<organization/>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="EMAIL-ALIAS" target="mailto:hackathon-chairs@ietf.org">
<front>
<title>IETF Hackathon Chairs Email Alias</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="MEETECHO" target="https://www.meetecho.com/">
<front>
<title>Meetecho</title>
<author>
<organization/>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="HACKNET" target="https://hacknet.meeting.ietf.org/">
<front>
<title>HackNet</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="WEBEX-ACCOUNT" target="https://ietf.webex.com/webappng/sites/ietf/dashboard?siteurl=ietf/">
<front>
<title>IETF Webex Account</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="GATHER" target="https://gather.town/">
<front>
<title>Gather</title>
<author>
<organization/>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="HEDGEDOC" target="https://notes.ietf.org/">
<front>
<title>HedgeDoc</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-106-SURVEY" target="https://www.ietf.org/media/documents/IETF_106_Meeting_Survey.pdf">
<front>
<title>IETF 106 Meeting Survey</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-110-SURVEY" target="https://ql.tc/8K1JeZ/">
<front>
<title>IETF 110 Meeting Survey</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-BLOG" target="https://www.ietf.org/blog/">
<front>
<title>IETF Blog</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="GITHUB-REPO" target="https://github.com/eckelcu/draft-ietf-shmoo-hackathon/">
<front>
<title>GitHub Repository for draft-ietf-shmoo-hackathon</title>
<title>draft-ietf-shmoo-hackathon: IETF SHMOO working group draft on running an IETF Hackathon</title>
<author>
<organization/>
</author>
<date>n.d.</date>
<date month="July" year="2022"/>
</front>
<refcontent>commit 6a8aad6</refcontent>
</reference>
<reference anchor="MEETING-WIKI" target="https://trac.ietf.org/trac/ietf/meeting/wiki">
<front>
<title>IETF Meeting Wiki</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="RESULTS-PRESENTATIONS" target="https://github.com/ietf-hackathon/ietf110-project-presentations">
<front>
<title>IETF 110 Hackathon Project Results Presentations</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
<date month="March" year="2021"/>
</front>
<refcontent>commit a6a12bd</refcontent>
</reference>
<reference anchor="PARTICIPANTS" target="https://registration.ietf.org/110/participants/hackathon/">
<front>
<title>IETF 110 Hackathon Participant List</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-110-HACKATHON-WEBSITE" target="https://www.ietf.org/how/runningcode/hackathons/110-hackathon/">
<front>
<title>IETF 110 Hackathon Website</title> Online</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-110-HACKATHON-WIKI" target="https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/">
<front>
<title>IETF 110 Hackathon Wiki</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="LOST-AND-FOUND" target="https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/lost&found">
<front>
<title>IETF 110 Hackathon Lost and Found</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="RESULTS-PRESENTATION-SCHEDULE" target="https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/resultspresentationschedule">
<front>
<title>IETF 110 Hackathon Results Presentation Schedule</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="TEAM-SCHEDULE" target="https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/teamschedule">
<front>
<title>IETF 110 Hackathon Team Schedule</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="HACKDEMO" target="https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon/hackdemo">
<front>
<title>IETF 113 Hackdemo Happy Hour</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="CODE-LOUNGE" target="https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon/codelounge">
<front>
<title>IETF 113 Code Lounge</title>
<author>
<organization/>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="TICKET" target="mailto:tickets@meeting.ietf.org">
<front>
<title>IETF Support Email Alias</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="RIPE-CALENDAR" target="https://www.ripe.net/participate/meetings/calendar/">
<front>
<title>RIPE Upcoming
<title>Upcoming Events</title>
<author>
<organization/>
<organization>RIPE NCC</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="NSRC-CALENDAR" target="https://nsrc.org/calendar/">
<front>
<title>Network
<title>Education Outreach and Training (EOT) Calendar for Internet Development</title>
<author>
<organization>Network Startup Resource Center Calendar</title>
<author>
<organization/> Center</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="CODE-SPRINT" target="https://www.ietf.org/how/runningcode/code-sprint/">
<front>
<title>IETF Code
<title>Code Sprint</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="BITS-N-BITES" target="https://www.ietf.org/how/meetings/98/bits-n-bites/">
<front>
<title>IETF
<title>About Bits-N-Bites</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
<reference anchor="IETF-IRTF-IAB-PRIVACY-STATEMENT" anchor="PRIVACY-STATEMENT" target="https://www.ietf.org/privacy-statement/">
<front>
<title>IETF/IRTF/IAB Privacy Statement</title>
<author>
<organization/>
<organization>IETF</organization>
</author>
<date>n.d.</date>
</front>
</reference>
</references>
<section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name>
<t>The IETF Secretariat, notably Alexa Morris and Stephanie McCammon, <contact fullname="Alexa Morris"/> and <contact fullname="Stephanie McCammon"/>, contributed significantly to the creation of the IETF Hackathon and the practices in this document. Among other things, Alexa <contact fullname="Alexa"/> drafted the initial breakdown of <xref target="roles-and-responsibilities">Roles target="roles-and-responsibilities">"Roles and Responsibilities</xref>, Responsibilities"</xref>, and Stephanie McCammon <contact fullname="Stephanie"/> created the initial Hackathon website and wiki. These have evolved over time and are used to run each Hackathon.</t>
<t>Greg Wood, Barry Leiba, Michael Richardson, Benson Muite, Dhruv Dhody, Karl Auerbach, Mallory Knodel, Lars Eggert, Robert Sparks, Thomas Fossati, Alvaro Retana, Erik Kline, John Scudder, Roman Danyliw, and Eric Vyncke
<t><contact fullname="Greg Wood"/>, <contact fullname="Barry Leiba"/>, <contact fullname="Michael Richardson"/>, <contact fullname="Benson Muite"/>, <contact fullname="Dhruv Dhody"/>, <contact fullname="Karl Auerbach"/>, <contact fullname="Mallory Knodel"/>, <contact fullname="Lars Eggert"/>, <contact fullname="Robert Sparks"/>, <contact fullname="Thomas Fossati"/>, <contact fullname="Alvaro Retana"/>, <contact fullname="Erik Kline"/>, <contact fullname="John Scudder"/>, <contact fullname="Roman Danyliw"/>, and <contact fullname="Éric Vyncke"/> also provided significant contributions to the Hackathon and to this document.</t>
</section>
</back>
<!-- ##markdown-source:
H4sIANFh3GIAA9196XLbWLLmfz4FwjVLuYOUvNTqG3emZVllq0uWNJJc1X0r
OjpA4IhECwTYWESzHX6AeYt5lpkXm/wy82wgKNu3+0ZMTP0oiyRwljy5b2c2
m026oivNi+TRVV9VRbVI0io5Pbn5KXmTZndpt6yrR5N0Pm/MPT1TmO52tvQ/
5HVWpSt6O2/S227GP7fLVV37h2ZPfphkaWcWdbN9kRTVbT2ZFOvmRdI1fds9
e/LkxyfPJmljUhr+talMk5aPJpu6uVs0db+mL6+7dJu8qVcmeWtMl1xkWdoW
dZWW5Ta5qMqiMo8md2ZLr+QvktOqM01lutkrLGgyabu0yv+SlnVFi9yadrIu
XiS/dXU2Tdq66Rpz29Jf2xX++PNkkva05ObFJJlNEvqvqNoXyfFBcpLdmZK/
kd0eL9OmNG3wfd0s0qr4e9rRyuj3os3q5HrbdmbV8u9mlRbli8Tghaz/fYYH
DrJ6xT9mdV91gM67quhMntCOOxq9vk2OVqYpsnQyqepmRYPfmxcEPYKh/5Qk
1++ufjn50wseyh4mn+DTJ9/7U0wu06YrsmKdVl1y3Tf3ZvtIXkmbhenonWXX
rdsXh4ebzeag5QdWdUWQxToPG9P2ZdceXr+d/fjm7OqP5z+8/f7wEabHVLOn
T36YvTk6/vno5s3F+ezX059PR9fzQ7CeX4u7Ys8KuibNDoBMBwRX/nSIT4cr
QgBC0cMNvXpIozkkC1Zy9e78/PT89ez44tXJ7Pry4vz64mpkLRbbj+vcJNfr
uiJ0eAAebjFtv14T4sz69rCVt9plsT78qpHxZhmNx4u5Onl7dPVzPHNDaNDc
Ja+L7k0/T67Mum6Ljuhiz8SLolv2cwb/okrnh/K67PXV0c3RzRVB/GRsd69S
QiEC253Zt6ncP+E356Hoz/L16c2bdy9355j5k5T9fHoTMfc4VDD9j3cn1zez
65Pr61M6rJHNXJsWBE/w+ltv2u5LNtSarDlsG/M3mezo9cn5q6OxOd4KZiVH
C1Pl6ZdMYXEy5TdlnoASTl5en96cjMwYEIKZExqYz8G+Zb05VEwDoh06YLYy
8duTkxsg//5p7Ua/cFLdZWsP7fXpNWHfDZ3Y7PpP1zcnbx+Y6sosipbgBt6o
THHPtE3w5AArzy9uTmhbZ2cjE53XnaENleWeYd1I6bzuu8OKHp9t6PEdSpod
HR9fvDu/eZiikqOMOXZyTFILS/0SdEnl3fYww8tGlkCs4vRsdkYwfRBRTiBE
krNiLw1Ex4aHV2l1WNLzEBmHb2LKk0mPzk5HCcLPSsKuaFqd/Kgs0nYwO37o
6hde4mf8xu/tShxmnhy/uYinAoqYbFk/sJ+VPsIcxFHX+ckAVFjvudkHGKyN
tIIDReMBbhG1nPzxgbMnWjHv7ak/hGMbPMgLpb/S9ZrYAoisFemVp+1yXqdN
/t/xZd+U/8pf8xJeE7sYcvLXBM29/HvBPx509UaP883Jq9cnry6OB2Ax+cK8
qrM9o4AU2jH+//TJd7MH9IrvHHF/UpMIGGVepIekMfYrAwLAUH+hof6iQ/1F
hjpY57fBOp4+eWAdT5983jr+Vh502eEPPz/9g/m3YJMvzy5ejwz7sqwXn7Oh
OT2np8cycnZ1cjnA7x1Jn5Dq9oCy/GkZqhrk4f4xBpJgXBVzYuAfU8JUGly/
O7u5nl3SHyfnNywVxlgKjitQR5v6rybrCDasWNJn0xJeMEMdcphP6xL4CFxZ
y6j0bzQaDXd5dHVzenx6eXR+8xmLC3TlB/jtuLyioQ7XfoD2cExNxWI/R02I
1/XPURUw92esaY8SHy/oH1Xinz4ZrOTsgrTBo/NXs5+IG7/65ALO6rYjkzVP
fiLmnP/TllLSsP/lVobcg+Kz62Piue/OPn1qYyieXGdLk/flvrP88iWrhRZh
vpuDJrk5OXr7+Wu+Menqn7/GjkaNFgV0e3Xy9mJ0Pc95PblZ1fTHeg0vQL9P
Hn7mWp77tSx1bF4HW4tnhHGvx0HzXAzFM8KIxT8IjmAJIMxSh8QJnZISOqaA
XIvR+WkdjHjOnena3w/1HEHi08uT2fHRGWyggaqBn5J3a2KsEAon9xDQDzCZ
plibA9KnPJsjTdaZCFlawhRqVHG/vjreMyvpa3D0wN/RdP0adEIHnJnk2MCN
kxzrQPuUl7bJGNTxhGr4X52O6nJq7zfFXk3uQS6K/81afl1me3lKbOF8Rv+c
jImVl0XX4mdogV9sa/34w+Ec71ezOWuRnlOfXuF/Ry+JIZ3+cnT8p9k18aST
tydjWz7Ew4f0MPGf4j7NtuJfghL2OStay0uz1r6EZcxmsySdQ/Rl3WQSGwxt
YirSlBsyiBPSUcWZSJi16qui2yZdTR/KkkwxkpsmIVaj8E0A26QxZQofGD1m
3rPlsmD2bu7r8h4frIcvYdceadPtQXKzLNrEapYJ6QD3RW7aJE1aeq6+pW9o
nUVGX3XLtEuW6b1J5sZUSd/SVFDJ7BoGW8HQxE6DAYgPlbyJYL9FlWyWRbZM
5nW3pE+ztWla2hjW3RCHoW16QgHvTxv6pm7bYl6aZENKTZLm6Vp5Nq8nGJ2X
jDdqdnbin+2BHMGqyPPSTCZfASpNnfcZRvh/4ECGC0iLFQ3wYjL5XXKU36dV
JitZp/SHQKk08jWdFr/sBksA+fuiKwj4820yJ9JbYFq8364NrQwD+B0U9/i+
aAo++XpNp6xcJTf3xG3XjCNEv7UDBq3qJYa1T9DpyRbThs46I9gTMyKsuhVH
VFq28j4vFA8S+WCwFUGIjlWAhe8LgMa0AB/hiJtu53xwurc0C7/XdcTM+HVe
POB+b5ptXZmD5Lq+7TZ4Olxpo8BsilVKFkba5wUduJkm874bIB4BsO3nrCGv
MFGDFZuGdJPNsuaRyCJMKkOY3qZNQbsPJioCRJIFYl1JsYJsgqac0jCmLGmZ
xaooAbwpCKOU9XndggZaGbwg2wVt0ZwbQkkL+bWp1yANWlRe85q67brI2Oev
APIIYvnlNClrIEaxcjhOVFEQFOqGfiyqrCTQBBgrQYJEnP70BIQRfufIQyJe
jCmvZxxoU4bYndkmobrvwXDskVK5wRyCClMQarZ3RVmCQ9ktN4TOwHUjZ2re
d8Q8DO34Pi37FKwi5SdaRyQBoyKkoinyvOC5FLkjQhaHkxwcnRkxSXwAlxTN
EaOalLiYG3XKg5j3BAlSUfA7sdWUtk1LM1XLzIq+XPartKIDZGGuACOkpxUX
ZJqC2ughjvZMMRW2IA/dNoSoOfznsuMWQR48S7OuoNe7jdd9t+5l4/ESD0Sg
b4jcaUmgshSUumjSFasyJa28B+Mr8DIeWdU0E0G+F8Pt3ij/qOhzz+AHx62I
+IqKd0iHTasGVec9c4nUYlxCjBozVhLeOUh+VQTqauIIS0IUOofbgodfrehY
yJygUwbiKg7QUolhEEOZYgUZYaVFuLrsRRow+9cTosn05NiFIrxhLxvGnul8
I/oEaEM+SGuIkIRnozdKnYF2SIdQ5ByQwstZ3TR0gBVBRI+KxGObrozfC+Hi
Ma0c3vqqAw8YY3cxwzascU6Z0glWawIv7/4gOaq2/ht6CvOmK9B5RHO0VcEm
MIjKsVsvCFIWO1ZwjAse4kH/DtEGdAJraWl5sgNIaF6BaVYMJfCxjNAkUJeZ
OROw6uhB4ePswmiVYYnsGGL9EbEO92C7rPuSmMu4sK4bPRr6fgxJKqG7Tbo9
SE7epzh7N7fIECsXSmLrMvpURBvkQjovSqgR4A4Wb0SRmWJeyOBbQe51p8jd
1XVpVTFTrv17U6LOCn6yKVadm3VZby1jwWBdTWjDvG5wCLfELYjcmGyJxk11
XzR1JUOyfrXqCX4KYEb0uWHYBOoBM2ELUjWmA7HTLgkM9ERPbC0jDQyaYSDT
GBQgEqZxnufDBxe0+PjxXxJS7SHIp8qZAWUGBp992sDXIEsTgU7nZRdMExK7
Bftv66zgA+ZN2c0AHeiFfrGUARyvky2ZW5wSbSHYLR1gl6zSLZAG2EG007Hy
oLJrMvmP06mhr94UYM+YhTQfErPd4ClCxxbIkfMmN8bcQebPzW2t2k4Lm9EC
iN/98Znly3I2InZTqBEps8r0vi6Y098SQOlstwYguDMABRMOETD0vboiPlNg
19iFnIQoHZZ98HxWCNDIIV0r5/E7cerAm7p0IwSIU0VbxFqZLdwXZiMCmtaI
13Bg2H2aQTtj06GDblTFywnZYqj0tB3Rc6XKhtV0YqUWbGrDrIRPs2YRBtFV
dCINVADa9QqcB4eDDfi1zw0rTCxRw22S3kVft7UgT7eE/paUpHBXXs7GcMos
j1NCxDbyos16Fs2OHqBuR2jhDR0dNtbyWtm+0iIT251RixJPYmw6PUIAi2VT
3mJj1qpO2R+eC3P7W19kdyUIK4NUhHJgdSF6GnkcfrHRwSlHur2l02OOw1pW
Ltxc+fEQtTpPCxCVTgFMSxquMreFwoI20zHFgY8r8MiSJUku7GS+3RGnogmQ
pDANa6QgfdGdJP2kVD0Fi4XwYDpYblurpdOPLAr4Q5aR7AB1wNhkbZIFD6vq
fyfLplUtu2E2CGQAl/hKw/HCJgYMomBeRCpy1dd9KxoEzo3ZIKRVGmoS03h/
G7U+mPyduiloUzSyLqvETUV4gIxHz432sZC8JSijTlOJTHgnRYgngmRnbVev
mb0o+dcNpAYt4JsnJCj6RjwPjXHbJI5FAjHN2QUgciNdifbx1z63BtmmqCrY
ULnJSqESwRCCIuEHaI6sx3wADIyxKdb0dN2LL31JEwETASIyuM0t2CJpSnPx
EChTaFniiYpA+m8lfhHCqV5kIc3YenD5k/MYtcPISbMlOJYRgInejDoQGBB0
YnK0TY01CKI6+aRHxya5Mx9Yf0DknRQNoUMcJXZr3i/TXvQka2WHUgbbik8b
eCZrpiP6lY1bVp/UYn1QEkAvnOq4f60b1Zr0TST3FCqyy5RNuLkR5wekkqkW
bHbroDtszoo+oRVFuESSUtQQuCWVu960nDOWJNdp1zc5awC83WiXYNP8FP57
8sOL509eJFd1vRIVAnhLWgBxT/ANjeMRWa/W4KT+vR9fPNl5D6c7Sy5TnKSS
fUaYZow9wjx8H/N6+N0RZ6Vnwwe++fZF8hN4KuIVfuqnz/jVs74iyt0Z+Om3
/CvTQ1XDLUKm8R0t67qiudqRF2Qnr5i6dn9+9sxvNCtJXWgVxMTL/j0Abj8X
Qp/Y5nMHP1EA6jXr5GYNime6TsJokRqkfJqq//qxvuEtXsY/R6+zjiU6Q8he
QqjjtI4JQFiOJLO16uiCiQopjR0DTSoSfkzL/vXveAUeG+A68L9+z78SFpDd
UG8qZhCl6YzSA7gCgm4W6UmSVaoAKd9AvMvhsLzg8ZypMuSZls2I/Cv+LjyZ
FRjV0pBq5O0Jz7EJQDR9sVh2Tgr9tS4q0aUUw+NjYVcJi1yBjzid1uI+o6Gq
YtUzd6Tp4c5oRWDxEumDczSzNitrqIUlOj+FSKGicQuW5dCn97D5mE+5V9kW
lYMWu6u1SlbmF5zFvq+soVVYmeVsDEFc0eSYtNgxrngsKofTxtVCS+HkIXNI
HDW1Y5tdzGsPwhB+7GCFm1G8trXKoK0qfacdOCWre+qpqWvVlTKYr1DFRF2F
ZGaXvHh5RH293wKjGMqFTsGPO5qH+qA+Lwcjky565Pr2XUubtiw9VnOA613R
QAwQo2pJvWPlf6nWR14r1288A/KYDoGlDy4AsyUpgCUkGKFZX92yfm5ytSqc
4xAjiakeBA9UUrHBo8fRQYHKGBS88lVrShLuVnsRz4G1dhd0Um3Hbtmi6q0u
DuRzdLIXDlhR7FhWNT58m/2/ym5TZ2XsAhRyUDUm79FWIMI62ZkdrEOYOYzi
Bo4oyD45/h39oHP7D7zW9Olcfdz6kGCH6D/0BzM4obuBwuRHUTMANmG1DXzm
cAxi/4VoBbF6B3cYY7b3BOIIhcwkbmHZ2Yj6Mli0LBBSSpg46AIULqayLj3w
mrjdgUGLhbQxsf5NiyOs3jr1wG88ZrnCKDUe5njIbyM5An/++isb3Z8t8e0M
OvVjZ+P9FgTz6VkO6koc/rH4zdhxm2bwbElMbFFzfEjsTcvjdrB3bkiBlCms
HTeOT2oGi5EzsoHJZOTLwAlTBSJTAKemGZxmxGVgI9tAXbBoNsOLNo496jkz
CogbnMi0c+5IdT0PJD3OoM4yWpS3MHa2qWZ0uFSEflL4uO5TImT1YeDQWTSw
xRCa8rtKxnQQ0eLxxeTlGAiJSCDelLVyYZGtMA0223Mo+BCKanR8+BAG8D9+
HLH8LWb704PBg2/C4L6QB8/Bf/VC9XM6gbpSh5iwC2HhtNexI8b7LlAD+Uec
ik4FoRNnd8tMAQmnCX3Tm5gGowCvWA8etAFvYZFcVAME8kjThk7lgZIwjqZF
aPC+ratACk2Jj5N9Tt/fkvWWPP2BmAIpu0+h6U/VaQkbsKTRJNQyJ+7gll2S
Ujzuv7G4x/p2H8kYFgqmYr+AIBuB1Bl7A1KKtLFFTdAu2pBRBc5BH6slSSCB
C/EsOlkv523Dk97jzxKxUqlMaptwWxW9FVRD6EasIrZikXDsEGtOF6oAWi1J
WCrpSWm7TOYpQ39AXMWi8iAMIiIJs0Z2NwgjCriiyMLgC898Whb+wDU+AQaP
ZCPbSBogbz6VVzAim60GFso7j9C6Dh8YX2rgif0l1p0QPHqA1HXV5zmg6oPX
UJbr+s4yr9ui8sYy80wDtzxcLcwW27Jm7k7Y1/aFDbBUbd9Yz7ANIYUQ865F
VSpB0NXW0dO4I9ICob5LlbMTEyxY77IKeIsT7deO3hkKfqHKwwom61sE14Od
4x3R/Vn5INHa+hmiFbUaObKkbhFEkqcEQT58CLKtPn60ocU2DPFoxZS4f1li
ereF0FkwrIhfWmeoyg2cnkwL7NzEg8xIxHea0u4yDj8Ii+Ro8N/6wnSKtKKB
m41Er5p+rUHGN0FoxvrcFuDCcLmVHKzfknmygC3fbYwiX7hsq1kEsXP9autS
HMLwtkRMA/XmAG4M2j3H30R6hYqQHgP9oL5ICUsErPlPR+eviYnnpNxrxJbd
nkWFYKbAMNN6lYT1hby4tQabzSfgU3NUCFiIKo3YaUfoA0crkzVpSxm7czn8
221qq9JulqayoaG0VH0P37XwOuAVOQmo0casTM4RwNueHlXenLmHgtSnwLHM
9s3ADB3TJIe6Y0uHjxQtgqm1qAkZwvP02xBsl+JS/LMNPNBxUSXkdd0Ui0Lq
UW1ua67uuyjkETjrx1x3QNdfUlAqoSJ8i7Ss44tfTl/Nnv6YLIvOKvIaWMjg
bNgdRMIkHIVm9YwGlWy06ZCMSsKGnNh/mifPnseeiqfff5eEue1wdbJAg4/3
6RNIWQQ6u6LkQQnEajTk8fZCaiBeIYUcxCY2nHrQd9bcDKM8qrWEoavUB7sD
F42E77FINmDjuBcOnMz94lZIEPaGHMqDDloiv6wrOQoKHyz0NvMeFo5wDqc0
BCqoeLJgU28RcVzaYJeDO+m0YXSxXWE3Vb+ai79fbWqfZGJzxniEcJ6pW0QF
HmYa3pWa9pHUVRCNunRYHlgvxgCR7Z6tXBkJu0a4FiRagG5LH8+ZSiokpz4g
MXIDtkpCqasbJWNOHQu0KdZihFGqZ2fcDAQHzHNT+Qjbskdu0pwQj0iiRQwm
zD3p9tNtBqFdlmz5/2qSO6R/WC04dVmKNr6H4uWNjUGmVZiN6ePOvyKSdG9d
C+9pxRy/A9krZ2CfVV+pzQSvjghFwDoE9F4H/yDvwHoMsSFE5nF2onPL3jN1
t+L7n5qCv5eM07L0dh/t2HLC0tzKKEWVF6TxkSHjiM9pIGnTcEoYGC+K8pf1
xrN6LIXjaTuRdLOK3ZysL+oCnbbEuBIx0oEKK77ZBmcfhlYj6wen5SCGZBkb
Bt0gf40zUkhp1HwdZLWprCo6a/uxD1XD1+wIDqI8TOHOoms1S6aDA5a27dgE
YxSWxAEdUY4bZMDVmkogJreNr4uSGCAfh+JSwR+bZgMWxqNlNBZG4WRgwjvo
cAixlsLSSWZELD0t+Uiek7014Owi7Zdpw7Bu0y2fJjuYdLtEk2LOBswzt0KU
n4a2ZgOB1dbPzGdpLRGE5NoehFp1HDQG3uec1/qTnp0iwxRCRpBtzWnNOp3N
wYl8EW2/WqVN8XdNGSCOh5Q7trjEdbssjCbMCSqMBy8CJZ3h7Y0BJEgqsF0K
UYy0rKN4q+u+SPmpDx/29EZwfoYS+nLksWN9jIm5a2LDdS7uGUJW9tdCE2SX
LZb4V8Qwb7eBzBw4PQld+66Pk8gjvrLPmLeKbWjY2Hww5MITO7exhXDoQbrP
TxLVFzUqcOoSnyYO2NLi+HerNBMp6TfYERwmJvALBcIzUqAvI6m85ESaDTQV
TkuC+/9fvFI7dTOwASF6pORGtULfweAkbw0bVLpgddxd+wYQsrNC3E9uaFHH
Nf2Ic2qCKLi+7Kw5EJ98J6TVD00KBbJJtqT5savMerFY6do59an2ISEDgHQ1
w2jzeZPAlyxZWZgq+bo4MAcQJ4ig+JOd8mLSTjTxSDNwmbK2NIcHeqxYHzTO
sMBp6o4zBt706cYU+5bMgpRokRbNC9t1OB45r0LwHLRPO4SVEs8bHQMLADJz
sV9sCgZQAUslfYNDR+wKgUkjBLhX48hNVmj6zgicAyfkUMarhN7FFQBM04Rg
2rJDwtzCkiG7pi1AaxejRAgGIIJHbCemaGtbsJayKjKVgEpwY6UrUbbLNMxK
di8RZ+wxCMlnSagG01GyWfmoB5tr4xuU8GmkCo4Oqg6pxnKu3ZEiVxiM+eL2
llCq6oTvtuEZqAehskx7rI0MsW2m+5P3CNIjyi9BUqm7MPrtaJpmcO4uu1OE
p62oCeqG2AidJuZgQVRnSYpNYuJaNiRp3YH0XJc5pxF7UMkAILVWy2Tq5G89
BC5JB1ZFCFmcv7T41GKZN0omWEXWZDNUs1wivOTtMHhQjGR3wpWEA3hJGgrH
yhzEmt3kVg+OgcMfmB9QPNvJu7Z0G4qjqToqogkN0pkrTCjL/sr3EgCoZbER
9EdCAeBmCDSQJhckbA9o22Y1cT0K7K8xGB4kF2I9YqhpmMmnqxaHnp4C27cZ
+x+TEvV7VlGQhaJyqbCmqFgtLOE2SJjyqbpOnCU31uU6VS+xOmkqY3I9dMmE
YIwQQ0JcuJJA81BiroWhOAw0jureDXn2oPLErSLInzPrvpFc9giI1uN7qu41
ZGTsRN2skdxqRiWzLMmEZmc7aVi29IkV7b413lkni0lZDYDTrfGJzm4VpCxX
9K7Fp58srb5UWp1MrtmKCGnQ7JJ0eOJC0WOY5VM/2rVR8cKrwFtkFC2sZxC8
Vukk3eW5jFbIDC5uC4QTIKps/rtTj7qh2E6j4HavNW9k04kNumdDLef1B8Df
s/85Mho7DcjbXe4+tkuOy1S0vSkqDSVragpDQh2RfGwuMwJfKTZqOhC9VHJK
ysgzk8mRJ8kCjd3govKJmza4zrn1Wj2BVcxNOKfGweh7zXgZ+UXQlHNnJTPt
Flbl2JJ+F5CgRopGV87YeDOjk2u6NpSWnX4nHLgKMgTWY248tt63AQNxuTo2
du+5dlgig2Qb+J7hWouzjsVcjNR4noLjZJwoCpQXXzyZxYYedO4Mi/DTIe9g
U1GR9UCVYBd+ldCA074l013EJvg0u/z2CXKFljgxmBNXnSr5NmNaVc8G5RT0
qgwqJqUbt+ctbOhxYLI3dQJ1RXHfmzrM0XLY7ShotNzDHh/A4bxchc9gTCQL
R3KIJLZwAKR8/sOT4OwlV1r8TTY++5/IAn93/So5tM8JCED8a9UrsKfrYKuW
SU2S5HfJt0+Sa7g6+cPTZ2jUkxf96n//L/mCRj+D2OJP33+b/PGM/3pGf9Gf
krMX4WZZupolgnzHrjbCpPui7lskHjcFOwawbcYPCQ5l8DG7cTRxwuWr7PMw
any/NeK/gHXArgFku5BG6vSFa2630BBFnaVrJHS3+oUWeK97TjsA3HwZ7YF7
LaCjQU7EjnfWF6Iwkkn6DLvTrG4VDGbxeL4N5OPZ8TR5VaB0r24kUBlk7AmJ
XnDadqE2O+3vSgyAy0j/+lJlTpPjOPFCVOVCEsWD/JrRIvmhoidBTZsANXCY
WCUw0sxCh0Tg3hmdbXwEx86Yamy3shdCLUP2sOuUDfyb9Lr085KXd5kLIfOq
gDAnpldAiFjlTGLNjBcrUbIIi4lQUFOnLIjkb2PDvku1ZxkVnDojSL1BxbF6
AjPipZK0P+c4iaxOjVwEQH32vAai9+dlsQ9Yc4nE5+bTPQ9o59xA7UUSNFOz
bfAYW3YzgnyUxzL6vG/SUGmK48HqnG2KOvdJWKkEvldrArVpvX/2k+711sTr
iwizqkPdnBEhaCWQpC5VivatDU5eBFnENhoezq0VjtOwYYTPxyw01q5V2FI2
Y8MvrkboAfh0w3DFIOpoHWwRmDF4LyWIo/Si1Mv52tAQv5egIK336TP+U9ER
NYa7fgKXaGrFjufcwnj98Ow/tHnnUZOwycR+PfDkDnWZlQHsinbF2JQRr9ZK
sKV1XnH2NyJv0H0RcXC1IlN5SgL51g8elpJMnWfaOuCsf5kdbNYVHdcOuTAn
7c76vsXhhuyE0MW2MRIC2NQSMsu5qjfjhgjSIzja/IvJ5OlBDCahBNalxH6w
QEM8XOhix25zK5g8Gx9Nfe7sJdLdPpAHyF4Td4Yyr3WexIthgfvtjNQDQvG+
M4OjJZGW+vgmG0F2BBIKGelG7lwHcd9cOnIgWMG/uJLo6LSJ2BRvF6mUpUsk
x1bdcFq0jQrtVPPbkFoUeEF+wyA8TUSBVITOpUtrRG4tlbhpZ6Kg7SAfUWJs
ghbAFp8bAhbvEwT6alOYMt/aiEbgNg8qzMVtx97ku6relOgXuctDSAGXAJ+G
pqRGqZKyRZ6NRZO0OZjuavUSCrPhdYkJM83JWWjc2Wb4iq1mT46bq2jBAm3F
1leGlQ1h4F2NYYTWkA7tkt8jRDpw2BghXk7wX9ucooHl81AuGcelxEgGWbI5
aJt0qyajIT0bGvotbMD456+/Um48Q4+wx+g7TtDJY7oZbZQYU9F4ZIu3tlvu
w9TkuR/H6qWSjkCqJyNqNde5lOhuEPJCDqsp+1sWZDTAh2LrRq2/oiQhhqm0
tHeKSErOOTigu0AFijLPpiMlJJJRGdTrWx5qi6Q0hOMaG4Qt2SOz0i02CHFL
8XMU3yxsAsVofXodfa8eW0FsUHwbqrcdh4Z8gya25xBeDucPlQgvHmwZjn1T
K/qjmi176sqUJVLlkqIRW+36iiPDU3BJwnhZUoljANvaSJ8lHpp4ejuV8L0G
YD1MCB/D/OwB755+Ag3RAENDKF/AmmzqUSfaP8RCLgZ/V3c25cR6H8YnhsPO
da5IngX1tcSo3rNvKdSemCQiGBdYfJn1kms35ziH1u3qym1pVyo4ZXPjAG5k
eHj247QimbdotbaXKzxpG1mcW2oT48W6Y19ynKyswyqm6v4PkreDfbGi8Hz2
rUrVNvTfqbF3Y0gEooOFV6vGwEnr0ed8RvCiLzQBtlIOUYsRKkDuXScL2K/u
9QhJhTp3bQE68XvCaSQeCj9txS7UxrqNWdcuXx6dhTinESqatRtiVMC3PloZ
uIwk1vLhw2gvW437gBdf3vxRNDbWLSUnYzpWHCG+YwgE3XDQpYX3iFZhjfAZ
Atflq590g0FpC0/55ubtmf6kTTmGIzaGW444+wtN0upNC/Cfdkp2+pCtKmhL
HByUIfFFYeO4rsBGuN6tyzplTBRAE+EHOXh7Eijo9Hp+z9UKjB7TwFn3KciL
r62Gbm6LUjgQv5Z+Zex6tqXkIhge5gYP6KnW/uKCQmmMxfHCbDxbHcFWOsy+
5cgBukJZLtb55I/hRQofP0aCicMMAuyU+w/FzJ2UzDV6Lx3SfkupufONfcJH
4S+UgvHclU7Kehx2Wr9U2t7xAXE3vrCvBO42gU6g6pmlSKiFlZeGeqToHFKU
hoZQ3wRZKDMkFwL4PT2KnFDZxdfPfjp6TA+2gPkWSSU6BtwWPKmNSKPj2tft
Y3Cg0SVDi5eopeV4EugKc80kSBMOFwQquCsAzKh53zrp4yyfAaJAHU8h2awe
xr9qEPyS3UJupQENILuPFcjU5isdL+mjmYcFB01d7RpbWuTIRB68E/pz1acX
uF13Fnel6aiTifrvBudPzIWFsE9EJDjiiOPtC2Ng+NBcULvUxL3tq0zYNhd0
Vc4txm2IcKKS6jpModB7BMCPrL4cs+fQwFAONWTjppHuQXVdunSigWLWW1eG
VEXIk8ImQoeoL4+yCS9iYHDbEpcRRZANLn6wNQ/BjRFEzurRUU2mtmrEjVcJ
bL5UGFPxemrYjo3OWVJKbiLQMcmzAxvGKKuOGJ50O2uohNdT0Ej9lKj5nkOA
OOdHr1mtfpTM/lvyiMPM8ueRZFjwUuWbpZ3z0UHyxnAXQpk6mmFfNNxW2sFc
Y10oTMCwlSehmu/z1aw7CimMhNboiCcpeK1NcPClfR1HNThJjhNyOkhE1TrW
Wz8EZ1f4nhn7ObLyn2CLB8k5ewqkjoad1+w6Y+PbeWYlTbYzi8hG6VxRsGJf
uE/lu5B38cU3tIxdgI44kqcu8XKsbvR3MIo7Gl6vuvn4kZHYel7RPF7UPT+H
+9oR00a+8c52JO/vNKv3xZL6OIQ0Krwj21f6IAwc6y6HKHTLE6TuWknRR7mj
UrxuV5IXg6xCphDt3tfpu6KB5JKdygJ7JzPNZlmoQuG7b+mOWzcAZ1hJLhLc
RpnLsAozRRzsTtxEHz4MLuGhg/0EZOKs4EA3itM5c3sr2A408QV69mgJXsrw
2C2u8OfKPzwKAtra8huhS1UnJhwA8pnCECfBPT6jqTDdspFs1WHqB9B958og
IFB40ULzqfFVY8kNXDzavTL2So8OoYugd5EDSv9Y+vXmrF1n+P7Ufaq6dmQ9
9IdzmAl7Cdr9hT3MokVZDi94NLxnglZUac8fV8wvquyeOherPYe3W3z8OJU6
64KxblxrSE6dezxEyrxoSdHcKm9j8vFQ8AxBotxdZLFLi5NsWdVlvShM0BZb
LOpgq2zKu9bI2taDe6hCf21UAhYxvQT2olWjpK3LbQxhFuHS2dDRcsNBjHsB
hQHWcw6l+a9t9K6g/VfJcYrqxyrC/zYmAHWrZak4DCMffssJKuWAXUnxgcgS
ro7hpCrXSUOigjbDO/BaYQ5ph4hEJVcMKmli4r8DGHzGTiFGet2kUmJz27uO
BbdN7+HEXVQ3vnWoQ/aphnU95mAJkiEZuIyPJfroJbJ2+8gAPefN0BGiI2r5
EjDIdLHF7tWFsSe1m4uwTN7apaSZbUmz1BZdsQrNbq5iUcnZ01ncouQbd0y2
YccDS/RSPL/rfBD9L3TUWgUwvFwHGmDU0Mzmg6o1OvAFO7KKoyOBQCYeQLtf
mLGlwj3siX7PpS1K/9be3iX+kUVo6i+rWBzW0RxMv/BOFTpxf3HOIVqKVurd
DHZodVKbnhF60S+g2+vK9hgIQrRCxjWTgnpSAJShH76ROwGVi2iKs+t2hEAt
4+xQ6jqmxUppbO/6ABP8nRXHf2C0gG2IskCHAKgSm1sovTljiUypUFEGJ6yw
X06wQ29kXBpnP1jfTD33fFpqdDl3PjI07PVk1hc1uPgGSBN/I8tcS4awIkx8
t844nugpjOBp3FIJ9fM2EyuVEMJuYIQOIAxzqUby6Bqtz/njBTKyHyWo4jLT
IArMiv2otkQQbuV1QVkRI47DIsOBmwpLaZaKd8TbMGzFbIRePFTNnd+VHt0d
59N49LLVlTLasJpy/2aLoMtWuNtzTqX9or3anTJutui4ahNzHrhQCKjw4ANj
mPHgBUdfjCjD9iKh2yFuurTXhz3eBFabx43MILAXH5br42kdlraIKfjVexTs
OXVh6hUJ6K5eOXcjs56JzW5X509QGe7ToBxs1XMVl0iNpkfqhR5ffbWvF9DR
eKuY3VO0tyl98YHFTHX/UXkUt6CFPgUo2rOy3wPUh8gDqrYr26IEVpD+JGOH
Gp+1SuQYvB6qEkZPgIEU9Sk5ikrTRoASXO30/zVcdvsVfC5Wam7QHpSMbgID
vKMvxiAe3TT2eTAfrR08SPZUM3HXOXGIL8p67gI+rlOetqeWohiprXuonDlo
9yKcgYQSbC22uKeuJIPTErY+481mJQyFQ6i5saPhvbr9kLqJOu+vBVL/xroq
J8RNk2uEY22F3FqvrHDXpLAQCkLKWc0FqS5oaeul2/1peFy55G6QHZZiCs7B
5sQJ+gtp9fhcrQOsUXl2t+djWlVEhZnWecVto6IiPWfRNq4744J76kmE0wZG
UCyMnB4XIMDy+EoIyckJL9dpu5TbL8ph59pxaMdDYRMM/dCcHrflM1b11P3G
yQ1O/2vttTzqq+E4LSDRxsu7sb5nNuBD2O1c4iCDb4rWtnLUDGOFsKhWNqw5
aCTMa+qrYCMaoqINxQURSBTlbIyhpTFyta/2QBQGhC88NvBNwUCHqEcZdLBP
+xo8HELRB4eUMqVQX23j3mYQ+OisXBfi8bHscscjIyhuA5Y3D3p87XJc8g56
Ug0CudMgrQSaL6Jbrev3PvRF7kBVzJOhQYJqljaQCxoKC2OCfH9KboY5t65F
JhcrSJtCU7ZmA9vb5p6Ad5C9azijgNRa47AMqq/YFcI4wVSkSUM+5soHdqlx
JXzM9Q665cBodKFtxP1gNYUPFDG27KLKXvn7WcFhGwwu2tG2PxpcfTB0/Q/E
mP/jYsvqekBgbTIRlwPuzw5w1x7ag9009vRkdLkbnKoHn8pc822HXmenRLD3
lbvntTtQ5rS9IA5kZ3ddcKwLjgOTvwvuFIr8QjutSzvn4sMMkXfcTeJC0D6z
3wc8d1tax0eGcivOB+a3gy4PDyfz43Q0uZuwPWqdG2Z0a/fe8AYm3H41XlcV
v+kOKOjR627vscnh6pIJ7kez4n8ljebaQn0NuF+qWdfSsJ9zu6sChUlwpAW3
5WgbMn7bNgXbaSbrE07jpsF+edBhfXcu5Dxu0L6Yu1U8CKy257apnCjlKvHz
3ikAVSpNLAR+roFI2CdwynO5hsZSC2a4FatOxG2yAoyXTs7MVYP+DjiR84tj
lqCLhjQvKTRaGfVUsidhh8pbNKfmcHJR2da4YVfE1loLki8brgKOSlVDYrPD
6iyWHQfppJ+z1SheH98IQzSQJaeX99/wu/THd9bqAB/gz6xq+NHQSoE7sHF1
gLaAnCbnRzfffTP1o1wSdyveJ6/ozBci08ImPK433uD8g9YCu31iVViMp6nb
VlQWLr5eWRGH6yQ6lzEcFzidu+3F/RNc507roWC3faosbYBQWnNvnFG3Wvfg
62PPCL0Du7Ig/YUmyYIurqXcNSip4ZXcOVjIlSpBRYPvijyAply86O8tSoMg
l/BhFQV825nNQ9s4lrLRxB9Cf3EsnJ+wMZCqyZWckRnaJM+SXy7P1d+u+pRW
uAjz0Eu7oiyHqBt8YCvFehUap9m8TY010SB84xSXcdRVZTLb/wxvnRtJtdAF
IEQxuBOx1CXbd++ZIlLW+I3Dqr1sIiwD8p4chyVRqdBB8rK2LVfjxVvc168f
Yko488zd57ZO1QCREwsZhuOVI42+ceOPNwsAJM465VKwEK14aLk4J0g41nI0
2k7QbMQecZTfATYvhgNN+uGDXGZtEwrZyCW91jG2UL+Eq/vXk5cnf/RObnF5
sokjHUtc/zQHbq94dpwLcyOFW0AAn4YCQA8rzrTJZG7td5eQold+arMlp2OR
dETdjxicxcrnB/GNSzKsT7O08QguVYlulYhNzSO7HqsUZu4yyqAUTgLq1h38
cBEcvglS6uO0h6PIA+UCpNJxUE0CGvWRvcKSM4aSc3r2kb9zRo4Ljmq1tbju
Aurpa7KvOBvK+yhaBziwPRQRMgBTwSt178YtqGiVZKYWcjqI14XcwXbRcF0h
PhHgGtGweEgfxGalcRp0P+CoDmtbTrSn5XqZzk03FRLy/mx7nURryluAHV2c
bNFc2vpueJ2/X+KEiw6AldwQNe3cvX8SxhWHnHfyCFKGrbjDfu2M9Efg852Z
16iLhtCTjEPQvG6wC9zDJ69en7y6OGY23un+oxOzOX6DoOXOtDfWIamX1UWe
qX0Xf8C9Ap2Hy9cRIcUqp7bwdJm2rk8ml2g4SYYe6psi7+SmkOPLd1E/IW2A
3UpaHPBaql8lr0jbNbsGfuM1rKru6UoEwYQsQwZnOyRGODu1kdJM1gM+EV7R
KjmNIoJUp3GRDbmVTbUBj9alSSFKJQqEHKSKy4OL2nG0SAniq3Jc5yjOc5Dq
0K20v+eGjiwrdiOzjj2MhmxiHze3bEolxQ5OADt+ZwvtREeFbe+ckOLu1IUG
ZvHgyqqv+Ep6pDVnArG3BlUR7WQSfD/W7cOWvEv/ceZl0iTfdpjvXFJG2B8i
uMtPwsyNSdx7osJrN4WnB1ESSNgDzpbbFZYGGuPcMJAGpZEM+lXR4k+ncfNu
0AVAe7Yx/tjppiyTRcraZiaCNSNcjga3hnTc1HGkHUdkxSHOvDRyLVT8onow
WCIZdCuqMqefDvOUX6Y5nHWRtK25a03bB+6JfaXWmi6yGT4fCDV7c+aNbcst
aktVJws0g4nreq0T3zoufC7JsIC56uKeYXEOmRh8UH0Zg775NsAXtt5c9Q5f
1/ed+/npk28OBs0SXEHxnDOaif2jPSf9C8V+X+Mqq57QEZz0uGMXOJhJQ/OR
8CFTAYpBbeuO509m3zz5z3Jz6LAOMw1ucXYZh7GmAAeAHerZk9lzGiryhwwa
LQ897F1QMyfKpTi5RPfx1XIHPjH1um/uiYdo0Frqa3YyN6Pm7Jzkqp1c5GW5
kSRsltRy83dCPq2kQAn1SDbqMJ3myXcz26fa3c4imxsuM7D6rYteFtMOb8Ot
9Y7lOstSEeRolsRZH8J8crBNdLt15ZFjebOOo+0WCWrjB57SqBNAGjPd9hJI
cCPX1Xi0DTxJduhX3y5r2/mFSwItPFt3f7J4FkZykiwQmb1f1fa64yvrEVc7
R2uaNO80uOJGyxldnlfjhmgGQ4i24isppd0Q32Cg3e/FN2AbNgIiQ1OTJbBO
GDfPUf+ai8TNjbs08p4okxt67awo5TPVKJK/vYszAMITHyr4Ia+0dy8fDNDQ
V8ncKFjEJx/47vEEs8uQNafaNWzE5PH37uwk6A8u5OCWk7aZaVbP1GKSGMou
GCqp7IULXq96kOdZr5MW4HAmIbHeVpWGAg4yQAq5onEPkp/Ndnc2pXv2U19I
PEXsqdyUcHZGMBprW4prF0pibT7tR+p44LlizVBwUOqQwhvFlya9h5J/q3nG
J+7KNPWXcijLlUlGDU5Qd+zanbKTwvh4BfzTbzVgMmAGn50KKN2f2fkGv2S2
LMpc4mxozfLWptj9NhYL/vPXX/GHGT48/vy6BXs/WBiSKHalHUC1yowZcuQ4
AjE2WHRtcxx39r3MafhjthE18FSlmqodlCVqkGpPjFYBvDcARTNc2yZlrDON
RinjS808D1XHcGYaZBejoZTH/cnkkzh+XFe3xaJvou35eX4bSbml8wy/fRyi
V/CmFgroNWr85Uy/ezwEqr5NP0vWwkNhvDEstUUSflwXCP7iscLW2pw97vNZ
2TS3tSESVmpHdGrX/MtXD3IE0DdXH4Z0LQQYxTuQ1BuaC/4wTitGBqi3X4J9
jKR0Ca2G6UyaKAL3M7BMkpt3GiESnz76RcqkcDwSh0lL54FdSVGaDibUvUJf
KI21x+oEhjgi6mrtrRfvdTgSUg1OYwpsl8agIalqqxvXWo+G+cVaJ4HpsGOn
jNso4cgwELjViBgc2HrArWx/N8JW++djUa6d6R526/4MwrpUhs06m+3OZ5Nw
tMelpOtHivHXpmApsfaXfvEVSqbRLtRSuCKlB9I2ELC+UB2qdJqHb1nnuhYi
PSZF8tH4C9YhK9d6SmsNd4BBZjm2rncnxVtW4ABd6zhHw67lwYc4235hHnxG
kz1crsfwYeaGLKh6jnE9GIGNorifGonx+1J6s37RiyHaogSidu2hX55dvGae
RZZZvagK2+dlpLYUWGNF2aBWVV2/7ErkXBO+16x2fYfk0i2nKhC2XVq9YBJ9
HWUlc06A2YqtGui8gbo7SgIcVXGjhtjxy45+4vsuDXsVhiLRlkIMU3b0XTCa
PA+lV+h03EnfYrkwGCJkE19wE+j0oStAhQ3/FqU5grnQ55kNQzwWDUqYxaru
TLgohnzQzMkZI3y1rbSJw2nrXbfq5uA+eT7BtLYarJTxO4c0lhHwKL7xbOp0
S1l7ybWA3Kh3CHJndH9ZR8jka2R9nV5fHD/+PAaqMie4z1eC8/64oDG0xBdR
IIZe5VxoSYZBjjt++Fpt2npeiLGvbt5SWx9ASbViSdwA9qKB1t2QRkrb6eXJ
7PjoDJWwiE1ghA8fzq+vjoNvIbEvVLIxevNNRi49orCHzNBeL+uuXjTpesnB
NrcXV5jGAR9+StU7dAfL7TesFzr3uL8nYdD6HTP+NmgpSgho/3wcxx/1FRzs
H9A32XbmHC9F8ybxX/lhtj+kUZbNxn+oyQc0JvEPa1qYsmPbN2cQkfeRlU2h
F17y25qsmzbzouMytZ0OQAl8YIu6YXPvktsSScXdbrPIgECiWYZFd9L/Nbo9
/MHbwIJeSxYagoVxfiIpCCTfgzLKe3F173hN2QTP3BVScSNkcZBz7vLQu4NT
tfYP92pSgEuzpkQvSfKFfqRi6UO7KTOBArpK70RnxVKMeAnES4ULWLecwUBK
jLg5iADQbX6lVbdxqzo5nJTraIgJieuJyVWVX7m4z99KcJAcyQVSdjzBxanz
4boo54a7ZNsgz+7mIazDDnTuFuN+xQZ94Avb32uKDzr0kqLd3UHyzin97Adh
PJI7C60XxF0hwBuQ9BhupjUNumk59w/tek3TcMnkiBtPbqwBglaCjnvwdAQt
d3CXnW6naPe88uU/9G/vGsbxDY2mDbxUPAY3OxC/U+AGDK7ZmrKpbFuV3nIe
pyQisFsZl2qxy12veiVomwaRpkHObJSHpDyKHT77bidKJJ9XEnhnVyeXyITc
teOdE9Rm9w6uoI12KIP+JjnCjkxlUOK3C1Ke+/ljX70v99YO+vYOk4E5moWr
GXCkx1E5r15Wfm46tsOhNsx8+sdjl8Y47mv/R1N9JGNeqq99P+kgjcbdY2j9
e+g3suZbA+xMQdPFKV86xZHt3aHG0vukD63PCA1SEziVjBspybxRDaXNsJBG
nUh0c8k+knweZsk0RjIsiV55eakWzw2zaexzn7/K09swf4bGKuuCi1g1BKh5
c7nrts4PROka8aE5QbBnRu3rU9yn2S4i3cTJ2ty+NLwjS82U0yv87+jl7PLq
9Jej4z/Nrm+Obk7enmgdadh+AGkh6rh2NUbrnqg+8/cw/zbsV0B4HKCoeAmj
m6k6rekL2yoMWqFuoT3xDLWdWl+L66B8X7QbX6JgsxXjGEB4S6jL7bSXx9k9
2dJ2b0dpLxAyM7wPiTUH8c9K5/L5dnyiLrqDttBbA7UKVeRzJ3dvGmTPXIpG
iEomlwwThqirPKyAHN4T6/IkOd1p9wIa+EBJ+IrqzF6EKtKpEVFEEXe1ldaP
sV5VPnD/JidNqbYQtDq0bUHzWtrlo5euBEsClTkPIOeiIXIhqphIIraOzo9G
8D2WTAjKyJOST4RXJ5PZbMYX/GKYI9eeg93Ckw8vRPKb/F8f3aZlax59DFre
RC5A2gEx4m1yVJr3afK2bppClITrzqwRcTbJ2+w4lV63fKkP7mRAmmKxqLgD
oYh4bXEdVE6M+ABs5pYXyUNBTATFrRr0ruOlpJ3I4vIG1QMygr19ju8MyRHA
phl/2x96gxDCjzP6cTa059QK3t1x1MfPThl5ebjHjPXy2Ly8pfRTFtPDZS6K
WmdLLLQj2U57hNfEP5Jf65qY7cu0ISl/Zop5Ok3eFkR+pkyu8C/hMY7jpanA
RN8i74fs22XT39P/65x0uJ/TpkyOetPM2Yn5FomANNjPFTxxU9xH0SYni4Vp
CAWuakKVDjdBNXcE7JtlvSKc+4lkH50lgH+fNjVBtEsrWshJU9wlP0N1mSZ/
qJcotcYltQ3GWRFzf0WEVhYbAen/+Z9NkSW/bKsM+TTIHHEBxwB/PF5Z7jKS
8FcPEGXyfwHCoiq60LUAAA==
-->
</rfc>