<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.6.2 (Ruby 3.0.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-kuehlewind-shmoo-online-meeting-04" category="info" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.12.3 -->
  <front>
    <title abbrev="Organization Online Meetings">Guidelines for the Organization of Fully Online Meetings</title>
    <seriesInfo name="Internet-Draft" value="draft-kuehlewind-shmoo-online-meeting-04"/>
    <author initials="M." surname="Kuehlewind" fullname="Mirja Kuehlewind">
      <organization>Ericsson</organization>
      <address>
        <email>mirja.kuehlewind@ericsson.com</email>
      </address>
    </author>
    <author initials="M." surname="Duke" fullname="Martin Duke">
      <organization>Google</organization>
      <address>
        <email>martin.h.duke@gmail.com</email>
      </address>
    </author>
    <date year="2022" month="March" day="01"/>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <t>This document provides guidelines for the planning and organization of fully online meetings, regarding
the number, length, and composition of sessions on the meeting agenda. These guidelines are based
on the experience during the COVID-19 pandemic.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
  Stay Home Meet Only Online Working Group mailing list (manycouches@ietf.org),
  which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/manycouches/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
  <eref target="https://github.com/mirjak/draft-shmoo-online-meeting"/>.</t>
    </note>
  </front>
  <middle>
    <section anchor="introduction">
      <name>Introduction</name>
      <t>In 2020, the COVID-19 pandemic forced the IETF to move all its plenary meetings to online-only events.
This document records the experience gained by holding plenary meetings fully online
and the guidelines that have evolved from this experience. The aim of this document is to determine rough
consensus of these guidelines in the sense that the most participants are sufficiently satisfied
with the current organization of fully online events. These guidelines, however, document only one option
of running fully online meetings. But as the IETF has done for in-person meetings, changes to the organization
of the meetings and the meeting agenda should be experimented with in the process of establishing future meeting guidelines.</t>
    </section>
    <section anchor="some-history">
      <name>Some History</name>
      <t>When the WHO declared a world-wide pandemic in March 2020, the IETF had to quickly cancel its plenary meeting
and organize an online replacement (within less than two weeks). For this
first online-only meeting, the agenda was reduced to a set of sessions that benefitted most from cross-area
participation, like BoFs, first-time meetings of a new working groups, and dispatch sessions, as well as the
administrative plenary in order to organize the official hand-over procedures that occur at the March meeting.</t>
      <t>With such a reduced
agenda, it was possible to organize the meeting within roughly 2 sessions (about 4 hours) a day and a maximum of two
parallel tracks. This was possible as all working group meetings were moved to interims which were then distributed over
the coming six weeks. However, this was often perceived as increased load over a longer time. But at that point of
time there was not necessarily an expectation that the situation would continue as long as it did.</t>
      <t>For the following meetings in 2020, the online schedule was switched back to be similar to an in-person
meeting (1-2 hour slots and 8-9 parallel tracks as described below), however, still with a reduced total length
of initially 5 hours a day and then 6 hours with longer breaks.</t>
      <t>All fully online meetings in 2020 have followed the time zone of the planned in-person meeting
location, but starting roughly around noon. Some flexibility with the start time to be "around"
noon has been used to mitigate the worse
possible time slots, even though, given the distribution of participants it is not possible to
avoid certain hours entirely. The in-person meeting location follows the 1-1-1 rule as documented in <xref target="RFC8719"/>
to rotate between Asia, Europe,  and North America. While the exact time slot used had led to various discussions,
following roughly the 1-1-1 rule to share the pain has/seems to have rough consensus.</t>
    </section>
    <section anchor="guidelines-for-online-meeting-planning">
      <name>Guidelines for Online Meeting Planning</name>
      <section anchor="time-zone-selection">
        <name>Time Zone Selection</name>
        <t>This time selection enables to have 2 out of 3 fully online IETF plenary meetings
during the day from most participants. Basically every full online meeting is for two regions
of the three regions described in <xref target="RFC8179"/>, roughly speaking, after sunrise or after dinner.
This has the tradeoff that it maps the third region in middle of night. However, that also means
for most participants only one remote meeting per year might
require a significant change to sleep schedules.</t>
        <t>The times are also seasonally adjusted to leverage differentials in Daylight
Savings Time. These time slots are as follows, in UTC:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Times (Northern Summer)</th>
              <th align="left">Times (Northern Winter)</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">North America Night</td>
              <td align="left">0500-1100 UTC</td>
              <td align="left">0600-1200 UTC</td>
            </tr>
            <tr>
              <td align="left">Asia Night</td>
              <td align="left">1300-1900 UTC</td>
              <td align="left">1400-2000 UTC</td>
            </tr>
            <tr>
              <td align="left">Europe Night</td>
              <td align="left">2200-0400 UTC</td>
              <td align="left">2200-0400 UTC</td>
            </tr>
          </tbody>
        </table>
        <t>The intent of rotating between these three slots is to scatter meetings
throughout the course of the global day, to maximize the ease of participants
to occasionally attend regardless of their location and what time of day is
optimal for their schedule.</t>
        <section anchor="rules-for-selection">
          <name>Rules for selection</name>
          <t>The IETF will select a start time from these three choices based on the past
three meetings. The following table covers all permutations of previous
meetings held in-person in Region A, B, or C; or remotely in the nights of
one of those regions.</t>
          <table>
            <thead>
              <tr>
                <th align="left">3 meetings ago</th>
                <th align="left">2 meetings ago</th>
                <th align="left">Last Meeting</th>
                <th align="left">Online Selection</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Any</td>
                <td align="left">Any</td>
                <td align="left">In-Person A</td>
                <td align="left">A Night</td>
              </tr>
              <tr>
                <td align="left">Any</td>
                <td align="left">Online A Night</td>
                <td align="left">Online B Night</td>
                <td align="left">C Night</td>
              </tr>
              <tr>
                <td align="left">Online A Night</td>
                <td align="left">In-Person B</td>
                <td align="left">Online B Night</td>
                <td align="left">C Night</td>
              </tr>
              <tr>
                <td align="left">In-Person A</td>
                <td align="left">In-Person B</td>
                <td align="left">Online B Night</td>
                <td align="left">A Night</td>
              </tr>
              <tr>
                <td align="left">In-Person A</td>
                <td align="left">In-Person A</td>
                <td align="left">Online A Night</td>
                <td align="left">see below</td>
              </tr>
              <tr>
                <td align="left">Online A Night</td>
                <td align="left">Online B Night</td>
                <td align="left">Online C Night</td>
                <td align="left">A Night</td>
              </tr>
            </tbody>
          </table>
          <t>Basically this table follows two rules:
1) When ever a fully online meeting follows an in-person meeting, the online meeting time is used that disadvantages most the participants of the time zone where the in-person meeting was held.
2) If multiple fully online meetings follow each other, the time zone selection should be rotated based on the most recent time zones that the in-person meetings were held in.</t>
          <t>The final case occurs in the rare event that back-to-back in-person plenaries
