<?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.17 (Ruby 3.1.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-shmoo-online-meeting-03" category="info" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.15.2 -->
  <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-03"/>
    <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="November" day="22"/>
    <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 with online
meetings 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 proposes guidelines based on this experience.
In general, participant surveys indicate satisfaction with the organization of
these meetings.</t>
      <t>Although these guidelines reflect lessons learned in 2020 and 2021, the IETF is
encouraged to continue to experiment with the format and agenda of fully online
meetings, using this document as a baseline.</t>
      <t>Hybrid meetings (meaning meetings that have higher remote participation than
onsite participation) are out of scope. However, some of the experience gained
from fully online meetings might also provide input for decisions regarding the
organization of hybrid meetings.</t>
    </section>
    <section anchor="some-history">
      <name>Some History</name>
      <t>When the WHO declared a world-wide pandemic in March 2020, the IETF canceled its
plenary meeting and organized an online replacement in 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
new working groups, and dispatch sessions. It also included the administrative
plenary to preserve the official hand-over procedures that occur at the March
meeting, as described in <xref target="RFC8713"/>.</t>
      <t>With a reduced agenda, the meeting format was 2 sessions (about 4 hours) a day
and a maximum of two parallel tracks. Other working group meetings were
scheduled as interims over the following six weeks. The IESG published a
purely advisory recommended schedule <xref target="INTERIM-SCHEDULE"/> to reduce conflicts
among those interims.</t>
      <t>Some participants said <xref target="_107-FEEDBACK"/> the period of intensive interims had a
greater impact on their calendar than a single plenary meeting week, and reduced
participation. Those interims tended to occur at times convenient for the bulk
of participants, which was convenient for most but could exclude those in less
common time zones.</t>
      <t>For the remainder of 2020 and 2021, the online schedule was switched back to be
similar to an in-person meeting (1-2 hour slots and 8-9 parallel tracks).
However, each day was limited to 5-6 hours in recognition that remote
participation is more tiring.</t>
      <t>All fully online meetings followed the time zone of the planned in-person
meeting location. As a six-hour agenda has some flexibility regarding the start
time while still fitting within a traditional 8-hour in-person agenda, the start
time was approximately noon, with adjustments of an hour or so to mitigate the
impact of early morning hours in time zones with many participants. As selection
of in-person meeting sites was consistent with the 1-1-1 guideline as documented
in <xref target="RFC8719"/>, this approach was intended to share the burden across all common
geographies roughly equally.</t>
    </section>
    <section anchor="guidelines-for-online-meeting-planning">
      <name>Guidelines for Online Meeting Planning</name>
      <section anchor="time-zone-selection">
        <name>Time Zone Selection</name>
        <t>The following algorithm was not used in 2020 or 2021, but enables most
participants to avoid late-night sessions in 2 out of every 3 fully online IETF
plenary meetings. Basically, every full online meeting is for two regions of the
three regions described in <xref target="RFC8179"/>, with one being roughly after sunrise
and the other after dinner. This has the tradeoff that the third region is in
the middle of night.</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="guidelines-for-selection">
          <name>Guidelines for selection</name>
          <t>The IETF SHOULD 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>This table follows two basic guidelines:
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 should be in 'B' Night. If it
was remote in 'B' Night, the next meeting should be in 'C' Night.</t>
        </section>
      </section>
      <section anchor="number-of-days-and-total-hours-per-day">
        <name>Number of Days and Total Hours per Day</name>
        <t>By 2021, online meetings were consistently over 5 days with roughly 6-hour
meeting days. The administrative plenary, which concludes with multiple open mic
sessions, would sometimes exceed this limit.</t>
        <t>Six hours of online meetings, with two 30-minute breaks, was a compromise
between the physical limits of attending an online meeting in an inconvenient
time zone, and the demand for many sessions with a manageable number of
conflicts. The IETF 109 feedback <xref target="_109-SURVEY"/> indicated broad satisfaction
with a 5-day meeting but only medium satisfaction with the overall length of
each day.</t>
        <t>The IETF did not seriously consider extending sessions into the weekend before
or after the main meeting week, although the Hackathon occupied the entire week
before (see <xref target="RFC9311"/>).</t>
      </section>
      <section anchor="sessionbreak-length">
        <name>Session/Break Length</name>
        <t>For fully online meetings there are typically fewer sessions per day than for
in-person meetings, to keep the overall meeting day to at roughly 6 hours.
With fewer sessions, chairs were offered only two options for session length
(instead of three).</t>
        <t>IETF-108, based on an indicated preference of the community, scheduled 50- and
100-minute slots, with 10-minute breaks, in order to keep the overall day length
at 5 hours. This resulted in many sessions going over time, which indicated that
10 minutes for breaks is not practical.</t>
        <t>The survey after IETF-109 <xref target="_109-SURVEY"/> showed high satisfaction with 60/120
minute session lengths and 30 minute breaks, and a significant improvement in
satisfaction over IETF-108.</t>
        <t>The longer breaks, while extending the day, provided adequate time for "hallway"
conversations using online tools, exercise, and meals.</t>
      </section>
      <section anchor="tracks">
        <name>Number of Parallel Tracks</name>
        <t>In-person meetings are limited in the number of parallel tracks by the number of
meeting rooms, but online meetings are not. However, more parallel tracks
increases the number of possible conflicts.</t>
        <t>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. If the number and length 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>IETF-111 used 9 parallel tracks for some of the sessions, and experienced
slightly more conflicts in the formal scheduling process, though there was no
statistically signficant increase in dissatisfaction about conflicts in the
survey <xref target="_111-SURVEY"/>.</t>
        <t>The IESG encouraged working group chairs to limit their session requests and use
interim meetings aggressively for focused work.</t>
      </section>
    </section>
    <section anchor="additional-considerations-and-recommendations">
      <name>Additional Considerations and Recommendations</name>
      <section anchor="full-limited">
        <name>Full vs. limited agenda (and interim meetings)</name>
        <t>The IETF-108 meeting survey <xref target="_108-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%. Respondents valued cross-participation and an
intensive meeting week for maintaining project momentum.</t>
        <t>Furthermore, a well defined meeting time, rather than spreading many interims
over the whole year, can make deconflicting with other non-IETF meetings easier.</t>
        <t>However, interim meetings can also help to reduce scheduling conflicts during an
IETF week and allow for a more optimal time slot for the key participants. While
interim meetings are less likely to attract people with casual interest, they
provide a good opportunity for the most active participants of a group to have
detailed technical discussions and solve recorded issues efficiently.</t>
      </section>
      <section anchor="flexibility-of-time-usage">
        <name>Flexibility of time usage</name>
        <t>This document RECOMMENDS further experiments with reducing conflicts by
leveraging the increased flexibility of the online format.</t>
        <t>An in-person meeting must fit all sessions into an acceptable length for
international travel (usually roughly a week), but online meetings do not have
that constraint.</t>
        <t>Therefore, it would be possible to keep most regular working group sessions
within the usual 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="RFC9311"/>, that week is already a highly active week for many IETF
participants and might provide an opportunity to schedule a few selected
sessions.</t>
        <t>This might work especially well for sessions that are of high interest for a
large part of community, such as BoFs and dispatch meetings, and therefore hard
to schedule during the main IETF week.</t>
        <t>At IETF 112, the IESG ran an experiment where the adminstrative plenary was
scheduled on the Wednesday before the official session week. The experiment
report <xref target="_112-EXPERIMENT"/> found that it led to a reduction in scheduling
conflicts but also a slight drop in plenary attendance, partly due to
insufficient awareness.</t>
      </section>
      <section anchor="inclusivity-and-socializing">
        <name>Inclusivity and Socializing</name>
        <t>Participation at the online only meetings in 2021 was high and had a stable
per-country distribution, even though time zones were rotated. This indicates
that online meetings support a more consistent geographic distribution of
participants than in-person meetings, where participation often fluctuates based
on the location.</t>
        <t>However, online meetings do not provide an equivalent opportunity to socialize.
Despite significant investment in tools to foster hallway conversations, many
did not use those tools, whether due to ignorance of them, dislike of the tools,
or a preference for the amusements of home (including sleep) over hallway
interactions.</t>
        <t>There was a slight decrease in submission of new (-00) drafts during 2020 and
2021, although the overall number of draft submissions remained stable, which
might result from the loss of these interactions. Informal conversations might
be important to inspire new work.</t>
      </section>
      <section anchor="experiments">
        <name>Experiments</name>
        <t>This document RECOMMENDS further experiments with the meeting structure. Often,
only practical experience can answer open questions. A given meeting SHOULD only
experiment with one major change at a time in order to be able to assess the
Furthermore, the IESG SHOULD announce any such experiment in advance, so people
can adjust to changes and potentially provide feedback.</t>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thanks to Brian Carpenter, Lars Eggert, Toreless Eckert, Charles Eckel, Jason
Livingood, and Sanjeev Gupta for their review and many from more for their
input and suggestions on the time zone discussion!</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <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="_107-FEEDBACK" target="https://mailarchive.ietf.org/arch/msg/ietf-announce/mIq1inolQXzsCaMcyBVscphHucw/">
          <front>
            <title>IETF 107 Virtual Meeting Survey Report</title>
            <author initials="J." surname="Daley">
              <organization/>
            </author>
            <date year="2020" month="April" day="17"/>
          </front>
        </reference>
        <reference anchor="_108-SURVEY" target="https://www.ietf.org/blog/ietf-108-meeting-survey">
          <front>
            <title>IETF 108 Meeting Survey</title>
            <author initials="J." surname="Daley">
              <organization/>
            </author>
            <date year="2020" month="August" day="13"/>
          </front>
        </reference>
        <reference anchor="_109-SURVEY" target="https://www.ietf.org/blog/ietf-109-post-meeting-survey/">
          <front>
            <title>IETF 109 Post-Meeting Survey</title>
            <author initials="J." surname="Daley">
              <organization/>
            </author>
            <date year="2020" month="December" day="07"/>
          </front>
        </reference>
        <reference anchor="_111-SURVEY" target="https://www.ietf.org/blog/ietf-111-post-meeting-survey/">
          <front>
            <title>IETF 111 Post-Meeting Survey</title>
            <author initials="J." surname="Daley">
              <organization/>
            </author>
            <date year="2021" month="August" day="23"/>
          </front>
        </reference>
        <reference anchor="_112-EXPERIMENT" target="https://www.ietf.org/blog/ietf112-plenary-experiment-evaluation/">
          <front>
            <title>IETF 112 Plenary Experiment Evaluation</title>
            <author initials="I. E. S." surname="Group" fullname="Internet Engineering Steering Group">
              <organization/>
            </author>
            <date year="2022" month="February" day="04"/>
          </front>
        </reference>
        <reference anchor="INTERIM-SCHEDULE" target="https://mailarchive.ietf.org/arch/msg/wgchairs/l382SqKVVHoTzFw9kIYl2boM6_c/">
          <front>
            <title>Post-IETF-107 Recommended Virtual Interim Schedule</title>
            <author initials="A." surname="Cooper">
              <organization/>
            </author>
            <date year="2020" month="March" day="13"/>
          </front>
        </reference>
        <reference anchor="RFC8713">
          <front>
            <title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title>
            <author fullname="M. Kucherawy" initials="M." role="editor" surname="Kucherawy">
              <organization/>
            </author>
            <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden">
              <organization/>
            </author>
            <author fullname="J. Livingood" initials="J." role="editor" surname="Livingood">
              <organization/>
            </author>
            <date month="February" year="2020"/>
            <abstract>
              <t>The process by which the members of the IAB and IESG, some Trustees of the IETF Trust, and some Directors of the IETF Administration LLC (IETF LLC) are selected, confirmed, and recalled is specified in this document. This document is based on RFC 7437.  Only those updates required to reflect the changes introduced by IETF Administrative Support Activity (IASA) 2.0 have been included. Any other changes will be addressed in future documents.</t>
              <t>This document obsoletes RFC 7437 and RFC 8318.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="10"/>
          <seriesInfo name="RFC" value="8713"/>
          <seriesInfo name="DOI" value="10.17487/RFC8713"/>
        </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>
        <reference anchor="RFC9311">
          <front>
            <title>Running an IETF Hackathon</title>
            <author fullname="C. Eckel" initials="C." surname="Eckel">
              <organization/>
            </author>
            <date month="September" year="2022"/>
            <abstract>
              <t>IETF Hackathons 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="RFC" value="9311"/>
          <seriesInfo name="DOI" value="10.17487/RFC9311"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61ba3PbRpb93r+iJ6mtWFUELcpxYms/7MiyHGvi11qKM7Nb
W1Mg0CQ7AgEGDYhmHP33Oed2Nx4U7ezMbmZiS0Cj+z7PfXWSJFGNbQpzqn9o
bW4KWxqnF1Wtm5XRb+tlWtrf0sZWpa4W+kVbFDv9tuQq/dqYxpZLp9L5vDa3
p+PV+4vyKivTNY7J63TRJNY0i8St1lWVVLIyWfuVyfEjlaeNOVUZ/lxW9e5U
23JRKWU39alu6tY1J8fHT49P1I3Zbas6P9WXZWPq0jTJc+6tlGvSMv97WlQl
ztsZpzb2VP+3q+qmNgs30W635g//o1TaNquqPlVaJ/hX4yR3ql9P9Y+tWRVm
a8tcHnvKX9v6l3T/VVUvT/VFbTPnqlKemHVqi1O95urpTbf6zyYsmmbV+t6B
z9sbMzwqrSGM/qmc8kNVLQszOkOWTVfTHAv/vORD2V2psqrXUMQt5Kgovv43
rWfH3ycvLi6ePzs7//FUtgsW8NXlxfULvtYfbN20aRHVp6/a+tbs9HuzgRC/
km960fGfxHPyF3CSFmYnT0WN+uT45Dg5/jaZfe+PSuulaXDWqmk27vThQxKd
1tkK1E1pFVPw+pAPHq7d8qHYSVqWVVtm5uH68teZLaviP//6mztPX2e7Zx9c
tlm9bLPtw688a0+Sq5/ef7j420HGnuwx9K9w8iSZPTrMyXa77TmYF1WgnjRF
43bhWCH16ZdIfarfVa5J/s/0zk6S489I/rP0Pk02PHtMdBDwbPYFqmez/xeq
Z5TyyT8pZRD2BapPkou/vrt4f/n64s31QcpP9LvClGm90xcfN3DVtSkbfXGb
Fq3g2WEevLNG+NEX5RJIho/JehN++KGu2s2YP6gE///2n+GPHGw8gYnpCExM
R6Bn9PLNNZlMrs5fXjz/6dXFmFXRDflN6OPvDaACu+Qm7/xdWLFrfZWtTN4W
5guq02dTfV5VIOWeizz6rIt82dm3y2yV2to9LB49Obn69ccPH15W17+92D69
ufxbcTKvXn/394x8qiRJdDp3TZ1mgPvrlXUa8aUVnW3q6haBzOnl/Xi2KQAl
VAriAzF1FNwWDG7KRyMdrAjBojbLtM75EXco2/Xc1BMNVSyb1UQ2ghhheTbu
44xz+NFpxAN+ErbS6RKyTqf6emWcGVKX1kbPUwc1YAN+4RVsgHh6a5uV9jSp
SJPO2zrSc/72w+XzZPZUb0CJWdts6qWztnmOWKG+pkrrKm8zkqfUZSk6mhz+
mILKQAdfil80lV5Xt0anRaFt43QwwU48CgtC/MZfO21uoQJHHocqqWFpde72
eVum+C7X851eVQUlrPa39zoJJ4isoV3Ieqzdgexwan/AlNxC6KZOiwl4RKzM
LFhttMcGB0POLdMM7WAFbpGKkLzMSeuehVCbrjcNSPqsgGO0S1k91inyi8Jk
DeyEId/h77Qms9bLX3gh0k16WVunQHXV1jCUnJLPqhIHtYY/9z7fk+ejumzl
bauz4n2LmejWeYsZqiWF6YnwuBbcvNzNa5v3wn+wNql4S/ekWeG8VQqDWNnl
ytRgc11BfJ1sRVJYVcKP4BF7b47E1Ku2ETfJgB1T/bLawmjgUa5aGz4/aCRq
UVfrsTV0RK1BCpgpXBV9H1Le4BB6fW4y671x5Mdq3/lXY96n9JwrUvTSugZJ
qFI/r4z3zp9fvuW2wDGoKdVIQYs82fLYzo2g5ddEtYGviYqzFCwVNIPG7Rv7
EJO4cRkZrQ1gKzOiMmxMixIR62Zb6a0xN/C3F1WtRLkLwGczcsmwvaci2Mk2
pTwACt7QUmBWM4IuKlrN4ToL2zRYtEbk0KKDrK6cS8B7OtYtINHeGP2segFr
EyqSBvbaqwn+U5otxXVDbpcMi84DaG4dNoG44vlTfRk0asusaPMASWm+tqUl
7DOX7QTYUPHwP/i0d9vFAmQhmkFIeQL4qmkY4LXFKm/DVZa1tcYPXC+qUp2c
IBuEj6y2c++vnz79x/sX50++nz26u4Nd/Ez3SzvxeYl66UZNBseklE96mT5I
5zT9b4F2be3gC4iZOyXei0T+o123a7F/aBWSBeKaQjPCUb9vG3rbSHa9ZLem
NsqFiJ2TfuvDOIRO5j1WFEW15cfOfoxWcy12efWD3rTzwroVP1YbSAlmk+a3
FhXTTsA7pgnxEMhkP9O4u6MevFSIXIvCZjDydF2JxwGzO6ogRHGtASI7IDDc
79OnYW3CLRm08VGVUzTcALBy228FFZPmJcwRD7Rdb4DhIYzaGv5WUDu19xeY
OQRQmP0oJuLwlhi0qkamTUEN6deNlwZjX2dHsHVHvhEALT01phzztrhRoH3I
7ERvVxbmTgPZ+0QcbQ4zQSAocgChmH8nQPF+RYWQR/rXbyhyKdEX4byapSHI
qymwA6EmgEqnSdLgEFL4O4JBdkO25rAnu2aqJvBQ4uQEakAk62T2YJaciCVr
V1TQH095kjzdN92jqeoQ3qTgGTYvZxbYv/FCfJx8532CDNLclqWNgaQJIWas
EcRKSAqxpLHMhCQSF58JD97yA4J0IouRRjJC8fPAYMQBXVRZ0P6ZE9P5mAi7
AUJXlButGHH+o53bwja7vVzRIf1tlBwJfRd8YEkmIFWsDkBiaZWQVC4MA7Ke
+EN6eQ/xZbghg/cGsAbcgOmD77IiCEtykOa/tK5hwCDsUn+yKSwEiMqUDqct
mfYwEkafWUA/NeNFVUvQ7zTSm5nffZ2Wu5E5i4SQRRifY4qj7psLkwEXDd4B
w0eZzCzB//r0SSA4ZClwxiEGP727m/g0RrhPgxcJMgSfdCtmGd736hxBO5WY
JTms9xy1NNWyTjcry0yNCRxT119RABU7ifx7rbBxLwuFoq8isPJrfU3p/Bct
6qqTgLoeIW5aLKsarK6F1LJqkI0NUkEc4N2Tbg9gmsPHBQfUCCDpiLcVQLKA
5pJSkp4utnCvmFjR2Xb60dgdmH7cS6+n+lnqkABj3SR8xo/2XIjOJmi2Jb4v
fWkj3oOUozame7gXNf9Ejc2+F42FMgYqMdwxyjxdELVdW9bWGQmFAlES7Pw7
OBPy91BQ0OfEi+EwBlHeA4Q8Wdk6D4SQXhtKL6mCSK3Ia+o147GaRiIphjOp
o+9J0KPjeDMqKBB4H0hYLBBhkYtjOVl7nu4Kbqeu0luBGNpArOvEWwIk1mLJ
3hAA+vj0p+vzU6V+129SrPpdPkRi8KaqyXKpr1pE2vrowJufJfjgDT5OWOD5
vw7886U3PJk76rM1u5GpfiNm9Ls+fnx8nMxmx8ekkL9/x99P4u/47szZfvns
EV8/7ZbPvsXvWN0vv2hRqJnugxO8TI6/7T7Y+93rRZxYTLiumlRMb24aBOcy
1Ffe3LxwrXiEA0bTTPp6dCW2RVegAbCcch3YL4tqDoxFCJoIDDLpQrLtS47U
rxv6nPIRPnU22kdDmAkwL4m43xmpRgwXEgi3q5AS8D0jHmq7aoMHOD0kBvgk
xmBCztf3QMeN4UTqh6uXb3969Ty8YlBiQPAHSXI+FFO2qmw2ro6ZcgFW/Pse
BMZo1RCAIDhYv8dMIPm6bYQ54Re59q2tWtf3I1amGERQ2vl774lnE/1sQoA7
/3f+6UM55Gg9NeKUUhl0EZlpTsCTKR3lUR/I02VFy9l/8AosddD8e8TqDow7
j/mCh+w9OOBB3gUQ9+Kfl2XyznN7xmfR0LtVgYzuRXzwrHtwPvjm3up++2d/
9O2Ykj/48Ox/8eHZIfKdIXbDRA7Te++g8OD8wMm+X+fNLGCjxJY5Y9Ggh3Kq
Zkdaqm4iMaz9UH7X7XAoSR1mvF1eJ94CAiQGSwBB+YlqBw4PtPeRN/jKIPoG
BOlyIbUFLHvkuJ/sMMzTJ6bq5EhfLvS6LRq7IbtfyFB9eiyxb7KXq/ZQ4FZS
FsyNh0hJ2QfuLbQjgyaMDtK2Lkzey3J98RgdOMTHhWUmmgkgsr5x0V9rRjRp
8fktWS4kTZVI2dCLwacZyK2UL4/C144xz/s26vvQreMp7BeE0D9koFPYytfS
qjRWMgPs983ZN/qBZaKp/aFHyKu6Nz454nuPOEdTakHOC5sqnzQOECvkDt88
+0akHwDKfOzp6GVvZZ03aNnaNsq3VKQbNnw9+aN9zuM+kk2+kfYyrQ1Jhi+q
rqHoQr+UbBzk8oVSz3YhZ9y3JVFnn2LT2ug8jxmFQv4ek6/vpNTo/IILfCwY
t1litRyLVmwuNWmsBqJtI9zDA2ymYlKKD4RRVkk+5UI1a8TpbKj/2AmwH0Op
AabvNd99hQBweHScgKgW0p2j1r/hK2lfsveOyMf0cZAr6M1qJ4mtP8ZXQRK7
faPtXoZbevzoi3HVuY9vDHDTHKU1fpQynTVQl337oosPgSCCa2XUo+paIbHd
EqZ7C0hC/IY9jzgJvLvrWtIwEJQ3+agzrcJBjxPmFJF4lg2h05fbdv25Xjaz
WURzP7ggZbEcnw4SjBz1BQsUx55L67Cp2BLbCTDhIL9B1YEEiZuzgcLEaG4g
HDZXQ/YuLp3acr/TMmib65cQQorfSwGbjQ2VOvPt2u+s/Lb6AYOQrwSfPprN
7u6OvNNceXoePqNl6FfCoG+IHMbbRqBbisTdxpc/UMeWlUjkjI5GGUvfCIer
eyDvJIW8MWYzEu/Am6Ria3p382Y+9Q3E8XkT7Qdf3n0rqTdyr1QaP1NHUuXT
Qvkk6FE9sCUcPc19gEJeR5mEEd+TSR8dxLyjZSGDk4om6zJj1sVtaRt4ed9I
fHyc0PYVyoLofJJ7B7ec3XNJKLqqaSuHJEOJBKIhlcdBGr6wq40DjPjCcexa
y4rS9G1MeGQEoZ4X6VTPjrUnxcvI08MgT1vecEpINQdD98OfYKFBVE/33RAg
zZ4RxxwHHOq744cojlQUykglHrUfRYo64fhGr7PL0i5ADZv5hK7b2NhXo2OE
46jHQHhRlUtT9wAoPaXeLQWiWNqEKQiOy9nUaEIqQcl8tYIqtunuKyVQV7uQ
1vvxUHCUpqoK7G8+mjqzLgDg2qD63Q9S72Kz71qaffrT177rd8dB477DiMfF
tl+sALqt9vqGnAqOFnRxqq6qtZtE1Bs5Ng+AxgdDJWkS7m0NX85qlntun4QK
evTFT8Rs8BESP4nC/doakjXSKuhM1Uc3v2mWbtKMHcHgX63jdP2J2iMFLtPQ
TLuTqaPPJLqsdmExeNFyCEmcjdOBQGOgjtrqUH4ISOIRjiGSXQn70eShlRaH
ZIqdExyBrJeZwxr2E/UwHj0EtApCkJiqM1M3hPpeY51keoo6cJrNfAJ+r2Hs
QW4wC+wxktv0k8FcOenC+JblQGnRtmQKU0Q8I5EyBXJE7i781CY05XhpDP7X
hHhAP41uGsyF+6JUGLmpH+nsH60CxABTuusyMjvqBi6DQe9BybL/RE+JnYKA
MEHgXqKQnwojiWFNvKy5+JZlNkW5qDIRNI+R3uZZ3jWbz0NsDyDATbtLIf6Z
+Dtv/elb2Fl03tACf8AP9ik4AgjQfpOw+K7PLghlfRbciai7sgXYTd0N95/H
/g2S0DZr2jpYA6C+mz9IpzL8diR5oAxkJSNJpYsUb7PFoLGqxGElrKaRGTUe
ffbjgvmuH/gEi5KxmQ8cPpsbkSctVrJIg/Ihtvb7PDn5tykk6zZVmUtTnrd2
8MrPUseTDQkTpepHXcPUKeSeeIl/g0X/wlbQumIUadccBLXSMqRPTDieNoy9
ZiFXLYY18ATlnJRTkuM4EJxKGJH4GzlX3QBxu6qATzuTAlXhFlh2w4w4mn4c
aITmbVmVctGoN0x4kIXYVD8Oume73FY6sihHN4Np4sCDe08Ld2AgKjlHpCOy
k1ra46jgQuy7dY3ZbjR3Y/bnGD8zpB5wKgYudvs44i5CYieXj5AoVix+hHXU
skR5+RxeKqXfTsU7CSlyGY4xN7xCKblWR4hUvUSU2/tdhzQAA87kxQuVG+ie
2VljslUpNQ5ACT7eQ62rilsTLt0w1DrXsviSqbjUhD6MvxgMruhdlE/r4Nv7
N6reX5y/ff364s3zK0QmMa7BdZRYVFJVYw3Ndyr00GN2EpE0Hw3NAs6HcOdn
55zoHZo6rlveQ7CNNCbHdQiNJ8vMxjeWQgD0qTuv56UB86A2YKN+IBEZuuxG
EWJCR4cTi7ySTFIUIOjCqgg7YWuP6rVUKBLOt7G674J6zIZDc2PZcq46hv3I
igpDwT5nWAgGDGsoieSkUi7iDEPlKA4KtPXjIe+XsIeYN3dzChnfjSsxGmaQ
AdGy7xZJ38wLLvSMOmAMxd9Ql3vzJvXpU1e6TUJbhx9ymFcQfqgFZtxUh/eG
AegBlfwQa+ggkplKt6dzs3LkYjIjCKPulFVXaKYNpDMN9u73oV40oNrwBgkI
EfwcFF6hm5Z6zJf6IDq8Rx1V8NKj+DFXDCurFkEIsYF3ZMb3XvqaMvQavD1B
w3WuhiwMbv6JTXTYR4dpdLzLGq8cIdOoUyn+hvfHus6lNHr2+zzSauuLwNBZ
/NnkpXGs4YZqjhdtYvAUSiQy9uepWi6NSzI0vIWLaL+o2jL0YC2vyoXLSIIl
fsxfDsBfDaClDdeDUFBJEqjzutpINzAw4bs9vG7lb/5Bk7ncpAMcuDZCoU63
UCQYC5XNJVtbiLq0HGriqiJ79jcZ9r4bx+lmaOnDm1YuTHZnvg9MC+FeclOF
ExtAgoJwEmSAZQNSc7baLFiSW1Rsr3b56WDyTp2Fnm8ommMN7Dwk7WOWa8UN
YhgcjN276Xc2Opsp+3jivDrUVJfK09T7l/4qZEUAjoL5EInyrQcVzKe7TDGI
/58B2YEjI9u1t7zC09zz6aAYM1XP4ay8aTiqrFHb+gsQglCsZ/nVgglgrUMN
rEcl8EQgRsUGWOvipZtQDYNnj6D+PiYOq+q076CsJ5SlXIGLowL5Tnphw4ZL
jPkpQpnprmisiOIP/GU3yY4LBIwj3wUI5Po45usOF6NO6IJGJzB9peLa+dp6
r+T4G8D3IDk+PvL/+U2XPsULQsp3k0eNudi46Yte+Xawswu3jVgFi12HTFt5
KPVdnW4yCSPoBqbxNlVkB54XyrVxX0I2UmyVr6l/6pbCL6Fy1vrhPqF33v7e
vvtXMpjhBb4ur5/qt7TriRIH7zpJwwuqkrWWju08aYH7kliYOtNLS3eO24bx
rYTU/Qu9nPOs019gHSgBSwQQBpkwrBq01SCKNOQUqXP+KqgZ5/wd9Ifj4n89
o6Wxxhg0OJudb86+iJO8QCvprBKe5C6E3EMWgnzI2lSNvwkh4vCeGlvZvrzM
bspqCyxfdppIyxtxv2e1xb7nab3hvR4gwKsUpe7FcmlqJMvXIF6S7IvsRh6c
I/rxKgx/Lyb6L7yloV5ZXrlAIu1D5VVa/mLMrf6hRd43GK1zRA3jkPSAbIsN
Cg52a5S/JCwJcwsaXBhwl3vDtz67/pP6B6PQ1touNwAA

-->

</rfc>
