rfc9501.original.xml   rfc9501.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.39 (Ruby 3.2. 2) --> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.39 (Ruby 3.2. 2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-ietf-shmoo-remote-fee-09" category="bcp" consensus="true" sortRefs="true" symRe <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
fs="true" version="3"> -ietf-shmoo-remote-fee-09" number="9501" submissionType="IETF" category="bcp" co
<!-- xml2rfc v2v3 conversion 3.13.0 --> nsensus="true" tocInclude="true" sortRefs="true" symRefs="true"
updates="" obsoletes="" xml:lang="en" version="3">
<!-- xml2rfc v2v3 conversion 3.13.0 -->
<front> <front>
<title abbrev="Open Participation Principle">Open Participation Principle re garding Remote Registration Fee</title> <title abbrev="Open Participation Principle">Open Participation Principle re garding Remote Registration Fee</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-shmoo-remote-fee-09"/> <seriesInfo name="RFC" value="9501"/>
<seriesInfo name="BCP" value="239"/>
<author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind"> <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<email>mirja.kuehlewind@ericsson.com</email> <email>mirja.kuehlewind@ericsson.com</email>
</address> </address>
</author> </author>
<author initials="J." surname="Reed" fullname="Jon Reed"> <author initials="J." surname="Reed" fullname="Jon Reed">
<organization>Akamai Technologies</organization> <organization>Akamai Technologies</organization>
<address> <address>
<email>jreed@akamai.com</email> <email>jreed@akamai.com</email>
</address> </address>
</author> </author>
<author initials="R." surname="Salz" fullname="Rich Salz"> <author initials="R." surname="Salz" fullname="Rich Salz">
<organization>Akamai Technologies</organization> <organization>Akamai Technologies</organization>
<address> <address>
<email>rsalz@akamai.com</email> <email>rsalz@akamai.com</email>
</address> </address>
</author> </author>
<date year="2023" month="August" day="28"/> <date year="2023" month="December"/>
<keyword>Internet-Draft</keyword> <area>gen</area>
<abstract> <workgroup>shmoo</workgroup>
<?line 42?>
<keyword>no-cost</keyword>
<keyword>meetings</keyword>
<keyword>remote participation fee</keyword>
<keyword>remote</keyword>
<abstract>
<t>This document outlines a principle for open participation that extends the op en process <t>This document outlines a principle for open participation that extends the op en process
principle defined in RFC3935 by stating that there must be a free option for onl principle defined in RFC 3935 by stating that there must be a free option for on
ine line
participation to IETF meetings and, if possible, related IETF-hosted events over participation to IETF meetings and, if possible, related IETF-hosted events.</t>
the Internet.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<?line 48?>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t>Remote participation for IETF in-person meetings has evolved over time
from email-only <t>Remote participation for IETF in-person meetings has evolved over time
to live chat and audio streaming, and, subsequently, to a full online meeting sy from email-only to live chat and audio streaming, and, from there, to a fully on
stem that is tightly integrated line meeting system that is tightly integrated with the in-room session and enab
with the in-room session and enables interactive participation by audio and vide les interactive audio and video participation.
o.
Remote participation has historically been free for remote attendees.</t> Remote participation has historically been free for remote attendees.</t>
<t>Given this more full-blown participation option, the IETF has started s
eeing an increasing number <t>Given this more full-blown participation option, the IETF has started t
of remote participants. This increase can be explained by the ease with which o see an increase in the number of remote participants. This increase can be exp
new participants can join a meeting or only attend selected parts of the meeting lained by the ease with which
agenda, and also by new participants can join a meeting or only attend selected parts of the meeting
a less strongly perceived need to attend every meeting in person. Financial agenda, and also by a decrease in the perceived need to attend every meeting in
person. Financial
considerations may also be a factor. considerations may also be a factor.
In order to better understand In order to better understand
these trends, the IETF started requiring registration for remote participation, these trends, the IETF started to require registration for remote participation,
still without any registration fee applied.</t> still without any registration fee applied.</t>
<t>With the move to fully online meetings in 2020 and 2021, however, there <t>With the move to fully online meetings in 2020 and 2021, however, there
was no longer a was no distinction between remote and on-site participants for those meetings.
distinction between remote and on-site participants for those meetings. Because IETF meeting costs and other costs still needed to be covered, a meeting
Since IETF meeting costs and other costs still had to be covered, a meeting fee fee was charged for remote participants, replacing the free participation that
was charged for was previously available for all remote attendees.</t>
remote participants, replacing the free participation that was previously availa <t>The introduction of a fee for remote participation raised concerns abou
ble for all remote attendees.</t> t the potential impact on both those who
<t>The introduction of a fee for remote participation raised concerns abou regularly attend IETF meetings remotely and those who are considering
t the potential impact on both, those who
regularly remotely attend IETF meetings and those people considering
attending an IETF meeting for the first time. In both cases, even a small attending an IETF meeting for the first time. In both cases, even a small
registration fee can be a barrier to participation.</t> registration fee can be a barrier to participation.</t>
</section> </section>
<section anchor="principle-of-open-participation"> <section anchor="principle-of-open-participation">
<name>Principle of Open Participation</name> <name>Principle of Open Participation</name>
<t>This document outlines the principle of open participation that the IET F Administration LLC (IETF LLC) <t>This document outlines the principle of open participation that the IET F Administration LLC (IETF LLC)
is expected to incorporate into decisions about the registration fee structure f or remote participation.</t> is expected to incorporate into decisions about the registration fee structure f or remote participation.</t>
<t>The principle this document states is simple: there must be an option f
or free <t>The principle is simple: there must be an option for free
remote participation in any IETF meeting, regardless of whether the meeting has a physical presence. remote participation in any IETF meeting, regardless of whether the meeting has a physical presence.
Related events collocated with an IETF meeting are part of the IETF's open proce ss <xref target="RFC3935"/> and Related events collocated with an IETF meeting are part of the IETF's open proce ss <xref target="RFC3935"/> and
are encouraged to follow this principle as well, if they offer remote participat ion at all.</t> are encouraged to follow this principle as well, if they offer remote participat ion at all.</t>
<t>This principle aims to support the openness principle of the IETF as de fined in <xref target="RFC3935"/>:</t> <t>This principle aims to support the openness principle of the IETF as de fined in <xref target="RFC3935"/>:</t>
<t>"Open process - any interested person can participate in the work, <blockquote>
<t>Open process - any interested person can participate in the work,
know what is being decided, and make his or her voice heard on the know what is being decided, and make his or her voice heard on the
issue. Part of this principle is our commitment to making our issue. Part of this principle is our commitment to making our
documents, our WG mailing lists, our attendance lists, and our documents, our WG mailing lists, our attendance lists, and our
meeting minutes publicly available on the Internet."</t> meeting minutes publicly available on the Internet.</t></blockquote>
<t>While RFC3935 explicitly notes that this principle includes a requireme
nt to open <t>
basically all our documents and material and to make them accessible over the In While <xref target="RFC3935"/> explicitly notes that this principle requires
ternet, it was our documents and materials to be open and accessible over the Internet,
written with mainly having email interactions in mind when talking about partici it was primarily written with email interactions in mind when talking about p
pation. articipation. This document extends this principle to explicitly cover remote
This document extends this principle to explicitly cover remote
participation at meetings. Particularly in this context, openness should be seen as open and free.</t> participation at meetings. Particularly in this context, openness should be seen as open and free.</t>
<t>This document does not stipulate that all IETF meetings or related IETF
events must have a remote participation option, <t>
because there could be technical or other reasons why that might not always be p This document does not stipulate that all IETF meetings or related
ossible. IETF events must have a remote participation option, because there
This document rather states that if remote participation is provided, could be technical or other reasons why that might not be
there should always be a free option to make the process as open as possible. possible. However, if remote participation
This document does not specify the implementation details of the free option is provided, there should always be a free option to make the process
and leaves this to the LLC. At the time of publication an approach to request as open as possible. At a minimum, working group sessions, BoFs, and
a fee waiver was implemented. Further, the administrative plenary are expected to provide a remote
it is of course strongly anticipated that at least all working group sessions as participation option.
well as BoFs </t>
and the administrative plenary of an IETF meeting provide an option for remote p <t>
articipation.</t> Note that this document does not specify the
implementation details of the free option and leaves this to the LLC. At the
time of publication, an approach to request a fee waiver was implemented.
</t>
<t>Moreover, in order to fully remove barriers to participation, any free <t>Moreover, in order to fully remove barriers to participation, any free
registration option must offer the same degree of interactivity and registration option must offer the same degree of interactivity and
functionality available to paid remote participants. Specifically, it must not functionality available to paid remote participants. Specifically, it must not
be possible to identify participants that used the free option. However, be possible to identify participants that used the free option. However,
of course this does not mean that all services must be provided for free to of course this does not mean that all services must be provided for free to
participants using the free registration option, but only those services participants using the free registration option, but only those services
that are provided as part of the regular registration. Offering additional that are provided as part of the regular registration. Offering additional
services to a subset or all participants at an additional charge is still possib le, services to a subset or all participants at an additional charge is still possib le,
e.g. if special needs are required. However, to promote inclusivity, e.g., if special needs are required. However, to promote inclusivity,
it should also be considered if those services can also be offered without whether those services can also be offered without
charge for those in need and who cannot afford the fee.</t> charge for those who are in need and cannot afford the fee should be considered.
<t>Further, the free option </t>
<t>The free option
must be clearly and prominently listed on the meeting website and must be clearly and prominently listed on the meeting website and
registration page. If the free option requires additional registration page. If the free option requires additional
registration steps, such as applying for a fee waiver, those registration steps, such as applying for a fee waiver, those
requirements should be clearly documented. Particularly, to avoid any requirements should be clearly documented. In particular, to avoid any
potential negative implications on inclusivity, any personal potential negative implications on inclusivity, any personal
information that is collected with respect to the use of the free information that is collected with respect to the use of the free
remote participation option must be kept confidential.</t> remote participation option must be kept confidential.</t>
</section> </section>
<section anchor="financial-impact"> <section anchor="financial-impact">
<name>Financial Impact</name> <name>Financial Impact</name>
<t>Fully online meetings as well as remote participation incur expenses, a s do other services that the IETF provides. <t>Fully online meetings as well as remote participation incur expenses, a s do other services that the IETF provides.
This includes items such as mailing lists, document access via the datatracker o r other This includes items such as mailing lists, document access via the datatracker o r other
online platforms, as well as support for videoconferencing, like use of Meetecho and others. online platforms, as well as support for videoconferencing (e.g., Meetecho).
Meeting fees are a way to distribute these and other operating costs of the IETF among participants, Meeting fees are a way to distribute these and other operating costs of the IETF among participants,
even though they do not fully offset the costs of either holding the meeting or operating the IETF. even though they do not fully offset the costs of either holding the meeting or operating the IETF.
As such, the intention of this document and the principle stated herein is not t o make remote participation As such, the intention of this document and the principle stated herein is not t o make remote participation
free for everyone, but to always offer a free remote option that enables remote participation without free for everyone, but to always offer a free remote option that enables remote participation without
any barriers other than the application for the free registration itself when th e registration fee any barriers other than the application for free registration when the registrat ion fee
is a barrier to participation. is a barrier to participation.
This principle applies to remote participation only, providing thereby one free option for participation. This principle applies to remote participation only, thereby providing one free option for participation.
In-person participation is not in scope for this document as the cost considerat ions In-person participation is not in scope for this document as the cost considerat ions
are broader than just the registration fee.</t> are broader than just the registration fee.</t>
<t>It is not in scope for this document to make suggestions for changing <t>Changes to the IETF's fee structure or overall funding model are not in
the IETF's fee structure or overall funding model. As defined in RFC8711, scope for this document. As defined in <xref target="RFC8711"/>,
it is the IETF LLC's responsibility to manage the IETF's finances and budget and it is the IETF LLC's responsibility to manage the IETF's finances and budget and
as such "[t]he IETF LLC is expected to act responsibly so as to minimize risks as such "[t]he IETF LLC is expected to act responsibly so as to minimize risks
to IETF participants and to the future of the IETF as a whole, such as financial to IETF participants and to the future of the IETF as a whole, such as financial
risks." Further, it is the responsibility of the IETF LLC Board "to act risks." Further, it is the responsibility of the IETF LLC Board "to act
consistently with the documented consensus of the IETF community" <xref target=" RFC8711"/>, consistently with the documented consensus of the IETF community" <xref target=" RFC8711"/>,
taking agreed principles like the one proposed in this document into account.</t taking into account agreed principles like the one described in this document.</
> t>
<t>If unlimited free remote participation is determined to adversely affec
t <t>
financial sustainability of the IETF, e.g. if the number of paying participants If unlimited free remote participation is determined to adversely
or the cost of free participation emerges to be a significant factor, affect financial sustainability of the IETF, e.g., if the number of
the LLC is expected to implement additional measures to manage these costs. paying participants or the cost of free participation emerges as a
This document does not and cannot restrict the LLC in its financial responsibili significant factor, the LLC is expected to implement additional
ty measures to manage these costs. This document does not and cannot
and therefore does not impose any limitation on the use of appropriate measures. restrict the LLC in its financial responsibility and therefore does
If the LLC decides to do this, they should make their decision and rationale kno not impose any limitation on the use of appropriate measures. If the
wn to the community LLC decides to implement additional measures, they should share
and consider community consultation as specified in Section 4.4 of RFC8711 their decision and rationale with the community and consider whether communit
in order "to obtain consensus-based community input on key issues". y
Further, they should describe the implemented process in sufficient detail for consultation as specified in <xref target="RFC8711" section="4.4"/> is needed
participants to make an informed decision about the use of the free option.</t> "to obtain
consensus-based community input on key issues". Further, they should describe
the implemented process in sufficient detail for
participants to make an informed decision about use of the free option.</t>
<t>As discussed in the next section, assessment of eligibility is difficul t. Consequently, any limit <t>As discussed in the next section, assessment of eligibility is difficul t. Consequently, any limit
on the number of available free registrations, which likely requires an assessme nt of eligibility, on the number of available free registrations, which likely requires an assessme nt of eligibility,
can cause unfairness and negatively impact openness which should be considered s can cause unfairness and negatively impact openness, which should be considered
eriously in any LLC decision. seriously in any LLC decision.
As such, this document defines the principle of free participation but leaves As such, this document
room for choices in the implementation by the LLC. Specifically, it cannot provi defines the principle of free participation but leaves implementation details
de to the LLC. Specifically, it does not provide
guidance on appropriate measures against misuse as any measures need to guidance on appropriate measures against misuse, as any measures need to
be adapted to the specific problem in a specific situation in order to minimise be adapted to the specific problem in a specific situation in order to minimize
both the both the
financial risk as well as its impact on openness and inclusivity.</t> financial risk and its impact on openness and inclusivity.</t>
</section> </section>
<section anchor="considerations-on-use-and-misuse-of-a-free-participation-op tion"> <section anchor="considerations-on-use-and-misuse-of-a-free-participation-op tion">
<name>Considerations on Use and Misuse of a Free Participation Option</nam e> <name>Considerations on Use and Misuse of a Free Participation Option</nam e>
<t>This document does not provide specific requirements on when it is appr opriate <t>This document does not provide specific requirements on when it is appr opriate
for an IETF community member to use or not use the free option to remotely atten d a meeting. The purpose of for an IETF community member to use or not use the free option to remotely atten d a meeting. The purpose of
the free option is to enable everybody who is interested in participation to joi n meetings without the meeting the free option is to enable everybody who is interested in participation to joi n meetings without the meeting
fee imposing a financial barrier. These cases cannot be limited to a certain gro up, like students or "self-funded" fee imposing a financial barrier. These cases cannot be limited to a certain gro up, like students or "self-funded"
participants, nor to any specific other restrictions like the number of meetings participants, nor to any other specific restrictions like the number of meetings
previously attended or previous level of involvement. previously attended or previous level of involvement.
The purpose is simply to maximise participation without barriers in order to mak The purpose is simply to maximize participation without barriers in order to mak
e the standards process as open as possible.</t> e the standards process as open as possible.</t>
<t>It is expected that participants who have financial support to use the paid regular registration option <t>It is expected that participants who have financial support to use the paid regular registration option
will do so. Paying a registration fee is a way for their sponsor to support the sustainability of the IETF. will do so. Paying a registration fee is a way for their sponsor to support the sustainability of the IETF.
For example, a higher late payment charge can be used to maximise this financial support. For example, a higher late payment charge can be used to maximize this financial support.
However, this document does not comment on the actual payment structure However, this document does not comment on the actual payment structure
of the IETF meeting fee other than the requirement for a free option. The fee pa yment structure is set by the IETF LLC such that of the IETF meeting fee other than requiring a free remote option. The fee payme nt structure is set by the IETF LLC such that
the viability of the IETF and the ability of IETF participants to work productiv ely within the IETF can be ensured.</t> the viability of the IETF and the ability of IETF participants to work productiv ely within the IETF can be ensured.</t>
<t>The LLC is responsible to ensure the financial stability of the IETF an d therefore should monitor <t>The LLC is responsible for ensuring the financial stability of the IETF ; therefore, they should monitor
trends in the use of the free participation option that could endanger the viabi lity of the IETF and, if necessary, manage the associated costs. trends in the use of the free participation option that could endanger the viabi lity of the IETF and, if necessary, manage the associated costs.
Aggregated data on the number and percentage of free registrations used should b e published, Aggregated data on the number and percentage of free registrations used should b e published,
as this will permit analysis of the use and change in use over time of the free registration option without as this will permit analysis of the use and change in use over time of the free registration option without
revealing personal information.</t> revealing personal information.</t>
<t>As the principle defined in this document aims to promote openness and thereby enhance participation, <t>As the principle defined in this document aims to promote openness and thereby enhance participation,
an increase in use of free registrations is a success, likely a sign of increase an increase in use of free registrations is a success, because it is likely a si
d interest, not necessarily a gn of increased interest and not necessarily a
sign of misuse, and should not be linked to the number of paid registrations. sign of misuse. The increase should not be linked to the number of paid registra
tions.
In particular, the number of paid registrations may decrease In particular, the number of paid registrations may decrease
due to various reasons other than misuse, for various reasons other than misuse,
such as restrictions on travel to physical meetings due to cost savings or envir onmental reasons, general cost such as restrictions on travel to physical meetings due to cost savings or envir onmental reasons, general cost
savings and lesser focus on standardization work, or simply loss of business int erest. Such trends savings and lesser focus on standardization work, or simply loss of business int erest. Such trends
can impact the sustainability of the IETF due to its can impact the sustainability of the IETF due to its
dependency on meetings fees to cross-finance other costs, independent of use of the free registrations.</t> dependency on meeting fees to cross-finance other costs, independent of use of t he free registrations.</t>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document introduces no new concerns for the security of Internet <t>This document introduces no new concerns for the security of Internet
protocols.</t> protocols.</t>
</section> </section>
<section anchor="iana-considerations"> <section anchor="iana-considerations">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This document has no IANA actions.</t> <t>This document has no IANA actions.</t>
</section> </section>
<section anchor="acknowledgments">
<name>Acknowledgments</name>
<t>Thanks to everybody involved in the shmoo working group discussion,
especially Brian Carpenter, Jason Livingood, Lars Eggert, and Charles Eckel for
proposing concrete improvements and their in-depth reviews.</t>
</section>
</middle> </middle>
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<reference anchor="RFC3935">
<front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml"
<title>A Mission Statement for the IETF</title> />
<author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/
>
<date month="October" year="2004"/>
<abstract>
<t>This memo gives a mission statement for the IETF, tries to defi
ne the terms used in the statement sufficiently to make the mission statement un
derstandable and useful, argues why the IETF needs a mission statement, and trie
s to capture some of the debate that led to this point. This document specifies
an Internet Best Current Practices for the Internet Community, and requests disc
ussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="95"/>
<seriesInfo name="RFC" value="3935"/>
<seriesInfo name="DOI" value="10.17487/RFC3935"/>
</reference>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="RFC8711">
<front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8711.xml"
<title>Structure of the IETF Administrative Support Activity, Versio />
n 2.0</title>
<author fullname="B. Haberman" initials="B." surname="Haberman"/>
<author fullname="J. Hall" initials="J." surname="Hall"/>
<author fullname="J. Livingood" initials="J." surname="Livingood"/>
<date month="February" year="2020"/>
<abstract>
<t>The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF evolved in w
ays that required changes to its administrative structure. The purpose of this R
FC is to document and describe the IETF Administrative Support Activity, version
2.0 (IASA 2.0). It defines the roles and responsibilities of the IETF Administr
ation LLC Board (IETF LLC Board), the IETF Executive Director, and the Internet
Society in the fiscal and administrative support of the IETF standards process.
It also defines the membership and selection rules for the IETF LLC Board.</t>
<t>This document obsoletes RFC 4071, RFC 4333, and RFC 7691.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="101"/>
<seriesInfo name="RFC" value="8711"/>
<seriesInfo name="DOI" value="10.17487/RFC8711"/>
</reference>
</references> </references>
</references> </references>
</back> <section anchor="acknowledgments" numbered="false">
<!-- ##markdown-source: <name>Acknowledgments</name>
H4sIAAAAAAAAA41a0a4jN3J951cQk4ckgCSMvRtkfV+y44lnM44nDuwJ/GAY <t>Thanks to everybody involved in the SHMOO Working Group discussion,
AdVNSfTtbipk99XIhgH/xgLJn+Qtf+Ivyakqks1u6c7uArs7V+omi1WnTp0q especially Brian Carpenter, Jason Livingood, Lars Eggert, and Charles Eckel for
arvdqtGNnX3QX5/toP/dhNE17mxG5/FXcAP+6KwO9mhC64aj/sb2frT4v6OL proposing concrete improvements and their in-depth reviews.</t>
Y5Dn3lirzH4f7NPHl1GtbwbTY7M2mMO4dXY8bOOp934beNntwdrty89Ua0b7 </section>
oBr879GH64PeN2el3Dk86DFMcfz05cvPXn6qHu314kP7oN8Oow2DHbf/TMsq
FUcztP9pOj9gq6uN6uwe9PfRhzHYQ9zoeO3pHz8oZabx5MOD0nqL/2rthvig
3+30v/7f/546e3FDyx+L0e9c+NGsv/Lh+KC/CK6J0Q/8ie2N6x50T0/vHieb
nv6jTQ/tGt/zg8tdv9zBqbbe70v4rnzE+7x6NFhcv7fNafCdPzqcrdryx4Cn
/2j4oWd2+WanvzXdT9Uu37jmNH/212wTIp6ut1Fq8KFHsJ8sufKbN69/99nv
/uEBn7vhMH+D/2y3W232BJwGcXp/clEDE1Nvh1H7aezcYKM2+lyAh9e1J0id
F5AaT2bU9sNohzbiD5ueCb6xEeEur7f2gCVbnD1bpfdXDXyMhGVeBW8Hq3vA
Su8t9j7AiViOt+HdB7JKrfb3+u0X79/o3lpaCTYP7Ua7gz77GN2+sxukTAf8
tvzc9uQj/ds+4aBR+ycb2OoM3J14pndtiyxRf0NfBN9ODW2mVMq5pQlkG9vg
hu3ZBgBrtuZkIvby3RP2lM1cD18G30sMtzjUVeEQHQKjG3IDDqDN1DoP7wRr
eqyzkVPFaR/tf02wvLtu6OTw0dR1yTF5UyQVjtiLTxHW0R1PeAHWIYkDeUJd
3HjiY8Pi4GFLRLDoKLS3HQzcFvl5QgcZtjwwAicG0uNPrrV+d98zdHoga/RI
ONPBhr0FODiu5DShGm1GQo+1Ec7/E3YjUMHu3gMNdL7tvvOXNe4EFxsJHjmf
9gKcAkU3WkuOMAMO0cCHkf4apn5vg/KHvG9ZEEjYaU6B9DgigXcBQvvh3BnG
Lc5MW/GX7L7LCemqBntZrMMv/uiBclPiIdC9pnPCuM42ZCW9BwgeeOH8sDni
GbMRFHTR08bKaASEjhf8cMRKQFljHWFqAM8wEmRtwDpcy1qwQvC402/cYJCJ
plONHyJCJgUDXjbXtA+nHOLtw069hYNDS3ClL7B20BNCFJjPFeyFFwBO5HwV
gez9AIy6QAaEujZVEV+EErgeHVBMXgXz4OTX1YuAizmfO2dbIOS7jN0e+UT2
EUSuqxygSOpPX376kv2If3yy0Sd/IfdsEs9cgJcBeQeP4nRGtdgQ4ReA2/FC
SM0AxRp+2Ea3Ag0fCUbHed+d+haL2AUn6QacE2UV2jv9Lac+mVacjE9hnUWa
z8ihk5Od4IVwhGexn7oDXqI44LQRJrWSYHdompY6Qxs4P0XC4xMIiHKdz4H8
vJeQ75klZg4kvBo27Ll46mBchLEAWgNOxcH3FFYy7IyHhxEo1K4/A2qafA2f
bJIXLyeP8x2nzoTumhafE+eG59NbZ+upwmRgkxeUvJJIYBEMiRnMd0Az0/EO
JM9mIHlBhBsuDjhk7OETdQPFRA1G700ITnJk4YAd1Y1ZscFht1Ls2ZLLbqrf
fa7mlrR71aJEzCZ+9dVr/Xf8Bf719wqbgMSEcGAoFvbh7KkMUFg96nLjIjPB
HKabI+MPRH8Kzwc9IWW2fFwcj+o8lRSgHpEnkbsq9kNd6Am/Nzjnb4lXQQ91
QDdJEjNDwl+Xk+Ukq0mVagO0zOkaqQ5RDkQLcFLVEmmQ5EDju843/Alz/Bo7
JohBmbTpy7+NC8mjv0/y5gdCqKI3sJWfgjlKBA60x0X8M7sLBl5s17Fywcrg
s8PBPpNfpBG6bpcgVK3h+kg7xOmMCI9FjQ1k1gJTBTvYthJmP/+cbP/lF2jE
F1/Xx9qy41kTWFZQSelQNszmEah4dbQDjxuSqo8DDntJUmTPZZkg1zLRIYV7
82hJI1CVpLA9eQf6PFlEVDPULa3iYpyQp5xDcoDFyen1iXi1793IgIMbsDJX
3ynQChmKSG969Ls/aZJf9EAHrKdPhTUMEXj6lElbVsggQLZNBObztO9cs+BR
MXgWky/oPfXdyeG7rHpJUsBZpMgGP3LGczYvDzQ03dSyApdqavOpGGtqb2JS
VETbZHo5X/IqLCCeZZb04mWY1mvTUDgdW7sWv0AfFwl1CY48IUkAP5F6OZkn
Oj2r1lkbEnEg5PBJS5mH85uO3S5ssuKIJefNXcPi7DC38hFXxZQH6iYPStlN
7Joqh0sSEiVhxC6bOQ0iJEbXEuVEKvAmJS+5iVhnp9fE3HpLOoEozJ0nYgsJ
GPl9WZCYGedOI3MKUxycZzmWd9I5KVm1t42Zok3M2GQ7R+r9mLZIRzK1kUQl
x19OVzGmJ4nPVpruYq6UaKX/WXsdtE5rJEaWJuFWEgvbUlj8EyerErOS/+Zt
lm1aBbXCHMXH8VmbZiejUrmDSG0uFPS1GNPaEcgrernaVVH0OgsXJyzBCnoE
9W+nXwkPctuFVyVpE34GkpXBG7TdeIUSDdSmTJJdjoBHkqkYAv2p30yBPLFR
jhkNSxK5RzuLcyiyRIZtgspI1kXBDBEj5ccx+Omc+66Y+Z/+/3P/JipRN3Bv
VdypD+vQnYUri7BVbUqRWpXSZ2r1O/RWnsWwq5S+KGl6BVsldRNv5M2GK0Gq
0ZVQSLsy3qV60QGi6an5P3K4DlVT6cYrV8jDJKLbdPxJ4VLe1rX3m7VvGSdC
gcxavCsQpCrks95pSXACUQvdzmGZom3XUNrpf0ldgpojm6RMgmhvzTBTQLTh
CQUrFiWTE6YIGVihFptPcaHT7/hwo/fTKD2jKNy8i5J9Q7UNZVWlSJJ6Xqy6
019TOJiV29aJs1WxnOcIPFoYdeoDFvbySKJ6M3UjLOa4hSmTFmV3xx2xCacx
nqTuNLK9qYq1s4M5wMFzcLncRcYEJ1ZhmZg6I1H2pFIOK5ewAMkPMuySeEP5
UcnSuU0D2rljNlyuPL3MrHnAIwkMKAJK5Sy/oZoc5gYZHTjZWz4FJBRNZVg2
2KxcSm5e7J6bR8L7It5nqELImrc3nJYdFuuQLV7FPmeaoE5gL5K3aJCvub+p
KSz1VqrSEXUZzAfJXEwhqmupzJmgyshpVzV3cANUN3MS0WOi1KhZo8/BZKoQ
pQj7ywwy9zBOJLd0Jyw2cGJqVjKFUz2sCP9+U1ATD070aM8jQeYguW867sfK
AES/5daTYnxvblAR8TMdSAO1RS3VwL0iKWif6vKcUosGLeVqTFWvaDsgAoI9
B3AlR0ttFMGmn5zhFVuDeggGfcR+WRCodIgz1Ad5WMzKx8jtAAGDh3XkG6TJ
0HD31LnH4ud38ALkhp9nFTD63TyMkFw2QNaVIkQjk+DAVVzwo61GHKj4wVTD
j0XT0XuqV/UAQ1kZ+/npeJL+B06lzEzDncOB2IlWKMtZxxudfNdmPq0HbmX/
vO1OvRJnb9Lkk4EsA41ls5pr7yxJWSy11J+ggSHUkmlZ69yDiSozTp7I+cEK
p1MuiXSSCmlyDeAlsojikXqawt4FYeY3yq5Sp31qe41wD0/Mmnn0dr/guDHa
7pCk+53Wn+YHH5t0rFtQHtNFkVP3UnUgRpGESMEJdk9ZaG/G/aud3pbh+o1I
pWggLrFB1NNZF/GMBTl6Nf3k/nwPCdhm1/1ILHLPE2CRt+NfsVuGRZyOR8hJ
3oaeQi0ajjizqgYHy9kKwRZooQIMUcT+6X1rO4jYuLo/+cM/fvJJlqAlr6B3
f/v1z5E5lI65dyyp2KABhaY8yU8dmBCt9Iv7qT3aUSYWiZJ++/W/vx9/qNbW
q1ESze/KVkhSlGDDkSfF2ruf4EIXH6PKNzRLUSF9KYNyktMvxxKG6jPd3mR+
PJQJNi+7++3X/yliXM+eWB2+XpXO8LmnwYJ+IfbLMDyOUrvLrchcCxkvYPpp
yWA0aJgGrP9C//zzP6V4/PILmiSZORiSu+2cF1FYlgcyA4s3aCYJ5hI8PJID
4/tpoKso6IIJ1N47MqVmipsUQHdkQ88IoRVa4Cjy6BQ0gzip4j34E2yGv24d
tNFZv9Encl3CPZNhYVHHTyVC4ZzCI3cmzlAa0F4xDbehMN1xYMmOY8o1A/eU
95BVGq5adUJ3xynIgjOeY6oIz3aUBLSk8mhwFVwz6rIt89+MrBV4chMW7IGu
osqSMM9zsSO5h9hkaqsVCzeWiD/NC7LlO5V0Hu0tQzA+TesZBRspfEma5Tba
hTKi5bMIIRlwLU3WhpxEBZFsdGa5+WP+aOqSrZTj0kEJCL+1Mtv//e73ZHwC
tCq9IbiARk97As6cEtu9kTl/3sMNZ+5bIMGuMrKLyNKdXsjpckKcvoF6sMtm
n9NGBgdEstMBkHEcUe7/+Qpk2cslvuXLPlI/tq08VmbaKyWZ+z1FqgA6ppli
SUhg335AEyJOIS1FbbqM6aE7OnfM7EKIc2QhPLvTr8kx5Xq2wEMlZMwJVV28
rAsyUMAXi0wY3IznNmB43o6NoiZIpkfTcDAu8KyLkJBVOg3F0pVLHoXJPlUn
MHdZELLpjigN3DNiI/usElKLnOMSdecK4w47kBiSkY3iC2ipkJ7VcwrCav6T
LmB5qHPT/qcMT0pbHScnU1w/3M1EEDSQHGlwFslpVG+G6/x1ulWlYYJpzTnR
Eo8z0s60FQLYs4PmT9HlTeWmosxVpCBiH75kopF2RTkoZrVaJ0KaL8dKsCiW
VWMF3KKneb0UM3j+P5IIfyfn4ru6N+T95e+Avj7fu4MqBJdHSeVYi96R9CfJ
Ram5lXsVt57DqkTCq4x7+IFNCrxFGnSuh4frK79yFUr388DQFJh6/UGtX5ax
n6hmEd173165yXexvrdwN7dpXi7sSwuYL6KrlkKRUmPe5/JelYwkjdk+/t1A
lJkEHXJvdS7ePGRpbGAG5dlf6rziOLXi1qBfkBbfkvaz7YsFy23gNHYhwbSE
JU+DpawxBorOmNmmnKu++pUb3pZ2zR8jH8ETMqTjX6xQuHeq9nu+v0ui8oOg
+m5vMvcli0zIw2H+IQGkWPz4mDhJ7lkcUGu0oH8KME/Xa4WT7r98gVmaJN7O
xvJc50KDLBTi6Gn8cZUo39yDcjNEzW9qqFCcWTBIbOp7t+dVFpVD6gs/GOI3
uu0/uSPFke8WoLU4F9PkKt01y6iycjkT782JsfQ8Xbuf2pSWXEBSk4jOgy5E
065zL6JquVv/HGHVZda3U2nyVE9T38tE7c4GBCV0HInViz5ntU9R5gR/cncc
WPrz6rvbBgPeolE7wYt/ucAlkLCZqouQVPqVz0C036Y77CRI59ZGrqT4GeGs
2e/jR+xLsjHrOQ8yhHaRX83kGrdWJXcHWwx6uQ/i28ljGq0/6x2+RR4spZUJ
KJBV+wcN4RtnpLVh3fzqeKQLdPqEZkt6qVZ4vkm/NkIZPs7FfCFZBJ6zkOA7
lniiSyOTbmQ4vc7UoZAiN901utJRTalmcYPMI1r2SvmxXO2fexcOeRgCGrOG
R2h54KirgSPd7L1aa5OqqV6NDNJVeh5QL+pwHlrY4cQiY3k7ouZfnc2Hues2
ZhMAnuK0yYJPGiVhYVmkLdVrwymcA+voaZWfFiUjF9YpFKUEDY+zgKnbOuHE
2SL+3de5DH83f/EF/vUYdCHbqdqJM+XJsHgst5QVYyQjVe7pF6WLgBcMlSBy
fP6tRqleaXXuOCPfRXPNtMOTC35gndjlPTf6aAeapPDjKj8u94RQ0QFc1Uy8
ZS5E7qdUvuiHC7RwKnSdl5+V7OnaRroSCQZUKHMV5zML8CTbPk7/+RzQeaq1
Z6rCQ0MDsPmkPGilowbsvU1zmvqnY3Rrl9/lXmBNI6uoQiqiw5sCmbLUjGsJ
mH/pxdVC048by6+48gwx5pWIdtMPBxTyZPSN72Szt6/+7dVf2Ogkv77jJ9Pv
CPjVVw21tZ1tjyw26TUzPIq2K6Iu6ZPSrvEP11c3q6mn44y06T4K4fwcSnXQ
r004U68JiH9JgNFfOUKI96DOrww0yxdHkOwo2fQapZhGOF80SFDpP3l+I8Nt
StKRtSFEs51/gSHqwA1bBIrvNZ6cveCM/w9uPEfX6C8AAA==
</back>
</rfc> </rfc>
 End of changes. 37 change blocks. 
266 lines changed or deleted 145 lines changed or added

This html diff was produced by rfcdiff 1.48.