occur in the same region. In this case, find the most recent meeting that was
neither in 'A' (if in person) nor in 'A' night (if remote). If this meeting
was in-person in region 'B', then the next meeting will be in 'B' Night. If it
was remote in 'B' Night, the next meeting will be in 'C' Night.</t>
          <t>To initialize this algorithm, IETF 112 is considered as an 'Asia Night'
remote meeting, and IETF 111 is a 'Europe Night' remote meeting.</t>
        </section>
      </section>
      <section anchor="number-of-days-and-total-hours-per-day">
        <name>Number of Days and Total Hours per Day</name>
        <t>Online meetings have converged to run over 5 days with 6-hour meeting days, roughly.
Only the administrative plenary, which concludes with multiple open mic sessions, is not necessarily time-bounded.</t>
        <t>Based on the experience so far, 6 hours of online meetings, with two 30 minutes breaks,
appears to be potentially a natural limit of what is handleable for most participants.
Respectively, the meeting survey after IETF 109 has indicated a high satisfaction with the distribution of sessions
over 5 days but only a medium satisfaction with the
overall length of each day [https://www.ietf.org/blog/ietf108-survey-results-informed-planning/].</t>
        <t>While there is a possible trade-off between shorter but more days,
a compact and potentially intense meeting was slightly preferred from the beginning by the community.
And, different than for in-person meetings,  also utilize time during the
weekend was never considered as a possible option.
So far, it was possible for all meetings to fit the requested number of sessions within 5 days, with the
respective number of parallel tracks, see Section <xref target="tracks"/>.</t>
      </section>
      <section anchor="sessionbreak-length">
        <name>Session/Break Length</name>
        <t>For fully online meetings there are typically less sessions per day, than for in-person meetings,
in order to keep the overall meeting day to at roughly 6 hours.
The reduction of the number of sessions per day led to the practice of offering chairs only two options for
session length (instead of three), in order to make session scheduling more practical.</t>
        <t>At IETF-108, based on an indicated preference of the community, 50 and 100 minute slot were used,
with only 10 minutes breaks, in order to keep the overall day length at 5 hours.
This resulted in many sessions going over time and thereby clearly indicated that only 10 minutes for breaks are not
practical.</t>
        <t>The survey after IETF-109 showed a high satisfaction with 60/120 minute session lengths and 30 minute breaks,
and a significant improvement in satisfaction over IETF-108. [https://www.ietf.org/blog/ietf-109-post-meeting-survey/]</t>
        <t>While the option to shorten the breaks was discussed during the later meetings,
a saving of in total 10-20 minutes per day might not balance the need to use the breaks for recreation or
at least some socialising.</t>
      </section>
      <section anchor="tracks">
        <name>Number of Parallel Tracks</name>
        <t>Fully online meetings are not limited in the number of parallel tracks by the physical restriction of a meeting venue aka
the number of meeting rooms. In order to reduce the number of possible conflicts, it is still
desirable to minimise the number of parallel tracks by balancing the requested sessions mostly equally over the available slots.</t>
        <t>But if the total number of requested sessions exceeds the capacity of the usual 8 parallel tracks, it
is possible for a fully online meeting to simply use more tracks. This also means, if the number of meeting days is seen as fixed, this decision
is implicitly made by the working group chairs requesting a certain number of sessions and length.</t>
        <t>As more parallel sessions usually also mean more conflicts,
chairs are encouraged to request plenary meeting time carefully but also based on realistic planning to avoid running over time.
Use of interim meetings should be consider instead where possible and sensible, as discussed in Section <xref target="full-limited"/>.</t>
      </section>
    </section>
    <section anchor="additional-considerations-and-recommendations">
      <name>Additional Considerations and Recommendations</name>
      <section anchor="full-limited">
        <name>Full vs. limited agenda (and interim meetings)</name>
        <t>The IETF-108 meeting survey asked about the structure of that meeting (full meeting) compared to that of IETF 107,
which hosted only a limited set of session followed by interims in the weeks after. The structure of IETF 108 was
preferred by 82% [https://www.ietf.org/blog/ietf-108-meeting-survey/]. While the limited agenda of IETF-107
could have been a good one-time replacement, the value of cross-participation and high active meetings weeks
has been recognised as important for continuous progress (and not only for newly initiated work).</t>
        <t>A highly concentrated meeting, in structure similar to the in-person plenary meeting, provides value for cross-participants.
Further a well defined meeting time, rather than spreading many interims over the whole
year can make deconflicting with other non-IETF meetings easier.</t>
        <t>While the time during an in-person meeting can be used very intensively, even a compact and full online
schedule does often not prevent day-job duties to occur in parallel. Therefore, allocating more time can also
make it more difficult for people to join and as such needs to be balanced with the option to distribute load
better over the entirely year by a more regular use of interim meetings.</t>
        <t>Use of (more) online interim meetings can also help to reduce scheduling conflicts during an IETF week
and allow for a more optimal schedule for the key participants. Of course these interim meetings are less likely
to attract people with casual interest but provide a good opportunity for the most active participants of a group to
have detailed technical discussions and solve recorded issues efficiently.</t>
      </section>
      <section anchor="flexibility-of-time-usage">
        <name>Flexibility of time usage</name>
        <t>This document recommends that new opportunities in the use and scheduling of online meeting time should be explored
that can help to reduce conflicts during the plenary meeting.</t>
        <t>Online meetings provide an opportunity to use more time more flexibly. While for an in-person meeting all
sessions have to be fitted into the available time people are willing to travel at once (usually roughly a week), online meetings do not have
that constraint. Therefore for the planning of online meetings, there is a trade-off between the number of parallel tracks, where more parallel tracks
mean more potential conflicts (as least of high-active participants), and the overall time in terms of hours per day or
total days used.</t>
        <t>As one example, it would be possible to keep most regular
working group sessions within the usually five main meeting days but have some of the more conflicted sessions in other dedicated time slots.
As the Hackathon for online only meetings is
usually held in the week before the online plenary meeting <xref target="I-D.ietf-shmoo-hackathon"/>, that week is already a highly active
week for many IETF participants and might provide an opportunity to schedule a few selected sessions.
If only one session at a time needs to be scheduled, it is easier to use a time slot that is well
assessable for most people in the community in various time zones. This might work especially well for
sessions that are of high interest for a large part of community, such as BoFs and
dispatch meetings, and therefore hard to schedule during the main IETF week.</t>
      </section>
      <section anchor="chances-for-inclusivity-and-lessons-learnt-on-socializing">
        <name>Chances for inclusivity and Lessons Learnt on socializing</name>
        <t>Participation at the most recent online only meetings was rather high and had a quite stable per-country distribution,
even though time zones were rotated. This indicates that online meetings support a more easy and therefore potentially
broader participation than in-person meetings where participation is often fluctuating based on the location.</t>
        <t>However, it has also been recognised that the online meeting does not provide an equivalent opportunity to socialize.
The observed slight decrease in submission of new (-00) drafts, while the overall number of draft submissions and
productivity seem to stay stable, might also be an indication of the loss of these interactions. The increase in interim
meetings potentially compensates for these missing interactions for continuous work (or may even increase
productivity there), but seems to be less adequate to spark new ideas.</t>
        <t>None of the data observed so far can, however, be interpreted as showing a significant trend. However, these factors
should be considered for the organization of future online-only meetings in replacement or addition to in-person meetings.</t>
      </section>
      <section anchor="experiments">
        <name>Experiments</name>
        <t>Similar as for in-person meetings, it is desirable to experiment with the meeting structure. Often only practical
experience can answer open questions. It is recommended to not experiment with a larger number of different
aspects at the same time, in order to be able to assess the outcome correctly. It is further recommended to announce any
such experiment in advance, so people adjust to changes and potentially provide feedback.</t>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <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>
        <reference anchor="RFC8179">
          <front>
            <title>Intellectual Property Rights in IETF Technology</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner">
              <organization/>
            </author>
            <author fullname="J. Contreras" initials="J." surname="Contreras">
              <organization/>
            </author>
            <date month="May" year="2017"/>
            <abstract>
              <t>The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process.  The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders.  This document sets out the IETF policies concerning IPR related to technology worked on within the IETF.  It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026.  This document also obsoletes RFCs 3979 and 4879.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="79"/>
          <seriesInfo name="RFC" value="8179"/>
          <seriesInfo name="DOI" value="10.17487/RFC8179"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="I-D.ietf-shmoo-hackathon">
          <front>
            <title>Running an IETF Hackathon</title>
            <author fullname="Charles Eckel">
              <organization>Cisco Systems</organization>
            </author>
            <date day="19" month="January" year="2022"/>
            <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 with
   adaptations for Hackathons that are online only.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-shmoo-hackathon-04"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAEz0HWIAA41bbY/cNpL+zl/B2+BgD9Bqz0zixJn7cGs78cbYJA5i7wW4
RXBgS+xuZvTSEaVpd5z893uqiqQodce7WaztkcS3ennqqWJNURRqcENt7/Tf
RlfZ2rXW623X62Fv9Zt+Z1r3mxlc1+puq1+NdX3Sb1r6Sn9n7eDanVdms+nt
w9386+VHVVe2psEyVW+2Q3E/2n1tj66tCr9vuq7o+Puike+L689UZQZ7p0r8
uev605127bZTyh36Oz30ox9ur6+/vL5V9/Z07PrqTr9uB9u3dii+ohWU8oNp
q/8zdddi1ZP16uDu9D991w+93fqV9qeG/vGzUmYc9l1/p7Qu8H+Nlfyd/m6t
/542yY9l/9+5/hezfNX1uzv9de9K77uWn9jGuPpON/T1ejrtX234aF12zdmC
X433Nl/K9BDG9JRX+VvX7Wo7W4M/W+/XFT78644e8uxKtV3fQB0Pls7246uX
z764+fIOz0mU6Q3+K4pCm40felNCcO/2zmvoa2xsO+hD3z3AMLzendvHoTZt
C3VpSJp2NzOWLRuL6FUHvULsvd2ZvsK/Fc3Qjs3G9itd23Y37Fc8EfZ+6LyL
83jrPf7pMRUvGqbSZmfbyqz1u731Nt+d6a3eGG8rFUbY9weI3bal1dXY01h6
+vLN/7z+qrj5Uh+wqG1cuRZBNK6qIGD1CVlU31VjSTtR6nWrb69vr1eXB5NM
Slvxy9dfv3ulh0433YPVpq61GzxkZVvTn5Ik6INg9PjrpO0DpO3XC+n3toRx
++UxdgbjKr056X1XkzDPp8/Fr0isNEUmpWFvBr032KF96OoHzLbtuwaPsfy0
EotXG9eQJobZ1hwfobLwuoZU3Hfjbq9KaMq2fvQyYKEaJwqhL6zsgDXaedgZ
WXHpIM9BVOjH7RYPsBTO4WFWfuug06Mb9jyqHPue9vFRuwtSPTOSFQR3xEuY
XjoQqwFoobsDaxxz9aPY90VbXusX46CNn3S+NyQffEIO4toCUoSrZ8Zf7k27
syw4GpRvXYm8JgVGnc3tXft9N9ZQfbQH2jqUx2IJ4oXLlnAaEoYFCm5q5/dy
imHspwknaazJ2t92jdXfOD8AbZX6aW9lsp++eQMllzVUUmmjgbV1VRwxcjJ9
LAuoKveZfwRxVHTSX0dX3kN8pYFBXXQGleEHrK2Nku4tEKa0rJ3HdEKsVNPJ
YDrY3bHTR2vv/dVav2JEcl5tXe+HmWOFNWRfQYhHKArnGdljOxzL22GGNWyb
G9varRtIvGyi7CBl33lfQBpGJZMl/QHD3L3VL7pX0DPvohignEmfmN7o1h5J
hPcsf3jMwQvmVc5jGogw7mBFhnW0AA8xMGUqeJkjjCbYThKERAAQtmc4iRJk
22LvMTW0gCALJOrFLoCA0fu7Ej6kgxOKBsNuYRA/kUH5Ec9MFJUS6a2gQpYg
UNq7TW3P1o4WFlTGyABN3E7yfWw2HZznM7jh2PsrrFGZE0vCIJ69d80oiHPs
SMrAUBgOhad79mVAz2x9/JtgdibYSfBHS0bfPYiuHdEE1+Dx3uFw/HIgY69I
uG4zkrpJXByfEItoRu/ei6mt9TcRN4a4jW47YDh8sbSOFjGEcyUMBCFI152R
6XAwUJEdaQpmEbBjEEUcOkf4s1VsMVgXe6KZ226AxZAvm97VJB92+nIQsEsA
imA5yqMjgwNAGEcfWTC0KG9pwAkrKPZVCN7brq67I50uScrlIS74oC/30H4t
G/LQKP2M+FrekzQ3tHjjgA7sR+2EeioaweOb4pbVrH3dDYJrzwqKnDO90h5B
M0qogOa32NtVhtJ+cKRhMkqTue4AAxfuQPgJBxlg8pDUUzGszK5Yx5+HxzxP
UAfIq7knCHyOBS4CfZSLhEuRWwj1rLDfOGhsJ0qEl2for+quDEABG8N5mLXt
knMY/APbbDtwQ8HibW3fu42r3XDSKerxOFlWxP8XGfgXRSM5Am0sTjp6MfcG
EtmBQ/NgOIi3anJbmoWVsuJAiW9oMyu9cw8B/ZNThOA6i9KOSQAZaYYEyjx0
DiZo+wEkJcgbAO56W5+ETpzJRkfZBOFKSL0p8D+EYHHwGKZZtvrDh0Bn//hD
4ZQ9DAFn3NjhSId/7h1Q6uux7w52pVn934P37/Xzhvg3SONPe1fbwKpAeidR
iOAoctUiwAe4Xgc6A0mUY8BmNflOVN9iwxjo90agBUJzrJkn3tqGgz8bEg/V
iTBxEF4kYfMsSv8Q+Da+/ES/oy3/L5neW1vbQFIZG+Uw8SGEDwpgp3VvNUEv
lPnp3Nw5Zi95pMoYM7kSx8AzwgY4Mx6CrYXIYjzNvPAjMhbOHBC3kQWQJCPp
Gfa9tfFhBgOs6f8gVd98AVWvkrj9AU7LUR25HpzYj23vPDGq8ACkuLV9oNP7
QNKANJVFYBTkhPk25hDe7F1fhQ3QqpIEkJBat9sPM9jHUFN7uJY1OAGd6JzA
Ji7Z26YbJhHA7pGLAi0bmlb1FuQIVgIC4natQ8TG6MAS2YZqaw8JgslE3gXQ
EY7M+/CINF3LsjfVL8iMxXBr2i8iNkSx3VqiyoBGxrKvzKnm5d+aB8a3dxyR
hCNPoCAr+OiTKxr6j3cvkTH+rr9Hgqp/54EI5uxcSL7127GBh11dePMTx128
weCC0iz568J/H3tDK+eOrL+nc2DE9dPr6+Lm5vqadkg/f04/38afMY4wIX1+
8ym9/jJ9fvMZfsbX0+cCHmnALV4W15+lAYufRS90RI7jgkek74hIkgmJmYtw
JX3ywD0y1+Ru+IRMnDxU+AfgMwWXXd1tEPDghyvGdiJKkXMR3VgiNEEjSJ4h
1BL7wGJtFXLwOuQIGO36CYIJLY/MLMgS8J7cHsyasqIGq4fkH0OiXRJyAZB+
JBPl1z4HpAAsR4rf8oLMfQpjIe2c5FPuOwfOIzl8zPoPxg9K3k/517sZjaFM
hyQGsxc+CGdrRuFKfNBDbx8Iy1UK7Htb56EaBv6jQMDzlX6xIjR5+V/0p3hx
fYoZFoMCzalS6O98ArA1ecinWSa368hklg++xZEStP8esT6BeXKVj7jG4sEF
1xHbb086/vm6LX6Q0z6nZ9HC01dhG+lFfPAiPXiZjTn7epr+xb8aO9/Jvxj4
/N8Y+PzS9hFzhU1e3u/ZQuHBywsrqynIMfkXg0uUhcIaucCdurnSnD9b4f2X
SGUalnPmea66GMDOglWF2ZGDgpKY6gGObqimwEFIXCUPRNsFTz3uQ8ZzgYYR
xSeXWKvbK/16q5uxHtyBzniRFssRgDzIozqC+dVirYmDTFULoWrV3Lt57z0y
nXaYhvspwTmvpUjiFvw3xMWtA8rpkoGQUttUb+opknEpKCT2SDiKoSs4i5nm
Fu7jLLCOM+NYraJYJ669hrWJ7mkVyvNjkSY7QFIYLQWRqtY6kg7N9+j5I/3Y
UaaiZdEr8Of0hmGF3wvgXK1JC7xezCKOnF1mgBU4y6MXj1aS4zA+2fdDloUD
CzeWF3nxSKyZJ3aDkkIIU5T89erjs7yMs0DuXcy6JBA5gt5d1+PEzUqQ/+bm
luyWiC7IbS8ZsqETp5D8SM15khRFwugbGm30ozwkP1oQKw5B+nuuJpPNg+JI
pvmOU8RvOAsh8oUXSr1ZGDLTYuwP7roT8tSPrWTtTyn8hYTx84LT2CgRepEY
6ZomlTTgcqVmFQoOWKasRyqo85zJxXA0op1lVgFy5xUAco5iQwmfpVz+Re5E
WX0YrHBr4I4x34VEzgrxklICtD69xrrtOFDI5Vx4pcwB/Lr3IcU8dIOwR2IQ
ujXD2FPaDe7BZIfJArPsFpwiYOIFUrxWP1pP1QtIpT6tZpUiP/YP9hS4u+j9
+kvm7fAwVzJiGL2H6kMp2AiupLx4mahGKapci5R4MzM3WLhyY3N5Mh5DBEIq
C1xHJYwjIvTP/TAc/N2TJ8fjce3ssF13/e7Jpu52T+inm+tnhZyl6K2Hbn0h
ly22KuJtyZOfqbwWE9DeinlPKTQlKQVlKZE8Ajx7kgttv+l6K5anDN+UUPZK
hp4riYmotzNc90z58RIsCOlAPxX8KT7unBS6N6dAO5tmhFvDrJ+31WpKIaTy
+mflbclHoAMBAwLyKX1UVEAj9smVLQ6NC0iYZCAV+LV6G+x4WXCkDZCC8suU
rZNYQTmV5SSoTXCQ6o6hIvk0OG/SeJ8sMxu1qFCtmEu8DRHtwwd5+scfgj1v
ZYknL8iF9LdSk+Ji2+XgKarnEsHpEFgFM/K0V4IrofofkbnKC8D3lC0ydQgG
nEEV1+eGlEAHZFhz4OR6WvSc6VpuJrmwm1gWkXsGcpySCXBHBkJLIXl1fUiA
CV1ElZwXqDBZ9KvHroWeqD66Fep/tZrVsxtzb+MGYrLB9UrygbC4qalyNzBm
FPC+1UQsmFlF8BCrZ3AMZ0w2vtJPr9mFKH0UJJRSEFMMolsruXXiM92coaX+
qApEZnxeiP/pJHZHkZcgQuocjQH9TtLedXRQxi52o1DB7C0ctATI9uzl8XBS
zV/sjgxGdshWhkiicpmR3s9QtyDU9Xsub/4p3H5+/QSZdZLUTKcSdFNEmQIK
V/bzIodr6GZZ7nZw/NkyfO6o0fW/wlzadAFoGFL3gJzryc8ZzAY7lMIcwanE
zCAgApdQ4MPJs5JXbfLsnDDXc81Ec7U5FKBvqHaQ5B4dhSs8HMCRs9PVV+BU
4j+jt/kGtpxk0qWBCKBX0Cj0jBDqqRbsO7rLcf4C1fkhotQ7qaN/+CQAE9Dn
IvIEa5AALsY39/llZT4EhcP+xOkPmS1ibQIMk2AGDJsuHe6Nmk8Y3/dd13jm
0MlfpJS/3EDEeQSIbY2V/CoUm/kaQIE9ud6EmyciW43zZ3OcH0L0EFU7xYnk
dURZqIL568hwLO5HjO7BuJrX49oNES+EYhdSK7aBaeEL89r3JdQulcbSIGRT
ST/A0OixmH52HmzAzt0y5F1OJcmm4U54QVbF6Di7K5uqlau46XPdMEEiCRPj
oKqfew/gC3f+tnR0EtoQLQRGR3JqQFSicczv3kIQCKLg2+t0I3AhthA6CH4Q
mPsA8FEg6TMWFbG3eB75cDISFdbldK+l2pmJfF52sixvC7iW+F4ESwyLZ09B
BB4JtwNoTs0uFEj5jiN2BySYXqt/SBEuXDJOPjflv5Hz6Bj8JCGf7jLbivsj
6Ae+BJ5wCcKb2AdtuAguLBxEP68q7pqBPb0Mq4TiF036o6WIRxe4/IxRhABC
P8BOIhaE+/HHNGB5iCtAy2zVqbpHOH3G5f09TbiJpUxgBkgGNSB0oQCfbgj5
siD8dCWsto80w3COEVKCLxCJOYvad+xhgczH3c9v8aebus1puvYNaMe3uRL5
pI44215Y7hmn7xNhxjzPbv/z34hHz85CUX7ltBB2WA/DvlAlmwnno3yNZ8AE
OjqnlW6CrCNCEqgHU4+8ZelLmLUksNo5iBuhtlnxBKdX6bKQuowQmX24vG4O
CJAUowlzwl0yXYEhYO96oqhsHhRCWP70VWuPzEioEsDtKICDK3JmXp+aP5D2
YtM9v01ZPgX+JPfsInle81k47WrqSZPT8zbnx+d089XIlw/UtUKNFJXdctdU
7vvI3w1/wxzbQ9WG26mYjSWbSYHguO9qq/gCpyT4IYIKcAwAFFsepBgGAbUF
G1ISO+K5o0upjJbkSdKlUiCvsxEaqvlmTZK7kEPzte08Ecxu3lS6vK86GxsV
+L62l2oYQL/4pdtgA4OTG8JU+Yrwy94BDwDSrijn4muCSMIDfLYMmorF4WKO
6qgBBfSW1XOw3UHC9S9gttLo4aW9pJXQyJWGwJSqKa+faNvUn8FNFQrZMXGz
pJt4xyz3axtO8mkjvd2NZFbjZWiGNgJoP6bPr2JwPYPweEwqOh4y6pIlJikS
ZRqVyw/4m3BgrphKLOfdxVuVpKnYW3kPCJ1fsb7ZxusguS052yGFPU4hqROp
PinO+LipM8qfxVoaphw8nGIiBb3gUQlvDgQBnB2lDXE9JwDJssRsQtwfOsXY
VVmEes4UbblvmTRm9+cS46jpMPQ3UmzzHgFa26nnT3juq6wJguIGGdzogZzL
PtU+hrdQNqZOq+kYbmo+JDvgDUx6OyuPhVvQvNWuhrYqxVOTJSyM4Ezz0gsy
w631eeExib2diTzkB5OL8b+kH4SaKAQ+2IouQQaMTCXSxPoQ7wq9bFB8t6C1
vEiwEbIiKvYGqgP7AdRoTjBx0MeRhKW+FTZuZO7LNKPqGGpo/SA2bAezYfkM
U857iS/VKrM62Xl57KO8fxX41ZxSyjs1cchUPcs0+Zi6pzgFw7QUxooL1n+1
So2aMeOXixrsy/YNe8c+VZ8pL0RuJykDM27CdSG9dGFi3xvQaysFr2h8eZsd
lxfCZQPDmpoT72WhK2UYFKeZAhAFn3F+cn82Ek40YxdqTqzzVIZqHRzd4LSx
+pA6BtZ0Dhr+DcSLuNpJ2SqoM+/GpFRDxY2FW5zEy3BoNo3sEmzJ2z98+O/X
xVdMvsIvEOzjktQmIlcvNBWnPxTVT6GgQSbLauR6pFSqKdhL98usCRl6lST+
z900wTZSMwCOXHhl8lqr19upGSQSU+ogEbHlwS/OVcVkV+hCRAOTNSkNoeRO
vEYZT/Mu6u7iy0GoqdRFD2JD03TPFtJEOSvZk+ZqqNSSmTplxbsAr0aIMrPL
FEkkrsEqd+IkzEunMpt0k3rukSXpqtT1Onl6KnSxBexNX83EnKErW3KKrhIt
Xu6JPvhQLC3rETyJjk2zfmvp9y48/jY9d3vHospv3FH1w5w5Z53p4VrvohXz
/ZkwSCHarTSPGep6Hrhdj/QC3y8Qu8F/T7ObipXK+u7ym08uPYar0qCeWO6L
zbsLuPUjW2bkFbCd00KY2Q2B2vSgUNQSPDs1k+BLd62Sos6+dZFPbmvi76Hd
Jb+Pih0lUE3qnnIDX+pIjr1IPdJt7yIWM3cV1prckPqmQP5ZLwuPDEq1Utru
Nt721JUr9x/E1rkzl1OPcdM48Uhq9IL/Pi6ur6/kV5Q4cqTiYYD2KczwN9kM
YtCH8PsibHTU7cc7GoD6Ygir4GTh/FmJOiu+153PfnuCnUvqoj62T05HCBxw
6mjJr4EoK0CqYIbpV3aIVdCGqRsvm3iZ6TEIPGZolN9MSYvOj8jGdRU6WmNz
4yawUBjYryO3nkIGMJ57FjEUaIh0f581zVZmMJmm+NKHWFbW/7sJkkDmMkia
SmVqqSzlZeWhBwWctevRmamw3PVenZdh6BosMJDzXySRcsD57xJ4uXiffjmB
cC8UX6THfOlCAk9fp9/Y8Eq9Demu8X96nyZhYFbtnH7pY8qRUuElptKUK5Br
8p5T0V9lF8SczLT+SMZMF89Sp2MTe82LJjotdRhyv+XSAen73CviPSGCEt2n
+Qik3EMhCXd+W0IuEA4mUUwUMQ4lcRGkBtgGpQJhU9uQ0C82B+IIbC3JnU6K
g0y2Vco2qUmmxNKwrEhyuVGSBsdfyVneoUaw2SJCU5+IVNjK+7Y7IkTvRIn/
D/SWdQc/OQAA

-->

</rfc>
