<?xmlversion='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-rfc2629 version 1.5.6 --> <?rfc toc="yes"?> <?rfc sortrefs="yes"?> <?rfc symrefs="yes"?> <?rfc docmapping="yes"?><rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-shmoo-cancel-meeting-06"category="bcp"number="9137" obsoletes="" updates="" submissionType="IETF" category="bcp" consensus="true" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" version="3"><!-- xml2rfc v2v3 conversion 3.9.1 --><front> <titleabbrev="Cancelingabbrev="Cancellation of IETF Meetings">Considerations for Cancellation of IETF Meetings</title> <seriesInfoname="Internet-Draft" value="draft-ietf-shmoo-cancel-meeting-06"/>name="RFC" value="9137"/> <seriesInfo name="BCP" value="226"/> <author initials="M." surname="Duke" fullname="Martin Duke"> <organization>F5 Networks, Inc.</organization> <address> <email>martin.h.duke@gmail.com</email> </address> </author><date/><date year="2021" month="October"/> <area>General</area> <workgroup>shmoo</workgroup> <keyword>virtualize</keyword> <keyword>postpone</keyword> <keyword>move</keyword> <abstract> <t>The IETF ordinarily holds three in-person meetings per year to discuss issues and advance the Internet. However, variousemergenciesevents can make a planned in-person meeting infeasible. This document provides criteria to aid the IETF Administration LLC(LLC),(IETF LLC), the Internet Engineering Steering Group (IESG), and the Internet Research Task Force (IRTF) Chair in deciding to relocate, virtualize, postpone,move,or cancel an in-person IETF meeting.</t> </abstract><note removeInRFC="true"> <name>Discussion Venues</name> <t>Discussion of this document takes place on the mailing list (shmoo@ietf.org), which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/shmoo/"/>.</t> <t>Source for this draft and an issue tracker can be found at <eref target="https://github.com/martinduke/draft-ietf-shmoo-cancel-meeting"/>.</t> </note></front> <middle> <section anchor="introduction" numbered="true" toc="default"> <name>Introduction</name> <t>Among the highlights of the IETF calendar are in-person general meetings, which happen three times a year at various locations around the world.</t> <t>Various major events may affect the suitability of a scheduled in-person IETF meeting, thoughfor some eventsthis may not be immediatelyobvious. For example:</t>obvious for some events. Examples of such events include the following: </t> <ul spacing="normal"> <li>A meeting venue itself may unexpectedly close or otherwise be unable to meet IETF meeting requirements due to a health issue, legal violation, or other localized problem.</li> <li>A natural disaster could degrade the travel and meeting infrastructure in a planned location and make it unethical to further burden that infrastructure with a meeting.</li> <li>War, civil unrest, or a public health crisis could make a meeting unsafe and/or result in widespread national or corporate travel bans.</li> <li>An economic crisis could sharply reduce resources available for travel, resulting in lower expected attendance.</li> <li>Changes in visapolicypolicies or other unexpected governmental restrictions might make the venue inaccessible to numerous attendees.</li> </ul> <t>This document provides criteria to aid the IETF Administration LLC(LLC),(IETF LLC), the Internet Engineering Steering Group (IESG), and the Internet Research Task Force (IRTF) Chair in deciding to relocate, virtualize, postpone,move,or cancel an in-person IETF meeting.</t> </section> <section anchor="conventions" numbered="true" toc="default"> <name>Conventions</name> <t>The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<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"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119" format="default"/> <xref target="RFC8174" format="default"/> when, and only when, they appear in all capitals, as shown here.</t> <t>In this document, the term "venue" refers to both the facility that houses the sessions and the official meeting hotel(s), as defined in <xref target="RFC8718" format="default"/>.</t> </section> <section anchor="decision-criteria-and-roles" numbered="true" toc="default"> <name>Decision Criteria and Roles</name> <t>The IETF LLC assesses whether an in-person meeting is logistically and financially viable in light ofevents,events and assembles information about various travel restrictions that might impact attendance. TheInternet Engineering Steering Group (IESG)IESG andInternet Research Task Force (IRTF)the Chair of the IRTF assess if the projected attendance is sufficient for a viable in-person meeting.</t> <section anchor="ietf-llc" numbered="true" toc="default"> <name>IETF LLC</name> <t>The IETF LLC is responsible for assessing the suitability of a venue for an IETF meeting and is responsible for any reassessment in response to a major event that leaves the prior conclusion in doubt. If such an event occurs more than fourteen weeks before the start of the scheduled meeting, it is deemed a non-emergency situation. Later events, up to and including the week of a meeting itself, are deemedanemergencysituation.</t>situations.</t> <t>In non-emergency situations, if the IETF LLC determines the scheduled meeting clearly cannot proceed (e.g., the venue has permanently closed), then itMUST<bcp14>MUST</bcp14> share the reason(s) with the community andMUST<bcp14>MUST</bcp14> consult on its proposed remedy. In less clear cases, the IETF LLCSHOULD<bcp14>SHOULD</bcp14> conduct a formal reassessment process that includes:</t> <ul spacing="normal"> <li>Consulting with the community on the timetable of the decision process.</li> <li>Consulting with the community on criteria to assess the impact of new developments.</li> <li>Publishing an assessment report and recommended remedy.</li> <li>Seeking approval of the IESG andIRTFthe Chair of the IRTF for the recommendation.</li> </ul> <t>In emergency situations, which lack the time for a consultation process, this document provides criteria that have IETF consensus andwhichthat the IETF LLCMUST<bcp14>MUST</bcp14> apply in its assessment.</t> <t>The IETF LLC will collect information about the likely impact to in-person attendance of national travel advisories, national and corporate travel bans, availability of transportation, quarantine requirements,etc.etc., and report the results to the IESG andIRTF Chair.</t>the Chair of the IRTF.</t> <t>These criteria, some of which are derived fromSection 3 of<xref target="RFC8718"format="default"/>,sectionFormat="of" section="3"/>, apply to venues that are re-evaluated due to an emergency:</t> <ul spacing="normal"> <li>Local safety guidelines allow the venue and hotels to host a meeting with the expected number of participants and staff.</li> <li>It is possible to provision Internet access to the venue that allows those attending in person to utilize the Internet for all their IETF, business, and day-to-day needs; in addition, there must be sufficient bandwidth and access for remote attendees. Provisions include, but are not limited to, native and unmodified IPv4 and IPv6connectivity,connectivity and global reachability; there may be no additional limitation that would materially impact their Internet use. To ensure availability, itMUST<bcp14>MUST</bcp14> be possible to provision redundant paths to the Internet.</li> <li>A reasonable number of food and drink establishments are open and available within walking distance to provide for the expected number of participants and staff.</li> <li>Local health and public safety infrastructure expects to have adequate capacity to support an influx of visitors during the meeting week.</li> </ul> <t>Finally, the IETF LLCMUST<bcp14>MUST</bcp14> assess the impact on its own operations, including:</t> <ul spacing="normal"> <li>The number of critical support staff, contractors, and volunteers who can be at the venue.</li> <li>The financial impact of continuing ameeting,meeting or implementing any of the possible remedies.</li> </ul> <t>The IETF LLCSHOULD<bcp14>SHOULD</bcp14> cancel an in-person meeting and explore potential remedies if it judges a meeting to be logistically impossible or inconsistent with its fiduciary responsibilities.</t> <t>In the event of considerations this document does not foresee, the IETF LLC should protect the health and safety of attendees and staff, as well as the fiscal health of the organization, with approval from the IESG andIRTF Chair.the Chair of the IRTF. The IESG should pursue a later update of this document.</t> </section> <section anchor="iesg-and-irtf-chair" numbered="true" toc="default"><name>IESG<name>The IESG andIRTF Chair</name>the Chair of the IRTF</name> <t>If the IETF LLC assesses there are no fundamental logistical or financial obstacles to holding a meeting in an emergency situation, the IESG andIRTFthe Chair of the IRTF assess if projected attendance is high enough to achieve the benefit of an in-person meeting. The IESG andIRTFthe ChairSHOULDof the IRTF <bcp14>SHOULD</bcp14> cancel the in-person meeting if that benefit is insufficient.</t> <t>The IESG andIRTFthe Chair of the IRTF are discouraged from relying on a simple head count of expected meeting attendance. Even dramatically smaller meetings with large remote participation may be successful. In addition to the IETF LLC's estimate, the IESG andIRTFthe Chair of the IRTF might consider:</t> <ul spacing="normal"> <li>Are many working groups and research groups largely unaffected by the restrictions, so that they can operate effectively?</li> <li>Is there a critical mass of key personnel at most working group meetings to leverage the advantages of in-person meetings, even if many participants are remote?</li> </ul> </section> </section> <section anchor="remedies" numbered="true" toc="default"> <name>Remedies</name> <t>If a meeting cannot be held at the scheduled time and place, the IETF LLC, IESG, and IRTF Chair have several options. The remedies in this section should be considered in light of fourprinciples, presentedprinciples (presented in no particularorder:</t>order):</t> <ul spacing="normal"> <li>Hold the scheduled sessions of a meeting in some format.</li> <li>Provide benefits of in-person interactions when possible.</li> <li>Avoid exorbitant additional travel expenses due tolast minutelast-minute flight changes, etc.</li> <li>Ensure sufficient time and resources to adequately prepare an alternative.</li> </ul> <t>The following remedies are listed in approximate declining order of preference.</t> <section anchor="relocation" numbered="true" toc="default"> <name>Relocation</name> <t>For attendees, the least disruptive response is to retain the meeting week but move it to amore accessiblemore-accessible venue. To the maximum extent possible, this will be geographically close to the original venue. In particular, the IETF LLCSHOULD<bcp14>SHOULD</bcp14> meet the criteria in <xref target="RFC8718" format="default"/> and <xref target="RFC8719" format="default"/>.</t> <t>Relocation that requires new air travel arrangements for attendeesSHOULD NOT<bcp14>SHOULD NOT</bcp14> occur less than one month prior to the start of the meeting.</t> </section> <section anchor="virtualization" numbered="true" toc="default"> <name>Virtualization</name> <t>The second option, and one that has fewer issues with venue availability, is to make a meeting fully online. This requires different IETF processes and logistical operations that are outside the scope of this document.</t> </section> <section anchor="postponement" numbered="true" toc="default"> <name>Postponement</name> <t>Although it is more disruptive to the schedules of participants, the next best option is to delay a meeting until a specific date, at the same venue, at which conditions are expected to improve. The new end date of a meeting must be at least 30 days before the beginning of the following IETF meeting, and a meetingMUST<bcp14>MUST</bcp14> begin no earlier than 30 days after the postponement announcement.</t> <t>Due to scheduling constraints at the venue, this will usually not be feasible. However, it is more likely to allow attendees to recover at least some of their travel expenses than other options.</t> <t>Note that it is possible to both postpone and relocate a meeting, though this has the disadvantages of both.</t> </section> <section anchor="cancellation" numbered="true" toc="default"> <name>Cancellation</name> <t>The IETF LLC, IESG, and IRTF Chair may cancel a meeting entirely in the event that worldwide conditions make it difficult for attendees to even attend online. Not holding a meeting at all can have wide implications, such as effects on the nomination process and seating of new officers.</t> <t>Cancellation is likely the only practical alternative when emergencies occur immediately before or during a meeting, so that there is no opportunity to make other arrangements.</t> </section> </section> <section anchor="refunds" numbered="true" toc="default"> <name>Refunds</name> <t>The IETFSHOULD NOT<bcp14>SHOULD NOT</bcp14> reimburse registered attendees for unrecoverable travel expenses (airfare, hotel deposits,etc).</t>etc.).</t> <t>However, there are several cases where full or partial refund of registration feesisare appropriate:</t> <ul spacing="normal"> <li>CancellationSHOULD<bcp14>SHOULD</bcp14> result in a full refund to all participants. ItMAY<bcp14>MAY</bcp14> be prorated if some portion of the sessions completed without incident.</li> <li>Upon postponement, the IETF LLCSHOULD<bcp14>SHOULD</bcp14> offer refunds to registered attendees who claim they cannot attend at the newly scheduled time. Attendees can opt out of receiving a refund.</li> <li>When a meeting is virtualized, the IETF LLCMUST<bcp14>MUST</bcp14> offer to refund registered attendees the difference between their paid registration fee and the equivalent fee for an online meeting. The IETF LLCSHOULD<bcp14>SHOULD</bcp14> offer refunds to registered attendees who do not wish to attend an online meeting.</li> <li>The IETF LLCSHOULD<bcp14>SHOULD</bcp14> offer refunds to attendees whose government forbids, or has issued a safety advisory against, visits to the host venue, even if the in-person meeting will continue. ItSHOULD NOT<bcp14>SHOULD NOT</bcp14> refund cancellations due to employer policy or personal risk assessments.</li> </ul> <t>These provisions intend to maintain trust between the IETF and its participants. However, under extraordinary threats to the solvency of the organization, the IETF LLC may suspend them.</t> </section> <section anchor="security-considerations" numbered="true" toc="default"> <name>Security Considerations</name> <t>This document introduces no new concerns for the security of Internet protocols.</t> </section> <section anchor="iana-considerations" numbered="true" toc="default"> <name>IANA Considerations</name><t>There are<t>This document has no IANArequirements.</t>actions.</t> </section> </middle> <back> <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="RFC8718"> <front> <title>IETF Plenary Meeting Venue Selection Process</title> <author fullname="E. Lear" initials="E." role="editor" surname="Lear"> <organization/> </author> <date month="February" year="2020"/> <abstract> <t>The IETF Administration Support Activity (IASA) is responsible for arranging the selection and operation of the IETF plenary meeting venue. This memo specifies IETF community requirements for meeting venues, including hotels and meeting space. It also directs the IASA to make available additional process documents that describe the current meeting selection process.</t> </abstract> </front> <seriesInfo name="BCP" value="226"/> <seriesInfo name="RFC" value="8718"/> <seriesInfo name="DOI" value="10.17487/RFC8718"/> </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 for the IETF and the various stakeholders required to realize this policy.</t> </abstract> </front> <seriesInfo name="BCP" value="226"/> <seriesInfo name="RFC" value="8719"/> <seriesInfo name="DOI" value="10.17487/RFC8719"/> </reference><xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8718.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8719.xml"/> </references> <section anchor="acknowledgments"numbered="true"numbered="false" toc="default"> <name>Acknowledgments</name><t>Jay Daley<t><contact fullname="Jay Daley"/> provided extensive input to make this document more usable by the IETF LLC. Many members of the IESG and the SHMOOworking groupWorking Group also provided useful comments.</t> </section><section anchor="change-log" numbered="true" toc="default"> <name>Change Log</name> <section anchor="since-draft-ietf-shmoo-cancel-meetings-05" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-05</name> <ul spacing="normal"> <li>Minor changes from IETF review</li> </ul> </section> <section anchor="since-draft-ietf-shmoo-cancel-meetings-04" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-04</name> <ul spacing="normal"> <li>Threshold for "emergency" changes to 14 weeks</li> <li>Clarified refund policy</li> <li>IETF Last Call nits</li> </ul> </section> <section anchor="since-draft-ietf-shmoo-cancel-meetings-03" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-03</name> <ul spacing="normal"> <li>Clarifications from AD review</li> </ul> </section> <section anchor="since-draft-ietf-shmoo-cancel-meetings-02" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-02</name> <ul spacing="normal"> <li>Added IRTF to IESG responsibilities</li> <li>WGLC Nits</li> </ul> </section> <section anchor="since-draft-ietf-shmoo-cancel-meetings-01" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-01</name> <ul spacing="normal"> <li>Added refund principles for hybrid meetings</li> </ul> </section> <section anchor="since-draft-ietf-shmoo-cancel-meetings-00" numbered="true" toc="default"> <name>Since draft-ietf-shmoo-cancel-meetings-00</name> <ul spacing="normal"> <li>Jay Daley's nits</li> <li>Distinguish the emergency and non-emergency process</li> <li>Eliminated USSTATE/UKFO references</li> <li>Clarified roles of LLC and IESG</li> </ul> </section> <section anchor="since-draft-duke-shmoo-cancel-meetings-01" numbered="true" toc="default"> <name>Since draft-duke-shmoo-cancel-meetings-01</name> <ul spacing="normal"> <li>Change to WG draft</li> </ul> </section> <section anchor="since-draft-duke-shmoo-cancel-meetings-00" numbered="true" toc="default"> <name>Since draft-duke-shmoo-cancel-meetings-00</name> <ul spacing="normal"> <li>Added mention of IRTF</li> <li>Discussed consensus on cancellation</li> </ul> </section> <section anchor="since-draft-duke-remote-meetings-00" numbered="true" toc="default"> <name>Since draft-duke-remote-meetings-00</name> <ul spacing="normal"> <li>Defined "venue"</li> <li>Added principles for selecting remedies and rewrote alternatives.</li> <li>Added local authority travel advisories</li> <li>Added some criteria from IETF 109</li> </ul> </section> </section></back><!-- ##markdown-source: H4sIAIB0EWEAA51aXXfbyJF971/R63mIPYdi7BnnY5SHWa0/lbVsx5KTk7Nn zx4QaJI9AtAMGqBG8fF/33urugGQkifjPIyHIoH+qLp161Z1n5ycmN73tTu1 z0IbfeW6ovf4ZNehs8+KtnR1Ld/YsLbnL65e2gvnet9uoilWq87tT9NT+Gr6 qQplWzQYtOqKdX/iXb8+idsmhJNSHj5p9MmTx783VdHjwU/Pz65efDYl/tiE 7vbUrsqd8bvu1PbdEPvvHj/+4fF3puhccWpfuRbLrM1N6K43XRh2p1YGNyb2 RVv9X1GHFkPeumh2/tT+Tx/KhY2h6zu3jvh02+gHrLIpdjus43+NKYZ+G7pT Y+0J/rPWt/HUXizt8+HayRe6oYuiw8Knb0O3ObUvf2ffup7LwajnbbmUn1xT +PrUNvLGcrus8M5/bvjlsgyNMW3oGph2706NMb5dz/88OTmxxSr2XVH2xlxt ndo+dJVvi87Xt3Yb6irafts5h7We7FwX4aRk12jxNwxQdLYPtvKxHGK0PsYB NoGJbFHt6Qi8j5Hb3nWt65f2dbhxe9ct7B5zhCFiC67buLb0Llp4Dnu5draw u7poW1eZO/NiJWtXRL+q3dJebX2kjYfGtb3ddWEPeGGczmM+X3Blha90Cdic Oasa33ruWfD25s0z+xD/PFqMK7Qv2o1vHd7GVJd9+vCKELAPz19cvsKz2J0Z n//gImxQbu1VEa/ty9Bhyw/PP1y9fGSfbQvfYb22cqWvOA7Wswux3wE8C9uE Pf4NnVHAYtiZlcUXactLdVbjq6p2xnzDxXahGkpuwpizJnBo7HHrN9sa//WR oZR3DbPWrq3gKGB7NsVGMT46dGFvtr7cmi0A69rk9943MGihji760W11KFMU F7BNqzYGPOsKq/1reqgpfkKIw99tzz9ubbFeu7KXZ+Pg+2Lla9/fcrGFjeXW VUPtqiMrmLS+BV4Lw2YrtBFD4/LAPUHA0dvQ2xV22DSu8ohyQDis9lzJko4x 7uei2dUE/7f2bMQTBhnwUh9dvZZhhtb9vMMyXYUByjpEByfZgEV3Nx5/YIqh LYA/upOjmLmzbOf+MfjONbK2apCnCrt1Rd1vNT4WtnYbGB5LU+JbjBMY2rX2 /4QVgGbM0Sx1tW3RD3QWAq2IgJ4tw1BXQNamKyoNMqB6LzCq5rHS4fEOUBnE 97YwKbJGD+oLjDrfc+8wJ5bAVa+Hjmuyq6GrBBDw/+GI5sZjU8UMqN/avxWI 7tLvfY3ROhd72d1uWNW+zGZAgEY4TfeQIj6veWhjsXZc1W/hMwww1JzW3jC0 d2DnisbAwrHIQDt0u4B4Hve/KtqoRmutK0MbGsx7MGHcFt0Ovu2AN0QrpggD whZQ3oM5xbPEmI63SEtQc8JqN7BIBggiomdoIX5lSkR8u8FAeHAPRyHYsenb 0bszaNkNor9riRLsg2bqfKkB1TCCjViFbk34bIsSSxTeo29aUF7HGNMVOMc9 fyUd2i/SoflKOrS/RIfm6+jQ/go6/IZSgtFPg2nyuna35B8krAcXHy+vHiz0 //btO/n84cVfPp5/ePGcny9fn715M37IT1y+fvfxDX436dP05rN3Fxcv3j7X l/GtPfrq4uzvD9QMD969vzp/9/bszQPuk8RkRneQfLFhEhSNBSQLgOAwF+Gh lRCf/a9n7+2Tp/bTp//48PLZd0+e/PD5c/rjj0/+8PTzZ3Ozda1OFlpgWP+E R0GuoO1CDFzUNay4A8HWYHVMEbfhpkXwdYTpua5sBMpC2cN1jX0gYHsAPK5h d1kugCu/r4tSyVpoAEwcHanXmUhUSiJIWSCs1770U2LBw+Dih/HRQne79q3u Ne3rD0/++PmzOPU5gMGx7LOMWI75IdQuOZkILSJnxOTYugTVAVBG5mOK2gDb JDPYiQNhYkDL82+z9xLnjGiGG1OQphO1LSdp8ABDOakmMuUqDFMKVH4wB7Er xpEARhraQVnNGcJezaTQvZFl5pH1LwPrUGeoXayXxG8Q/D8dUxSNEgfxDgFJ jivsaIgjC9Ih32jcweqT+TEGdryjks9EqTP7JELuJHYlMHnwMKPLBu8bryU3 66gSOvBSeiZl05mwMGLy2sEXgkfQnpe00Jb1IGAi44RhBfF5vsbqYEKsQ961 oSwH4LwJjE1wt1kjE8AXyDbOXUcE61p/wrZ6iOwsqyatMooTJE/GlEPih82h vNuTLG1vbfT9IBBa2jcFs3fGGpzNDdEOXG+Vjcjp1XppAqMCZSE0kmdp7X1T SIR/YX5MqQARX1aOUQ8Uxvt3BfUDzCFaQMkUVwBV6fDzQ7fcLBez7LQtpBxo ihbbyqqpeiSPtDSNUDHzrhjT0LuhBSVYERAcCPVKM7QEDa0hz8OHkvzpQ2gp zL7jsJbiqrqFOxG8gIiRVYLwgJfFuLdE4hiDQhmGlDCuD4ElG4oxSxt6wEXR h890bhrhniWGVjkT4riX8Em4qDKBpYGXv2qog/ysUcxnEoFg6NbdmAqQqcNO ZKUM+56KKm41juxsU52DIOrFjJ3jRNQHo9X46iXQJe/tqBGoo3K1cPlKWQe8 kmhFlNDWTUPNQHY/wKSKsHVRXo9GSlyTHKpkmky0OEqT96gWSTiI71TNkAYw jiYcnSw7XWCDXQGyXkEz2WU5cdiNZ4IMdc1i5C7Bc7TaX7N+SD6AY0aCNDNC pW+yFs3yu4LyC50nFsffuNJ7herCJM058iV+bCMdmCqDfwwFvgF63EFlsbCu L5fJyeJvjSvaVxL3F/ypVgCPZvMutJbCzGpK5ZfO7wGZdRcagEVym/2ez3z6 9OOYshfJ0phMWCCFEQfo3IkDrgAJjJJroBleJMTesNSxFPvY+WaA02uhIuTn cDMjF25AJITsawvBOKsWckSZUVhDGa/AsFjsjm2R0u8KVmIcBRy+XksEnAtb g05GQS24k9gdU64q7mxMXYxukSvkdkFHCQ6pPEg5FK8MvWcdd9D+0DAA9vAl QotwXqC6ity2Cg9TFbcnfTipWM6CauOfRM9VlVc0UPA42wxRKt1ZMgeYKlRI rMYoX3TlaymgGthuViZY+z5vNWbO4yrUc6T52jeeluyDQngvPjBD24TKrz1+ OX+/f6rAer//PSOyJUj2gLDKp00dVsq15TZh+0957djZivOYvCs8KDNqCIqB b1JhKAitZ3GodsvmhAbFdq6CIR9g7HksLca0g9nudzTrPwYySKfot9nRY+2T Km/NVcLyE7TWIVSy0wqy7dpCAhbCxlr105CBPRTxRS4qpVhmIVvUwr4o5Xvt kIXMeiPb/go0mwnNGkmptuacqdpOsXXUBdCxNZjIqkUFXoGpkeVhZJH4AdDa pSzC1+vhZy6BdutDx7ZGl5XKGIjIKVjMS2hsOGxxRMl3s5rSM8sSWKobxUlW QcIQ5OvJAGQsaU3ktYkBFoSfNDGxMEXfPtRDS0XNGiFIV3HFOJ3CeJlHH0uC WbbleL4dJEFO+g6O8ewe0cOac29T2jQjuiTF+lSKH8qQe2rauQqGT2oqzR1i FeNL7OhY1Gu+Nz8N1UYacfktLSUPahysL6+Eq22ZKfEr6UFoEgY3aw855Ivu dlLdDBdd9LnKmqSNxRLzfv1B1YgPWA/pghI5Oje5HNUmwpclSJ+7fTNsJlBS 3GZOmshZSsQbB4osFC5rH7E5k95POiV0m6L1/0wZUntQWcpIzvpS8tMKDD8Y XSMCpYtMMZArlOXDjkcFOs1sr7kWujMgTDap6bEwVaJTNrVrUkxq80zeooMm 7IUVNl+yypUEV1cH2JMMcK/YWnxRtelaDLDzpUKQvWLrWumoMjuXWw+/y4Ar 16JIFwTMAZvLtsmKx7Megl2i/W5hvhaKN3kSzyQ0JbJlPoq4Z09UJoADSrRi k9VJB5XGYSneYBhGKMFGuTUIiCdhMMbbrCJ/AajzBIn6T4MookioAYXxmEPg VRewfc6lIxNLwkoJDYUlc+56qJGSzqecneUDEPKbyEThmdYWmmnu2aU2D3Lk aa9a0mYr/S3JHHIiFZP4S22B9J0stGYTW3vt2PfqNmvDsU9B0aeZVjpHZEhl YQS/vIacX9/+KEppxPNEwA3gRXSw56bubUluPQrp2B+ucrJjH0zNox/4Tgwi 50N9QVbDUHfPlxbCQ8SL7P0w/XXZGT+yb/QhcaWE4xQ3qWpdERE18X9U5Upl IukSxcrEXwtBXzrmmRwjuTLKDhCxO7GjhsJE1amzFpNkTiSD5JP9qY2vseXE dgMbFqABABdb3tGfba+PgT101wO8yoO5hIfXYIijrYxNuHnPgGOIuNcCR6vG JDRS+B3ZXjqTReplsbU4KicVQ/vgmatCt4JcY09zknCpqGG0tSTBpPprCA9g uh0ArbXuu9Qm+cKwguGwL1S9zdTs6JmpN0+OSkIF8IadduQDVr415ZrI1EQe 60B9rmcxyTN8tmYuFMNKsvhZApElO8oOoRAaWJSWtD+dNvW/IbzyWQn0DRV8 zlsKmdpxj2CmbtiJWB57VV6W3bm+8O0dsUTJbdj0plDVrhYVwKzNr1IF+lbf LbDioYGFJaNnx2j9rCUtgLZxYdMVu21iMz2+ShSEqnRDeZYHBktN+LrTOZGT LelV5EL8qGUrDhq/+EF6uJOplF5SyRrZwrCMolwldx1BoHJ5PbepnbrvRtpz 0uOR7hxIHmaAOtumJl/a10Fr7qB9+VffIVXWSSooOiIPhaoUwbmT7nKXAatx POHRg2wl/1SGHhYXQmhHR1cgf545tqxj0+H0aABUTgKqXrsYqfuh2sfMhcFu prdSOR2GnuyRYh5PfEGhvE+HKfzGmLM6HZhqlhV0zVCajZc4JB7XGAqIFnAD rmJv1GAJ06jVeZw7O7RDucsMjFyLErG0lSS5TLkQQGpFfmW00UAv+HyEPKt4 2GtpKOZSw5zIcay0kjKbJmUZDB1htf+LGPz+MZ66PWjbrhwgr+Gt+JjIYX6m lLr+Y2c6FY4bZWE2Qb3rFIR5kmLdOy3WdjOzW+acAdSRvPJcaTBZWbISdowo 8JLHZjXJPJCHOEj4pvQ1Xngw4/WJmU9Tq4oUIp2TKZSEfEoeNE42yt0eKaXN MWtrmMmxSk5xxryl6NEW6Z22iZwPZQMkyhYKcPPiKQFROn3bpOx5kn0gATiU 4nh+KWgspWZp+UAvFbdjdTUigzVUJ/27eUUjulPuKPAseQ7AfPzNICUd9kec hI2KGNFvxgiHYcxdua4NIhFVohlkMipTX+YyV08hYhJbMfWTDc+q24PuqFZG rugTghkMcr6GfA1bHdye4pFXggLJvpU0yWROWpllSU3s83s3wrNmfm8iRRCM kEr9mTNn0rGTHIcICVKRa0c786LCaM70SxVrLIni7MrRxPgAj29WqMmYREmJ opgmP9ArvFQgmNYrGHoINwL4ITCxBp8stGUIogI4feqXPsICxgiaqrQs6uQE gdbBd6RyubdARpRynKumC3RhytFmzVXBBKIokJR40Ux6/nPHpP1NVxkKHT6N qYF7wL1LNigvzv7OjI6BO+mjQglL8NLS6backGuWfmVg9cMnmbXYyKaurJSH vrUfd6E9oKo7GT8wQ6VVJfK4xwc322DKuvDNWDuQpVJkJEIDTFlKHSjtpT0b x9CCo2diY4kGhzq/V5jp9HqThDgt5ke6+5zPXXXUYdK1y5rFqNPSzSyMhXbW SdzBuP2Nk4st7CrueDVi7lzQrhsPtZnG97xH1dPn+TRTicAeFMZfa1DDHlUV hOtvfNRqPFnzzgy5b/VLkxy4CpE03TThsle+itLNAg8bUTkV87Y2ZdLhBT5s kKB4dUdafmMPXJrvKVvl6ozEdbfMT0cs0klzAueDKBcflbMgyQWDcQBxuMWO prszOjSD0Mfr2YlOHA8zdvOOtpiOV7OYY0V5d9ovH72ttCOnrjxXnAfexA9Y odz0ARrSnUgSawcuHs0RQ72Xjsy9fSkahn5ihooDlJFCqREWvHSgXLLl4Z3Y 4zs8Pt30k1absD8PtuHOOLaKYx6Jt2dzZ5y9t1CGWin3/Ozt2T0TzbpU8sT8 fCndOVwV5TVHOCuv23CDUN7Ir8b8GZt6jni4za3rSguTyATj293QqwvkEtN8 RyJZhijkrZ0JgnlpLljkN47N3tntxdQf4R+Xry/evTtqLhR1DNMChghc1UbP KVO20RtZ9k3YiLK49Az8f3FlOJ48/h3i7MK3vEiQrnRJt0lw07m9dzdfNdxT CVskAKoF8dyDsZ33YJwCBnvyVG8eMIWgKNPTlhQuGhBsycilDIq5Z0wcLfu6 X7Oa76fR8yVO2d3Z839nb9+xMVDR/qLKsAlx23F7mXz+CtHw9mtX+2QcP9th 7JeIJbe3q86P3b2vG/sxxh6R/JuopvzWPmcx1m4GYWOS/9h6JRgPr1YkocY2 Bk+xWknVHy8vr86uXvz243+/fGfHbsKRV0MquqR3TFHLvvTx6nmj+5csk/AN q//tlb7yVUM8Ho3b6G06YRH4Ua3AO92umh2587bCgTi/by7tzB3N8jzd+0pX zMZ5j7wZHQ/lD3s3ks5vOjnGnGQs4juPIZdmrV6vFwV6fBQ/PikCamxoTDH9 5PEP5v8Bl717M6kwAAA= --></rfc>