<?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-rfc version 1.6.13 (Ruby 3.1.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-shmoo-online-meeting-00" category="info" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.13.0 -->
  <front>
    <title abbrev="Organization Online Meetings">Guidelines for the Organization of Fully Online Meetings</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-shmoo-online-meeting-00"/>
    <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="July" day="11"/>
    <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="21" month="June" 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-07"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA41bbY/cNpL+zl/B2+BgD9Bqz0zixJn7cGs78cbYJA5i7wW4
RXBgS+xuZvTSEaVpd5z893uqiqQodce7WaztkcS3ennqqSpOURRqcENt7/Tf
RlfZ2rXW623X62Fv9Zt+Z1r3mxlc1+puq1+NdX3Sb1r6Sn9n7eDanVdms+nt
w9386+VHVVe2psEyVW+2Q+HssC38vum6ouMvi0a+LK6vVWUGe6dK/Lnr+tOd
du22U8od+js99KMfbq+vv7y+Vff2dOz66k6/bgfbt3YovqK5lfKDaav/M3XX
Yr2T9erg7vQ/fdcPvd36lfanhv7xs1JmHPZdf6e0LvB/jZX8nf5urf8+2n1t
j66t+LHs/DvX/2KWr7p+d6e/7l3pfdfyE9sYV9/phr5e36ev/2rDR+uya84W
/Gq8t/lSpocwpqe8yt+6blfb2Rr82Xq/rvDhX3f0kGdXqu36Bop4sHS2H1+9
fPbFzZd3eE6iTG/wX1EU2mz80JsSgnu3d15DU2Nj20Ef+u4BJuH17twyDrVp
W6hLQ9K0u5mZbNlMRK866BVi7+3O9BX+rWiGdmw2tl/p2ra7Yb/iibD3Q+dd
nMdb7/FPj6l40TCVNjvbVmat3+2tt/nuTG/1xnhbqTDCvj9A7LYtra7GnsbS
05dv/uf1V8XNl/qARW3jyrUIonFVBQGrT8ii+q4aS9qJUq9bfXt9e726PJhk
UtqKX77++t0rPXS66R6sNnWt3eAhK9ua/pQkQR8Eo8dfJ20fIG2/Xki/tyWM
2y+PsTMYV+nNSe+7moR5Pn0ufkVipSkyKQ17M+i9wQ7tQ1c/YLZt3zV4jOWn
lVi82riGNDHMtub4CJWF1zWk4r4bd3tVQlO29aOXAQvVOFEIfWFlB6zRzsPO
yIpLB3kOokI/brd4gKVwDg+z8lsHnR7dsOdR5dj3tI+P2l2Q6pmRrCC4I17C
9NKBWA1AC90dWOOYqx/Fvi/a8lq/GAdt/KTzvSH54BNyENcWkCJcPTP+cm/a
nWXB0aB860rkNSkw6mxu79rvu7GG6qM90NahPBZLEC9ctoTTkDAsUHBTO7+X
UwxjP004SWNN1v62a6z+xvkBaKvUT3srk/30zRsouayhkkobDaytq+KIkZPp
Y1lAVbnP/COIo6KT/jq68h7iKw0M6qIzqAw/YG1tlHRvgTClZe08phNipZpO
BtPB7o6dPlp776/W+hUjkvNq63o/zBwrrCH7CkI8QlE4z8ge2+FY3g4zrGHb
3NjWbt1A4mUTZQcp+877AtIwKpks6Q8Y5u6tftG9gp55F8UA5Uz6xPRGt/ZI
Irxn+cNjDl4wr3Ie00CEcQcrMqyjBXiIgSlTwcscYTTBdpIgJAKAsD3DSZQg
2xZ7j6mhhbYqgES92AUQMHp/V8KHdHBC0WDYLQziJzIoP+KZiaJSIr0VVMgS
BEp7t6nt2drRwoLKGBmgidtJvo/NpoPzfAY3HHt/hTUqc2JJGMSz964ZBXGO
HUkZGArDofB0z74M6Jmtj38TzM4EOwn+aMnouwfRtSOa4Bo83jscjl8OZOwV
CddtRlI3iYvjE2IRzejdezG1tf4m4sYQt9FtBwyHL5bW0SKGcK6EgSAE6boz
Mh0OBiqyI03BLAJ2DKKIQ+cIf7aKLQbrYk80c9sNsBjyZdO7muTDTl8OAnYJ
QBEsR3l0ZHAACOPoIwuGFuUtDThhBcW+CsF729V1d6TTJUm5PMQFH/TlHtqv
ZUMeGqWfEV/Le5LmhhZvHNCB/aidUE9FI3h8U9yymrWvu0Fw7VlBkXOmV9oj
aEYJFdD8Fnu7ylDaD440TEZpMtcdYODCHQg/4SADTB6SeiqGldkV6/jz8Jjn
CeoAbTX3BIHPscBFoI9ykXApcguhnhX2GweN7USJ8PIM/VXdlQEoYGM4D7O2
XXIOg39gm20HbihYvK3te7dxtRtOOkU9HifLivj/IgP/omgkR6CNxUlHL+be
QCI7cGgeDAfxVk1uS7OwUlYcKPENbWald+4hoH9yihBcZ1HaMQkgI82QQJmH
zsEEbT+ApAR5A8Bdb+uT0Ikz2egomyBcCak3Bf6HECwOHsM0y1Z/+BDo7B9/
KJyyhyHgjBs7HOnwz70DSn099t3BrjSr/3vw/r1+3hD/Bmn8ae9qG1gVSO8k
ChEcRa5aBPgA1+tAZyCJcgzYrCbfiepbbBgD/d4ItEBojjXzxFvbcPBnQ+Kh
OhEmDsKL9GueP+kfAt/Gl5/od7Tl/yXTe2trG0gqY6McJj6E8EEB7LTurSbo
hTI/nZs7x+wlj1QZYyZX4hh4RtgAZ8ZDsLUQWYynmRd+RMbCmQPiNrIAkmQk
PcO+tzY+zGCANf0fpOqbL6DqVRK3P8BpOaoj14MT+7HtnSdGFR6AFLe2D3R6
H0gakKayCIyCnDDfxhzCm73rq7ABWlWSABJS63b7YQb7GGpqD9eyBiegE50T
2MQle9t0wyQC2D1yUaBlQ9Oq3oIcwUpAQNyudYjYGB1YIttQbe0hQTCZyLsA
OsKReR8ekaZrWfam+gWZsRhuTftFxIYotltLVBnQyFj2lTnVvPxb88D49o4j
knDkCRRkBR99ckVD//HuJTLG3/X3SFD17zwQwZydC8m3fjs28LCrC29+4riL
NxhcUJolf13472NvaOXckfX3dA6MuH56fV3c3Fxf0w7p58/p59v4M8YRJqTP
bz6l11+mz28+w8/4evpcwCMNuMXL4vqzNGDxs+iFjshxXPCI9B0RSTIhMXMR
rqRPHrhH5prcDZ+QiZOHCv8AfKbgsqu7DQIe/HDF2E5EKXIuohtLhCZoBMkz
hFpiH1isrUIOXoccAaNdP0EwoeWRmQVZAt6T24NZU1bUYPWQ/GNItEtCLgDS
j2Si/NrngBSA5UjxW16QuU9hLKSdk3zKfefAeSSHj1n/wfhByfsp/3o3ozGU
6ZDEYPbCB+FszShciQ966O0DYblKgX1v6zxUw8B/FAh4vtIvVoQmL/+L/hQv
rk8xw2JQoDlVCv2dTwC2Jg/5NMvkdh2ZzPLBtzhSgvbfI9YnME+u8hHXWDy4
4Dpi++1Jxz9ft8UPctrn9CxaePoqbCO9iA9epAcvszFnX0/Tv/hXY+c7+RcD
n/8bA59f2j5irrDJy/s9Wyg8eHlhZTUFOSb/YnCJslBYIxe4UzdXmvNnK7z/
EqlMw3LOPM9VFwPYWbCqMDtyUFASUz3A0Q3VFDgIiavkgWi74KnHfch4LtAw
ovjkEmt1e6Vfb3Uz1oM70Bkv0mI5ApAHeVRHML9arDVxkKlqIVStmns3771H
ptMO03A/JTjntRRJ3IL/hri4dUA5XTIQUmqb6k09RTIuBYXEHglHMXQFZzHT
3MJ9nAXWcWYcq1UU68S117A20T2tQnl+LNJkB0gKo6UgUtVaR9Kh+R49f6Qf
O8pUtCx6Bf6c3jCs8HsBnKs1aYHXi1nEkbPLDLACZ3n04tFKchzGJ/t+yLJw
YOHG8iIvHok188RuUFIIYYqSv159fJaXcRbIvYtZlwQiR9C763qcuFkJ8t/c
3JLdEtEFue0lQzZ04hSSH6k5T5KiSBh9Q6ONfpSH5EcLYsUhSH/P1WSyeVAc
yTTfcYr4DWchRL7wQqk3C0NmWoz9wV13Qp76sZWs/SmFv5Awfl5wGhslQi8S
I13TpJIGXK7UrELBAcuU9UgFdZ4zuRiORrSzzCpA7rwCQM5RbCjhs5TLv8id
KKsPgxVuDdwx5ruQyFkhXlJKgNan11i3HQcKuZwLr5Q5gF/3PqSYh24Q9kgM
QrdmGHtKu8E9mOwwWWCW3YJTBEy8QIrX6kfrqXoBqdSn1axS5Mf+wZ4Cdxe9
X3/JvB0e5kpGDKP3UH0oBRvBlZQXLxPVKEWVa5ESb2bmBgtXbmwuT8ZjiEBI
ZYHrqIRxRIT+uR+Gg7978uR4PK6pf7Xu+t2TTd3tntBPN9fPCjlL0VsP3fpC
mi22KmK35MnPVF6LCWhvxbynFJqSlIKylEgeAZ49yYW233S9FctThjsllL2S
oedKYiLq7QzXPVN+vAQLQjrQTwV/io87J4XuzSnQzqYZ4dYw6+dttZpSCKm8
/ll5W/IR6EDAgIB8Sh8VFdCIfXJli0PjAhImGUgFfq3eBjteFhxpA6SgvJmy
dRIrKKeynAS1CQ5S3TFUJJ8G500a75NlZqMWFaoVc4m3IaJ9+CBP//hDsOet
LPHkBbmQ/lZqUlxsuxw8RfVcIjgdAqtgRp72SnAlVP8jMld5AfieskWmDsGA
M6ji+tyQEuiADGsOnFxPi54zteVmkgu7iWUR6TOQ45RMgDsyEFoKyavrQwJM
6CKq5LxAhcmiXz12LfRE9dGtUP+r1aye3Zh7GzcQkw2uV5IPhMVNTZW7gTGj
gPetJmLBzCqCh1g9g2M4Y7LxlX56zS5E6aMgoZSCmGIQ3VpJ14nPdHOGlvqj
KhCZ8Xkh/qeT2B1FXoIIqXM0BvQ7SXvX0UEZu9iNQgWzt3DQEiDbs5fHw0k1
f7E7MhjZIVsZIonKZUZ6P0PdglDX77m8+adw+/n1E2TWSVIznUrQTRFlCihc
2c+LHK6hzrL0dnD82TJ87qjR9b/CXNp0AWgY0u0BOdeTnzOYDXYohTmCU4mZ
QUAELqHAh5NnJa/a5Nk5Ya7nmonmanMoQN9Q7SDJPToKV3g4gCNnp9ZX4FTi
P6O3+Qa2nGRS00AE0CtoFHpGCPVUC/Yd9XKcv0B1fogo9U7q6B8+CcAE9LmI
PMEaJICL8c19flmZD0HhsD9x+kNmi1ibAMMkmAHDpqbDvVHzCeP7vusazxw6
+YuU8pcbiDiPALGtsZJfhWIztwEU2JPrTeg8EdlqnD+b4/wQooeo2ilOJK8j
ykIVzF9HhmNxP2J0D8bVvB7Xboh4IRS7kFqxDUwLX5jXvi+hdqk0lgYhm0r6
AYZGj8X0s/NgA3buliHvcipJNg13wguyKkbHWa9sqlau4qbPdcMEiSRMjIOq
fu49gC/0/G3p6CS0IVoIjI7k1ICoROOY995CEAii4O516ghciC2EDoIfBOY+
AHwUSPqMRUXsLZ5HPpyMRIV1Od1rqXZmIp+XnSzL2wKuJb4XwRLD4tlTEIFH
wu0AmtNlFwqk3OOItwMSTK/VP6QIF5qMk89N+W/kPDoGP0nIp15mW/H9CPqB
m8ATLkF4E/ugDRfBhYWD6OdVxbdmYE8vwyqh+EWT/mgp4lEDl58xihBA6AfY
ScSC0B9/TAOWh7gCtMxWnap7hNNnXN7f04SbWMoEZoBk0AWELhTgU4eQmwXh
pythtX2kGYZzjJASfIFIzFnUvmMPC2Q+7n7exZ86dZvT1PYNaMfdXIl8Ukec
bS8s94zT94kwY55nt//5b8SjZ2ehKG85LYQd1sOwL1TJZsL5KLfxDJhAR+e0
cpsguxEhCdSDqUfestxLmF1JYLVzEDdCbbPiCU6vUrOQbhkhMvvQvG4OCJAU
owlzQi+ZWmAI2LueKCqbB4UQlj991dojMxKqBPB1FMDBFTkzr0+XP5D2YtM9
v01ZPgX+JPeskTyv+SycdjXdSZPT8zbnx+d089XIzQe6tUIXKSq75VtTue8j
fzf8DXNsD1Ubvk7FbCzZTAoEx31XW8UNnJLghwgqwDEAULzyIMUwCKgt2JCS
2BHPHTWlMlqSJ0mXSoG8zkZoqObOmiR3IYfmtu08Ecw6byo176vOxosK3K/t
pRoG0C9+6TbYwOCkQ5gqXxF+2TvgAUDaFeVc3CaIJDzAZ8ugqVgcLuaoji6g
gN6yeg62O0i4/gXMVi56eLle0kpo5EpDYErVlNdPtG26n8GXKhSyY+JmSTex
xyz9tQ0n+bSR3u5GMqvxMjRDGwG0H9PnVzG4nkF4PCYVHQ8ZdckSkxSJMo1K
8wP+JhyYK6YSy3l3sauSNBXvVt4DQuct1jfb2A6SbsnZDinscQpJN5Hqk+KM
jy91RvmzWEvDlIOHU0ykoBc8KuHNgSCAs6O0Ia7nBCBZlphNiPtDpxi7KotQ
z5miLfctk8asfy4xji4dhvuNFNu8R4DWdrrzJzz3VXYJguIGGdzogZzLe6p9
DG+hbEw3raZjuOnyIdkBb2DS21l5LHRB86t2NbRVKZ6aLGFhBGeal7sgM9xa
nxcek9jbmchDfjC5GP9L7oPQJQqBD7aiS5ABI1OJNLE+xLvCXTYovlvQWl4k
2AhZERV7A9WB/QBqNCeYOOjjSMLSvRU2bmTuyzSj6hhqaP0gNmwHs2H5DFPO
7xJfqlVmdbLz8thHef8q8Ks5pZR3auKQqXqWafIx3Z7iFAzTUhgrLlj/1Spd
1IwZvzRqsC/bN+wd+1R9prwQuZ2kDMy4CdeF9FLDxL43oNdWCl7R+PJrdlxe
CM0GhjU1J97LQlfKMChOMwUgCj7j/OT+bCScaMZbqDmxzlMZqnVwdIPTxupD
ujGwpnPQ8G8gXsTVTspWQZ35bUxKNVTcWOjiJF6GQ7NpZE2wJW//8OG/Xxdf
rbNfINjHJemaiLReaCpOfyiqn0JBg0yW1cj1SKlUU7CX2y+zS8jQqyTxf+6m
CbaRmgFwpOGVyWutXm+nyyCRmNINEhFbHvziXFVMdoUuRDQw2SWlIZTcidco
42neRd1dfDkINZW66EG80DT12UKaKGcle9JcDZVaMlOnrHgX4NUIUWZ2mSKJ
xDVY5U6chHnpVGaT26Se78iSdFW69Tp5eip0sQXsTV/NxJyhK1tyiq4SLV7u
iT74UCwt6xE8iY5Ns35r6fcuPP42Pd/2jkWV3/hG1Q9z5pzdTA9tvYtWzP0z
YZBCtFu5PGbo1vPA1/VIL/D9ArEb/Pc061SsVHbvLu98cukxtEqDemK5L17e
XcCtH9kyI6+A7ZwWwsw6BGrTg0LRleDZqZkEX+q1Soo6+9ZFPrmtib+H6y55
PyreKIFq0u0pN3BTR3LsReqRur2LWMzcVVhrckO6NwXyz3pZeGRQqpXSdrfx
tqdbudL/ILbON3M59Rg3jROPpIte8N/HxfX1lfxyEkeOVDwM0D6FGf4mm0EM
+hB+X4SNjm778Y4GoL4Ywio4WTh/VqLOiu9157PfnmDnkrqoj9cnpyMEDjjd
aMnbQJQVIFUww/QrO8QqaMN0Gy+beJnpMQg8ZmiU30xJi86PyMZ1FW60xsuN
m8BCYWC/jnz1FDKA8dyziKFAQ6T7++zSbGUGk2mKmz7EsrL7v5sgCWQug6Sp
VKaWylJeVh56UMDZdT06MxWWu96r8zIMtcECAzn/RRIpB5z/LoGXxvv0ywmE
e6H4InfMly4k8PR1+o0Nr9TbkO4a/6f9NAkDs2rn9EsfU46UCi8xlaZcgVyT
95yK/iprEHMy0/ojGTM1nqVOxyb2mhdNdFrqMOR+y6UD0ve5V8Q+IYIS9dN8
BFK+QyEJd94tIRcIB5MoJooYh5K4CFIDbINSgbCpbUjoF5sDcQS2luROJ8VB
JtsqZZt0SabE0rCsSHL5oiQNjr+Ss+yhRrDZIkLTPRGpsJX3bXdEiN6JEv8f
iIjShDk5AAA=

-->

</rfc>
