<?xmlversion="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.4.5) -->version='1.0' encoding='utf-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.30 (Ruby 2.5.9) --> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-editorial-rswg-rfc9280-updates-04" category="info" submissionType="editorial" xml:lang="en" number="9920" obsoletes="9280"updates="7990, 7991,updates="7991, 7992, 7993, 7994, 7995, 7996, 7997,8729"8729, 9720" tocInclude="true" sortRefs="true"symRefs="true">symRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.31.0 --> <link href="https://datatracker.ietf.org/doc/draft-editorial-rswg-rfc9280-updates-04" rel="prev"/> <front> <title abbrev="RFC9280 updates">RFCEditor Model">RFC Editor Model (Version 3)</title> <seriesInfo name="RFC" value="9920"/> <author initials="P." surname="Hoffman" fullname="Paul Hoffman"> <organization>ICANN</organization> <address> <email>paul.hoffman@icann.org</email> </address> </author> <author initials="A." surname="Rossi" fullname="Alexis Rossi"> <organization>RFC Series Consulting Editor</organization> <address> <email>rsce@rfc-editor.org</email> </address> </author> <date year="2025"month="July" day="31"/> <keyword>Internet-Draft</keyword>month="December"/> <abstract> <?line68?>69?> <!--[rfced] FYI: We updated the abbreviated title as follows to align with the title of the document. Note that the abbreviated title only appears in the PDF output (in the header at the top of each page). It does not appear in the TXT or HTML outputs. Original: RFC 9280 updates Updated: RFC Editor Model --> <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> <!-- [rfced] Because this document updates RFCs 7991, 7996, and 7997, please review the errata reported for these RFCs and let us know if you confirm our opinion that none of them are relevant to the content of this document. Links to errata: https://www.rfc-editor.org/errata/rfc7991 https://www.rfc-editor.org/errata/rfc7996 https://www.rfc-editor.org/errata/rfc7997 --> <!-- [rfced] FYI: We have removed the following text from the Abstract as this document is no longer a draft. Original: This draft is part of the RFC Series Working Group (RSWG); see <https://datatracker.ietf.org/edwg/rswg/documents/>. There is a repository for this draft at <https://github.com/paulehoffman/9280-updates>. --> <!--[rfced] We note that this document says it "establishes", "specifies", and "creates" the Editorial Stream. Should any of these instances be updated for consistency (perhaps use "specifies")? Current: (Abstract): Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein. (Introduction): This document specifies a fifth stream, the Editorial Stream, for publication of policies governing the RFC Series as a whole. (Section 6): This document creates the Editorial Stream as a separate space for publication of policies, procedures, guidelines, rules, and related information regarding the RFC Series as a whole. (Section 9.7) This document specifies the Editorial Stream in addition to the streams already described in [RFC8729]. --> <t>This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility of the RFC Series Working Group (RSWG), which produces policy proposals, and the RFC Series Approval Board (RSAB), which approves such proposals. Second, policy implementation is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC). In addition, various responsibilities of the RFC Editor function are now performed alone or in combination by the RSWG, RSAB, RPC, RFC Series Consulting Editor (RSCE), and IETF LLC. Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein.</t> <t>Since the publication of RFC 9280, lessons have been learned about implementing this model. This document lists some of those lessons learned and updates RFC 9280 based on that experience. This document obsoletes RFC 9280.</t> <t>This document updates RFCs7990,7991, 7992, 7993, 7994, 7995, 7996, 7997, 8729, and8729.</t> <t>This draft is part of the RFC Series Working Group (RSWG); see <eref target="https://datatracker.ietf.org/edwg/rswg/documents/">https://datatracker.ietf.org/edwg/rswg/documents/</eref>. There is a repository for this draft at <eref target="https://github.com/paulehoffman/9280-updates">https://github.com/paulehoffman/9280-updates</eref>.</t>9720.</t> </abstract> </front> <middle> <?line93?>153?> <sectionanchor="introduction"><name>Introduction</name>anchor="intro"> <name>Introduction</name> <t>The Request for Comments (RFC) Series is the archival series dedicated to documenting Internet technical specifications, including general contributions from the Internet research and engineering community as well as standards documents. RFCs are available free of charge to anyone via the Internet. As described in <xref target="RFC8700"/>, RFCs have been published continually since 1969.</t> <t>RFCs are generated and approved by multiple document streams. Whereas the stream approving body <xref target="RFC8729"/> for each stream is responsible for the content of that stream, the RFC Editor function is responsible for the production and distribution of all RFCs. The four existing streams are described in <xref target="RFC8729"/>. This document specifies a fifth stream, the Editorial Stream, for publication of policies governing the RFC Series as a whole.</t> <t>The overall framework for the RFC Series and the RFC Editor function is described in <xref target="RFC8729"/> and is updated by this document, which defines version 3 of the RFC Editor Model. Under this version, various responsibilities of the RFC Editor function are performed alone or in combination by the RFC Series Working Group (RSWG), RFC Series Advisory Board (RSAB), RFC Production Center (RPC), RFC Series Consulting Editor (RSCE), and IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/>, which collectively comprise the RFC Editor function. The intent is to ensure sustainable maintenance and support of the RFC Series based on the principles of expert implementation, clear management and direction, and appropriate community input <xref target="RFC8729"/>.</t> <!--[rfced] Paragraphs 3 and 4 of Section 1 both state that this document "defines version 3 of the RFC Editor Model". Should this sentence in paragraph 4 be removed to avoid repetition? 3rd paragraph (for reference): The overall framework for the RFC Series and the RFC Editor function is described in [RFC8729] and is updated by this document, which defines version 3 of the RFC Editor Model. Under this version ... Original (4th paragraph): This document defines version 3 of the RFC Editor Model. This document updates [RFC7841] by defining boilerplate text for the Editorial Stream... Perhaps (4th paragraph): This document updates [RFC7841] by defining boilerplate text for the Editorial Stream... --> <!--[rfced] We note that both the header and the Abstract list the RFCs that this document updates (i.e., RFCs 7991, 7992, 7993, 7994, 7995, 7996, 7997, 8729, and 9720). However, the last paragraph of the Introduction says that this document updates RFCs 7841, 8729, and 8730. Note that RFCs 7841 and 8730 are not included in the header's update list and the other documents in the header's update list are not mentioned in this paragraph. (RFCs 7841, 8729, and 8730 were updated by RFC 9280.) Please review and let us know if any changes are needed. Current: This document updates [RFC7841] by defining boilerplate text for the Editorial Stream. This document updates [RFC8729] by replacing the RFC Editor role with the RSWG, RSAB, and RSCE. This document updates [RFC8730] by removing the dependency on certain policies specified by the IAB and RFC Series Editor (RSE). --> <t>This document defines version 3 of the RFC Editor Model. This document updates <xref target="RFC7841"/> by defining boilerplate text for the Editorial Stream. This document updates <xref target="RFC8729"/> by replacing the RFC Editor role with the RSWG, RSAB, and RSCE. This document updates <xref target="RFC8730"/> by removing the dependency on certain policies specified by the IAB and RFC Series Editor (RSE). More detailed information about changes from version 2 of the RFC Editor Model can be found in <xref target="changes"/>.</t> <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t> <?line -18?> <!-- [rfced] This document contains key words, so we included the 2119/8174 boilerplate at the end of Section 1 (immediately before Section 1.1) and added RFCs 2119 and 8174 as normative references. Please let us know if you prefer that this boilerplate be placed in a different location in the document (e.g., as Section 1.1). --> <!-- [rfced] FYI - We added quote tagging in the .md file in a few places (notably in Sections 1.2-1.4). This produces <blockquote> in the XML file, which is used for direct quotes as well as OLD/NEW text. --> <!-- [rfced] Sections 1.2.3 and 1.3.2 are both about entire new sections that have been added in this document. Instead of repeating the entire section in two places in the document, would you like to include a summary in these sections with pointers to the body of the document? Perhaps: 1.2.3. RFC Consumers Section 3.3 was added to define the term "consumers of RFCs" and set relevant policy in respect to consumers of RFCs. Perhaps: 1.3.2. Consistency Policy Section 7.8 was added to define the policy reissuing an RFC to maintain a consistent presentation. --> <sectionanchor="changes-to-9280"><name>Changesanchor="changes-to-9280"> <name>Changes to RFC 9280</name> <t>This section details the changes made toRFC 9280<xref target="RFC9280"/> by the RSWG starting in 2022. If you arereading this document and donotcare aboutinterested in howitthis document was changed,you canskip directly to <xref target="overview"/>.</t> <!--[rfced] Should "might" be updated to "can" in this sentence? Original: As these structures and processes have been exercised, the community has found places where they might be improved. Perhaps: As these structures and processes have been exercised, the community has found places where they can be improved. --> <!-- [rfced] The parentheticals below appear in the body of the document. Because the new text is defined and explained earlier in the document, may we remove these parentheticals? It improves readability. Section 3: (The text in the next paragraph is added by Section 1.4.) Section 3.3: (The text in this section is added by Section 1.2.3.) Section 4.3: (The text in the next two paragraphs is added by Section 1.2.1.) Section 4.4: (The text in the next paragraph is added by Section 1.2.2.) Section 7.6: (The text in this section is updated by Section 1.3.1.) Section 7.8: (The text in this section is added by Section 1.3.2.) Note that if these parentheticals are removed, the following sentence in Section 1.1 will need to be updated. Original: The rest of this introduction is a list of changes to RFC 9280. Those changes are instantiated in the rest of the document, with cross-references between the list of changes and the main body. Perhaps: The rest of this introduction is a list of changes to RFC 9280, which are instantiated in the rest of the document. --> <t><xref target="RFC9280"/> contained significant changes to the publication model for RFCs. Those changes created new structures and new processes for the publication of RFCs. As these structures and processes have been exercised, the community has found places where they might be improved. In addition, gaps in some of the processes have been found. This document updatesRFC 9280<xref target="RFC9280"/> based on these findings.</t> <t>The organizationforof this RFC is different from typical RFCs in order to keep the section numbering the same asRFC 9280.<xref target="RFC9280"/>. To keep the section numbering the same, theintroductionIntroduction section is much longer, withlots of sub-sectionsseveral subsections that refer to the main body.</t> <t>Therestremainder of this introduction is a list of changes toRFC 9280.<xref target="RFC9280"/>. Those changes are instantiated in the rest of the document, with cross-references between the list of changes and the main body.</t> </section> <sectionanchor="rpc-roles-and-responsibilities"><name>RPCanchor="rpc-roles-and-responsibilities"> <name>RPC Roles and Responsibilities</name><t>RFC 9280<t><xref target="RFC9280"/> created a new structure for the RFC Editor function. It established the RFC Series Working Group (RSWG) and the RFC Series Approval Board(RSAB),(RSAB) and gave new responsibilities to the RFC Production Center (RPC). Broadly speaking, it says that the RSWG writes policies for theeditorial stream,Editorial Stream, the RSAB approves those policies, and the RPC implements those policies.However RFC 9280However, <xref target="RFC9280"/> does not specify which group is responsible for defining or building the specific code and tools that implement the policies agreed upon in this process. The rest of this section updatesRFC 9280<xref target="RFC9280"/> to deal with this and other related matters.</t> <sectionanchor="tooling-code"><name>Toolinganchor="tooling-code"> <name>Tooling and Code Used for Publication of RFCs</name> <!-- [rfced] FYI: In Section 1.2.1, we added "[RFC8711]" to the end of this sentence to match the text in Section 2 of this document and RFC 9280. Current: Section 2 states: | Policy implementation through publication of RFCs in all of the | streams that form the RFC Series. This is primarily the | responsibility of the RFC Production Center (RPC) as contractually | overseen by the IETF Administration Limited Liability Company | (IETF LLC) [RFC8711]. --> <!-- [rfced] References to Sections a) In Section 1.2.1, per the context, we believe that Sections 3.1.1.2 and 3.2.1 are referring to RFC 9280, so we have updated the text as shown below for clarity. If this is not correct, please let us know. Original: RFC 9280 mentions tool developers twice. In Section 3.1.1.2, it encourages "developers of tools used to author or edit RFCs and Internet-Drafts" to participate in the RSWG. Section 3.2.1 says that "RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis". Current: [RFC9280] mentions tool developers twice. Section 3.1.1.2 of [RFC9280] encourages "developers of tools used to author or edit RFCs and Internet-Drafts" to participate in the RSWG. Section 3.2.1 of [RFC9280] says that "RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis". b) Please review the following section pointers in Sections 1.2.1, 1.2.2, and 1.4. Would updating to either "Section X of this document" or "Section X of [RFC9280]" improve clarity and be more precise? Note that currently, these section pointers link to the section in this document in the HTML and PDF outputs. Current: Section 2 states: ... Section 4.4 provides a pathway for resolution of conflicts between the RPC and the author(s) of a specific document. ... Section 3 says: --> <t><xref target="overview"/>says:</t> <ul empty="true"><li>states:</t> <blockquote> <t>Policy implementation through publication of RFCs in all of the streams that form the RFC Series. This is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETFLLC).</t> </li></ul>LLC) <xref target="RFC8711"/>.</t> </blockquote> <t>The same section alsostates</t> <ul empty="true"><li>states:</t> <blockquote> <t>The RPC implements the policies defined by the Editorial Stream in its day-to-day editing and publication of RFCs from all of the streams.</t></li></ul> <t>RFC 9280</blockquote> <t><xref target="RFC9280"/> does not define any other group that is responsible for implementing policies.</t> <t>ThroughoutRFC 9280,<xref target="RFC9280"/>, the RSWG is consistently assigned responsibility for writing policies (not deciding on implementations). The RPC is consistently assigned responsibility for implementing policy decisions, but examples given generally describe decisions made at the single document level.RFC 9280<xref target="RFC9280"/> does not cover any specific responsibilities for designing and building the tools and code used to publish documents.</t><t>RFC 9280<t><xref target="RFC9280"/> mentions tool developers twice.In<xreftarget="rswg-participation"/>, itsection="3.1.1.2" sectionFormat="of" target="RFC9280"/> encourages "developers of tools used to author or edit RFCs and Internet-Drafts" to participate in the RSWG. <xreftarget="intent"/>section="3.2.1" sectionFormat="of" target="RFC9280"/> says that "RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis".</t> <t><xreftarget="working-practices"/> in RFC 9280section="4.2" sectionFormat="of" target="RFC9280"/> mentions a specific implementation when discussing the working practices of theRPC.</t> <ul empty="true"><li>RPC:</t> <blockquote> <t>In the absence of a high-level policy documented in an RFC or in the interest of specifying the detail of its implementation of such policies, the RPC can document ... Guidelines regarding the final structure and layout of published documents. In the context of the XML vocabulary <xreftarget="RFC7991"></xref>,target="RFC7991"/>, such guidelines could include clarifications regarding the preferred XML elements and attributes used to capture the semantic content of RFCs.</t></li></ul></blockquote> <t><xref target="RFC7991"/> is the only editorial implementation-related RFC mentioned in9280.</t><xref target="RFC9280"/>.</t> <t>The following is added to <xreftarget="rpc-responsibilites"/>target="rpc-responsibilities"/> of this document:</t> <!-- [rfced] Will readers understand what "text and graphical formats" means here? Does "graphical formats" refer to the HTML and PDF outputs or to something else? Also, we suggest using "and" rather than "or" in thisdocument.</t>sentence. Original: The RPC is responsible for detailed technical specifications, for example specific details of text or graphical formats or XML grammar. Perhaps: The RPC is responsible for detailed technical specifications, for example, specific details of the publication formats and XML grammar. --> <blockquote> <t>The RPC is responsible for the development of tools and processes used to implementeditorial streamEditorial Stream policies, in the absence of an RFC with specific requirements. The RPC is responsible for detailed technical specifications, forexampleexample, specific details of text or graphical formats or XML grammar. The RPC may designate a team of volunteers and/or employees who implement these operational decisions. The RPC is expected to solicit input from experts and community members when making implementation decisions. The RPC is required to document implementation decisions in a publicly available place, preferably with rationale.</t> <t>If the RPC has questions about how to interpret policy in EditorialstreamStream documents, they should ask the RSAB for guidance in interpreting that policy per the process described in <xref target="resolution"/>.</t> </blockquote> </section> <sectionanchor="conflict-resolution"><name>Conflictanchor="conflict-resolution"> <name>Conflict Resolution for Implementation Decisions</name> <t><xref target="resolution"/> provides a pathway for resolution of conflicts between the RPC and the author(s) of a specific document. No appeal pathway is given for resolution of issues that may occur when a conflict arises with an implementation decision that applies to the entire editorial process (not just one document).</t> <t>The paragraph below is reflected in <xref target="resolution"/> of this document:</t> <blockquote> <t>If the RPC is responsible for interpreting policy decisions at both the document and editorial process tooling level, conflicts on either level will involve interpretation of written policy (or theacknowledgementacknowledgment that policy does not exist to cover a given situation). In any case, the conflict resolution will now use the same path of appeal: to the RSAB.</t><t>The paragraph above</blockquote> </section> <section anchor="rfc-consumers"> <name>RFC Consumers</name> <t>This text isnowreflected in <xreftarget="resolution"/> intarget="rfc-consumers-definition"/> of thisdocument.</t> </section> <section anchor="rfc-consumers"><name>RFC Consumers</name>document:</t> <blockquote> <t>The IETF mission statement <xref target="RFC3935"/> is clear that the documents it produces are intended to be consumed by anyone who wishes to implement an IETF protocol or operational recommendation:</t> <ulempty="true"><li>empty="true"> <li> <t>to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to make the Internet work better.</t></li></ul></li> </ul> <t><xref target="intent"/> introduces the term "consumers of RFCs", referring to them as "constituent stakeholders" who should be considered by the RSAB when approving Editorial Stream policy documents.</t> <t>"Consumers of RFCs" is now defined to mean those people who read RFCs to understand, implement, critique, and research the protocols, operationalpracticespractices, and othercontent,content as found in RFCs.</t> <t>The policy to be followed by the RFC publication streams and RFC Editor in respectofto consumers of RFCs is as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Consumers of RFCsMUST<bcp14>MUST</bcp14> be considered asaseparate constituentstakeholderstakeholders from IETF/IRTF participants. While IETF/IRTF participants and others involved in the development and production of RFCs may be consumers of RFCs, the two are distinct, overlapping sets.</t> </li> <li> <t>The <eref target="https://www.rfc-editor.org">RFC Editor website</eref>MUST<bcp14>MUST</bcp14> be primarily focused on consumers of RFCs.</t> </li> <li> <t>Consumers of RFCsMUST NOT<bcp14>MUST NOT</bcp14> be required or expected to become IETF/IRTF participants unless they wish to extend, update, or modify an RFC.</t></list></t> <t>This text is now reflected in <xref target="rfc-consumers-definition"/>.</t></li> </ul> </blockquote> </section> </section> <sectionanchor="updates-from-rfc-formats-and-versions"><name>Updatesanchor="updates-to-rfc-9720"> <name>Updates to RFC 9720</name> <!--[rfced] This document updates RFC 9720. Will this sentence be clear to readers as is, or should the "updates" text be restated here for clarity? Also, we updated the section title as shown below (i.e., we used "to" rather than "from" and the RFC number rather than title) to align with other section titles in the document. Let us know any concerns. Current: 1.3. Updates from "RFC Formats andVersions"</name>Versions" [RFC9720], "RFC Formats and Versions", updated [RFC9280]. Perhaps: 1.3. Updates to RFC 9720 [RFC9720], "RFC Formats and Versions", updates [RFC9280]. This document updates [RFC9720]. --> <t><xref target="RFC9720"/>, "RFC Formats and Versions", updatedRFC 9280.</t><xref target="RFC9280"/>.</t> <sectionanchor="reissued"><name>RFCsanchor="reissued"> <name>RFCs May Be Reissued</name> <t><xreftarget="stability"/> in RFC 9280section="7.6" sectionFormat="of" target="RFC9280"/> says:</t><ul empty="true"><li><blockquote> <t>Once published, RFC Series documents are not changed.</t></li></ul></blockquote> <t>That sentence is replaced in <xref target="stability"/> of this document with:</t><ul empty="true"><li><blockquote> <t>Once published, RFCs may be reissued, but the semantic content of publication versions shall be preserved to the greatest extentpossible.</t> </li></ul>possible, as described in <xref section="2.2" sectionFormat="of" target="RFC9720"/>.</t> </blockquote> </section> <sectionanchor="consistency-policy"><name>Consistencyanchor="consistency-policy"> <name>Consistency Policy</name> <t>A new policyinis added to <xref target="historical"/> of thisdocument was added:</t> <ul empty="true"><li>document:</t> <blockquote> <t>7.8. Consistency</t> <t>RFCs are copyedited, formatted, and then published. They may be reissued to maintain a consistent presentation.</t></li></ul></blockquote> </section> </section> <sectionanchor="purview"><name>Purviewanchor="purview"> <name>Purview of the RSWG and RSAB</name> <t><xreftarget="policy-definiion"/>target="policy-definition"/> says:</t><ul empty="true"><li><blockquote> <t>Policies under the purview of the RSWG and RSAB might include, but are not limited to, document formats, processes for publication and dissemination of RFCs, and overall management of the RFC Series.</t></li></ul></blockquote> <t>The following is addedinto <xref target="policy-definition"/> of this document immediately following that sentence:</t><ul empty="true"><li><blockquote> <t>Such policies will not include detailed technical specifications, forexampleexample, specific details of text or graphical formats or XML grammar. Such matters will be decided and documented by the RPC along with its other working practices, as discussed in <xref target="working-practices"/>, with community consultation as for other tools and services supported by the IETF LLC <xreftarget="RFC8711"/>."</t> </li></ul>target="RFC8711"/>.</t> </blockquote> <!-- [rfced] FYI: Since RFC 7990 has been removed from this document, we have updated the title of Section 1.5 accordingly. Original: 1.5 Updates to RFCs 7990 through 7997 Current: 1.5 Updates to RFCs 7991 through 7997 --> </section> <sectionanchor="updates-to-rfcs-7990-through-7997"><name>Updatesanchor="updates-to-rfcs-7991-through-7997"> <name>Updates to RFCs79907991 through 7997</name> <t>All instances of "RFC Editor" or "RFC Series Editor" in <xreftarget="RFC7990"/>, <xreftarget="RFC7991"/>, <xref target="RFC7992"/>, <xref target="RFC7993"/>, <xref target="RFC7994"/>, <xref target="RFC7995"/>, <xref target="RFC7996"/>, and <xref target="RFC7997"/> are replaced by "RFC Production Center (RPC)".</t> </section> <sectionanchor="rewording-to-obsolete-rfc-9280"><name>Rewordinganchor="rewording-to-obsolete-rfc-9280"> <name>Rewording to Obsolete RFC 9280</name> <t>Many parts of <xref target="RFC9280"/> talked about changes to be made. Because this document obsoletes <xref target="RFC9280"/>, these parts were updated to indicate that the changes were made.</t> </section> </section> <sectionanchor="overview"><name>Overviewanchor="overview"> <name>Overview of the Model</name> <t>This document divides the responsibilities for the RFC Series into two high-level tasks:</t><t><list style="numbers" type="1"><ol spacing="normal" type="1"><li> <t>Policy definition governing the RFC Series as a whole. This is the joint responsibility of two entities. First, the RFC Series Working Group (RSWG) is an open working group independent of the IETF that generates policy proposals. Second, the RFC Series Approval Board (RSAB) is an appointed body that approves such proposals for publication in the Editorial Stream. The RSAB includes representatives of the streams <xref target="RFC8729"/> as well as an expert in technical publishing, the RFC Series Consulting Editor (RSCE).</t> </li> <li> <t>Policy implementation through publication of RFCs in all of the streams that form the RFC Series. This is primarily the responsibility of the RFC Production Center (RPC) as contractually overseen by the IETF Administration Limited Liability Company (IETF LLC) <xref target="RFC8711"/>.</t></list></t></li> </ol> <t>As described more fully in the remainder of this document, the core activities and responsibilities are as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The RSWG proposes policies that govern the RFC Series as a whole, with input from the community, the RSAB, and the RSCE.</t> </li> <li> <t>The RSAB considers those proposals and either approves them or returns them to the RSWG, which may make further changes or remove them from further consideration.</t> </li> <li> <t>If approved, such proposals are published as RFCs in the Editorial Stream and thus define the policies to be followed by the RSWG, RSAB, RSCE, and RPC.</t> </li> <li> <t>The RSCE provides expert advice to the RPC and RSAB on how to implement established policies on an ongoing and operational basis, which can include raising issues or initiating proposed policy changes within the RSWG.</t> </li> <li> <t>The RPC implements the policies defined by the Editorial Stream in its day-to-day editing and publication of RFCs from all of the streams.</t> </li> <li> <t>If issues arise with the implementation of particular policies, the RPC brings those issues to the RSAB, which interprets the policies and provides interim guidance to the RPC, informing the RSWG of those interpretations.</t></list></t></li> </ul> <t>This model is designed to ensure public processes and policy documents, clear lines of responsibility and authority, transparent mechanisms for updates and changes to policies governing the RFC Series as a whole, and effective operational implementation of the RFC Series, thus meeting the requirements specified inSection 4 of<xref section="4" sectionFormat="of" target="RFC8729"/>.</t> <t>The remainder of this document describes the model in greater detail.</t> </section> <sectionanchor="policy-definiion"><name>Policyanchor="policy-definition"> <name>Policy Definition</name> <t>Policies governing the RFC Series as a whole are defined through the following high-level process:</t><t><list style="numbers" type="1"><ol spacing="normal" type="1"><li> <t>Proposals must be submitted to, adopted by, and discussed within the RFC Series Working Group (RSWG).</t> </li> <li> <t>Proposals must pass a Last Call for comments in the working group and a community call for comments (see <xref target="calls"/>).</t> </li> <li> <t>Proposals must be approved by the RFC Series Approval Board (RSAB).</t></list></t></li> </ol> <t>Policies under the purview of the RSWG and RSAB might include, but are not limited to, document formats, processes for publication and dissemination of RFCs, and overall management of the RFC Series.</t> <t>(The text in the next paragraph is added by <xreftarget="purview"/>)</t>target="purview"/>.)</t> <t>Such policies will not include detailed technical specifications, forexampleexample, specific details of text or graphical formats or XML grammar. Such matters will be decided and documented by the RPC along with its other working practices, as discussed in <xref target="working-practices"/>, with community consultation as for other tools and services supported by the IETF LLC <xref target="RFC8711"/>.</t> <sectionanchor="structure-and-roles"><name>Structureanchor="structure-and-roles"> <name>Structure and Roles</name> <sectionanchor="rfc-series-working-group-rswg"><name>RFCanchor="rfc-series-working-group-rswg"> <name>RFC Series Working Group (RSWG)</name> <sectionanchor="purpose"><name>Purpose</name>anchor="purpose"> <name>Purpose</name> <t>The RFC Series Working Group (RSWG) is the primary venue in which members of the community collaborate regarding the policies that govern the RFC Series.</t> </section> <sectionanchor="rswg-participation"><name>Participation</name>anchor="rswg-participation"> <name>Participation</name> <t>All interested individuals are welcome to participate in the RSWG; participants are subject to anti-harassment policies as described in <xref target="anti-h"/>. This includes but is not limited to participants in the IETF and IRTF, members of the IAB and IESG, developers of software or hardware systems that implement RFCs, authors of RFCs and Internet-Drafts, developers of tools used to author or edit RFCs and Internet-Drafts, individuals who use RFCs in procurement decisions, scholarly researchers, and representatives of standards development organizations other than the IETF and IRTF. The IETF LLC Board members, staff and contractors (especially representatives of the RFC Production Center), and the IETF Executive Director are invited to participate as community members in the RSWG to the extent permitted by any relevant IETF LLC policies. Members of the RSAB are also expected to participate actively.</t> </section> <sectionanchor="chairs"><name>Chairs</name>anchor="chairs"> <name>Chairs</name> <t>The RSWG has two chairs, one appointed by the IESG and the other appointed by the IAB. The IESG and IABdeterminesdetermine their own processes for making these appointments, making sure to take account of any potential conflicts of interest. Community members who have concerns about the performance of an RSWG Chair should direct their feedback to the appropriate appointing body. The IESG and IAB may remove their appointed chairs at their discretion at any time andtoname a replacement who shall serve the remainder of the original chair's term.</t> <t>It is the responsibility of the chairs to encourage rough consensus within the RSWG and to follow that consensus in their decision making, for instance, regarding acceptance of new proposals and advancement of proposals to the RSAB.</t> </section> <sectionanchor="mode-of-operation"><name>Modeanchor="mode-of-operation"> <name>Mode of Operation</name> <t>The intent is that the RSWG shall operate in a way similar to that of working groups in the IETF. Therefore, all RSWG meetings and discussion venues shall be open to all interested individuals, and all RSWG contributions shall be subject to intellectual property policies, which must be consistent with those of the IETF as specified in <xref target="BCP78"/> and <xref target="BCP79"/>.</t> <t>All discussions in the RSWG shall take place on an open email discussion list, which shall be publicly archived.</t><t>The<!-- [rfced] The URL in this paragraph redirects to this URL: https://datatracker.ietf.org/group/iesg/statements/. Is this the intended page this URL is meant to point to or is an update needed? Note that there are four links titled "Guidance on Face-to-Face and Virtual Interim Meetings" at the redirected URL, but they have all been superseded. Current: The RSWG is empowered to hold in-person, online-only, or hybrid meetings, which should be announced with sufficient notice to enable broad participation; the IESG Guidance on Face-to-Face and Virtual Interim Meetings(https://www.ietf.org/about/groups/iesg/statements/ interim-meetings-guidance-2016-01-16/)(https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/) provides a reasonable baseline. In-person meetings should include provision for effective online participation for those unable to attend in person. --> <t>The RSWG is empowered to hold in-person, online-only, or hybrid meetings, which should be announced with sufficient notice to enable broad participation; the <eref target="https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance-2016-01-16/">IESG Guidance on Face-to-Face and Virtual Interim Meetings</eref> provides a reasonable baseline. In-person meetings should include provision for effective online participation for those unable to attend in person.</t> <t>The RSWG shall operate by rough consensus, a mode of operation informally described in <xref target="RFC2418"/>.</t> <t>The RSWG may decide by rough consensus to use additional tooling (e.g., GitHub as specified in <xref target="RFC8874"/>), forms of communication, and working methods (e.g., design teams) as long as they are consistent with this document and with <xref target="RFC2418"/> or its successors.</t> <t>Absent specific guidance in this document regarding the operation of the RSWG, the general guidance provided inSection 6 of<xref section="6" sectionFormat="of" target="RFC2418"/> should be considered appropriate.</t> <!--[rfced] Section 3.1.1.4. Is "requested to provide" correct as is, or should it perhaps be "shall provide"? Note that there is a similar instance of this text in Section 3.1.2.6. Original: The IETF LLC is requested to provide necessary tooling to support RSWG communication, decision processes, and policies. Perhaps: The IETF LLC shall provide the necessary tooling to support RSWG communication, decision processes, and policies. --> <t>The IETF LLC is requested to provide necessary tooling to support RSWG communication, decision processes, and policies.</t> </section> </section> <sectionanchor="rfc-series-approval-board-rsab"><name>RFCanchor="rfc-series-approval-board-rsab"> <name>RFC Series Approval Board (RSAB)</name> <sectionanchor="rsab-purpose"><name>Purpose</name>anchor="rsab-purpose"> <name>Purpose</name> <t>The RFC Series Approval Board (RSAB), which includes representatives of all of the streams, shall act as the approving body for proposals generated within the RSWG, thus providing an appropriate set of checks and balances on the output of the RSWG. The onlypolicy- makingpolicy-making role of the RSAB is to review policy proposals generated by the RSWG; it shall have no independent authority to formulate policy on its own. It is expected that the RSAB will respect the rough consensus of the RSWG wherever possible, without ceding its responsibility to review RSWG proposals, as further described in <xref target="workflow"/>.</t> </section> <sectionanchor="rsab-members"><name>Members</name>anchor="rsab-members"> <name>Members</name> <t>The RSAB consists primarily of the following voting members:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>A stream representative for the IETF Stream: either an IESG member or someone appointed by the IESG</t> </li> <li> <t>A stream representative for the IAB Stream: either an IAB member or someone appointed by the IAB</t> </li> <li> <t>A stream representative for the IRTF Stream: either the IRTF Chair or someone appointed by the IRTF Chair</t> </li> <li> <t>A stream representative for the Independent Stream: either the Independent Submissions Editor (ISE) <xref target="RFC8730"/> or someone appointed by the ISE</t> </li> <li> <t>The RFC Series Consulting Editor (RSCE)</t></list></t></li> </ul> <t>If and when a new stream is created, the document that creates the stream shall specify if a voting member representing that stream shall also be added to the RSAB, along with any rules and processes related to that representative (e.g., whether the representative is a member of the body responsible for the stream or an appointed delegate thereof).</t> <t>The RFC Series Consulting Editor (RSCE) is a voting member of the RSAB but does not act as a representative of the Editorial Stream.</t> <t>To ensure the smooth operation of the RFC Series, the RSAB shall include the following non-voting, ex officio members:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The IETF Executive Director or their delegate (the rationale is that the IETF LLC is accountable for implementation of policies governing the RFC Series)</t> </li> <li> <t>A representative of the RPC, named by the RPC (the rationale is that the RPC is responsible for implementation of policies governing the RFC Series)</t></list></t></li> </ul> <t>In addition, the RSAB may include other non-voting members at its discretion; these non-voting members may be ex officio members or liaisons from groups or organizations with which the RSAB deems it necessary to formally collaborate or coordinate.</t> </section> <sectionanchor="appointment-and-removal-of-voting-members"><name>Appointmentanchor="appointment-and-removal-of-voting-members"> <name>Appointment and Removal of Voting Members</name> <t>The appointing bodies (i.e., IESG, IAB, IRTF Chair, and ISE) shall determine their own processes for appointing RSAB members (note that processes related to the RSCE are described in <xref target="rsce"/>). Each appointing body shall have the power to remove its appointed RSAB member at its discretion at any time. Appointing bodies should ensure that voting members are seated at all times and should fill any vacancies with all due speed, if necessary on a temporary basis.</t> <t>In the case that the IRTF Chair or ISE is incapacitated or otherwise unable to appoint another person to serve as a delegate, the IAB (as the appointing body for the IRTF Chair and ISE) shall act as the temporary appointing body for those streams and shall appoint a temporary member of the RSAB until the IAB has appointed an IRTF Chair or ISE, who can then act as an RSAB member or appoint a delegate through normal processes.</t> </section> <sectionanchor="vacancies"><name>Vacancies</name>anchor="vacancies"> <name>Vacancies</name> <t>In the case of vacancies by voting members, the RSAB shall operate as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Activities related to implementation of policies already in force shall continue as normal.</t> </li> <li> <t>Voting on approval of policy documents produced by the RSWG shall be delayed until the vacancy or vacancies have been filled, up to a maximum of three (3) months. If a further vacancy arises during this three-month period, the delay should be extended by up to another three months. After the delay period expires, the RSAB should continue to process documents as described below. Note that this method of handling vacancies does not apply to a vacancy of the RSCE role; it only applies to vacancies of the stream representatives enumerated in <xref target="rsab-members"/>.</t></list></t></li> </ul> </section> <sectionanchor="chair"><name>Chair</name>anchor="chair"> <name>Chair</name> <t>The RSAB shall annually choose a chair from among its members using a method of its choosing. If the chair position is vacated during the chair's term, the RSAB chooses a new chair from among its members.</t> </section> <sectionanchor="mode-of-operation-1"><name>Modeanchor="mode-of-operation-1"> <name>Mode of Operation</name> <t>The RSAB is expected to operate via an email discussion list,in- personin-person meetings, teleconferencing systems, and any additional tooling it deems necessary.</t> <t>The RSAB shall keep a public record of its proceedings, including minutes of all meetings and a record of all decisions. The primary email discussion list used by the RSAB shall be publicly archived, although topics that require confidentiality (e.g., personnel matters) may be omitted from such archives or discussed in private. Similarly, meeting minutes may exclude detailed information about topics discussed under executive session but should note that such topics were discussed.</t> <t>The RSAB shall announce plans and agendas for their meetings on the RFC Editor website and by email to the RSWG at least a week before such meetings. The meetings shall be open for public attendance, and the RSAB may consider allowing open participation. If the RSAB needs to discuss a confidential matter in executive session, that part of the meeting shall be private to the RSAB, but it must be noted on the agenda and documented in the minutes with as much detail as confidentiality requirements permit.</t> <t>The IETF LLC is requested to provide necessary tooling and staff to support RSAB communication, decision processes, and policies.</t> <t>The IAB convened the RSAB in 2022 in order to formalize the IAB's transfer of authority over the RFC Editor Model.</t> </section> </section> </section> <sectionanchor="process"><name>Process</name>anchor="process"> <name>Process</name> <t>This section specifies the RFC Series Policy Definition Process, which shall be followed in producing all Editorial Stream RFCs.</t> <sectionanchor="intent"><name>Intent</name>anchor="intent"> <name>Intent</name> <t>The intent is to provide an open forum by which policies related to the RFC Series are defined and evolved. The general expectation is that all interested parties will participate in the RSWG and that only under extreme circumstances should RSAB members need to hold CONCERN positions (as described in <xref target="workflow"/>).</t> <t>Because policy issues can be difficult and contentious, RSWG participants and RSAB members are strongly encouraged to work together in a spirit of good faith and mutual understanding to achieve rough consensus (see <xref target="RFC2418"/>). In particular, RSWG members are encouraged to take RSAB concerns seriously, and RSAB members are encouraged to clearly express their concerns early in the process and to be responsive to the community. All parties are encouraged to respect the value of each stream and the long-term health and viability of the RFC Series.</t> <t>This process is intended to be one of continuous consultation. RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis, so that when the time comes to consider the approval of a proposal, there should be no surprises. Appointing bodies are expected to establish whatever processes they deem appropriate to facilitate this goal.</t> </section> <sectionanchor="workflow"><name>Workflow</name>anchor="workflow"> <name>Workflow</name> <t>The following process shall be used to formulate or modify policies related to the RFC Series:</t><t><list style="numbers" type="1"><ol spacing="normal" type="1"><li> <t>An individual or set of individuals generates a proposal in the form of an Internet-Draft (which must be submitted in full conformance with the provisions of <xref target="BCP78"/> and <xref target="BCP79"/>) and asks the RSWG to adopt the proposal as a working group item.</t> </li> <li> <t>The RSWG may adopt the proposal as a working group item if the chairs determine (by following working group procedures for rough consensus) that there is sufficient interest in the proposal; this is similar to the way a working group of the IETF would operate (see <xref target="RFC2418"/>).</t> </li> <li> <t>The RSWG shall then further discuss and develop the proposal. All participants, but especially RSAB members, should pay special attention to any aspects of the proposal that have the potential to significantly modify long-standing policies or historical characteristics of the RFC Series as described in <xref target="historical"/>. Members of the RSAB are expected to participate as individuals in all discussions relating to RSWG proposals. This should help to ensure that they are fully aware of proposals early in the RFC Series Policy Definition Process. It should also help to ensure that RSAB members will raise any issues or concerns during the development of the proposal and not wait until the RSAB review period. The RSWG Chairs are also expected to participate as individuals.</t> </li> <li> <t>At some point, if the RSWG Chairs believe there may be rough consensus for the proposal to advance, they will issue a Last Call for comments within the working group.</t> </li> <li> <t>After a comment period of suitable length, the RSWG Chairs will determine whether rough consensus for the proposal exists (taking their own feedback as individuals into account along with feedback from other participants). If comments have been received and substantial changes have been made, additional Last Calls may be necessary. Once the chairs determine that consensus has been reached, they shall announce their determination on the RSWG email discussion list and forward the document to the RSAB.</t> </li> <li> <t>Once consensus is established in the RSWG, the RSAB shall issue a community call for comments as further described in <xref target="calls"/>. If substantial comments are received in response to the community call for comments, the RSAB may return the proposal to the RSWG to consider those comments and make revisions to address the feedback received. In parallel with the community call for comments, the RSAB itself shall also consider the proposal.</t> </li> <li> <t>If the scope of the revisions made in the previous step is substantial, an additional community call for comments should be issued by the RSAB, and the feedback received should be considered by the RSWG.</t> </li> <li> <t>Once the RSWG Chairs confirm that concerns received during the community call(s) for comments have been addressed, they shall inform the RSAB that the document is ready for balloting by the RSAB.</t> </li> <li> <t>Within a reasonable period of time, the RSAB will poll its members for their positions on the proposal. Positions may be as follows:<list style="symbols"></t> <ul spacing="normal"> <li> <t>YES: the proposal should be approved</t> </li> <li> <t>CONCERN: the proposal raises substantial concerns that must be addressed</t> </li> <li> <t>RECUSE: the person holding the position has a conflict of interest</t></list></li> </ul> <t> Any RSAB member holding a CONCERN position must explain their concern to the community in detail. Nevertheless, the RSWG might not be able to come to consensus on modifications that will address the RSAB member's concern.<vspace blankLines='1'/></t> <t> There are three reasons why an RSAB member may file a position of CONCERN:<list style="symbols"></t> <ul spacing="normal"> <li> <t>The RSAB member believes that the proposal represents a serious problem for one or more of the individual streams.</t> </li> <li> <t>The RSAB member believes that the proposal would cause serious harm to the overall RFC Series, including harm to the long-term health and viability of the Series.</t> </li> <li> <t>The RSAB member believes, based on the results of the community call(s) for comments (<xref target="calls"/>), that rough consensus to advance the proposal is lacking.</t></list></li> </ul> <t> Because RSAB members are expected to participate in the discussions within the RSWG and to raise any concerns and issues during those discussions, most CONCERN positions should not come as a surprise to the RSWG. Notwithstanding, late CONCERN positions are always possible if issues are identified during RSAB review or the community call(s) for comments.</t> </li> <li> <t>If a CONCERN exists, discussion will take place within the RSWG. Again, all RSAB members are expected to participate. If substantial changes are made in order to address CONCERN positions, an additional community call for comments might be needed.</t> </li> <li> <t>A proposal without any CONCERN positions is approved.</t> </li> <li> <t>If, after a suitable period of time, any CONCERN positions remain, a vote of the RSAB is taken. If at least three voting members vote YES, the proposal is approved.</t> </li> <li> <t>If the proposal is not approved, it is returned to the RSWG. The RSWG can then consider making further changes.</t> </li> <li> <t>If the proposal is approved, a notification is sent to the community, and the document enters the queue for publication as an RFC within the Editorial Stream.</t> </li> <li> <t>Policies may take effect immediately upon approval by the RSAB and before publication of the relevant RFC, unless they are delayed while the IETF LLC resolves pending resource or contract issues.</t></list></t></li> </ol> </section> <sectionanchor="calls"><name>Communityanchor="calls"> <name>Community Calls for Comment</name> <t>The RSAB is responsible for initiating and managing community calls for comments on proposals that have gained consensus within the RSWG. The RSAB should actively seek a wide range of input. The RSAB seeks such input by, at a minimum, sending a notice to therfc-interest@rfc-editor.org (mailto:rfc-interest@rfc-editor.org)<eref target="mailto:rfc-interest@rfc-editor.org">rfc-interest@rfc-editor.org</eref> email discussion list or to its successor or future equivalent. RSAB members should also send a notice to the communities they directly represent (e.g., the IETF and IRTF). Notices are also to be made available and archived on the RFC Editor website. In addition, other communication channels can be established for notices (e.g., via an RSS feed or by posting to social media venues).</t> <t>In cases where a proposal has the potential to significantly modify long-standing policies or historical characteristics of the RFC Series as described in <xref target="historical"/>, the RSAB should take extra care to reach out to a very wide range of communities that make use of RFCs (as described in <xref target="rswg-participation"/>) since such communities might not be actively engaged in the RSWG directly. The RSAB should work with the stream approving bodies and the IETF LLC to identify and establish contacts in such communities, assisted by the RSCE in particular.</t> <t>The RSAB should maintain a public list of communities that are contacted during calls for comments.</t> <t>A notice of a community call for comments contains the following:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>A subject line beginning with 'Call for Comments:'</t> </li> <li> <t>A clear, concise summary of the proposal</t> </li> <li> <t>A URL pointing to the Internet-Draft that defines the proposal</t> </li> <li> <t>Any explanations or questions for the community that the RSAB deems necessary (using their usual decision-making procedures)</t> </li> <li> <t>Clear instructions on how to provide public comments</t> </li> <li> <t>A deadline for comments</t></list></t></li> </ul> <t>A comment period will last not less than two weeks and should be longer if wide outreach is required. Comments will be publicly archived on the RFC Editor website.</t> <t>The RSAB is responsible for considering comments received during a community call for comments. If RSAB members conclude that such comments raise important issues that need to be addressed, they should do so by discussing those issues within the RSWG or (if the issues meet the criteria specified in Step 9 of <xref target="workflow"/>) lodging a position of CONCERN during RSAB balloting.</t> </section> <sectionanchor="appeals"><name>Appeals</name>anchor="appeals"> <name>Appeals</name> <t>Appeals of RSWG Chair decisions shall be made to the RSAB. Decisions of the RSWG Chairs can be appealed only on grounds of failure to follow the correct process. Appeals should be made within thirty (30) days of any action or, in the case of failure to act, of notice having been given to the RSWG Chairs. The RSAB will then decide if the process was followed and will direct the RSWG Chairs as to what procedural actions are required.</t> <t>Decisions of the RSAB can be appealed on grounds of failure to follow the correct process. In addition, if the RSAB makes a decision in order to resolve a disagreement between authors and the RPC (as described in <xref target="resolution"/>), appeals can be filed on the basis that the RSAB misinterpreted an approved policy. Aside from these two cases, disagreements about the conduct of the RSAB are not subject to appeal. Appeals of RSAB decisions shall be made to the IAB and should be made within thirty (30) days of public notice of the relevant RSAB decision (typically, when minutes are posted). The IAB shall decide whether a process failure occurred and what (if any) corrective action should take place.</t> </section> <sectionanchor="anti-h"><name>Anti-Harassmentanchor="anti-h"> <name>Anti-Harassment Policy</name> <t>TheIETF<eref target="https://www.ietf.org/about/groups/iesg/statements/anti-harassment-policy/">IETF anti-harassmentpolicy (https://www.ietf.org/about/groups/iesg/statements/anti-harassment- policy/)policy</eref> also applies to the RSWG and RSAB, which strive to create and maintain an environment in which people of many different backgrounds are treated with dignity, decency, and respect. Participants are expected to behave according to professional standards and to demonstrate appropriate workplace behavior. For further information about these policies, see <xref target="RFC7154"/>, <xref target="RFC7776"/>, and <xref target="RFC8716"/>.</t> </section> <sectionanchor="rfc-boilerplates"><name>RFCanchor="rfc-boilerplates"> <name>RFC Boilerplates</name> <t>RFC boilerplates (see <xref target="RFC7841"/>) are part of the RFC Style Guide, as defined in <xref target="working-practices"/>. New or modified boilerplates considered under version 3 of the RFC Editor Model must be approved by the following parties, each of which has a separate area of responsibility with respect to boilerplates:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The applicable stream, which approves that the boilerplate meets its needs</t> </li> <li> <t>The RSAB, which approves that the boilerplate is not in conflict with the boilerplate used in the other streams</t> </li> <li> <t>The RPC, which approves that the language of the boilerplate is consistent with the RFC Style Guide</t> </li> <li> <t>The IETF Trust, which approves that the boilerplate correctly states the Trust's position regarding rights and ownership</t></list></t></li> </ul> </section> </section> <sectionanchor="rfc-consumers-definition"><name>RFCanchor="rfc-consumers-definition"> <name>RFC Consumers</name> <t>(The text in this section is added by <xreftarget="rfc-consumers"/>)</t>target="rfc-consumers"/>.)</t> <t>The IETF mission statement <xref target="RFC3935"/> is clear that the documents it produces are intended to be consumed by anyone who wishes to implement an IETF protocol or operational recommendation:</t><ul empty="true"><li><blockquote> <t>to produce high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet in such a way as to make the Internet work better.</t></li></ul></blockquote> <t><xref target="intent"/> introduces the term "consumers of RFCs", referring to them as "constituent stakeholders" who should be considered by the RSAB when approving Editorial Stream policy documents.</t> <t>"Consumers of RFCs" is now defined to mean those people who read RFCs to understand, implement, critique, and research the protocols, operationalpracticespractices, and othercontent,content as found in RFCs.</t><t>The<!-- [rfced] Is "RFC Editor" correct here, or should it be updated to "RFC Editor function" or something else? Original: The policy to be followed by the RFC publication streams and RFC Editor in respect of consumers of RFCs is as follows: --> <t>The policy to be followed by the RFC publication streams and RFC Editor in respect to consumers of RFCs is as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Consumers of RFCsMUST<bcp14>MUST</bcp14> be considered asaseparate constituentstakeholderstakeholders from IETF/IRTF participants. While IETF/IRTF participants and others involved in the development and production of RFCs may be consumers of RFCs, the two are distinct, overlapping sets.</t> </li> <li> <t>The <eref target="https://www.rfc-editor.org">RFC Editor website</eref>MUST<bcp14>MUST</bcp14> be primarily focused on consumers of RFCs.</t> </li> <li> <t>Consumers of RFCsMUST NOT<bcp14>MUST NOT</bcp14> be required or expected to become IETF/IRTF participants unless they wish to extend, update, or modify an RFC.</t></list></t></li> </ul> </section> </section> <sectionanchor="policy-implementation"><name>Policyanchor="policy-implementation"> <name>Policy Implementation</name> <sectionanchor="roles-and-processes"><name>Rolesanchor="roles-and-processes"> <name>Roles and Processes</name> <t>Publication of RFCs is handled by the RFC Production Center (RPC).</t> <t>A few general considerations apply:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The general roles and responsibilities of the RPC are defined by RFCs published in the Editorial Stream (i.e., not directly by the RSWG, RSAB, or RSCE), by existing RFCs that apply to the RPC and have not yet been superseded by Editorial Stream RFCs, and by the requisite contracts.</t> </li> <li> <t>The RPC is advised by the RSCE and RSAB, and it has a duty to consult with them under specific circumstances, such as those relating to disagreements between authors and the RPC as described in <xref target="resolution"/>.</t> </li> <li> <t>The RPC is overseen by the IETF LLC to ensure that it performs in accordance with contracts in place.</t></list></t></li> </ul> <t>All matters of budget, timetable, and impact on its performance targets are between the RPC and IETF LLC.</t> <t>The RPC shall regularly provide reports to the IETF LLC, RSAB, RSWG, and broader community regarding its activities and any key risks or issues affecting it.</t> <t>In the event that the RPC is required to make a decision without consultation that would normally deserve consultation, or makes a decision against the advice of the RSAB, the RPC must notify the RSAB.</t> <t>This document does not specify the exact relationship between the IETF LLC and the RPC; for example, the work of the RPC could be performed by a separate corporate entity under contract to the IETF LLC, it could be performed by employees of the IETF LLC, or the IETF LLC could engage with independent contractors for some or all aspects of such work. The exact relationship is a matter for the IETF LLC to determine.</t> <t>The IETF LLC is responsible for the method and management of the engagement of the RPC. Therefore, the IETF LLC has authority over negotiating performance targets for the RPC and also has responsibility for ensuring that those targets are met. Such performance targets are set based on the RPC's publication load and additional efforts required to implement policies specified in Editorial Stream RFCs, in existing RFCs that apply to the RPC and have not yet been superseded by Editorial Stream RFCs, and in the requisite contracts. The IETF LLC may consult with the community regarding these targets. The IETF LLC is empowered to appoint a manager or to convene a committee to complete these activities.</t> <t>If individuals or groups within the community have concerns about the performance of the RPC, they can request that the matter be investigated by the IETF LLC Board, the IETF Executive Director, or a point of contact designated by the IETF LLC Board. Even if the IETF LLC opts to delegate this activity, concerns should be raised with the IETF LLC. The IETF LLC is ultimately answerable to the community via the mechanisms outlined in <xref target="RFC8711"/>.</t> </section> <sectionanchor="working-practices"><name>Workinganchor="working-practices"> <name>Working Practices</name> <t>In the absence of a high-level policy documented in an RFC or in the interest of specifying the detail of its implementation of such policies, the RPC can document working practices regarding the editorial preparation, final publication, and dissemination of RFCs. Examples include:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Maintenance of a style guide that defines editorial standards for RFCs; specifically, the RFC Style Guide consists of <xref target="RFC7322"/> and the other documents and resources listed at <xref target="STYLEGUIDE"/>.</t> </li> <li> <t>Instructions regarding the file formats that are accepted as input to the editing and publication process.</t> </li> <li> <t>Guidelines regarding the final structure and layout of published documents. In the context of the XML vocabulary <xref target="RFC7991"/>, such guidelines could include clarifications regarding the preferred XML elements and attributes used to capture the semantic content of RFCs.</t></list></t></li> </ul> </section> <sectionanchor="rpc-responsibilites"><name>RPCanchor="rpc-responsibilities"> <name>RPC Responsibilities</name> <t>The core responsibility of the RPC is the implementation of RFC Series policies through publication of RFCs (including the dimensions of document quality, timeliness of publication, and accessibility of results), while taking into account issues raised by the community through the RSWG and by the stream approving bodies. More specifically, the RPC's responsibilities at the time of writing include the following:</t><t><list style="numbers" type="1"><ol spacing="normal" type="1"><li> <t>Editing documents originating from all RFC streams to ensure that they are consistent with the editorial standards specified in the RFC Style Guide.</t> </li> <li> <t>Creating and preserving records of edits performed on documents.</t> </li> <li> <t>Identifying where editorial changes might have technical impact and seeking necessary clarification.</t> </li> <li> <t>Establishing the publication readiness of each document through communication with the authors, IANA, or stream-specific contacts, supplemented if needed by the RSAB and RSCE.</t> </li> <li> <t>Creating and preserving records of dialogue with document authors.</t> </li> <li> <t>Requesting advice from the RSAB and RSCE as needed.</t> </li> <li> <t>Providing suggestions to the RSAB and RSCE as needed.</t> </li> <li> <t>Participating within the RSWG in the creation of new Editorial Stream RFCs that impact the RPC, specifically with respect to any challenges the RPC might foresee with regard to implementation of proposed policies.</t> </li> <li> <t>Identifying topics and issues while processing documents or carrying out other responsibilities on this list for which they lack sufficient expertise, and identifying and conferring with relevant experts as needed.</t> </li> <li> <t>Providing reports to the community on its performance and plans.</t> </li> <li> <t>Consulting with the community on its plans.</t> </li> <li> <t>Negotiating its specific plans and resources with the IETF LLC.</t> </li> <li> <t>Providing sufficient resources to support reviews of RPC performance by the IETF LLC.</t> </li> <li> <t>Coordinating with IANA to ensure that RFCs accurately document registration processes and assigned values for IANA registries.</t> </li> <li> <t>Assigning RFC numbers.</t> </li> <li> <t>Liaising with stream approving bodies and other representatives of the streams as needed.</t> </li> <li> <t>Publishing RFCs, which includes:<list style="symbols"></t> <ul spacing="normal"> <li> <t>posting copies to the RFC Editor site both individually and in collections</t> </li> <li> <t>depositing copies with external archives</t> </li> <li> <t>creating catalogs and catalog entries</t> </li> <li> <t>announcing the publication to interested parties</t></list></t></li> </ul> </li> <li> <t>Providing online access to RFCs.</t> </li> <li> <t>Providing an online system to facilitate the submission, management, and display of errata to RFCs.</t> </li> <li> <t>Maintaining the RFC Editor website.</t> </li> <li> <t>Providing for the backup of RFCs.</t> </li> <li> <t>Ensuring the storage and preservation of records.</t> </li> <li> <t>Authenticating RFCs for legal proceedings.</t></list></t></li> </ol> <t>(The text in the next two paragraphs is added by <xreftarget="tooling-code"/>)</t>target="tooling-code"/>.)</t> <t>The RPC is responsible for the development of tools and processes used to implementeditorial streamEditorial Stream policies, in the absence of an RFC with specific requirements. The RPC is responsible for detailed technical specifications, forexampleexample, specific details of text or graphical formats or XML grammar. The RPC may designate a team of volunteers and/or employees who implement these operational decisions. The RPC is expected to solicit input from experts and community members when making implementation decisions. The RPC is required to document implementation decisions in a publicly available place, preferably with rationale.</t> <t>If the RPC has questions about how to interpret policy in EditorialstreamStream documents, they should ask the RSAB for guidance in interpreting that policy per the process described in <xref target="resolution"/>.</t> </section> <sectionanchor="resolution"><name>Resolutionanchor="resolution"> <name>Resolution of Disagreements between Authors and the RPC</name> <t>During the process of editorial preparation and publication, disagreements can arise between the authors of an RFC-to-be and the RPC. Where an existing policy clearly applies, typically such disagreements are handled in a straightforward manner through direct consultation between the authors and the RPC, sometimes in collaboration with stream-specific contacts.</t> <t>However, if it is unclear whether an existing policy applies or if it is unclear how to interpret an existing policy, the parties may need to consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or stream approving bodies) to help achieve a resolution. The following points are intended to provide more specific guidance.</t><t><list style="symbols"><ul spacing="normal"> <li> <t>If there is a conflict with a policy for a particular stream, to help achieve a resolution, the RPC should consult with the relevant stream approving body (such as the IESG or IRSG) and other representatives of the relevant stream as appropriate.</t> </li> <li> <t>If there is a conflict with a cross-stream policy, the RPC should consult with the RSAB to achieve a resolution.</t> </li> <li> <t>The disagreement might raise a new issue that is not covered by an existing policy or that cannot be resolved through consultation between the RPC and other relevant individuals and bodies, as described above. In this case, the RSAB is responsible for (a) resolving the disagreement in a timely manner if necessary so that the relevant stream document(s) can be published before a new policy is defined and (b) bringing the issue to the RSWG so that a new policy can be defined.</t></list></t></li> </ul> <t>(The text in the next paragraph is added by <xreftarget="conflict-resolution"/>)</t>target="conflict-resolution"/>.)</t> <t>If the RPC is responsible for interpreting policy decisions at both the document and editorial process tooling level, conflicts on either level will involve interpretation of written policy (or theacknowledgementacknowledgment that policy does not exist to cover a given situation). In any case, the conflict resolution will now use the same path of appeal: to the RSAB.</t> </section> <sectionanchor="point-of-contact"><name>Pointanchor="point-of-contact"> <name>Point of Contact</name> <t>From time to time, individuals or organizations external to the IETF and the broader RFC Series community may have questions about the RFC Series. Such inquiries should be directed to therfc-editor@rfc-editor.org (mailto:rfc-editor@rfc-editor.org)<eref target="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</eref> email alias or to its successor or future equivalent and then handled by the appropriate bodies (e.g., RSAB and RPC) or individuals (e.g., RSWG Chairs and RSCE).</t> </section> <sectionanchor="administrative-implementation"><name>Administrativeanchor="administrative-implementation"> <name>Administrative Implementation</name> <!--[rfced] Should "implementation" be singular (option A) or plural (option B) in the following sentence? Original: The exact implementation of the administrative and contractual activities described here are a responsibility of the IETF LLC. Perhaps A: The exact implementation of the administrative and contractual activities described here is a responsibility of the IETF LLC. or Perhaps B: The exact implementations of the administrative and contractual activities described here are a responsibility of the IETF LLC. --> <t>The exact implementation of the administrative and contractual activities described here are a responsibility of the IETF LLC. This section provides general guidance regarding several aspects of such activities.</t> <sectionanchor="vendor-selection-for-the-rpc"><name>Vendoranchor="vendor-selection-for-the-rpc"> <name>Vendor Selection for the RPC</name> <t>Vendor selection is done in cooperation with the streams and under the final authority of the IETF LLC.</t> <t>The IETF LLC develops the work definition (the Statement of Work) for the RPC and manages the vendor-selection process. The work definition is created within the IETF LLC budget and takes into account the RPC responsibilities (as described in <xreftarget="rpc-responsibilites"/>),target="rpc-responsibilities"/>), the needs of the streams, and community input.</t> <t>The process to select and contract for the RPC and other RFC-related services is as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>The IETF LLC establishes the contract process, including the steps necessary to issue a Request for Proposal (RFP) when necessary, the timing, and the contracting procedures.</t> </li> <li> <t>The IETF LLC establishes a selection committee, which will consist of the IETF Executive Director and other members selected by the IETF LLC in consultation with the stream approving bodies. The committee shall select a chair from among its members.</t> </li> <li> <t>The selection committee selects the vendor, subject to the successful negotiation of a contract approved by the IETF LLC. In the event that a contract cannot be signed, the matter shall be referred to the selection committee for further action.</t></list></t></li> </ul> </section> <sectionanchor="budget"><name>Budget</name>anchor="budget"> <name>Budget</name> <t>Most expenses discussed in this document are not new expenses. They have been and remain part of the IETF LLC budget.</t> <t>The RFC Series portion of the IETF LLC budget shall include funding to support the RSCE, the RFC Production Center, and the Independent Stream.</t> <t>The IETF LLC has the responsibility to approve the total RFC Editor budget (and the authority to deny it). All relevant parties must work within the IETF LLC budgetary process.</t> </section> </section> </section> <sectionanchor="rsce"><name>RFCanchor="rsce"> <name>RFC Series Consulting Editor (RSCE)</name> <t>The RFC Series Consulting Editor (RSCE) is a senior technical publishing professional who will apply their deep knowledge of technical publishing processes to the RFC Series.</t> <t>The primary responsibilities of the RSCE are as follows:</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Serve as a voting member on the RSAB</t> </li> <li> <t>Identify problems with the RFC publication process and opportunities for improvement</t> </li> <li> <t>Provide expert advice within the RSWG regarding policy proposals</t> </li> <li> <t>Provide expert advice to the RPC and IETF LLC</t></list></t></li> </ul> <t>Matters on which the RSCE might provide guidance could include the following (see alsoSection 4 of<xref section="4" sectionFormat="of" target="RFC8729"/>):</t><t><list style="symbols"><ul spacing="normal"> <li> <t>Editing, processing, and publication of RFCs</t> </li> <li> <t>Publication formats for the RFC Series</t> </li> <li> <t>Changes to the RFC Style Guide</t> </li> <li> <t>Series-wide guidelines regarding document content and quality</t> </li> <li> <t>Web presence for the RFC Series</t> </li> <li> <t>Copyright matters related to the RFC Series</t> </li> <li> <t>Archiving, indexing, and accessibility of RFCs</t></list></t></li> </ul> <t>The IETF LLC is responsible for the method and management of the engagement of the RSCE, including selection, evaluation, and the timely filling of any vacancy. Therefore, whether the RSCE role is structured as a contractual or employee relationship is a matter for the IETF LLC to determine.</t> <sectionanchor="rsce-selection"><name>RSCEanchor="rsce-selection"> <name>RSCE Selection</name> <t>Responsibility for making a recommendation to the IETF LLC regarding the RSCE role will lie with a selection committee. The IETF LLC should propose an initial slate of members for this committee, making sure to include community members with diverse perspectives, and consult with the stream representatives regarding the final membership of the committee. In making its recommendation for the role of RSCE, the selection committee will take into account the definition of the role as well as any other information that the committee deems necessary or helpful in making its decision. The IETF LLC is responsible for contracting or employment of the RSCE.</t> </section> <sectionanchor="rsce-performance-evaluation"><name>RSCEanchor="rsce-performance-evaluation"> <name>RSCE Performance Evaluation</name> <t>Periodically, the IETF LLC will evaluate the performance of the RSCE, including a call for confidential input from the community. The IETF LLC will produce a draft evaluation of the RSCE's performance for review by RSAB members (other than the RSCE), who will provide feedback to the IETF LLC.</t> </section> <sectionanchor="temporary-rsce-appointment"><name>Temporaryanchor="temporary-rsce-appointment"> <name>Temporary RSCE Appointment</name> <t>In the case that the currently appointed RSCE is expected to be unavailable for an extended period, the IETF LLC may appoint a Temporary RSCE through whatever recruitment process it considers appropriate. A Temporary RSCE acts as the RSCE in all aspects during their term of appointment.</t> </section> <sectionanchor="conflict-of-interest"><name>Conflictanchor="conflict-of-interest"> <name>Conflict of Interest</name> <t>The RSCE is expected to avoid even the appearance of conflict of interest or judgment in performing their role. To ensure this, the RSCE will be subject to a conflict-of-interest policy established by the IETF LLC.</t> <t>The RPC service provider may contract services from the RSCE service provider, and vice versa, including services provided to the IETF LLC. All contracts between the two must be disclosed to the IETF LLC. Where those services are related to services provided to the IETF LLC, IETF LLC policies shall apply, including publication of relevant parts of the contract.</t> </section> </section> <sectionanchor="editorial-stream"><name>Editorialanchor="editorial-stream"> <name>Editorial Stream</name> <t>This document creates the Editorial Stream as a separate space for publication of policies, procedures, guidelines, rules, and related information regarding the RFC Series as a whole.</t> <t>The Editorial Stream shall be used only to specify and update policies, procedures, guidelines, rules, and related information regarding the RFC Series as a whole; no other use of the Editorial Stream is authorized by this memo, and no other streams are so authorized. This policy may be changed only by agreement of the IAB, IESG, and IETF LLC.</t> <t>All documents produced by the RSWG and approved by the RSAB shall be published as RFCs in the Editorial Stream with a status of Informational. (Note that the Editorial Stream is not authorized to publish RFCs that are Standards Track or Best Current Practice, since such RFCs are reserved for the IETF Stream <xref target="RFC8729"/>.) Notwithstanding the status of Informational, it should be understood that documents published in the Editorial Stream define policies for the RFC Series as a whole.</t> <t>The requirements and process for creating any additional RFC streams are outside the scope of this document.</t> <sectionanchor="procedures-request-of-the-ietf-trust"><name>Proceduresanchor="procedures-request-of-the-ietf-trust"> <name>Procedures Request of the IETF Trust</name> <t>In <xref target="RFC9280"/>, the IAB requested that the IETF Trust and its Trustees assist in meeting the goals and procedures set forth in this document.</t> <t>The Trustees were requested to publicly confirm their willingness and ability to accept responsibility for the Intellectual Property Rights (IPR) for the Editorial Stream.</t> <t>Specifically, the Trustees were asked to develop the necessary boilerplate to enable the suitable marking of documents so that the IETF Trust receives the rights as specified in <xref target="BCP78"/>. These procedures needed to also allow authors to indicate either no rights to make derivative works or, preferentially, the right to make unlimited derivative works from the documents. It is left to the Trust to specify exactly how this shall be clearly indicated in each document.</t> </section> <sectionanchor="patent-and-trademark-rules-for-the-editorial-stream"><name>Patentanchor="patent-and-trademark-rules-for-the-editorial-stream"> <name>Patent and Trademark Rules for the Editorial Stream</name> <t>As specified above, contributors of documents for the Editorial Stream are expected to use the IETF Internet-Draft process, complying therein with the rules specified in <xref target="BCP9"/>. This includes the disclosure of patent and trademark issues that are known, or can be reasonably expected to be known, to the contributor.</t> <t>Disclosure of license terms for patents is also requested, as specified in <xref target="BCP79"/>. The Editorial Stream has chosen to use theIETF's<eref target="https://datatracker.ietf.org/ipr/about/">IETF's IPR disclosuremechanism (https://www.ietf.org/ipr/)mechanism</eref> for this purpose. It is preferred that the most liberal terms possible be made available for Editorial Stream documents. Terms that do not require fees or licensing are preferable. Non-discriminatory terms are strongly preferred over those that discriminate among users. However, although disclosure is required and the RSWG and the RSAB may consider disclosures and terms in making a decision as to whether to submit a document for publication, there are no specific requirements on the licensing terms for intellectual property related to Editorial Stream publication.</t> </section> <sectionanchor="editorial-stream-boilerplate"><name>Editorialanchor="editorial-stream-boilerplate"> <name>Editorial Stream Boilerplate</name> <t>This document specifies the following text for the "Status of This Memo" section of RFCs published in the Editorial Stream. Any changes to this boilerplate must be made through the RFC Series Policy Definition Process specified in <xreftarget="policy-definiion"/>target="policy-definition"/> of this document.</t> <t>Because all Editorial Stream RFCs have a status of Informational, the first paragraph of the "Status of This Memo" section shall be as specified inAppendix A.2.1 of<xref section="A.2.1" sectionFormat="of" target="RFC7841"/>.</t> <t>The second paragraph of the "Status of This Memo" section shall be as follows:</t><ul empty="true"><li><blockquote> <t>This document is a product of the RFC Series Policy Definition Process. It represents the consensus of the RFC Series Working Group approved by the RFC Series Approval Board. Such documents are not candidates for any level of Internet Standard; see Section 2 of RFC 7841.</t></li></ul></blockquote> <t>The third paragraph of the "Status of This Memo" section shall be as specified inSection 3.5 of<xref section="3.5" sectionFormat="of" target="RFC7841"/>.</t> </section> </section> <sectionanchor="historical"><name>Historicalanchor="historical"> <name>Historical Properties of the RFC Series</name> <t>This section lists some of the properties that have been historically regarded as important to the RFC Series. Proposals that affect these properties are possible within the processes defined in this document. As described in Sections <xreftarget="workflow"/>target="workflow" format="counter"/> and <xreftarget="calls"/>,target="calls" format="counter"/>, proposals that might have a detrimental effect on these properties should receive heightened scrutiny during RSWG discussion and RSAB review. The purpose of this scrutiny is to ensure that all changes are deliberate and that the consequences of a proposal, as far as they can be identified, have been carefully considered.</t> <sectionanchor="availability"><name>Availability</name>anchor="availability"> <name>Availability</name> <t>Documents in the RFC Series have been available for many decades, with no restrictions on access or distribution.</t> </section> <sectionanchor="accessibility"><name>Accessibility</name>anchor="accessibility"> <name>Accessibility</name> <t>RFC Series documents have been published in a format that was intended to be as accessible as possible to people with disabilities, e.g., people with impaired sight.</t> </section> <sectionanchor="language"><name>Language</name>anchor="language"> <name>Language</name> <t>All existing RFC Series documents have been published in English. However, since the beginning of the RFC Series, documents have been published under terms that explicitly allow translation into languages other than English without asking for permission.</t> </section> <sectionanchor="diversity"><name>Diversity</name>anchor="diversity"> <name>Diversity</name> <t>The RFC Series has included many types of documents including standards for the Internet, procedural and informational documents, thought experiments, speculative ideas, research papers, histories, humor, and even eulogies.</t> </section> <sectionanchor="quality"><name>Quality</name>anchor="quality"> <name>Quality</name> <t>RFC Series documents have been reviewed for subject matter quality and edited by professionals with a goal of ensuring that documents are clear, consistent, and readable <xref target="RFC7322"/>.</t> </section> <sectionanchor="stability"><name>Stability</name>anchor="stability"> <name>Stability</name> <t>(The text in this section is updated by <xreftarget="reissued"/>)</t>target="reissued"/>.)</t> <t>Once published, RFCs may be reissued, but the semantic content of publication versions shall be preserved to the greatest extentpossible.</t>possible, as described in <xref section="2.2" sectionFormat="of" target="RFC9720"/>.</t> </section> <sectionanchor="longevity"><name>Longevity</name>anchor="longevity"> <name>Longevity</name> <t>RFC Series documents have been published in a form intended to be comprehensible to humans for decades or longer.</t> </section> <sectionanchor="consistency"><name>Consistency</name>anchor="consistency"> <name>Consistency</name> <t>(The text in this section is added by <xreftarget="consistency-policy"/>)</t>target="consistency-policy"/>.)</t> <t>RFCs are copyedited, formatted, and then published. They may be reissued to maintain a consistent presentation.</t> </section> </section> <sectionanchor="updates-to-this-document"><name>Updatesanchor="updates-to-this-document"> <name>Updates to This Document</name> <t>Updates, amendments, and refinements to this document can be produced using the process documented herein but shall be published and operative only after (a) obtaining the agreement of the IAB and the IESG and (b) ensuring that the IETF LLC has no objections regarding its ability to implement any proposed changes.</t> </section> <sectionanchor="changes"><name>Changesanchor="changes"> <name>Changes from Version 2 of the RFC Editor Model</name> <t>The processes and organizational models for publication of RFCs have changed significantly over the years. Most recently, in 2009, <xref target="RFC5620"/> defined the RFC Editor Model (Version 1), and in 2012, <xref target="RFC6635"/> defined the RFC Editor Model (Version 2), which was then modified slightly in 2020 by <xref target="RFC8728"/>.</t> <t>However, the community experienced several problems with versions 1 and 2, including a lack of transparency, a lack of avenues for community input into policy definition, and unclear lines of authority and responsibility.</t> <t>To address these problems, in 2020, the IAB formed the RFC Editor Future Development Program to conduct a community discussion and consensus process for the further evolution of the RFC Editor Model. Under the auspices of this Program, the community considered changes that would increase transparency and community input regarding the definition of policies for the RFC Series as a whole, while at the same time ensuring the continuity of the RFC Series, maintaining the quality and timely publication of RFCs, ensuring document accessibility, and clarifying lines of authority and responsibility.</t> <t><xref target="RFC9280"/> was the result of discussion within the original Program and described version 3 of the RFC Editor Model while remaining consistent with <xref target="RFC8729"/>. As stated earlier, this document obsoletes <xref target="RFC9280"/>.</t> <t>The following sections describe the changes from version 2 in more detail.</t> <sectionanchor="rfc-editor-function"><name>RFCanchor="rfc-editor-function"> <name>RFC Editor Function</name> <!--[rfced] Although this sentence appeared in RFC 9280, perhaps the readability could be improved by including parentheses as shown below. Let us know your thoughts. Original: Several responsibilities previously assigned to the RFC Editor or, more precisely, the RFC Editor function, are now performed by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination). Perhaps: Several responsibilities previously assigned to the RFC Editor (or more precisely, the RFC Editor function) are now performed by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination). --> <t>Several responsibilities previously assigned to the RFC Editor or, more precisely, the RFC Editor function, are now performed by the RSWG, RSAB, RPC, RSCE, and IETF LLC (alone or in combination). These include various aspects of strategic leadership(Section 2.1.1 of <xref(<xref section="2.1.1" sectionFormat="of" target="RFC8728"/>), representation of the RFC Series(Section 2.1.2 of <xref(<xref section="2.1.2" sectionFormat="of" target="RFC8728"/>), development of RFC production and publication(Section 2.1.3 of <xref(<xref section="2.1.3" sectionFormat="of" target="RFC8728"/>), development of the RFC Series(Section 2.1.4 of <xref(<xref section="2.1.4" sectionFormat="of" target="RFC8728"/>), operational oversight(Section 3.3 of <xref(<xref section="3.3" sectionFormat="of" target="RFC8729"/>), policy oversight(Section 3.4 of <xref(<xref section="3.4" sectionFormat="of" target="RFC8729"/>), the editing, processing, and publication of documents(Section 4.2 of <xref(<xref section="4.2" sectionFormat="of" target="RFC8729"/>), and development and maintenance of guidelines and rules that apply to the RFC Series(Section 4.4 of <xref(<xref section="4.4" sectionFormat="of" target="RFC8729"/>). Among other things, this changes the dependency on the RFC Series Editor (RSE) included inSection 2.2 of<xref section="2.2" sectionFormat="of" target="RFC8730"/> with regard to "coordinating work and conforming to general RFC Series policies as specified by the IAB and RSE." In addition, various details regarding these responsibilities have been modified to accord with the framework defined in this document.</t> </section> <sectionanchor="rfc-series-editor"><name>RFCanchor="rfc-series-editor"> <name>RFC Series Editor</name> <t>Implied by the changes outlined in the previous section, the responsibilities of the RFC Series Editor (RSE) as a person or role (contrasted with the overall RFC Editor function) are now split or shared among the RSWG, RSAB, RSCE, RPC, and IETF LLC (alone or in combination). More specifically, the responsibilities of the RFC Series Consulting Editor (RSCE) under version 3 of the RFC Editor Model differ in many ways from the responsibilities of the RFC Series Editor under version 2 of the RFC Editor Model. In general, references in existing documents to the RSE can be taken as referring to the RFC Editor function as described herein but should not be taken as referring to the RSCE.</t> </section> <sectionanchor="rfc-publisher"><name>RFCanchor="rfc-publisher"> <name>RFC Publisher</name> <t>In practice, the RFC Production Center (RPC) and RFC Publisher roles have been performed by the same entity, and this practice is expected to continue; therefore, this document dispenses with the distinction between these roles and refers only to the RPC.</t> </section> <sectionanchor="iab"><name>IAB</name>anchor="iab"> <name>IAB</name> <!--[rfced] Since the RFC Series Oversight Committee is first mentioned in the text below (Section 9.4), may we include its acronym? Original: Under version 2 of the RFC Editor Model, the IAB delegated some of its authority to the RFC Series Oversight Committee (see Section 9.5). Perhaps: Under version 2 of the RFC Editor Model, the IAB delegated some of its authority to the RFC Series Oversight Committee (RSOC) (see Section 9.5). --> <t>Under earlier versions of the RFC Editor Model, the IAB was responsible for oversight of the RFC Series and acted as a body for final conflict resolution regarding the RFC Series. The IAB's authority in these matters is described in the IAB Charter (<xref target="RFC2850"/>, as updated by <xref target="RFC9283"/>). Under version 2 of the RFC Editor Model, the IAB delegated some of its authority to the RFC Series Oversight Committee (see <xref target="rsoc"/>). Under version 3 of the RFC Editor Model, authority for policy definition resides with the RSWG as an independent venue for work by members of the community (with approval of policy proposals being the responsibility of the RSAB, which represents the streams and includes the RSCE), whereas authority for policy implementation resides with the IETF LLC.</t> </section> <sectionanchor="rsoc"><name>RFCanchor="rsoc"> <name>RFC Series Oversight Committee (RSOC)</name> <t>In practice, the relationships and lines of authority and responsibility between the IAB, RSOC, and RSE proved unwieldy and somewhat opaque. To overcome some of these issues, <xref target="RFC9280"/> dispensed with the RSOC. References to the RSOC in documents such as <xref target="RFC8730"/> are obsolete.</t> </section> <sectionanchor="rfc-series-advisory-group-rsag"><name>RFCanchor="rfc-series-advisory-group-rsag"> <name>RFC Series Advisory Group (RSAG)</name> <!--[rfced] In the second sentence, it is correct that this document "establishes" the RSAB, or should it be "describes" or "specifies"? Original: (The RSAG is not to be confused with the RFC Series Approval Board (RSAB), which this document establishes.) Perhaps: (The RSAG is not to be confused with the RFC Series Approval Board (RSAB), which this document specifies.) --> <t>Version 1 of the RFC Editor Model <xref target="RFC5620"/> specified the existence of the RFC Series Advisory Group (RSAG), which was no longer specified in version 2 of the RFC Editor Model. For the avoidance of doubt, <xref target="RFC9280"/> affirmed that the RSAGhas beenwas disbanded. (The RSAG is not to be confused with the RFC Series Approval Board (RSAB), which this document establishes.)</t> </section> <sectionanchor="editorial-stream-1"><name>Editorialanchor="editorial-stream-1"> <name>Editorial Stream</name> <t>This document specifies the Editorial Stream in addition to the streams already described in <xref target="RFC8729"/>.</t> </section> </section> <sectionanchor="security-considerations"><name>Securityanchor="security-considerations"> <name>Security Considerations</name> <t>The same security considerations as those in <xref target="RFC8729"/> apply. The processes for the publication of documents must prevent the introduction of unapproved changes. Because multiple entities described in this document (most especially the RPC) participate in maintenance of the index of publications, sufficient security must be in place to prevent these published documents from being changed by external parties. The archive of RFC documents, any source documents needed to recreate the RFC documents, and any associated original documents (such as lists of errata, tools, and, for some early items, originals that are not machine-readable) need to be secured against data storage failure.</t> <t>The IETF LLC (along with any other contracting or contracted entities) should take these security considerations into account during the implementation and enforcement of any relevant contracts.</t> </section> <sectionanchor="iana-considerations"><name>IANAanchor="iana-considerations"> <name>IANA Considerations</name> <t>The RPC is responsible for coordinating with the IANA to ensure that RFCs accurately document registration processes and assigned values for IANA registries.</t> <t>The IETF LLC facilitates management of the relationship between the RPC and IANA.</t> <t>This document does not create a new registry nor does it register any values in existing registries, and no IANA action is required.</t> </section> </middle> <back> <referencestitle='References'anchor="sec-combined-references"> <name>References</name> <referencestitle='Normative References'anchor="sec-normative-references"> <name>Normative References</name> <referencegroup anchor="BCP78" target="https://www.rfc-editor.org/info/bcp78"><reference anchor="RFC5378" target="https://www.rfc-editor.org/info/rfc5378"> <front> <title>Rights Contributors Provide to the IETF Trust</title> <author fullname="S. Bradner" initials="S." role="editor" surname="Bradner"/> <author fullname="J. Contreras" initials="J." role="editor" surname="Contreras"/> <date month="November" year="2008"/> <abstract> <t>The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces Section 10 of RFC 2026. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="78"/> <seriesInfo name="RFC" value="5378"/> <seriesInfo name="DOI" value="10.17487/RFC5378"/> </reference><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5378.xml"/> </referencegroup> <referencegroup anchor="BCP79" target="https://www.rfc-editor.org/info/bcp79"><reference anchor="RFC8179" target="https://www.rfc-editor.org/info/rfc8179"> <front> <title>Intellectual Property Rights in IETF Technology</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <author fullname="J. Contreras" initials="J." surname="Contreras"/> <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><xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8179.xml"/> </referencegroup> <referencegroup anchor="BCP9" target="https://www.rfc-editor.org/info/bcp9"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2026.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5657.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6410.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7100.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7127.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7475.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8789.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9282.xml"/> </referencegroup> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2418.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7154.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7322.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7776.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7841.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7991.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7992.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7993.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7994.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7995.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7996.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7997.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8711.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8716.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8729.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8730.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9280.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9720.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> </references> <references anchor="sec-informative-references"> <name>Informative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2850.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3935.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5620.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6635.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8700.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8728.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8874.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9283.xml"/> <referenceanchor="RFC2026" target="https://www.rfc-editor.org/info/rfc2026"> <front> <title>The Internet Standards Process -- Revision 3</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="October" year="1996"/> <abstract> <t>This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="2026"/> <seriesInfo name="DOI" value="10.17487/RFC2026"/> </reference> <reference anchor="RFC5657" target="https://www.rfc-editor.org/info/rfc5657"> <front> <title>Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard</title> <author fullname="L. Dusseault" initials="L." surname="Dusseault"/> <author fullname="R. Sparks" initials="R." surname="Sparks"/> <date month="September" year="2009"/> <abstract> <t>Advancing a protocol to Draft Standard requires documentation of the interoperation and implementation of the protocol. Historic reports have varied widely in form and level of content and there is little guidance available to new report preparers. This document updates the existing processes and provides more detail on what is appropriate in an interoperability and implementation report. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="5657"/> <seriesInfo name="DOI" value="10.17487/RFC5657"/> </reference> <reference anchor="RFC6410" target="https://www.rfc-editor.org/info/rfc6410"> <front> <title>Reducing the Standards Track to Two Maturity Levels</title> <author fullname="R. Housley" initials="R." surname="Housley"/> <author fullname="D. Crocker" initials="D." surname="Crocker"/> <author fullname="E. Burger" initials="E." surname="Burger"/> <date month="October" year="2011"/> <abstract> <t>This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="6410"/> <seriesInfo name="DOI" value="10.17487/RFC6410"/> </reference> <reference anchor="RFC7100" target="https://www.rfc-editor.org/info/rfc7100"> <front> <title>Retirement of the "Internet Official Protocol Standards" Summary Document</title> <author fullname="P. Resnick" initials="P." surname="Resnick"/> <date month="December" year="2013"/> <abstract> <t>This document updates RFC 2026 to no longer use STD 1 as a summary of "Internet Official Protocol Standards". It obsoletes RFC 5000 and requests the IESG to move RFC 5000 (and therefore STD 1) to Historic status.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7100"/> <seriesInfo name="DOI" value="10.17487/RFC7100"/> </reference> <reference anchor="RFC7127" target="https://www.rfc-editor.org/info/rfc7127"> <front> <title>Characterization of Proposed Standards</title> <author fullname="O. Kolkman" initials="O." surname="Kolkman"/> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <author fullname="S. Turner" initials="S." surname="Turner"/> <date month="January" year="2014"/> <abstract> <t>RFC 2026 describes the review performed by the Internet Engineering Steering Group (IESG) on IETF Proposed Standard RFCs and characterizes the maturity level of those documents. This document updates RFC 2026 by providing a current and more accurate characterization of Proposed Standards.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7127"/> <seriesInfo name="DOI" value="10.17487/RFC7127"/> </reference> <reference anchor="RFC7475" target="https://www.rfc-editor.org/info/rfc7475">anchor="STYLEGUIDE" target="https://www.rfc-editor.org/styleguide/"> <front><title>Increasing the Number of Area Directors in an IETF Area</title> <author fullname="S. Dawkins" initials="S." surname="Dawkins"/> <date month="March" year="2015"/> <abstract> <t>This document removes a limit on the number of Area Directors who manage an Area in the definition of "IETF Area". This document updates RFC 2026 (BCP 9) and RFC 2418 (BCP 25).</t> </abstract><title>Style Guide</title> <author> <organization>RFC Editor</organization> </author> <date/> </front><seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="7475"/> <seriesInfo name="DOI" value="10.17487/RFC7475"/></reference><reference anchor="RFC8789" target="https://www.rfc-editor.org/info/rfc8789"> <front> <title>IETF Stream Documents Require IETF Rough Consensus</title> <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/> <author fullname="E. Rescorla" initials="E." role="editor" surname="Rescorla"/> <date month="June" year="2020"/> <abstract></references> </references> <?line 1876?> <section numbered="false" anchor="acknowledgments"> <name>Acknowledgments</name> <t>This documentrequires that the IETF never publish any IETF Stream RFCs without IETF rough consensus. This updates RFC 2026.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="8789"/> <seriesInfo name="DOI" value="10.17487/RFC8789"/> </reference> <reference anchor="RFC9282" target="https://www.rfc-editor.org/info/rfc9282"> <front> <title>Responsibility Change for the RFC Series</title> <author fullname="B. Rosen" initials="B." surname="Rosen"/> <date month="June" year="2022"/> <abstract> <t>In RFC 9280, responsibility for the RFC Series moved to the RFC Series Working Group and the RFC Series Approval Board. Itisno longer the responsibility of the RFC Editor, andtheroleproduct of theIAB in theRFC Seriesis altered. Accordingly, in Section 2.1 of RFC 2026, the sentence "RFC publication is the direct responsibility of the RFC Editor, under the general direction of the IAB" is deleted.</t> </abstract> </front> <seriesInfo name="BCP" value="9"/> <seriesInfo name="RFC" value="9282"/> <seriesInfo name="DOI" value="10.17487/RFC9282"/> </reference> </referencegroup> <reference anchor="RFC2418"> <front> <title>IETFWorkingGroup Guidelines and Procedures</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="September" year="1998"/> <abstract> <t>This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="25"/> <seriesInfo name="RFC" value="2418"/> <seriesInfo name="DOI" value="10.17487/RFC2418"/> </reference> <reference anchor="RFC7154"> <front> <title>IETF Guidelines for Conduct</title> <author fullname="S. Moonesamy" initials="S." role="editor" surname="Moonesamy"/> <date month="March" year="2014"/> <abstract> <t>This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force. The guidelines recognize the diversity of IETF participants, emphasize the value of mutual respect, and stress the broad applicability of our work.</t> <t>This document is an updated version of the guidelines for conduct originally publishedGroup. Many people inRFC 3184.</t> </abstract> </front> <seriesInfo name="BCP" value="54"/> <seriesInfo name="RFC" value="7154"/> <seriesInfo name="DOI" value="10.17487/RFC7154"/> </reference> <reference anchor="RFC7322"> <front> <title>RFC Style Guide</title> <author fullname="H. Flanagan" initials="H." surname="Flanagan"/> <author fullname="S. Ginoza" initials="S." surname="Ginoza"/> <date month="September" year="2014"/> <abstract> <t>This document describesthefundamental and unique style conventions and editorial policies currentlyRSWG participated inuse for the RFC Series. It captures the RFC Editor's basic requirements and offers guidance regarding the style and structure of an RFC. Additional guidance is captured on a website that reflectstheexperimental nature ofactive discussions thatguidance and prepares it for future inclusion in the RFC Style Guide. This document obsoletes RFC 2223, "Instructions to RFC Authors".</t> </abstract> </front> <seriesInfo name="RFC" value="7322"/> <seriesInfo name="DOI" value="10.17487/RFC7322"/> </reference> <reference anchor="RFC7776"> <front> <title>IETF Anti-Harassment Procedures</title> <author fullname="P. Resnick" initials="P." surname="Resnick"/> <author fullname="A. Farrel" initials="A." surname="Farrel"/> <date month="March" year="2016"/> <abstract> <t>IETF Participants must not engage in harassment while at IETF meetings, virtual meetings, or social events or while participating in mailing lists. This document lays out procedures for managing and enforcing this policy.</t> <t>This document updates RFC 2418 by defining new working group guidelines and procedures. This document updates RFC 7437 by allowing the Ombudsteam to form a recall petition without further signatories.</t> </abstract> </front> <seriesInfo name="BCP" value="25"/> <seriesInfo name="RFC" value="7776"/> <seriesInfo name="DOI" value="10.17487/RFC7776"/> </reference> <reference anchor="RFC7841"> <front> <title>RFC Streams, Headers, and Boilerplates</title> <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/> <author fullname="L. Daigle" initials="L." role="editor" surname="Daigle"/> <author fullname="O. Kolkman" initials="O." role="editor" surname="Kolkman"/> <date month="May" year="2016"/> <abstract> <t>RFC documents contain a number of fixed elements such as the title page header, standard boilerplates, and copyright/IPR statements. This document describes them and introduces some updates to reflect current usage and requirements of RFC publication. In particular, this updated structure is intended to communicate clearly the source of RFC creation and review. This document obsoletes RFC 5741, moving detailed content to an IAB web page and preparing for more flexible output formats.</t> </abstract> </front> <seriesInfo name="RFC" value="7841"/> <seriesInfo name="DOI" value="10.17487/RFC7841"/> </reference> <reference anchor="RFC7990"> <front> <title>RFC Format Framework</title> <author fullname="H. Flanagan" initials="H." surname="Flanagan"/> <date month="December" year="2016"/> <abstract> <t>In order to improve the readability of RFCs while supporting their archivability, the canonical format of the RFC Series will be transitioning from plain-text ASCIIled toXML usingthexml2rfc version 3 vocabulary; different publication formats will be rendered from that base document. With thesechangescomes an increase in complexity for authors, consumers, and the publisher of RFCs. This document serves as the framework that provides the problem statement, lays out a road map of the documents that capture the specific requirements, and describes the transition plan.</t> </abstract> </front> <seriesInfo name="RFC" value="7990"/> <seriesInfo name="DOI" value="10.17487/RFC7990"/> </reference> <reference anchor="RFC7991"> <front> <title>The "xml2rfc" Version 3 Vocabulary</title> <author fullname="P. Hoffman" initials="P." surname="Hoffman"/> <date month="December" year="2016"/> <abstract> <t>This document defines the "xml2rfc" version 3 vocabulary: an XML-based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the v2 grammar described in RFC 7749.</t> </abstract> </front> <seriesInfo name="RFC" value="7991"/> <seriesInfo name="DOI" value="10.17487/RFC7991"/> </reference> <reference anchor="RFC7992"> <front> <title>HTML Format for RFCs</title> <author fullname="J. Hildebrand" initials="J." role="editor" surname="Hildebrand"/> <author fullname="P. Hoffman" initials="P." surname="Hoffman"/> <date month="December" year="2016"/> <abstract> <t>In order to meet the evolving needs of the Internet community, the canonical format for RFCs is changing from a plain-text, ASCII-only format to an XML format that will,listed inturn, be rendered into several publication formats. This document defines the HTML format that will be rendered for an RFC or Internet-Draft.</t> </abstract> </front> <seriesInfo name="RFC" value="7992"/> <seriesInfo name="DOI" value="10.17487/RFC7992"/> </reference> <reference anchor="RFC7993"> <front> <title>Cascading Style Sheets (CSS) Requirements for RFCs</title> <author fullname="H. Flanagan" initials="H." surname="Flanagan"/> <date month="December" year="2016"/> <abstract> <t>The HTML format for RFCs assigns style guidance<xref target="changes-to-9280"/>. The authors are indebted toa Cascading Style Sheet (CSS) specifically definedthem forthe RFC Series. The embedded, default CSS as includedtheir contributions.</t> <t><xref target="RFC9280"/> was authored by <contact fullname="Peter Saint-Andre"/>. It had additional, extensive acknowledgments.</t> <!--[rfced] We updated theRFC Editor is expected to take into account accessibility needs andfollowing terms tobe built along a responsive design model. This document describes the requirements for the default CSS used bytheRFC Editor. The class names are basedform on theclasses defined in "HTML for RFCs" (RFC 7992).</t> </abstract> </front> <seriesInfo name="RFC" value="7993"/> <seriesInfo name="DOI" value="10.17487/RFC7993"/> </reference> <reference anchor="RFC7994"> <front> <title>Requirements for Plain-Text RFCs</title> <author fullname="H. Flanagan" initials="H." surname="Flanagan"/> <date month="December" year="2016"/> <abstract> <t>In 2013, after a great deal of community discussion, the decision was made to shift from the plain-text, ASCII-only canonical formatright forRFCs to XML as the canonical formatconsistency withmore human-readable formats rendered from that XML. The high-level requirements that informed this change were defined in RFC 6949, "RFC Series Format Requirements and Future Development". Plain text remains an important format for many in the IETF community, and it will be one of the publication formats rendered from the XML. This document outlines the rendering requirements for the plain-textRFCpublication format. These requirements do9280. Please let us know if that is notapply to plain-text RFCs published before the format transition.</t> </abstract> </front> <seriesInfo name="RFC" value="7994"/> <seriesInfo name="DOI" value="10.17487/RFC7994"/> </reference> <reference anchor="RFC7995"> <front> <title>PDF Format for RFCs</title> <author fullname="T. Hansen" initials="T." role="editor" surname="Hansen"/> <author fullname="L. Masinter" initials="L." surname="Masinter"/> <author fullname="M. Hardy" initials="M." surname="Hardy"/> <date month="December" year="2016"/> <abstract> <t>This document discusses options and requirements for the PDF rendering of RFCs in the RFC Series, as outlined in RFC 6949. It also discusses the use of PDF for Internet-Drafts, and available or needed software tools for producingdesired. Acknowledgement(s) -> Acknowledgment(s) Editorial stream andworking with PDF.</t> </abstract> </front> <seriesInfo name="RFC" value="7995"/> <seriesInfo name="DOI" value="10.17487/RFC7995"/> </reference> <reference anchor="RFC7996"> <front> <title>SVG Drawings for RFCs: SVG 1.2 RFC</title> <author fullname="N. Brownlee" initials="N." surname="Brownlee"/> <date month="December" year="2016"/> <abstract> <t>This document specifies SVG 1.2 RFC -- an SVG profile for use in diagramseditorial stream -> Editorial Stream --> <!--[rfced] Abbreviations a) We note thatmay appear in RFCs -- and considers some of the issues concerning the creation"IAB", "IRTF", "IESG", anduse of such diagrams.</t> </abstract> </front> <seriesInfo name="RFC" value="7996"/> <seriesInfo name="DOI" value="10.17487/RFC7996"/> </reference> <reference anchor="RFC7997"> <front> <title>The Use of Non-ASCII Characters in RFCs</title> <author fullname="H. Flanagan" initials="H." role="editor" surname="Flanagan"/> <date month="December" year="2016"/> <abstract> <t>In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs.</t> <t>This document updates RFC 7322. Please view this document in PDF form to see the full text.</t> </abstract> </front> <seriesInfo name="RFC" value="7997"/> <seriesInfo name="DOI" value="10.17487/RFC7997"/> </reference> <reference anchor="RFC8711"> <front> <title>Structure of the IETF Administrative Support Activity, Version 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"IRSG" are theIETF evolved in waysonly acronyms not expanded. We assume thatrequired changes to its administrative structure. The purpose ofthisRFCisto document and describe the IETF Administrative Support Activity, version 2.0 (IASA 2.0). It defines the roles and responsibilities of the IETF Administration 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> <reference anchor="RFC8716"> <front> <title>Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLC</title> <author fullname="P. Resnick" initials="P." surname="Resnick"/> <author fullname="A. Farrel" initials="A." surname="Farrel"/> <date month="February" year="2020"/> <abstract> <t>The IETF Anti-Harassment Proceduresintentional because they aredescribed in RFC 7776.</t> <t>The IETF Administrative Oversight Committee (IAOC) has been replaced by the IETF Administration LLC, and the IETF Administrative Director haswell known; however, since other well-known abbreviations have beenreplaced by the IETF LLC Executive Director. This document updates RFC 7776 to amendexpanded, please confirm whether or not theseterms.</t> <t>RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated those updates, so this document also updates RFC 7776 to remove those updates.</t> </abstract> </front> <seriesInfo name="BCP" value="25"/> <seriesInfo name="RFC" value="8716"/> <seriesInfo name="DOI" value="10.17487/RFC8716"/> </reference> <reference anchor="RFC8729"> <front> <title>The RFC Series and RFC Editor</title> <author fullname="R. Housley" initials="R." role="editor" surname="Housley"/> <author fullname="L. Daigle" initials="L." role="editor" surname="Daigle"/> <date month="February" year="2020"/> <abstract> <t>This document describes the frameworkshould be expanded on their first mention foran RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This document obsoletes RFC 4844.</t> </abstract> </front> <seriesInfo name="RFC" value="8729"/> <seriesInfo name="DOI" value="10.17487/RFC8729"/> </reference> <reference anchor="RFC8730"> <front> <title>Independent Submission Editor Model</title> <author fullname="N. Brownlee" initials="N." role="editor" surname="Brownlee"/> <author fullname="B. Hinden" initials="B." role="editor" surname="Hinden"/> <date month="February" year="2020"/> <abstract> <t>This document describes the function and responsibilities of the RFC Independent Submission Editor (ISE). The Independent Submission stream is one of the stream producersconsistency. First mentions: IAB (Section 1) IRTF (Section 1.2.3) IESG (Section 3.1.1.2) IRSG (Section 4.4) b) We note thatcreate draft RFCs, with the ISE as its stream approver. The ISE is overall responsible for activities within the Independent Submission stream, working with draft editors and reviewers, and interacts with the RFC Production Center and Publisher, and the RFC Series Editor (RSE). The ISE is appointed by the IAB,"RPC", "RSWG", andalso interacts with the IETF Administration Limited Liability Company (LLC).</t> <t>This version obsoletes RFC 6548 to replace all references to"RSAB" appear both in theInternet Administrative Support Activity (IASA) and related structuresexpanded form withthose defined by the IASA 2.0 structure.</t> </abstract> </front> <seriesInfo name="RFC" value="8730"/> <seriesInfo name="DOI" value="10.17487/RFC8730"/> </reference> <reference anchor="RFC9280"> <front> <title>RFC Editor Model (Version 3)</title> <author fullname="P. Saint-Andre" initials="P." role="editor" surname="Saint-Andre"/> <date month="June" year="2022"/> <abstract> <t>This document specifies version 3 of the RFC Editor Model. The model defines two high-level tasks related to the RFC Series. First, policy definition is the joint responsibility oftheRFC Series Working Group (RSWG), which produces policy proposals,abbreviation andthe RFC Series Approval Board (RSAB), which approves such proposals. Second, policy implementation is primarily the responsibility of the RFC Production Center (RPC)ascontractually overseen by the IETF Administration Limited Liability Company (IETF LLC). In addition, various responsibilities of the RFC Editor function are now performed alone or in combination bytheRSWG, RSAB, RPC, RFC Series Consulting Editor (RSCE),abbreviation only, andIETF LLC. Finally, this document establishes the Editorial Stream for publication of future policy definition documents produced through the processes defined herein.</t> <t>This document obsoletes RFC 8728. This document updates RFCs 7841, 8729, and 8730.</t> </abstract> </front> <seriesInfo name="RFC" value="9280"/> <seriesInfo name="DOI" value="10.17487/RFC9280"/> </reference> <reference anchor="RFC9720"> <front> <title>RFC Formats and Versions</title> <author fullname="P. Hoffman" initials="P." surname="Hoffman"/> <author fullname="H. Flanagan" initials="H." surname="Flanagan"/> <date month="January" year="2025"/> <abstract> <t>In orderthere doesn't seem toimprove the readability of RFCs while supporting their archivability, the definitive version of the RFC Series transitioned from plain-text ASCIIbe a pattern. Is this intentional, or would you like toXML usinguse theRFCXML vocabulary; different publication versions are rendered from that base document. This document describes how RFCs are published.</t> <t>This document obsoletes RFC 7990. This document also updatesabbreviated forms after thestability policyfirst expansion inRFC 9280.</t> </abstract> </front> <seriesInfo name="RFC" value="9720"/> <seriesInfo name="DOI" value="10.17487/RFC9720"/> </reference> </references> <references title='Informative References' anchor="sec-informative-references"> <reference anchor="RFC2850"> <front> <title>Charter oftheInternet Architecture Board (IAB)</title> <author> <organization abbrev="IAB">Internet Architecture Board</organization> </author> <author fullname="B. Carpenter" initials="B." role="editor" surname="Carpenter"/> <date month="May" year="2000"/> <abstract> <t>This memo documentsdocument? --> <!-- [rfced] Please review thecomposition, selection, roles, and organization"Inclusive Language" portion of theInternet Architecture Board. It replaces RFC 1601. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="39"/> <seriesInfo name="RFC" value="2850"/> <seriesInfo name="DOI" value="10.17487/RFC2850"/> </reference> <reference anchor="RFC3935"> <front> <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 define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement,online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> andtries to capture somelet us know if any changes are needed. Updates ofthe debate that led tothispoint. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="95"/> <seriesInfo name="RFC" value="3935"/> <seriesInfo name="DOI" value="10.17487/RFC3935"/> </reference> <reference anchor="RFC5620"> <front> <title>RFC Editor Model (Version 1)</title> <author fullname="O. Kolkman" initials="O." role="editor" surname="Kolkman"/> <author> <organization abbrev="IAB">Internet Architecture Board</organization> </author> <date month="August" year="2009"/> <abstract> <t>The RFC Editor performs a number of functions that may be carried out by various persons or entities. The RFC Editor model presentednature typically result inthis document divides the responsibilities for the RFC Series into four functions: The RFC Series Editor, the Independent Submission Editor, the RFC Production Center, and the RFC Publisher. It also introduces the RFC Series Advisory Group and an (optional) Independent Submission Stream Editorial Board. The model outlined heremore precise language, which isintended to increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC series, while maintaining RFC quality and timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. This memo provides information for the Internet community.</t> </abstract> </front> <seriesInfo name="RFC" value="5620"/> <seriesInfo name="DOI" value="10.17487/RFC5620"/> </reference> <reference anchor="RFC6635"> <front> <title>RFC Editor Model (Version 2)</title> <author fullname="O. Kolkman" initials="O." role="editor" surname="Kolkman"/> <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/> <author> <organization abbrev="IAB">Internet Architecture Board</organization> </author> <date month="June" year="2012"/> <abstract> <t>The RFC Editor model described in this document divides the responsibilitieshelpful forthe RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described, as is the relationship between the IETF Administrative Oversight Committee (IAOC) and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620, and obsoletesreaders. Note thatdocument. This document isour script did notan Internet Standards Track specification; it is published for informational purposes.</t> </abstract> </front> <seriesInfo name="RFC" value="6635"/> <seriesInfo name="DOI" value="10.17487/RFC6635"/> </reference> <reference anchor="RFC8700"> <front> <title>Fifty Years of RFCs</title> <author fullname="H. Flanagan" initials="H." role="editor" surname="Flanagan"/> <date month="December" year="2019"/> <abstract> <t>This RFC marks the fiftieth anniversary for the RFC Series. It includes both retrospective material from individuals involved at key inflection points as well as a review of the current state of affairs. It concludes with thoughts on possibilities for the next fifty years for the Series. This document updates the perspectives offered in RFCs 2555 and 5540.</t> </abstract> </front> <seriesInfo name="RFC" value="8700"/> <seriesInfo name="DOI" value="10.17487/RFC8700"/> </reference> <reference anchor="RFC8728"> <front> <title>RFC Editor Model (Version 2)</title> <author fullname="O. Kolkman" initials="O." role="editor" surname="Kolkman"/> <author fullname="J. Halpern" initials="J." role="editor" surname="Halpern"/> <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden"/> <date month="February" year="2020"/> <abstract> <t>The RFC Editor model describedflag any words in particular, but thisdocument divides the responsibilities for the RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described,should still be reviewed asis the relationship between the IETF Administration Limited Liability Company and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to replace all references to the IETF Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 Model.</t> </abstract> </front> <seriesInfo name="RFC" value="8728"/> <seriesInfo name="DOI" value="10.17487/RFC8728"/> </reference> <reference anchor="RFC8874"> <front> <title>Working Group GitHub Usage Guidance</title> <author fullname="M. Thomson" initials="M." surname="Thomson"/> <author fullname="B. Stark" initials="B." surname="Stark"/> <date month="August" year="2020"/> <abstract> <t>This document providesaset of guidelines for working groups that choose to use GitHub for their work.</t> </abstract> </front> <seriesInfo name="RFC" value="8874"/> <seriesInfo name="DOI" value="10.17487/RFC8874"/> </reference> <reference anchor="RFC9283"> <front> <title>IAB Charter Update for RFC Editor Model</title> <author fullname="B. Carpenter" initials="B." role="editor" surname="Carpenter"/> <date month="June" year="2022"/> <abstract> <t>This document updates the IAB Charter (RFC 2850) to be consistent with version 3 of the RFC Editor Model (RFC 9280).</t> </abstract> </front> <seriesInfo name="BCP" value="39"/> <seriesInfo name="RFC" value="9283"/> <seriesInfo name="DOI" value="10.17487/RFC9283"/> </reference> <reference anchor="STYLEGUIDE" target="https://www.rfc-editor.org/styleguide/"> <front> <title>Style Guide</title> <author > <organization>RFC Editor</organization> </author> <date /> </front> </reference> </references> </references> <?line 1485?> <section anchor="acknowledgements"><name>Acknowledgements</name> <t>This document is the product of the RFC Series Working Group. Many people in the RSWG participated in the active discussions that led to the changes listed in <xref target="changes-to-9280"/>. The authors are indebted to them for their contributions.</t> <t><xref target="RFC9280"/> was authored by Peter SaintA-ndre. It had additional, extensive acknowledgements.</t>best practice. --> </section> </back> <!-- ##markdown-source:H4sIAAAAAAAAA+1962/cVpbn9/tXEPaHSI2qsi0nfmUxGEVR0gby8FpOZweD wYJVxZLYZpHVJEtyjZH/fc/7nkuyZCeZHSywPRikZYm8vI9zz/v8znw+D33Z V8Wr7O13F9nluuybNvuxWRdVdvK3ou3Kps6enoZ8uWyLW37o5dmLx9l+t877 ogvrZlXnW3h93eabfl7QAGVezdvu7nreblb49Fyenj/+MoSuz+v1/86rpoa3 +nZfBBj3aZBHXmXPX758PMP/PqH/ntF/n9J/v6T/fkX/fUb/fT7LXjw/exma ZddUBb2PHwyh3LU0etefPX788vFZeH/3Kntd90VbF/38W5xsWOX9q6ysN03o 9stt2eFi3x12MC1bRgj5vr9p2lchm4csg6fhC28W2V+bzWab1/grXv6bfF/5 3zbtNXzv4vynn/BfxTYvq1fZDh5a3PBD/1qu8rpewHM8NI18vsjeNjAP+Pdm X1U89HlVfCg7+wO8kdflf+Y9zJYP5Kpoy6LLLpq621d9WV/LOQb7cNutin+F w5Dzoa+Gumm3MMptAYvLvrl48/yF/vBSfqD/hS+cffnkhfz4/MlXX+qPT8/O 9Mfnz5/pjy++fKI/wknGH91vz+KPT+OPX8Yfv4o/Pos/PpcfXzx/8iT++Mx+ PHtpPz7VDyM16I/Pz+DHgAfuFo7Le/GVPvP05VP99lfPzvS3z57Zb188f/w4 flB35cWL51/GD9Kart792w+X3//y+ttL/FeWyS276g9VkX2/L9cF/zpvrwsg w5u+33WvHj26u7tbpAf1qMNXrvGNR/QK3pNX2SavOh7CKJT+jwgv3uUQ5vN5 li+7vs1XfQjvboCU4NLut0XdZ92uWJUbJJ5bvetZs8n6m2LEDhZZ9g5+vcWf w7rYlDW81d812U15fTOvilvgGH3eve+ytqhghuusb2wgplAY4ruy7fpZ2DVV uTpkNEyJhJzBrPDhvzclTKstuh0Qc7ksq7I/+BnxQOHXpn2PdP592+x32cnb q1+/P51ldzfl6ibbtc16v4LJyUfg37umg92aZcB4dKQgl+Z8B3+/zavsmyZv 1zjU+Tc2VE5/hKe6PQ/MA8E6ropVU69tIeV2VxW4o7kuZteW27wtqwN98OiC whuaLb11USB7gim8uTjN8i6DL9Ch7fMKhmnwhIqizpY85OvLd9+F8/UWNhDP lkb4odyWuPM/lLl86aLZ7vL6kJ3g49kPP1ycwuRf11m+XtO+z8ItzLLZd+kU cWfGdLDZ1zzTvC2yurnLdkWLd6lYB2LnQHvAxmDe22VZ84xksnhAswz3Fv77 5mI2zbaCfAcO4eLylI9L5020U+NOzGBET8MFCJRlVXY3BZGQDAK8G+5aW+Tb DKaY7fbwyIrnBAvb7Ps9rGFEhkFH7ZSMkGCAyK5vaB3wS6CsDr7EN2Cd3RRt UdaLEK7KelXwQ+m3VGTOsgpehcVmN/ltkS3xLKsib3GUfNns+0hFSNq0SLpt i8GlhbXC/LpmW/AZNV1hQ9uAsHUiUaPMXuYd/Alm1d/ksG8fdngAMOvhB0yY 2quLIeNwY3e/W2Lj5JBb26gojenS5G0/vu3Z1G3/OoPLkP0PZZswmxwvy/ui XZRFvyHGWazvrh+hHvLIjvXRv+Bi4czwczkQPdxoJJcDUUkfZwMbZINfl/3N frkAun6EErwQCf7IqzYwLnHabbleV0UID1HZsLuNC4UlFf/YA7XSp+BiMp2d wEJPdaXCBfN2dVMiU+qY3a1BGqyUp+pacEdUocn6YnVTwzOVsnSmP+B5QJbV fo2367qoixaeIL5SLvf0QLZpmy0zFB0LOEGBM6BzKuproHOYBgwAG7Dd18hW gDvdFVWF/0vqHLDOSBzIH4kukE3kt6CAwP0s4EMFEmxY3aDIw5UAY0KucVvm yQTg9XO8YN0KZglrBpby8aOI3t9+I97RhXiH6LrB7V/Twsqa2WVH1/HJy2dI ZTYb3oJeLoiw9zVyqS2yILh+TjYS9+gW4Vekl5xPhn8pb+IJLJv1Qad39vK3 3+hwixx2Tx4tu2CsFXeByKygudJd2/Bt5Kdnx1huKB2HdsPsovjAFa1RFsjR 4tCwFbRdLLzDptnD5ECZJOKRBdLGTO02LodenNQYQp5tyk1/k8x8yHtnU8yX uC6OcI0yrWZml1z4HO/m3Q0woQXfHHwQ17JpQSO+A3ZgG+DfitJ9avuOLZHe g7/zRV6zyHJLFmXAdJ7P0ZR+qdeFsBN5/I8L2s8XsvdzzFmi9qxvyw7ZXqr2 4BBHNBIvs8PI1BjL7E+pJmGsmuipPHmC15xVsFVTVcUKlXW41LBo0Ku6wrSn wX6Jjlry1UJm2gAD61DUd2AJ5rBheHnAJsIncuQQMF+w/na7ZlLyOImJdw14 CvIIOjISn31INb9ZtkIJDF+o82v6tVzLtljx343vwGhAbo6nlvUOdAB/94ZC 9z4KDCNdfUpc0+hooQHZL1XxAc6+bMqqaHeot4Mo+dDb9Rpe6GMjB3+hYGQQ rFW+8ldb5tfCpc7uQKCO9EI8CSSi+yePpp1+YsssGAdaF7sC7lwN2hzc9hWc DJyxcRrjWmvTns+/oaNwZx0J+fJ0EX5siCvCMBVxDLEZ8U6SrgZSrL4uRHzq gZwdO5AMbH2QVrCt+1r4jwxAx/zwYXYh4wHFmr728aE8NO+bOf7mN6GIjqlJ 5seSSSe0zddFMopTwVFYt3RrYQpnj8/OFuH1Jjs0e2I0cL5r0zxt94l+G1D3 Yc0k0Gn5N6D9l312h2YKfXg9o3Fwnd37cickj+ZPA4tF/n1bFne0WjpHWs5v JAZzUqS78romvaWOmysWpJcfpBETeZJcg/1A9VdfWMEakMvUxR3KJWBjcPdZ MuCvovpu8nOkq8OY57SjXTEcIr4etY/iQ9GugCWtZyLW9Trf5J0cN94EeOeO 1E54CJQNMJl7pAfgHqSBwDk4myy7zncdHlHU8YvJj9P4Q+39PrUfFwVXHo+5 U9Hq3ElRCcaXcdBys4FZw6isJh52pGOSPgXza1oSc032vih2rB8JZdb77ZKU Rv4tSG0U6tGcePdZ7/Celk6RtofROEKjHETiddHOmKVUTU+8udsv5/Jgx+pV W2x4pjgg8n9S3GQLWlTKaZvLLv0aGQlob+GfV+MrOqQ/vCBljSpxXxIhlrXa /yZenF6Bc161TdfNaX5oi4HMKfo7PFx8dvhpVXH8CoB5gHzO3jaVPPB2oGCQ /sukoPcjT29Iok2NZOprb2NHFeseVSNRxe53tOCT10jQOKGRauRcSEfUkkX4 pm3yNWr8uyLHmcyQMXX5QU6e+N5dW/bqESrd9Tc/r2mxOK3o92HjWl9zDiTY cJP8w8cWWfhrc1cAy4t3cN3AaMhDWRIdRLu5pk2b0O1VMqO2t9yX1dquhZh3 wGnWBc+naSpZq02JOYauNr8G0wv9AUjRNZO5sJPF+ALoDRvxEbQ9C9gqkd4l U1sDn2rN5wcyEo6mI7J8mL2DqeHE8bkLnO8vyIlwfW/GfBfEXc/Pz3Ftv6Gg iHKDTvRVCP+SvZl0uamXZoKh45rReJD7p2YP7RiK9ZGXkvjp5/vwjpHm5/nw PqkoT/nwmG8RW9XjyquuQfmOyhjs0rspKnU0of4rmcnIaQZ7VsI76/yAygf8 D90VPcypXSYJMd7nhWM/dgv46+gAEPrhi8BEPL4NiWPMrhluAh06KiTRy2bK Tknb38HWwpsVOi1Qx4A1D04Sv4AMwg+enfA0VyXdPLw4Cb11p3xzaIt/x3fG KznQVzp21oDlDhpFviUj4xqMnlpcFkg9asDGF1jZy/m6dzCk91+QS34xsfkr JEPae2MmI8bLPIh0MjnyhAsxz8FfExvad+yaEleM9wS506dlk0SGt2F0mF4D NhRGEUp0Qr5GtZjChugHhGPY0VajLQgcHYRjs29zlIIP3LtIbDQZnQNHQ5Bv IsGKIwqN0iT21z2g+dp3CpXUSDkL4DxsQwrfYcJ8QLJhW6CWAmwSyK4inxNa wmbSlC39qi/7PTuR8vfFTVOt8ZWTYnG9mMkM4bRZ+sAPgw2Zyc7CyFtZIy7j NCMvD/z3uiHXUw4094AU6jsWwvMd8hrYTDArcEHjrc/jmQ8YKKinNfqPVvuu 02OWYTMb1rjem4sFcpnXvGn5skPdhTxOPh6kBC7kwPpQzvNiN4bod4VKIBGP 0axDAwf/gMxoMGNS9DAuY+JZRTNaIXYPFosFx9sqMp7b4hr0D/3ABmMKThHC ja/yA3IU9FSZa9FRtKyZHHgfTKv7Xz/+kN02q3y5r/L2kP27xDz/Y8ZzvI4T WBHdsFsWhoHHo7t2MLsdqYUtfB+HL5SRkw+hZ0dfESl/le9oDaxTb1EHXXk/ Ixs3bH7h3JBGWCo0dXVwulC6z3OV7XhqQkh8khYZQC5dVc0dWZYdGjI8I7jO u9U8YS5KmomRKYMIM53yc8rl2KrL1PhPNIt0G6ISNNTuHKWUY8JlsqR77Pji P/ZgyPLJ3zdH8xQcd8STY5h5e/yAWvC4JqImFIX57oZGYJ9Dh7/E84c/bEEf ifPY5gdh0sjAchgB1ggj3TbVHk4dWQds0SP8Lny1ORRkhTapmgiKKzIdmmVe RdmSLBedXSuJP3S0ib34q0jqsy9MBYJawMopibNsSTcfXuHpr8muJ9GOo28S SxGFBIWvxRvI7J7JHYLfHPhsdaXoWn7Nd5e+i/Y6hWeYT5qXAykKGRSM0ytD g09eDmnLOMSMbXyRD3n3nm0KPH7kAuR1RO1KB+XLntvgu8Jc+0jZQ781UB4c LwtGUbMvmnoDr/Zo+cnf6HOv0y371rbs48OVvDJ3wyFr8KNnFONYowEBkrK/ uctZh4nPkGkqI6WGK+6oGkss705Qfm28AIq3/6cGTS60LfQ7pao/4w+WXbcv RCTjDWhWq33LRJbbbMASL5Ep0JHnQ+3NqIdHgW9XztpEFtd621BPgnTCv+9R UtVR0TqNhHSEOSRHPVT6UH1bNuIPTbxu4wmIfcSq3cxtPaykKEmRZsF7V4Ie XtbACG6L+HkTm6jt9kWtczkRJpuv3tfNHXCxa+UOkSpNe6TwEYkbViPlnDpQ eGj8U/ZlgXa5yrtCvWJyKu4kaYqYRLAXfz5ZM3j+RCZEDq/MAQA3SIQE6Gw5 sUi8o7cUx8VR4JZXzKJGt2RK3OC1QXZ/YUrWx4eYdmNK12/8NTK5JDWMrSva GZKhmCvEMpSd/rRd/hQ71FstHYV9Qz26qYmzLQtV8cgKk2Ao8uc7SWbwnBpo mOYCw/XNCtRF1HEd326LFUWU15wXhsoZKrj8cdLJgLvlaIfM0FgvbtHPGoXV INTrlsA2GZzfvtAEB7ygu6KhaCmJnxkeImutHPlIA8royUQlKKc3c1oZyIPB UxTWAx4C/yQtxTRw9chxfgdMGkz2ByPt+MGMnXzsQCSy2eK3HhxTxx/QXgub lsMAbtfycRDPZqZisd6RkTzQb1G7enAxmpiSqJrcuPoir9VrxBuJc0EHPBss 8MgeQ4gUXJ9FMoA7j4YqyCnebQvVi8Ag0gAJ5CkjKu/RXSNa4SwzJzVbC2Sw vbuxzBgmU1buorMAL473AFggWQIq4kGEIZETwq0UOZHuC2mKnQyOrp15Ntq7 7Mdfrt4NDoeCw12BfKAvjhlbrJfgjXn0+i1eG7X06JR+vQFd7chf4y51ykHN jeu1UFE+1fGjE0aJFG92XAkzQsyXo3A7heBXcADIRCsgMQrIF0RCc3Le/Lvb ybtiCfy1+I+T41mCp7ZV0Wu1AboU1/9oPot79vunn2kgU8NIcY0K4BJZzdHt 29cViSrUgZCRUQz2A7K9mbgUZzjgtlmjG5S1bo10kgp8hKF75jyPGVsaP/tF vJV07g9w774T7RkPSjKZuwcafXp+Rqkkxx+cWT6Ay4ESqQHbBKf8DSb0kDKy RuEhP5IWhd5y8vkMzHDzYf6MrNSsyyQdLnJezrLTaNiaNgkzRdCSJiWykzCr EqiPAqHic+xTRqU6aXY8HbMb/VWXSCe6P9DVR+QGPKi9jfme1xRj6Ho+dVQg OlKForLKrjJgL+LKJXVUfzln1gP7eM4xO1O5P36EFSIDBoEFG6v+6rjkXExP WvfzxYtF5r8Gv4P/t1SgVbM74PXB1bOhRT+K0urSijip4DDcMxZiJYUvWfEU DyDviGiaTJxv9uTFNu8JeieJWaKQ+fhwx38m0uHlCoGz+pJ6vpFG9pJeggd7 z8gcZhRPA5+x0lQlXua+mcUNFHtzNoiT+vOXJCMgE00+Mf5GfFPydFz+wyip 4rjHYETEJWg0awykETPT53t/C2hjrrwbSDVLW/l/q3HOc5EwCE9FPLZryTpz 3jCVp2gsYSCTzRV0dbGYHvnfSGCLk04544TvT0OLZoqLl1LOkI+VPxE9KXiL SU2QdBien8YcfG7O4kHCcjkeymmgFofBTE+4wmSGoBYjzsMHUao9wK17MErA eGDpWTgersU5rOI/zvw/nvp/fOn/8ZX/xzP8By5Vf/Ecs78o80HYKCz4wT0R nQcSbsUUtLXomT9Lsqxx+RB+ROsHhSIt2ac79Hn13tJ9XTx5WZArfxG+KVY5 G0TTCblusJl4b/hDd5hcoCKLfBacMhqtEv0cPclfCw+znyXCpveU01U+PrTI 2ygJqWSfwCgk5uOq7lSBQzZhqk4Abu6ThYoAVwnwOVmBmcboAj5ztGjgriFj vve1B4NRJ0sJiCXVqEXXdgclVFtrppFytkA3hHZZs0vHpQexYmD4+cmwuHwf 1EJcGdIlZpmqryKWJAT7wIhRi8Y6mb/F9nQQ9khahIms2+jkV7U+yZWMib95 HdjvR98yzipykwLxgwMcFyhx1uDCU8IfjeuGT8d1pwO74Y8EdsMfDuyG+wK7 CZcNIUmD3mJGGlaFHWJWCSogqAoMdSF1u7RFQKFwy7dTLMb0ylJOlzfD/iIU ApoEk5dPnGA6pxt6/HrOAsux6CDufWqUhmgl6U/+dXG5iN8G5UUtPsuuMFIn XwV7u1yiBlj7QFBt0e/bWv5tziNMMuSEC1TiyPWw2bdsCQtXJDfjFsYK9CrN 2p6RqahG95fs9caSx2eD4iDO2bXAUd4ZrSb3MYgLgTdgrwH5NEh/xPzG9QQp poF9413kkJxu4MVl9N7KLc3XKN5tU8RBS3sN1Mmu7uCCJy7lxyaUBiBJ44ue hkABSUvcRa+rKGBtXnas6ZHrlnwDJWZIsXJDRLbWWiqTU3DESVBWF/enshrC n8tqCDGrgahAVkTe5pjWOg5UsomMscEYhAp6Dkv0WSmdq3u7cbeEd9T8uFzn FNN72BPBh00PldsYaojnPZM0VhGtga64VRClXuJOTXLOt+T0ec5qiDnVvF/O WqCZ0CkGFw5h7ygHP+FzA3ZLwUyKEDBraPO6g92CV8O2QFoouy2LN01IoihT 1J1sH0aKQxhzJmYemw2nlCd+svGh0SYZg5vxPd0WGrIpkvCgyzEGqr2SrJwv seJlmNN9H+c2hs+ULdtfi1WtgUZS3URgfhtVJzAlh+ZjCG+O7s+Yc0stiPgp Y+FbiNaXD+/zwYsiZwxwixGSJabcL7cYZ2ArM183O7YpZmpFihXDFz0MJjWl ly2mvrTLO5z/Dzn8fEFFIk2brbS8SjhIosUFojlvHo1eO8Hqso8f8Q9gT01/ GJboK4gG808Vu8CK3cIdxx824sN/gREf/rwRf/LuRooFZI9r/DmGZ8ysX2KB lPo4fjsN4f8hcz38/2Cuk9F6leS4ULZwDIPdc+foIXJhoZSWRI1PpP9KWgmr 2Yfstqj3FPPmQirNCxCi8suuKjCNya8/SITx+meY1D8XOlGfO4aO2XFCmfol OO2IDoas2r2qb2DikIv7eIrY1yGNGVCF0fLvGOugwsa+nN/ATei6LbtAVVSn 4XyQDPxoLLQzowy9dWU3uOepq12YJp05pbi9fffdLBtsr1a6vL68Ai04yZwL XbPp73DuQF8w3TX93B1gT9SOivqg8AfOXTP1CFnJILNu8JHPS88bD+LPBINj 6BVRTRpZ257lrsueDN0KZFjeVgeLi1ky3YSJ6wpXY1gn+HIIvdewE3U22mkx pe3GMZ+X3Z/h8JuNJvKRqdhQCiCxKzIaj5jdb6dQAU6jqUQfvPxQrPakwnxL hTawnxxfvhVKCZ5wKRF5mJbjqNkyH8RjX7QsuAPHpWPA2BYbc92zH1N64wR6 ZDNV1wQfN0pmJCV9emsvbvKy7YS74IwwHQf9Nyv6w4wyLpw/RM3sq+91X0Kj FuHgmfNv7KTkabwSICxwlTXrWSVQ5F0dUpEpKUvsZZNxRaWVP5EWjHuHFmW+ WjV7pKAN7dmuwb0sud5a0zQ2xnUoNjHOlGqouge9C6uitTwkYoFcBpq7dDXc J9o4jWJz0RUvKGyKYr3MV+/1cF3Voa5GC5jdBgXdILSU2SKWDYo7y2eSASfm v6CEw+wWFFY9Lb4vt1qcQPg4XGqPPlaO1FDgHS5BoNDRlDMDeVJ5TdmZ9Lkv Ogr8Y65Nr/Jl2nEjsyMzRVKGM1ZkUayi6dKFgW2pU2UtlzmfPSwXBdcprCZs pdCEk3vYvT1zIgtIodj1elRSeRa9FwFMcfyjqlbxj2m6C90MdMjiQz+rqcKX xNW4qoOXK/woLsd2TcG5cZh00YEIQeOTPpDjV0OiEhs7wBvO5NAWsDy0mLCG HIcWy6dT/ZEyhSkmWKPFahFBcpsiqz8qZLnY0wZOAQlsHCdQcRiqA95zNhQ6 NA5mAZtzR7RyF4sTkxwNXJWHxMO7kJhrHz8S/pEUg/O/2FpDTSGuNeWaPFO6 /ETb6h6B9QcCXnJvUimXTjQGTy1tkRAfJMgb6xeK7a65KyQVEjMb4PtzFKxY JdjUaFPPMXmXQuo3h2VbogTiY4of0wyXvK6BQ63E5IL93Wxw/2CbQMsQ31BB JdJhiUVVWaI2fR1Z7vfqXIB1fQcLR2cK/i+H0MsWj4klerkF+SBkk2QvGEgH cbhHTISP4DAR70jSrLpHQdwZc13UXP0a87PHT57NHz+ZP3n26NRnKiJUQyOL yDvKuSbIG9m2SMWyL2p10BCdpk6aiyDwLqdbIXEOpKo9l5QjuWNKHVETf8kf ZXorsXg5ZUhwIcjURyI1n4QiVfnajwhegJhc5k/g+5kfxHKZ+AKlFKEckyJT uEeSTRikLOH7sv/rfkmQHunVeMv4VmC6caS843QeEl6r3MrajaFsC9iatZU7 sOOIkpM7qoki0ymXFBEOxet9DbG2LEmFpF+7ZZMLsacgCArshirOzjGZu4/2 oM+2TYdMjQvbcOSK0WGMPylkig0lhJb4eJ5ZlI8nFyZzypz4XbjcQlSmJOWZ 2SRn7eFHQHDg4tCC0sRPTL9mcy8I50xOwdJaTZGZRZ+c2UifrMpMTT6yofLl fMf//G1kAt4LoXUsyBQEnSSNNc3kpuSYwdtFtSVCrZAvQ+VliHguA4kuzjre SfbvJgpQV/SMRVOs3rM9vcwriVLzKMCVdvve+2RES6JiCfGziSbAqAZeAWbs ibYgv84wGuhgaJYHo7ivqW6Vlk8V3nWTRBvNR8qKSrvdE1qDuFsbLtcDJRaZ XZ/m7EcFAXMa0ceheXmkRSGjCJFReC8U1axjmq8m8bCrgqLXBe0rfHUYQIsL d0EklvqdxVQGZjDyjg3oXprT/tDMCqE+UZGV+ixC1PU+nCdzj97K26ZnlkRv U3TrXDP2U4q02DVdS44XvLI4U82Cj8cBI5FK84/aJJ/1GVjBxFeswuz+j5x/ 81nfeDteiv2eLIf7vxIf+5yPOWIdfzMkfza4zQi78frq0sKfBPERZxbGM7u6 tHDQPfFlQaWh/HwSI1wkILXvjM6kNfHM8E1EsA3AqWwu8CMXVKu4SyxoSGgs 7k5MVaI3g3A2LNNdFrFGysVCo0+RjO69FvQbNw8JtCLBGiRHIRIXlmlHPXgC nbLio9DLQmx1quZKVty0SS5CWBcViE/KLAHm0Gy0GvkzDoLxFNL90jgL3mj0 eVmhgciAfLgEmfYosyEgqIREpmj62wbLKrx0H7gMYyBarFHVBVMeUjf1nOc8 A6YKw6DW3CQ8xcT5hF+Gd5PMR9m4EzoYrUPiLBZh0V4nEIdCPqqC/nwkrVO+ uNM7SCFBtM4Tz/Y9kztW3vKH5pUAntg5oA6rp8AOnbj75iZBvySIneh2+Fqc NBPPStbm+NwwW6Aq87IzEDwxhOnIvBOQbiRrMzbPdYEu0rIPXkfLTF33nmwK K1G+GKt+JN3OoztJMDu2pELB5v2NFyDyj+9W6q+h+vRyUcBVZ6/ua2QfkVsL ChcyVKZrc3ZFX9cgPOQ+kFQ5Y8kT55A559gQ4BWzDSZA5BB0GGNnWXaZr27C wOfkVR128d8xQos4nVCdiXyfEpaEY/DxH/E6IXjgaLNYIQ/GHOD5IUmh41uw UXpSTHEwibSwOr8BxSngZ27zFWiKpVWXoYdgT3EolCLlxuntODewfMCKb/Gf lCCxINonT1Xeufy8eH5IMnB6GYcD8l2+KnuamoaB7squCM7y5AXDZPnKiKWL xgK514iLKveZmfZxknP63PBgEu2BJ5TSk1PPQ1zc9DBNVyT1ITKAzti9n0ol okLgfmVl80WXcKQIVJZggsHv2Iw8iyv21tcmQWpP01mkdvi8E2ZsMBModhVv h17Yv+mhp6eH1bZGDsBFU7IaChjzAMDO+4Sr85ij5e7Wcb4KNIe1QpQIBtu8 KkS5EABMOnFeCOWpCEdptJaJ+cyweCki3iaIYcRAKCZa5QdEkbEz4YUfcEPj HjhwKrgvBRV9YDgiB078odzut3zAiAV68vQ028KMbzCKgBqaGQc6shRxrvcE P0o2PL06p9eQzstGFTecnvN1cckJL0ZmUGs0Bz9uHz7f9EXrhuBB0XoCAe5O METAB95jNtS5RDfWbPgA37KAE4ZP/AQ8VKUoptSQfwT34QZuBNn1cf+i+rPb MXpartsR7GoAv0WLkyxGMkddBWscKjGtwzDaVNRYSqMgVcitnZX1WxKXcTaX XN9aUFZXNw1e8Jyd7pIstW3YLjTmuqfkL9Q7deH4V3oX/sCHb577jBB5BXwL F4MzZAoghuOjAe5+8Uw60e7vm84nHOtqvvvIlV5bRKoFbnLEt1vW8zBwMsIE gcFgAIjQvShmxOFVQYIEcTLhkSt7UTBMkixGZ0DwaVr4TuWfrW0t0SXZ5wkA MGgABBghrhfvzyc1W4cgiWaV+ez1kFj+tF+bo7vGNmyOUx7uWcgr9CBgYlGz K1cG0EapVBQsK9ccOUNngpg0vK91UQXJ1ThVza6RHCM6bC4z5S+RJpckX8Aa bkkHu+JoCPrNNZ1L9wZHLT4MElFG8I9Bph6H52yewtR/oEXaHjRphHOYKsW5 2zIEpePbOONzVqc9hhhqOatrrPO1bHugdDtKdl6Fce0g+7gOQrsuMxb1narA 5Kkcni2wBBfjPoG2UsdV8P/oO/exnphfJE5wjoehTzhR7NUbigTGphW9nrjW Izeg12ogY9BSGt0hKfFXCpHMHTzc0dbPeK8FU5xmooftiteIIlI7nDIveosm 4bEpfGLgrR8mBonjUWmI1UIBKBQIG04ZT0g7yR7kmPsf9wyTbkUpB31jgLbi Jvu9PuJ3onDBhG+LWiH/iC8ybCj67Az7kY2e8j8LVdSQOWMW54a1uei4JMAA MQRTvFqukuMJDTBOY4uK1IScSH+UAWZhEGWzBGpOHQElh3YM/jhKEJbSWJQP rznC+vGhFKKP4q7xOLRWBLYCFJylovuZuhaVumGWo8+3pNRULjiW+6bhB5ZF 2luCVYlBdJUukWbTHUlaklQJsOVIaVCW1SMNZquyBXrWUi1hWYktiHdR45Dh 4uefLi7f/mTSukNzYmgBRq8uOom0tkkrOjnRWZBxEWkUE6R7S5khpCEMjeHU w6hEO5kamW99C5IegYw07E+zxTkAA7lmlxgFxDtQ7Upy7V83oI9scna5reHC UoA5lt5zzCWA+VoWt6M0As0StciPNNeIyd4zjZyzLY/TTGdHwWP1ZnPKB2L+ w7oryZMdrjOkA1ByNS76A6p3msxig/EfSwWwZnWVGHPDxazsyrk1Fmh5Qqga KykJoSZfDj6GACbFnpQpj3yvCUvo1pwTasNNgbKfvn9rVTDTBaIRopLN4AQ3 g2DQN6qKI6i6z5jE9gPRXfAnkNrCn0RqCwlS2yzrxGtLbmhcM6XJYKZhx4Aq Ih5j2CuvKE5mMZQZO12dnVNjRLAlVPRu0vdBJON0WavrgGkAf6Dgjnl2egzJ ouqZBMvgsDf5Ck+LLWUE52nySvjkr3LJgVPafR+W+OpRGkvWdMAYyIqYAOY9 PNpIiDPOz2uXU0LhAgrqJZmDsSQvbqJch0A1YpxKlWYfZidpPklMZEd7ew/2 MIpyTcayqg/LIJCyz8mUEsbGxfpHC/yRkYfZ8ToKz5Kz8tPqQ7AcOBX9nQ/6 f/7L6J0yI6qLSXDZydJXWKcv0uGtCQV7gyVWKRM8NQ8WN1VxWSUG7CcbrrP7 mmkIH/ZpSQwsM5y2S9sJd0T1ao2NuW+6NZKeg5fNoo6qRaL+xrc42bdFOPfi k3L9CJMzZm16fjzTi7jLD0EeYRWYaxcbNvCIT5o9bmdE+6b+zxDzBdFvF8HQ 4ZNyL4iPmliKNVltiLgIaPlirilcE+Bsq27MXSdykD2swj0JnUdzObvgr5xU ZfqkKbrIkr+QxoQl7VmdKzdFtXMFRkpZnCbCtY85Jyy7rLmQCLnP0RA5Ri5e YYrITX04kbwcNs+xzAvP1CrZYqpm9FGM0AqTm1mTJQi0XvYhOtPoY5ovQC4o K9XVLM/O0mrtKMLoKDz34/tw3jOOPAmGmXCAZNhlUZF6w3dYcS4GaQGu44yQ L3KtWzb1ekZ7QZUUN0bKccK4HMelaSTXXKZKvrhcH1dfHAF9lhwIq4r6ur+Z jdaAH3dxDg2BDjW20SoIzqwLJ70l+0p8xNJn0z2lenYNzXHIlpOW7HlyRIgj 3jGSU7ZsbSfMUQpiblWgZ4RtuP1S4OMrK3KLPlUs2595j5Fts0W6ossoY+wX 86x5fk9WQNwWdK3TB1pU4CQYfhh6IGhzbJPFK+3Mi2nfEK4Ktv0Oc4OQ0cUQ e5LsCsdP03V5t11ShDrI7kmcJER14f6SruPJJ1LlxQeUHIC9SyARckyCa4Xz DEOtefzdQXCTC5QTcZh4Y1I9kHoL2CQIXu09FqyrnkF3cK2Kf6RBnavZIzCr gpHbw+fPt+y7otpkMXEhJCpqFJp4eOK16VYgnpXpxYkSULWZIfBrVNrBcEXw ++C2fEa5BpG+7ztQU4KDIPI4B2QslxjtiXsvhXzTM3DEOOQy5MIhZAHOEGfO byN7N3UycQS/TOYer7ScX3rnJPUzHsUIW5BdQ7nE2ZboUWOtnzEN4qX6lTmu T4x1fBUtEHfi7D1o8EYBU1TZF/2M0dq3nkhCAxlIW/0bc6KQoApkWfaXLPu3 y6tXKf912clSS6nPiodh8DyJ4G5wS+UcGBIUlPbACTa8rzre28uLX64uZTh2 06O5F0vMJOxAYcYIWdlsguqxNBKYHYkSaIPk2dAnwgYEyOoq1xoCVRdG5jZe DqntzbKf0CyDPyOSWhR1gUtBUXnA9UnwVwvVXAJfzRqjgUoTs6ej9czCreGL TjdxwWt8R5pATpoQRsuYdrBA5TAMp+JhbxBOL7d1o82qp6e7/y79ouocrnwh HrFGqjBXSbwh+FdYMDfzlC5oBIghnMYZgrFC/3d/me0L8lLZh0GfNiQJrYz1 KUQWXvFPhimfRzbyeZi/4/6ZztI+ZLA5+8rsiU9xmpNYxSwe8aFmFxW5dDeA w1TAODFEx1ShDryR6+2YZSB2nzcFjlTeRM06lj5RWz5Us4PxVZSHbrQZ0ABW fY98kTHiQvcjMGak+Em8vOXoLE5KDatZRu4IGTPEMVn5vsN2AJoNi8q0IUDA v8i5T4nzErL2Wr01frzvuEyWRm7CGurM61V0l13dyQgq4/waOI6W7nzeYZH2 E6bUz1zwojLf8Uk5yWiffo8E1z5YAV3LFPxCI8DdR8k1RroYH3LZmczQbYOP iwlhBsNQ1k2OFbj6bMbZieNUbthqiUxZtIwZI+d7mKSkl0HIzUY3aTjT0QMS 8xdMmVIEPCqLPtMKD9esQkt0MbVM0tEH4DZHvxm/l1MJ0MbQozoC2FNu5qB7 VK2K7ZfrnkF6CoRP3xdjtIEuOGz9Y7hUEQKqlCgs0TfX4SRAgNTGyBJZnM5H pYscvRxCuTDblCJWmMosgSlFF6mmt9wRNKx6nCgIR1jSKDAwfZmy/eEX+3Yl qX1c3Ms6qMaOYmkn22au4y+iXRI/TtMNxpjhBpBjsMr4j/Q6YRqRu08c1dNa QnMvXXOHvcjxR/zCZqKo9dpxs8OIcA4vEIoPEBM7WHf73iGJ0VMdR4wZ9IlA PjCijAhY2/12huQkWlKsNUPSQlxX1a/+NYW0zU7QnuybV/c8c3okIaEhJpWU CGXU1IwQEDDwCsSDUODTsQJuplRQXkQyX9v/0rzl0ugwJthozoIRkVaMn7K0 KRUNnL4S0f9C7F1APmJJmDATexTTH7RyZ6eDXlYhfmQBdVFZnM1b1Eg7tcxH 5swZLiC3rshwovZj6JHv1H3XNeTkpOsolZ+nnNGI+XDa5dA5229yxWj6hH8z HPVvZp/l3wzT/s0BbGziOqCzZj7zAW4xN7ik0BaGsajymvKvivYwuAIpGVAn gvcU1dAQUJgIh071NjqVTtV0efyoXtkPdh+L+prib16FUgpMbiSvjTDVNUCh JQxJRZVvnGwcD68O6zKMz2REQ7B3+YpxdYZTnlHnq84jpWCmWukDoml+C83R gehKEol1PRxuMjJqmUG0tlfGYZ0Sda7XlsJn9+kg0oFUHCgaAtFKISlBphLQ ZQEcmJLZaUe/MO+m9nJ/9QW/RTFZas+AnUFhkC3BoAw8wfzsL29/yCxkJzxm EI2ipWvv39EI9YEtzFohK1rXxmQzUjqTYrAwyDLLTvZd9ILuu71rCDMX3SJG g6i44ILAvbAIvt2vzDUgjVM0P0LOVfecV74u8jXtqz8OPLmB95eU3QpVLsJC YamNms9dQwlLSZL2kk0vjPRv+MrCLebr7BrLCPiCeKTTRLXwGXz3ftGt2piK a/rM0EeUh3uIklXNRHNHYpLaFE0gi2OT8VRiIjXq7kmHFE3a8B4R9jRpzGWN TJ26QfvmXw6KbmiyYTmPxBHlCcyrYjrDPpug1g3A0NDP95KDoi4lBE5qfc06 gXlMoudAN4oLg9S/JfrVObUHQWrhH4jrRjiM2FzFAs7aFtk8zlnshxMTa52n j8Ul9yEhYqgonR+jFfWaPrgBac0AIMGAIwh0k0A4dhZq0jlGVxdNxra1RCyD k6ePTxGXkLMzMWoofQVaa1alCefxu/jQjCAmiNkF0PaIraNfkduyeNcyr8xL CbYjqfEb142XnCen4fo7c+FJdIJeiCgjaXCKPAl3VioC55dXsgz1oMv1CyH2 IvKm1njTp/dbJhWm9zvRiUo3PMpoLoWQFDifxiZaPv657KhjKjEhbWqkwEe+ AywWUNzTnQkxe+Totf13WUW+Qkkhxo+DgL11hsPINQ6GMMdZU0hOyFwMVrXj phKkfM2Cn7oHj0Ho4f2qH4V0qSOtwWwEnq4j2Waj5U73XijBmAr3UXiWULhI hCikyRYwC81/MzuRttOYEcW9xCTPkpBWG1Q4ThXBhvL0NX95HeOAudG0UhG1 jWqVrvEUkKnBzTsNQlKYFSW30KuK5HJRPoToXX+NQF/W0EBgvVw65yQmGNz7 3w+KMRhpLsCpj07ZoBh0s0rQBA0TpG8l54tLXAPbmKqI1aBn3pZtU3OkodZ8 Rm5VA6e1RQ5lzcEDxlf0opIKLW2mSU9ao66PrgM4EuzDYJ1r0A21CG+GOGpp qxEyYDHcaoDrcJAbzvAFDSiCeIkjcV1sMamrFZQjy2FCucPOMhqzBPMxw84f QX0loxxvuV0RZMbSTZ4/+cqBzD9/jrjywXDlXzx/8sxas6Hy8E0D177dVdya F3+zdL9xaSzPX3z5hDKE2kLTlk0DueoPsPXUxxL17KBJo8cwBSmKcGdZVSWB iLuvxtBX4DxQ6eyRPfVf9Um6x0AvHTaoJAvOOA0QxmG6uUlb9sDycgyrDGAD uDufJhU2yXStyJaIe0U2snbs5m84JGhRcN37pKB0BP3LCeUOaPrzBhAHXVlb YChY3pd/bt9F44xzACQc4dCLj38RtPjrfX5t/sd0BmGMazSijaQY+V27j5hD 969PWB6ov9xCmh6g97/oonYWcVNatE6lV9JdDaRzU+64N8J9TdV8354RgKjL +U6hQ9O+bAggaiv8Z2e2f3ZmiygD/+zM9s/ObP/szPZf3ZnNgMbTdrLM7RvF KHljGCXhzVSrjo6LXVNSPdJfg/x3G9BetP4lacDQcWmsqQT6UGtzGfW4iIAX ScHN8hBocrFbw5HolKItoAqg3taYaYP5aKxJwO4RzsmMKu0+lOw1Z76hjWYP pphzB4YgYE99dih6Nt27PeanFCIAJ2uUZlrPx3YTkAMV+Wk0qku7JXTU/CGp 0UTIBjMKKNTei5623hOGUxjWS2ylYMjw1ZKKIWmDkUsbg+BTflOr9D6L2vvM w1S742RRk11XxH/tE3nLXtFTCTOZrYmYu2+bRq5qse7OKy0uJPJZ7tfXBbZV KbcFxZVl07Y7BBkQ9C0H0Rr6vL0uxKKZaoysc3Wtz9lwBR1rzyDG6j1tC3Ts mUGnbyrRcTsQIgcEbSxa5+2NChvBaaStYNCGew+8oC2795TKrKkMjH1IL0Ww CmCwCovUxyPwrbpJcXDeFYneKyFpPx8sgJHsjAhuSDgV/kFmReywCTZkjqHM jmcg/UycS2NmMyNThSLaSTrcoJOVltormhMt80NOfYor5jWg1vrjC0Zijmq/ 9nD0PAfSmBzXWalzWkhEFEsvLNsdw8Vg2KXX4jwlTX/2gc6+7G3QLBk0tnr3 gKf0jgM4w0FkAA4pCZa9A+nysNUbAeMi8Axq/0QlDYEys+Ha43rFBTOxgYT6 JJW6Ccoa39WYtj1Z/joGphIcgajUukT7wMtJuha8uUgRbZPvE9NLSlRDXVw3 1p3GwS7rnbYuZ3KXuYIgHwHhEVkgHzIoMFYsPW+AtWBzMGrmNfEpxqXp0wQw +O4XXaLnVYjWysjClnhTbDbENvwVjVaLhVe9pz4ckTVUXv1/XZpJttiUNBtA rWsxuRdPkeuFBN4z7vdwlCG+bkSFYapqJYtAyqAljoiFYJp4uaPGf/yRyFy5 H7yvGaBOFAQu5WIpkUvTno0hvxOC8JhdpMGhS1lqwyNXlkuGKdEwZziw6zyB JvRQ9e4ejFHLiFnkgTdESi3xXrNVeXxQBHvCuEO5SVlNs2MB5vB2ShNIh5mr fjWrj6Ja65izbhJzfIyINbfl7KC87uBANTk2pQtMbmD+YX2FYKur6EcbtMzQ 3hZvzE7jEsfU1WYSMkf8WQ05+zY5qS3KH5OUKDbGKJSmxXLIU1kgxXIighAQ cI8xLBC3AjQ/pQkd+EZsjjvsTZKC4IbC7uWuZaFEQnhDCOyO1VjznnH3mEW4 ZBloXSxIR/8xJ3+BAdeDMYjuKoTUFf1MY9txDtGtixWHOPjXsQcMBQImfF8R EFTxeJ8/PTvjAswQHXIOrIdtBcrl6ijrgOG/Pn68evdvP1x+/8vrby9F63zt A9wpfDAlP2t7GU1TEAh4NoopJ0pLRY41HNP4FX6NlsMNs4bfqjnD2bVyqfJD s4+NmtGOid23OBwmISDuisM3E5vg3DarfInK5iHtsUr0dB3nsEqAslfwgksu HzRqYU8PTAE/UGiTNpKSPYO8F7EZyCrf9QbXOOg8HaI5jIYm0PPboVn38WG7 W80ToVtoXh32PjzSIEBUV/xxfJdcIpFrOnO8B+VJzP+mqwr2QW1BZbt95uBD +4E21UXB3L3KKVctzjdIrjfDKSNP4ySMpAhN1Hbhl8KWI9dzbbxiMEieOpIR hEWghAEzvnKkeoybSLL4oXp2dPu3ROPTeJpcvH0p1yDeRun3QL+1rnt4xa2x p1p1hkg5hA+PysAUKzFNJ/hS0cg/OAf1AmNXdkG5uTknfaLVSMeGg3dO627q xNGIubaSPUXJQpQRFyekadWc4MX1v+btZYMycIOngs46ZuckN48/dKmZWXYB HY2i19JojUIyDt5WqwB8sqBtnwEfvD7/6Zx0AT6EuVKEJYLNCJCcLxFKtk3G udwJGhR7GqjD5+ft8Bo2qrnei1Wis1Y8Bh7mLSs/NBCbgtZqNPkogeG5/PI3 hgne7a+vNVPKpYYcfzOm7kkSmE+LUbWOVsccAqHIRh0/owIt3gPT6/x1G4bD CHlyhR6CghsfqqVLVIR2DYYR5aVrqrV03TwjgqA02/RwPwN6FVyqWH4hrEcE 1PDShlXetvQiSSESsWMHnAR4KLMPzSKDUz0ErDHxqAHcrrTUsEXppiZgGxpL INXQQib8Xnf8uAd+lKh/j903TJoIuCUkGwGNx/aGvR+f/8lZkGXsDblyIF5R 8bARnU9oQKe2OfGt2ApACkzYVfzmIjEbBkq6rkbgaG09eM1H5e/UmguzJFiz tlsI9BW7GqfNPzEBlJqEEiAMW8o0trxjBHdOD4o9mdV7ReaDP/1QSrdYblJy T86qEtuosUAUbWNysPbUYnmmbQqsXk1TnldwG1wyRfT8k4W6bNhpIpYe2R8k XhAAmIOZnY64LjiOGgelBaIHvkWtTmHr9PmVsklgzsgNpfEp/wPdRNQ/XB6W Gu0pKSDtc1KcqAGFSZMTVj8IpYE1r+Qh6vxLzzGGISVieVwYQUph9LUQXTNm M+wQYBNlUQvUk6ff+VGyT3QJk2mXyXzUDYPZJwwUEke7jG4XJIWGukA5eWMM UYSOUCXIF+Q2qzy6OvAraLNWHlXxaPtLDCNZC8xuEMgWrLb5qlkXFsc+Aqo9 DGo12kgvAYQ3Tdr1bXaaTwyFSqniyE6NhTmRR3lcusV9c/xvbdSp8+AuN+KF IHTlnFB8bpsKlOGi4IjCI/yueUIxhBt3iP01PhAbwS79cn1kraNN7DPX09zk DQmlcSs3gmtgbT0Vw9Nf8266WOR95M3Mpcsj07HCEQpfzMQMg9+oHqF47uyb Qiqg76LzM2aLs+dJcrctD9Hw2mrnvBPacl2eey5e5/KZ7j1rUnj8vg2PDWoe Ue2NEjEFGFH3eFqlGIT2Gzz8bycjTOcTESawGeNYIXwbuYR+WhT8kTNkaLEP sy3R3cJ9wH28xzXM5MuGvbKWhc4psHP6V66acW5WbYYu8G6S1AfbrLmQbKUP Ej5hEA2zMtIdiGlUEBV/Y4vFQK0ZtBzLTAM0U5N3GzijOACDo5d1iED3Zj8M LAV1HSLP/Gtzh5XtlJXLFY4gsyhDx/I0x1ug+YxNy68F99qIVsfvSymmwNgh 90B1IEjFvHmQneN84LlVwH0ukOI4E8Huh9dvEXzfjKORknJKaImILKQAgnkW qY/9mD57Dp2t42wkDQNSufuouZU2ou8Vf8tBF/DCdB8J5t83otcEOjAUjk4y ehOPoOhF/XtqEw7ZSQwLS/M4VAlh4wgILUyqcKOKTR26G3TR+tTKV23TdXMv Bw/DBY3C3IK30UyfmUagkxxxtsGkhJ2MPkZBYiOvkzL0W01gyuswpPFGctRW qMf1gszICS56V/0lDVMRZd1K2bOkpzF6fIgkJXdUmStc3dtCfYSYLpd3Hg5k Quaf5KeB5xZdXm4riOuQk+ugzCZpiCAQiGHqeFWYYE28JMzHzAyp66XtDYYg mmCnnixPsyWyc52ZnILLg1YExjzUsS+XIpDyUL+7s7kS3TzJ/Tc5e6xpipeE GiEw8Q5TJNOC9tc3wvOSqRFlnQGAKdYwsytANre0X+IwBMNzcd5U/Lwpwuiz 6xGNmedyIjoo6NZ1cwcC5VqVpyi0LYBO5MwxsVtKtufiE1Da9zT+6YLavaAH wwjM7mrcNm0Ff0eFlKS5Y+/YXd5TMjFXJ7wa4EYhcLBGqS5Y1ITwHXmCSkZG 4br/AVdPW7yYEebj7Cr1NK3CIcs5fS+X+N1QjRIbRpzJEuOFWaCWF3uSMPRt a3pmLyXRfM73FURPPnHKGFwhr8q8++wiaJXvtcvR0s4glkA/FoPsJ3tzccpR rLi9gp6aFAeJS+2UT+x8jYXh7ESAvRtmlr2zPIKxB4vmlb6uiMEY2sLOoy7P JbI6Q7TJj4QFkvgiolJJMrL1Fh01g4yhj64gZBgP9UjqWRIUpjYiINZht64K 8Q74XIIQ5K+d/ZXSVeqC885jJyuTVT6/kzJGQowSuaSGwQIHWRZiZrKIpsyV mKbN7aCuLL0ahsKoKIGWBC992NrnMW5pGfO4jFib9U4+EdwnYg8271O16XHq FdMo5QNh8CNo8EPnMHI5TtVfT0SLGBWHEUgGLTMM3TdCNCHugaThGvuV40qo cJQiwsIZ1X8BtaXO1xSHHSbb/iUNb8eC/c7iePQJmYFHIOK5F7subUulmIzi MafJvdH6/JO33705ZXPVXpoFieYQHo7yQf1yWgW8uHfGuSNmy55Qpxuxe4ne BE+kU93tbRMNqoEGjmUoMSGgTpSl4W2Zina9E5ATTu6QHn9yrJ9qJsKrn1im /M7fiZlvao2TFsa82YPcU58x87k8nvSg4MZzqtc1HZVLznPvRW2SvbIseCVH RAv5gkZsVfZNrWRDYoMLpbgkTvjZN3Q5Q/ixYaSzoqaGPb7rxqCbr1Qdov6l z/MBHIIDxSMHORakJYVQA54wbjyI7nAnJ4Y8RMAiJSq52RPSRHCedNYrLi5j fsEoRTneB9fRMsQehDeD3DLWdIcNUuVIOWra9Hnl/J1BZnuiH0pav8LngBP1 p4LPbkq0WbiIf2e4D9PMFPlCzDdIGgIfbd2IfVhXE91/7+/1CEZdiaxQHYRh F/3vvpBPqmu4NVhFZE513MUuM/2TuniYpzEdSPHLh0jhxq2pe83xzHBtYTfg xFexf9qga6UG/rgRq8bPFKbOBXWGJRkehL8hqlOIC+mliHRBcRYY943Y/uxr 1DjnMPIY9ZBhp+HjY6Rpe0YgcJM16bnOfM9D2B82c9UdYVpQmh3SJy4Nqm2k 9Ehtlv2lJee8eH6GeOi0z5INMHNBxtkoQ0aRVXBN7tfqMDaRa4dP+BQSbfeU kZbL8bPzO13UKPHGeJdkptDEJKMDB/i1WHJYAXfjyCya3YFK5iyn/Ci2PYFj UCiINgEzcj/YdgzzQ2RDEqbzX5Q0S1wwqhYmFWYgbPJq75JWcAAx+bHnG8WT GMNAGpel2be+O621MiMYWE1rkkoip9Jnzp1/b25xkinI7DLmFqPbGD9o2ncI b8cZu+K0zweFe8P0+0ggIV0J45WUhTqhJuTpIIVR6+YlOI9OTIb/AiWEeyNs shSLtey8NsUzDp2AI1ii1jgowfXYVDZBGKg7LnNnTXfsCpts+DyZk6YAWngk QkF+ta9jLISxUPzGCoUGbaIeBfCUKhKxD5MkKBzA2RTqQcQhc2yyVXFPBCBK 1iJ9ubdhMMSvDIFxEISqqHaop5XJWtRnI0rkfbfQ689Gz8M758j0jYvjX9qd C+EN4eL4rCz7Km2O3E9B85zIIcb9DfFq5x6AxvXWcrEuPU/tDKPUG+yjWs+a Z2sCLYpMwn/2izTLgtpJMDrmMu2skJ1os8a8trdPZ1FNEDEUDN55cD15H99Z d1HaUdd190gTVsKEIFAy33v24nIYD1xS/1ULu5FvvY5NJ31nyiRrPeaYD6am bl5rygKXpN2X3CHYOuH0VgrXBe8KB11wuFYqaMq7yGalL4O6KKypJipaVLnL LjbdIN7AiwiDzPXABIP8zsZMdyW/bco1GSOZuI+KvFXSm0JUxnvwd1BJ1Xcs xBExqPACI7251JSSg42BJqDoTc6simGAebMx3EBVjTz+nXi5pkqx2DhXKmu1 4oDtKjPdXcIZzEV+HfSlmYD+rgoCV8hTcSpDyMPrxPPItt25dHTl2jTv8scs A0VjQFurarrJETisKE149YuMxGPax7GZGCubRQqORSPaxRc5UFxVqq2FxDbp olzgJZHlMSwHGdZosWOIqXhUOpLWG3e7XFjKQGmMCRDRazFzqt4sa/eVtsFT 94yXD6m8S1up5MiSKq1cGk0xbXhEIFK451JwRm47qrwNf2SSXoiFz5jk19gt ivmqIBUm26oJiqUVRP2n+hyoa+224a/bIOZ9xMBkE+JL4kLVO6eV16SKyy5g HMyiRmqun38zC9zRfFAiiVfhE42KST0eOEqSVqQhBpNgS7gq+Ui5r2puoPAg nvoGZIVtNOEjnfxkvTwnB1A837iNfaPf9xVULflWJT/5XYtyDDjiN8ivLlgS WfHJjIEiGWWVc/M4wx1N1HVaVyezcGbW4jQMcK5FwZMVZskKqbwwBigE8KBp 1px57U7ik5XTHFWLnMP8xvfcoqQxpst3YhUlZg8nvXNdpjj12Wv2fVdK7rlr SuGYi+s6yd2t1D/qvUeEgULKAu3my7MXjxVE9DVhe1t3Tuvjbq9JXXXH/ypo qejrxMQJbUWKb2AzNbdQngxW/WEB383Ihya7ZINSB9m0TagmBsV+FShM79g6 q9X9kDt/FJWrDB1VRlQgRCmfEU0x9BwXCOj1ljBgwsnrN29P7dEJYOerURVB OvW8ey9pT64jl6newcPUUIoqF3fhsSrG9zbn4iZXctFZrNdkGZ+JADGKY05g bNIyyNi7jVXdrgjuYCS/HTeN4LYI+U8zZcj8Qt0cK3k5+grsUj4DPIBqpBEb 8pZDV+io6wjkj1O2WPXWfWKXgZZW7+uqBPMEy3uGA5gikhT+UPJBVWysfJh3 ABvEigCiIBvQCeXREAKPyitNPNLV0L4kNQRyfXJziQD/Whd4FNlbFFVHSQLY ud9vykGYsVqA9UGSLRUPcjSOCqohWphGjem0ByCqFi2hss2DqL5tUbr4AEnY CUp4KYRQWmFbx/Ymq1576UcWd6K3nfBQnDhddGZybTtnHQTrynIY2Bf6qGWr 2/YgfGLyZbjr6EcnLZ63i+fCsSUkUuMOlP8xQeu6xAkOjk7sFaqQtdtjulFg zcHdz9w2WGVlNo1rV+7aR6fmwwCJ2KLDw2h1F2MRVtGKgYWqXFJ4lReo3ReC 4gymdthYBLk78Y5GECmGMjpo4/FNwTlmvJkkYFqtZ8OxCbu7nuNi25JKHxuM ruF4IWk/Gxch/Y4bNTDdu4WEkmA7MYhkiXHWG91tqk8OtUy82M5XvNBJg+34 tiTvFYx9EZ1bEVJBYDvJKcexEOx2iY+oEj5A9NcmpBzKsZS0kIhtcZDH3YzE WXppslNpooo3zGCM5hQ/zlxn9ITD2BuaEGkD6eibpgQf5S0PrkwTouD/j6Dt PjA8Mi32+6S6s+D2QFLixSWfMJcEik7sNsbP9LV5w8aFYdy4cMicWMEWWDVK PJrScrRvy9GO15zBkh9XB8mrX7adz4ISLWmwc1m6cyZPhmwHEUZBtHzIzhdn iyexYpcgEEXDgUGaev1nPhljOf+SEkUpDWETVNR7OkeGpHOk61AkvFlbL41G khry8D01Mx0ZKPHBc+1ooXX0lC9kvCto4HSF6vuajGL2Oh0kv0s9NIjYpkbF 11hFGDT2ciaEnOEuyx4jOOuf2uIU6VkeeLr4anykD7O/Rhx/0SJ9DC7uxceH DrJ/0A++ogpvBiOJgOoyVOx5QWHkOEqlqBBSkW1Y2eOIYWa5ESq3uQdJr4qg fkzgZ9nB62JyMRzpQDpJ3tmdRBTfNDtFdq5LILIzBhWV/k2zQXOP4CpIkaGD fkCZUpV2TWEe3CU7JFadaMEB7AIYo8BJwmT2YJIcIvA29RawvhoKFyXlZuLw FhFubMdGKV3BbmYd631PIfRsLKmVr6TaqQ8Wr9M/CNSQ8+Zd+2uMz+at+DU1 dTPExkszd/rYzYF7xkaMOkk/Y4Wh5AjetxEUctRC1qUkJEoGA+ACX10j7DJp kDVhSMMhRBh8qadqSCCz+mYi7NyH8hgWVr4ZNd/49UTy5BLz5C27o/67CXpl 3lmkkOMfRqZoHAqsIceCulxj4bPAqX3+71ihSnpHh2TCE/9BQErZK+NxYT57 AZegKME/nN7DTTBw82OXhRFfmE2N7Nw6jJnURxUPGyNg2Q668xmgvc3rrpIe R5hGpoirXebiDTK92H6qe6/1ZjsMJtJ94M34loJpdILvhpRj1sKayaU/7IqB aWOu05AgXpjRjcw8egQFDbT0stmV4ARWHaUStpS6HOTP2GEdjUW4Azl6EhWb cpdzE3vhk0gDN/ttI55r8uMX+6q51vzF7H9q1PsTp80sQtxS6puXKK1GzjWd maWhTwbp1AGHjhGqx0lAlFKZGJttCAiAukjzNd1WBwTCawDJJu6Njw87/flT cLTspVVA2oIbjlKaN/UJNRqcJViT+iA3EeeIZopyMUCBUBRmZ4jvzMUnouqa XeI9R5t6u9tyO7H7xe0fZCkDFFyMh8Lnb4ramAeQRy59RYT7kc1ELTcsYsQH AQrsZ0P8ruJLc9ZpaW/NzblqdgemlZnwPrZlNW/Z1kIldYfh/rMLxdrMOMCI GNjmG539smPdCt4gtUOFQwjyF/gqhq7ldjGpoZQXTN4m1b6tkEFd1tZgJZa6 RVwgcUggscTzj15rTIHkHGA4Q/Kic7e7k/w0a5a+eHbKtR7z1rAKRwsmhvhk g+w19PXT7R1gvRCcYHQfejRkTT+CGcf+cw8tEYdcVX8TsPGzo2DjHx/Ky78l +bZa+e2y97EbFb7SjTrPqdmGNB80+pC2nhITvcgOwEUY90R8hPhnKpk9e/z4 5SwQG/nq2dlj0MoMLnhq4ie6tienBmt29vjJmQzx7BlBU3/eEGenlirLGk8d DM29q1Akc9/7s8dnj/kiscP/BfE6E65J9F6kA2pXa8tbT9PWjAk9ISZ95kN8 OfUEpWNDWQqGg2D62+9z7gpGnv5B7jSnbFi1ixpXM8lf55o+Tr9qNiGmPY5A XQ9ovSS9r1nLpUXMdEuim16AWtLdDt9xIcS3rswaVH+sOBbYN7IOffuoVB12 PVR9hILcDJIsW9y6KtWpw16EX2ptqA1G+q5cqUUEXERmMzxBB7lsnoYIqwln hU7FIjmgqUz2AQJYmj3jAzbHI4oKSyRudirXobKbwtffo6wr672HYHI63TYt /A+iHzC74rSyiUs9i5+I8DBepZbkfYLMIfAQpavsE3Tl4jx67aTlLiPTuC6s ZvIJdlFl9IPUEe27T/dW4G3klGdUB4eYRj6UR+7zntQR9NGXfMW90GmWXYPQ hJ0PWonBHx1gnbJ1nSgflufTt8an0XfYUJ9M6lFtWP+yiu/g9nJ20pWwlFGq rbZ9R7GlMCFjWA1QPgNVusLj2D3NY73JIxv51kw8kHcpAGo/AGWmomXOKfNR ZZCalTSSpoKB7VLg7E4t6KOJdLc5t4L21T3UYeQam9UVWBxGiW8n5mhZPCGf VnAM+XSW5NGlHEEuVjLA2XiAASAEpRbH/PRBvmxIRnvq824nR0vnkr795fht j59AQMzkjDiJHqCnfv4v6R2tdp16fJQYzOcucHmz8InM4Kjh2phf0hamY5JA G4LFb1OEQpcETAyCokIJ4ukwgu0+OVoG+nrI1a8GJuKH8IUNetcocie1BKuD bzwnH4iZ9ZhYr1ZlWUfXXrLWp8S7Eiwo7LbgUX+wQEBEmGVcNVbilpRUiCBI gqRaiSKNn2BeiweDzlt6axTtY4jKOmQQrvzDlBxJ8GzXMUi3AfZaxCq1Ke+a Madk90LAMkM3ed19jwHKijkzKmWQ7P4+Wjpw5JRISKJ5TU3cKJEtnHDuU2e9 kUh2uKbyAw53ahyug5ljthx2t6I4EJGURoIiFDhyOWJ4R1ldGLC6Hz2sgAs9 H1+u4iMerfz4ZEOhwEKPG0hxWArMBmqtbpHsT++3oBUPPnfUpOA0ZKHwWZBw O1XgOdAI115Fy4wv1YijNuB4sNbOJIwFmJ5d2oc2seysN/0SceKHY8YPWzYw 1iGJGdhSLsrOkoL060daKbDX1r/PfRLcZRsKTy66LgiGXE1sis3yJ33Op6Bo oHJXfM1RQUXYToDWy04Kw4zotc3GAMygK5I2DhsuRElQpnlLsNGbaM6iA0Wr 5cj5R2vgzkN1i0M3yqTxvebKi17rEgjXAq0brrOdKmQ/lowX29R90Tn7ptTF a3VIOYgO6MzBiG7hgXBCjP7sxVeUjJQP/FOs8j1l4fPL0dsRpndHIZrXFmQh Y9/XoA0Ywc+2dxeWQC9dzYD9rabmoUwhjE8pfons+aGxiNtM5diGQMKx8I7L JiJ+PZmhDDZI/YtiGYQrUGCI1BP2N2oETs0fV0gFV0VPc7J6PPhWYoPwoC/S 9vkjMae9QIMtTC58UAA/XPwg390R7eShvL36+YJL+eBYJjiJL63hCU9bTUOk e5+c/Jol0c8ihJB/StBzX9+VRbVm1y8SF7VdbHb5P/aS5I23kFrYuPieNaKd eWsmKFNxkhQ/ig3dI2c3VvozlQW75DBGpQleYaKsQbGcRtt5jg1UMOODA7mw k+ffn2LFvjh7jjuynOMo6k+k2n5gl2cRxixn8nPeGVQ34nVNA7CfIwW/U2gP zNYXpReUp/2yT3YY456luE1iz+jvyS1IggNOYJmjtxgTYt/xHfheU1+tjdpm n57RsYg3rfEb0NC16tBLEFdSvjidzAC5P+tjnKAbNVWre9bk0QpjB4cheICz v8NDDNfu6TJcJK2JJG8BBWinTwybF0mHnMGobFtoUNWcnep9OWrtUDoJaqyC bBe0J5s+uq8t6UDdsVmmGSFb1N8w2kfiHnWqgdjxW3pCuViESEs5iiqRT2Ob KexTWIeBPYWPURnjINhB2MGGbGr7JQkyQZvxMAaWLbDzLnGXJIh6IzNp9fQu D8FwXaQ6WuSvQG2qDe1Q7FAPZYRVF2aKGZ9YlFNoadXoVW6pk3fAXEsSoOoW Cs46VTysSpHqGQxzxvCONMws9luRJMwe3ZpBh3P5hHjVtohUVRdzDXmd+qbf tK2ouXDnnLBG4E0FxJReuMOydTIXBH81VswNytf0n6AFKvGcJn1y+ayOXQNf vBfW0Vc4kHcUJEQLdWXhDJyRVZb4hlcPGWp26kYeAWFajYBwWYCNwHDDMTDc 7PPBcMM0GG6y8xFOtRtX6R7vSmRV3DD68TZHQrqMUCZzOGAXJn6k1MUQDN8h CISvN47ixK0ShBaUW0zPtfiez+cEzYoHc56iSHXDOQoc//GELG3FQeJwEX6k MBMnKvhKeMeITG/OuZNzdNzK9ami/1E9AdICgjiz/A7hGtV/SqxDIRFbZmrL WMS9VW5dtjFdtyScz5FTmYdhhf0NlihnV8g0z+f1Gu/ja0zrWbvyhhlHezvu SZ1uJgz/fwDgcfMWxwkBAA==H4sIAJAYS2kAA+2963LcRpYu+j+fApv6YbKjWBIpWTf3toemZTcjZFtbktvT 4XDsQFWhSIyqgGoARbpGW+9ynuU82Vn3XAmgKNrq7jkT58xEtCkSSORl5bqv bx0fH4eu7FbF8+z1t+fZi0XZ1U32fb0oVtnhX4umLesqe3gU8tmsKa6HD4VF Pa/yNby+aPJld1zQ38p8ddy0N5fHzXL+7PTpg+PtZpF3RXv84FGotutZ0TzP nj07fRDaLq8W/ztf1RWM0DXbIsA3HgZ5/Hn25Nmzkwn+7yn970P630f0v5/T /z6m/30yyZ4+OX02yZ49gUHrWVuvCnofPx5WeXX5PCuqsCmfZ7909XyStbt1 Uyxb+KFuOvzp11BuGppC250+ePDswWmY593zrKyWdWi3s3XZ4la83W1gorbI gNN8np0+OP38+OQ0hJBvu6u6eR6y45Bl8DJM4dU0+0u9XK7zCn/Fe/Uq3678 b+sGJnhxfvbDD/ivYp2Xq+fZBh6aXvFD/1bO86qawnM8NI18Ns1e1zCtoMOe rYrfytZ+SaPigb0pmrJos/O6arerrqwu5QiDfatp58W/wWHJ+dGHQlU367wr rwtYT/b1+asnT/WHZ/ID/Re+cPro5Kn8+OTk80f648PTU/3xyZPH+uPTRyf6 I5xu/PE0/vgw/vgo/vh5/PFx/PGJ/Pj0yclJ/PGx/Xj6zH58+EB+RLLQH4Fi noeA5+xWi2t6+rk+8/DZQ/32549P9bePH9tvnz558CB+ULfi6dMnj+IHaU1v 3v7t5Yvvfrr45gX+K8vk6r3pdqsi+25bLgr+dd5cFkB9V123aZ/fv39zczNN T+d+i69c4hv36RWmxGW+ankIo0T6PyMFOfhwfHyc5bO2a/J5F8Kf/8fx8S/w gWLxa/bt3y6eZz8XGd/BRdZdFRnf/pL/jVPO8jZb1qtVfdNmXZ3lq/Kyym7K 7irg4/xIvaR3gUFs10XVTbMf6g7+dpV3e8asq9UuyzebIm9aoHB8Krz65tus 3nabbZcd8q+yqyJfFE0mw3T1Br9U5PMruDGXxdE0u+jgo0DvVd3JcDra239/ C1uR/eXt9y9l1HYawo9NeVlW+Yo2CzcJyUPW34bwE2+E/TVhf8fHX/L2Zbp/ r1ZF3hZ4Q4sGvl/tsnfF7qZuFm12OCt2dYVbWreyEza/uHFHsLNNtm1xQ26l AHhxfjUdmcLXxTzf0heAG+j+64JwDW1krMBAgQULE93Q3AOeS3FD21s0Td7l WVNsgFHCSeHU4PcwOA2DrwKrhdlm76r6JiuX2a7eZvO6WpbNGva4CfWmrFCI 0HIrYPRCGOssbwoYeFVc5zA7oCL8HrzZ4WTpGTd7OKaXZfWOqI3n9Dzcsjf8 yH34LS70zk8+vvOTT0a2XW/OVX6NC1vX13J9+KYg3+2K37ps2dRr+v2ZXkC4 TelZlUi9GYjFS6R0lq19Sn1Lb+Bf8PFN3nR65RzP/7lu3uGHv2vq7SY7fP3m 5++OvsC326LI/qyrBcLIcSbvimZaFt2S17u4ubyPUvy+Tqu9/+WUv1zA0cFH mTBa3KKdkIbNKe/wUfvEJTCH7Ww6r9f3UbAVItjue/XgS0fMuqmwn5XjG36T 2nwHfKLLDgpQI2arsgW6PJiEg3ZTzMtlif8gAj2YNwUOf0Cb80KFN3Bd+P16 mr25qrerBV3VehmYuuH6gmoyhx2cRVaIKwQCbcsWaHS+yw43RXOVb1q6rO6z R1+FcL5tGpgkiJbsUM/5iM7tWzzB1W7SW41bxOg88ev4+mYLT4FugncKznu5 7bZwGJsafrnLFsUSbhv9zQ4t2zT1YjsnWgQquLzCUfAL8HtYYAvfo9fgATzX sprinC+qjl7DsY4cvdnm62qBCJblsrvKWprmZHTykz2zp2njIJdwWZqKrkhK wDl+4OYKFDqa1puCZpQ9HpuTnPP49tFAbQH3BJ6B6efz4iOTmvAOLWB/4WeS tSvYJvi5AQJumbiAgSFtsLonOgQM0xSXebO4+3qeTZ8c3bbJo0sCqZYvFnzc zD/pZtMf4TMr+O8CaaKdN+UMjhee/0V0ol/5qsHjYd8nr1X792zFC78pcYJs zXYAkRBM9KbOrsrLq2Pg62BDdHkLTFs2SZl83I4pXoem7SZhSMAlr/o/6hKm BUewwZs3K1dltxsyujDG6Caw0SXqBXwBWr0l8G/gWqAq8RHKSEFO6GwDf7+G Xf66hiPEoc6+tqFy+iM81W55YB4I1gEnCbLdFlKuQZjijua6mE1TrvOmBB0H P7h3QeGV3bvsHN4HAXD4+tX5EVIOSkdkJFtkIBleGWDjVTbjIS9evP02nC3W sIHIb2iEl+W6xJ1/WebypfN6vUFWd4iPZy9fnoPGlF1ESpqEa5hlvW3TKeLO DOlgua14pijLUQEAjoiXAC4EGXWobQHVAdefAdejJ2WyeECTDPcW/vfV+WTc UAnyHTiE8xdHfFw67+ldWWkYY6V35aNhPx/9GBN9U4IA4YfSb6mOOQHdqW1h sawyzPAsQQNrcJR8BgpqpCLmJLBIum3T3qWFtcL82notyhWqlzq0DQhb51RA VnJnoO4tMtXOit82eAAw6/4HzKS2V2F9b++gXt7RbsfJoSUGo5Jpsi4Xi1UR wr3My6Hs/b0S//kBvw0kVPx9C0dNpwlUzYd0CN8/UkISFoJ6cok3umVesQCt bq4MSReAO3yB160CfbYr5lcVPLNSfsiHBwwDznS1RcYeLouqaOAJupTlbEsP ROXOxoJrRJo6LbKoQIErYBowANyK9bbCOwlX+6ZYrfC/5BHJ0VowwptmomwD febXYK8DcYPsago87TC/QmORrLBqh1cObKpkAvD6WZtKgffvxWj98IEuXhsi ARKtwtVZ0MLKinlNS7R88uzxMzgimw1vQSfUJbxxgVd8jfcXaNcJFhZL0/Az XpCcT6YV2Uxv4gnMapBYMr3TZx8+0OGScSePlm0wvrQq1B5J7Ya8S5SREX4V Ssfe3DCbSGu4ogUyUjlaHBq2graLJV9Ygn2TocuFiMfkLmzM2G7jcqZ7JXy4 sxq1T10Jd9Oh8Obgg7iWZZOvC7BN39kG+LeiaBzbvn1LpPfg76o0E793SxZJ agrDXdSMnyq0+GkYefyPS6m7S6jbrahJojMsrssWjaBUZ8Ah9ohzL/DCwDM3 FHgfk+thKNf1VE5O8Jqz/jIHUxRVTtDNdrhoUErawlSP3n6Jglfy1SrZ+IaZ wi62W2BUsGF4edY5PYHmEs43tNsNegtGrFEnbvCuAU9BHkFHRrKnC6naNMnm KL7gC1V+Sb+Wa9mw2jyJfAdGA3JzPLWs0Gnk715qWL4CQ+CyyTdXLZAeDvMI p6H6+AlwIrqMubc9TRnIDu5MvgdmYNIILdIA7hQQ3UanAN+eOZcBsPLrukTb YlN0pIWAQfkQ6Cq+cIgXtimWwEphMDWG/vDNxtftlvQvt9kMe642vty73dnd bze+Pbzf2XTq/B3Z4aPuKq5+zPb7HezkbW/Oprr8Iu7pX3FlrAKSSCpXRbNZ ESWQ/4Z3FIcYOBNw1q/EK/DxSf/+D6vtPvbh230nRM/efypEoM4JUiJ1x1p6 J4w7EA/LaTGd/E5FL6SK3hFGRW7ARGxY0q1y+Hgkbzm7RPkjd88t0+L5wC56 pRKd/t7zbA/ZXwObLp1odkzycZ8+U3Ln/dFdg82EPYy2gTiYx9+RD5CWWVf6 BXba8YKnpLcm0w86QVANm8LfOVPBj4DW2NssHtsRdyyKBFARq8uCNRNQPmGN U+eg+gdQ5d7rcNvQzFJgaGBzq3wuekvPy96A0kKBhYHRiGtFIbnvGzjQLxL2 kc+sWcekqASwVmA66MUD0pqD6MmRIas7StUy3G+9chdnX/NHIyONwvrFkdy/ u3OlMPCljO0UCTA8BdCs3DGEfcdw5zMIXmfrn8KdjyDcdgQqfR8+0E/sO4Fw 6wncbfu/r0nxhmFWdMWiM45tab0FZKHpgZzuO5BsnlcolEHHr0TFlQFIk0BZ +67YZRzYOfj+pzdvDyb83+yHH+nn1y/+108Xr198gz+/+cvZy5f2Q5An3vzl x59efhN/im+e//j99y9++IZfht9mya/Cwfdnf1Pn9o+v3l78+MPZywPjKnYM eN9BmZixCtdsmoJMNTSAnXj/+vzV//1/nTyCBf4PDHuenCBB8D+enjx5BP+4 uSpE1aIQHf8TNm0XYngNlY55vik7dqvBAV7VNxU5Q2C7/vQL7syvz7M/z+ab k0dfyi9wwckvdc+SX9KeDX8zeJk3ceRXI5+x3Ux+39vpdL5nf0v+rfvufvnn r9A/nB2fPP0KOEEaHOp5qsFcBXJvIw1hKgJw+iiFkCjxMO7jISTXXSKfBZ6H 11gPyzWYNagGwyHNiiXeB/vr9OSIleUFDM4WPI7OYhC+gEdmAf+oWYKpKyJm JMy3ocdCDM34WQLVIUNhGstBZ1/SkKBn1GK7ipy1TTksppfTCQbD/KzHApzf /u0iO0b1hlaT/X1L8j2/vETmIsNO1wuwqFcFf34J0pGm04ZDkMVgt6CFoB9q 4UunxyfTR0esHUaP8Z9nMN139IEvdeR///4ljTwJrOuWFADi8BCbJjyj1vt1 fnz5zf0fXvxMvHpsSX4mUzZITqYPp6d0iUl3Yy6GOgSJ8Zus1VdIKYoeHN6U PjeYgjbVdqCfINGgZZF3yoplTBmPgtE3tWxX/5RAwSdjBs9/Vb4jBiM0i/GV 7XqdNzt5qS2CzZEEyKYmRtRqIIC8Pb08ga9MgQbVhDZjSjyfbOQ1vBxQICuF PIS9ukH/Bq0Z3XkkcTk1oGjW2cFc3xPPa3tAm9uSZ46DzxQDErd9RQ4FPEMY bPDuNJ0cnM+UJqYRwVc0SjLDJ9One2coH22Ksm23eBogc3Ct8BQZ1SgRcxzM oo4dXrpW7WMhpHDvXnYu0g1eNe/u+3siso67+hh/80H0Ez1plpbsilPxuAYN Fkch2U0vffA+ezSJm07u2emD09NpuGBuEPVo2Pii7ZgGQQr0pBJuBn9sAUzv XbmRS4OBEfwsmrCozQ4sdjGjD9bl5VV34AOz8N4ByOsoAtXK/qoXMz9rJXsB bB4wKzCyR9QQvfjxGhW/Fc28bHGWopdG58IV5b+gZiC35IZC4igTM5oeCd01 +0MTovnXzEGUlziDIcNBDQbsD9ioq6JDVzeGuldwWknKjL+iIbKSmGHCrIg0 0DLGQMjV/RvMi/4Fw63KwrJwIitZ5zuUeez4kF1J5/QVZvPIMtDXly/E34XR 08gFaGMP316JLixzr/DnaFSWegmBnKOEeYRmVMJQxgZzl2Z8GORTyUCPxgeS WRGDjR6ofWOe9Md89AkrPYX/T4Z7Mn388bU6wzMO9bA/M+Byf2jbHvKcQrTQ y+UoIUi2EHnI2GUQs2qcTy041QFkDsheNHhFC5alpIk0bzkYG1OOSu90oCQX suLhz/Mhj53iABhu8zY2J490nNsmJxQ/kchSTJnL5k3dtsdR54K5djd4/ckz 0vu4eiBQQNDtTNjLp61mEjTM/TtWIczFywtRb+G9trysKHxWdf6D/aAoRTVJ gWIpm+4p53UsWOlJmSb+KjJOC+MM4q0w5h/nu3+c8fu4enaJTkHYyBinLUY/ TuP3I7CJSa1i2bnTYV3AejEw2WqQp7nMq/I/bReIHPCkcVjTxjleudtQsJPM ApghGCToj63BPCk2HKiTa8XZ26o4tvmaUkHdpGDed3ptMuLgi5xijdkVnP7G lwT+SJ5t0DBnid7LporSlL8UfBXwN7iY33Uf0vV84v3+9OsN6t3rV+fZ63ol D7zuxbx6t0+uS55emCQSMIj0XPi0iRgeuCUAloQRbsudoQcvkbxxPoN4nUsK 2hMrm4avmzpfYBgaVBOcyATz/swhHJXTm6bsNM+ndAxhGEjlV9CnpBk9nDYR k79sebD1FpbqPzYN5sb2R2D5x+zG2glbvaTtG4k9m3cVfp5ty5Vljmn6AbCg RcFTquuVLNtmFY0JCu9cNijzthu1sdmgRT4zDQMBobdujMGQtQKbJt6/kqmP fd+a07XOOzTpiEzvZW9hdmzILMAwgin/pJbxqyFPBgOl4+ePcXkfxvJpL6pU IZqgwsiKxMEvEt789UCJSHwiaaSNrKlufiVGIesmOujpINXYvIyS5uId5fEt igy2z8nU+z+ZGH79rC9NFBqRR+ozE9WaR9EUAjpd9F/27pc6WvvZZPL6/iS5 u+aUyUBjmWUfjUBrZpmM4eLQdk5jdsjryBfhoNQNEkJ+NHL2m8Kle/zWETGA 1VIW16I9mhsFNVR4iaIoqGSeiAIJH2M55LQecb2RBPZlD0QrOVASuTLZOqIc 4BXsPJgg2YUKFb7s87pBQ1bz6L3LbG+ZgQSFWrrXcNuu4SsbcpHclPNi6vdA loS8j8qEqnm9BY0fNu7AvYenTiyCfFIYS6ZKEOQsmMxuefs4hKYIHX+DKdst XSNMJAc+skEfnsg2ZK1TNw3czRiNg3EOiJOuCxTy5PlFO33OSQ0WOig5ebor uy3nA+Xviqt6tUCXDloO5P2T2QL75cx7+KG3McyYB56Zo4xydqiaqrqsKVKV t2V70LvBvwh3+/WjO9/bdsy1St7/3ftPh+aP4A/tP47CRwBfirOJwvCjhyEB rVvO4/bDoNj5Hc9jeBizoywNWvZtOd51cxX2vLTIBciU5fAT2u+gneAS6ebK 1S5KklEHeob/PuDyB3ghkr8H28wD1eD1ptMSZ5jqjAlEcMfBNPjKRZXnTGCc iercnnEVIOTeqZCKftae4JHjpvIk/OKrb74NsUwpUvFQClG6hHcTZJRQt6D0 fCClq5ucCzRARNQry2fDOh0QTF2ikgbSeFT7YRI4xPNcooNX9ZFo/aXffkiU +FxtwujMixLz/XNyj38IX36q2LyDwByVl/8ASflpMnJPlpZYLWRWKZXkK5BO Y3v3dkw3dWqg+uJkfmPVAyW8s8h36B6G/9AtV+VtbO/JVhzu/jQ1P0z3FUc3 1dXQdWT1l1XXoQ6c5DpH/Rp2hKih1mwu/szEOCOOFf3jWELYotehWPRPGT+C BoIfPzvkmc5LUrnxVia02B6xykwb/Tu+M1zMjr7SchbxDCM5v+Vryn67LK+B jCSdeBULNuIL7JQXQ6eFIX1iLRVaTMePYI5USidgF3dgf7H9QY4aOfvEAmFh xjweJqFSTdKEXZZySgUfka7w7FC+ZvH1T1RufpdkTeYigjXO5HcI1k+Sqp8g UuP8H/X30Y7Bse4et8VwPmY6z7dtq4d+I/b+BvldOXdZta/OUy50wRuZz1qy tUhIuPofJX2hEokGc5SrtiCDhozwdbGYY5oIhqjwD8iselPHx6kOx4x2Ndgx AGI3BAQUF1dT+VavNmtJCYbRS0I5VPkO2Q0mV1s2vEvHlzWLEaJbg2Hh63qe z7YrDIFS9tSzZye/TniOsX4MXkTK0agp6RhWYdCbHYfYG/g+Dl8oo6dIfse5 6UW8DfN8Q2tgLWONPqq5T42XECbnFMHcgECkRIISOwzXoLfPx2rr46klWWyJ o4wYZdTkShfzfP++2cyP+6wHPt9Xy573rMOf0YXfUFYdLBM9eVQgAUSLF5IN NPQuYdiDXJic9QMXfl3kYEaid/arLPsGGeLByFOJ99ArXlofjlTa1QF9tjBR WFaxQt3vDKQyWZ/t9vISKXdLd+cA3oZBcxJ3wDSq7KBuLCxpLolhKa9JmKFn SBKa9pekUIkECxOq/zMVTaK7uMdEp81wn/CXSFnwB4zc90KV/7B5TfZOrOet 12nhKSTzYn1yRPsZL+QQZrrWmhATYtHhrpcmetEGKlLkK+WQzTETY+d0FK5/ 35ZNIQLxH7d9n3ioOhGMt7KopzwiGAEWCSNdg00AlIl3DPboPn4YPlvvCgpw 1KmjEYEJNgVruPkqKinJejGdfy6h+ZZ2sZOMfFIiOdtf1QoNrqhoJYm0Jkdv n+OPf022Pann2vsmJwQx0aEWZxVVFNGZCMulDCE6XF0p3NovUeAx0dKnMRpE NWgsYilBhxIe6phx5zJLBvRlMoXT6VSnyNt30T+NZICyI5eiARuYRURuH1Df mFB4v0AnWn7Eq9FZey7mH8YT1CrEz12kO/eN7dz7e2oxHrvhUKD40T/B9vyd pucPNWcrrOw7parTww9ijk0hqhxehHoOZjvTWm6zyXIsiJF0pbxvDRgRZQre sXIRDEmjilJUT4JsjP/Yon5TRcX9SCRmDNuzh5Hoebni6zM4ujGJ6dUxU9NG TSxPO32rJPNFAokzfLgicduz7TFxZwlbI74X1v8oBF9WwGCuXRaqaW9ojnVF pXM5FO6dz9FnCuzxUphOpHIzbajujpO0yMaRc29B8abhjzj6iunveVtoHFdO 2VEGJwnAvms+C1nfSE9EdkRezy1IBTdSLk+SkwY3A9FCTGXXRCvNi+kfqH/2 OBYbf/R436qjQfCo2DFAm0SqGCIVsVLHhVMWHXOVCl3MbuRgZod52JojIdMi t4EUlKIEuJFqai8L4HrQXGC4rp6DBYOGmJMMTTGnqtwF/eI5cs8vyQ7jz5OZ AOwzR6N54pBgTCL2CmbdItiHAIe5LbTGGm//pqip5pRE3ARPlE0prh/TiDOX 5WIgHvXynN7MWw4Tves9RSVUwKDgn8z+37/ncjjcZQklCzzDvnTDSRp16Aj6 puUnx8zEA9pwEQVyIsBNm+jKIbnAjMsKZ8d1l523z3H6B+eD+XH04sb8RbgP oDtroJO3FKeEargUB9VOF59EkgBOgP4VEIkKjiGlzyKXiExA2HkqMRNz4oKL arNYtkVZifHyZSbXQNbHVMtWh9shuJxerbTaXAntSfj7I9meZMIY0BURcHac DXYwo1T29KQwAV6xRvb6A0gVwit0/+I13iP1T9Bp/XyFycvjf4071SpztUQE r/mKwqsOTZ0vSr941eNCmEliahrVMFNdM4azkMGugNTYP6+kdEzH8Ivbzpti Buy3+PVwP4rSkW1WdMgugUQlkWUk4fbWTceEfaqcFP2PVOaoec6QA+3dxG21 IlmGmhfyNwoc/IbccCJhwAkOuK4XGMFnfZ+zMX6SWLkGERF1MElV3QuNwCgH bNYmmap0IMyz66AGb44kSJNotYS0yA5kuAOWLjOO55N9TrlILkL5VTA71cc1 1bVsUG4+wCnVfTfi6jvoajVoAxu0SLUHSfIHZ/ckZq8gmSXYcHK35esMOznI L59mL12hAYnvGranqdpeIA9zBzM7CbpKBziZb50FKQCW7UEQHDwK8cAJ/Dq5 5eGJbZZFhHp2cfrthAr+wHda/x1+f3/VHI2apNzBL9Adfpf1pO4a0WLgKgE/ +BrxNEhFXqAyIz9+8M7FJ9PHQ9doqp/8iJRsPrME1CUKb00UlyRwUoMRssGy OFspRlN1CfOSyLU+oh8RZX10EsbzdGHsgt/nJ/OiQyrF8JJg6IM4F4i15jri GV0y7lTH3ANV1ZZ0bqqD6plhFruLnlo6wGiS9YoJ2OjSXx6z2INzOePcRzEu E18b7A/qAqBCfVShfDJ9CpTsvkr89rUCfMzrzQ6ZN24YOxfoR7n8DiyEoQJ2 /W1OKxn2lzEgU321pUiheZoxtMNFnqDtvL+34T8TRfKqU8V5SIyvNMazlfJy pIpbvsH5m+KWZQJRUl1JIK8DZmqUJ96WSS8B1ROPgIgAjSm4hIlaEuFSre/w DQagCR/xq45txeCO+MIwB0bob126dW+8V11NJNubf633iicjaWY8F4mNLaTS wEUXVP9DNwLmj7LgwdABC59BYIPvKEc/9I7KQ8f2EOFnUCqn+aok7iPHzCfP n4i+RuQSFDwRRAxXzCrR317wd5j+xhhSSA1Pnj17QA4nyhFWrAiBG/L4KmE0 lUkhWWNC1edgZs9rCjWsdn2PNP65J+BanoIG5wkEsyeRx985Sd8h0TVQosae BO1l5ZAYYfYHUdvkBI5BNfCBhSU4wDGxf5z6fzz0/3jk//G5/8dj/Acepf7i CQLcUCKZCCg40INb8gYOJH0XsTgWYgH+KGBalgQWwveo6KBySqtMUjDz1TuD A3MpypiNAkriNIyDvUbArn7MnCsrujaFFSCPJaNiRaeBfo6e5K+Fe9mPktKh rIrLpd/fs1SPQRF8yd7AQeKFz9B1Bwniog5jOILAo06mKhYdUuBdgI8sc5KA dveCCt7U5MbrPDZhb9RRqEHiyhUatpXxGMn2rbTSXZl7oNtPu6wAWkNowogo 2P/8eI41fx+MNMo4WnDdlnopI2RhsA8MZJUo4qP4AexzCML/ST8z+X0do8Nq ZidwULEGNq8CO/7pWyY6RImgtO7eAQ4hyxkYaeop4Q8n3f7hdNs/kj4U/nD6 UPgd6UMJ0hulqy23q5UW5I7UQ8RaBXaQNkVAoXfNt1OcOOmVJRw65xYJfxIK AWWKycun4DOd0w3dfz1BaJGcjhEino1I25iu79LyEXgifhv0N3W/WI6+kTo5 Etkt7dL9izUmZTZFt20q+be5eRHkgnP2UaMlv+By27BvSrgiBRhQCgd6lWZt z8hUVL39EzrmFR9v0gMPZVgySzTIW6PV5D4GBbKlDdhqglea9LXHHYbrCQK2 Cfsm6Cmvzt0Gnr+IcRu5pfkC1RfbFAnN0F7XUtlbR8SupH7EJpSmrJDSG51/ gVJYDJsM4y2iYTZ52bKyS0Eb8tWVWHHDyhsR2UKxVk1OlRiid4k9urhPypIL n5YlF2KWHFGBrIjiTBFWZZjYwq4qzCWJYeig5zBDb7LSuQa2andLBJlAAy6M gxorRNgvyIdND5XrGGSM5z0RGBXF5qErbgijaTinVURQruVjEDHOj4uwcbxf zmCimXDRvAuGsiOMk2UIrSBht5T8QrFBZg1NXrVcLBrWBdJC2a5ZvKnjhMLM UXfajzodhpyJmcdyyah5iet6eGi0ScbgJnxP10VhUAs+QcBh3CSuAQSiC68d bN3bWzm3MXymbNn+SrwSmmpAqpsIzG+i6gR29cCADOHV3g0asm7Bu5TYQUTG DdHQ9PlgfPKiyRkHXGNwdIbZNLM1RgTZ0s4X9YaNpola0mKm8U0PvUmNKWbT sS9t8hbn/xJBx84JLo+Q3dceyytV46iOJPf23+C1Q4TUf/8e/wAG4/iHYYke JbU3/1SzC6zZTd1x/GFHRvgHODLCpzsyfk/d+vv36vH5gBXi/2/ySIT/73gk wHZ9k6RGUhFqjIDfcvPoIXLrobAWyOaPlJRKNiJr27vsuqi2lPTCkLGaHySk 5Ze+WoGFTNG2Xv6kV0PDqBo61YlaejAzRmpgtfG//KAeCQdwQsbtVrU4sHQo 4rQ/2/iLkAbyCEt19h8SgkRP9PEV3Ie2XbMnWSV26kgO79/zoxFS2Gwz9FtK QVq87WnkS1gnnTllS79+++0k622vAq5dvHgDynCShB3aetnd4NyBxmC6C/q5 3cGeqDkV1ULhEpz0bFoSMpReknbvI3csYxsM4s8Ew9ZbbVaD8HLA4LYsfl06 fmjnIMnyZrWziLVlYY9Yug6iO8Zagy+317vNobD+TotFbTeOub3s/gSHXy41 A5wsxppyx4llke24x/p+PdY84ChaTPTBF78V8y1pMt8Q6g7sJ2eBXAulBE+4 VPXST89z1GypTxL4KBoW34GzR2JShy3WCjuy7PuU3rgaG9nMqq2DD+MmMxLw Yr2151d5iZhQZoGiixTdOHP6w4RSrpxbRLndm+90X0KthmHvmbOv7aTkabwS IDBwlWx4lUCQN1VI5aZkLrKvTYYVxVb+RLowbh3aleiF3SIBMVjnpsatLBlY XrOqlsZ0KFozTJisyeUbNFYq/kLigIx3nbu0Vdwm2jcNKwtqGS0oLItiMcvn Vq7m4JV1NYrU7vYn6P6gvRwBfUq/sXwkGSG44l9QyGEyGsorbpXVlWsWMxUh S6iblQN9lBUDFyBQ9G3Mn4H8SBCD6VuftZSVA7Ry0alsGffdyNTIUpHKk4xV WRSraL20oWdeSjW+GNvM9exhuSS4SGEzYS3IBZyIx07tiRNXQAfFptNzEmCT 6MAIYI3jH1W5in8c5KbdI58sPvSjWit8QRySdwKbwKFNNm0EMA+ToloQH6tc 0uNz/GpIlGJjBXi7p9IXCmEHJ4yUj0OL8dOqBklVJhRWrdBotaAqeU4pXWCf gOWCTxs4bbtg4zhhisMQ2vmWMxfRp7EzI9j8O6KXu9ikWOVo46osJP7dhp7F Rk0RBfKe/8UGG2oJca0px+SZ0s0n2lYPCaw/UDdG9yahg+hEY/zZUpeprwVF 0AfQXj+9fhnBH0zBbgq+6kI08Dd4LnZSG+0DRkd9H3YMmw5KtmF7f5pdSNMy ZKGWRLjhPDsemJBcCunuRkwAf0DyJ2e1YCQzIvFXHgOqo0SWnJJZtuQIwM5v GMJaZAffqZ8C9udb2ED0y+B/iTz+WjZ03Bfi1PheyO9Aq+d0B2AkmKGlAew4 ZIbcheJroB+jf3YAlWxiBnPc15v6ppC0c8zpgg0/xtcQ7Keu0H1xjHU1lMBz tZs15cKug3ZByFyiX15VIAjmYt7CFJZLpNQK2+Z14ogrGHJ/hngoWaKcfkEH kbGwum2Psn17BC8nmVtGASRMmA7aASGI++hYV3asfqTj0wcnj48fnByfPL6P va1cVjj2/6hlJXlLVVFYVSWbF3mG7I0aeTRCK1nq2Lw0emVot9MNkdAS3uIt fwvZC6Yb0+3lbxlq8z/2WP+hh5r9cuczDf0z/fWfdqLj5xnief7eA43HGT7h OONRpkIN4adTeQ7yhJxlyOPNq6eNYH0dbqx0wz635pFj8ZbvxPAf+QLlybaF QYDBnZPE+SCloN+V3V+2M0rBSyXLa24f++HDESfetFwyQYrfXHpjIL9TeYzV afXCSkzZ9Ur1PS3VrpPnIZdkR87sUXEXIrpPkvVPv3bLJsbdURgRld2aMH/O sCCqi+4UX6mSDpna5bbhGbdclJAL/qR9lWwoIbSel1Rz0XhyYTRf2qmufSzR pPj4EUmzg4YbSonRwV89UFQXScYMMRmzJIOHWj3MsP8j0Zu+9lXWF2cENiYq VVAF0Ly5fVwinNjp9PFYpaDZUlL51J8ySFQ8IHSgaJ0GVmGxx4fAZ1h/SojJ KlvMlplE5zx7SfqVgTaPZOXi1/tnzMBY9aftwB9cfs/lNRqGT31e5ETKZ8cb /ueHgQ/s1laD+4LtZCgOQBgmcgo5U6oZbrGrFrl01WgIsXVXz6yRoAXvpGAS exMQgZOp7Vgxf8dOxVm+kgQdHkX6NTvXtNiJVGQs8Qa2hgI1F/AOAO4yJNAw /aQI13BstjO28QWBwdHqSYmr6iTpwkJFbKw16y3hk0vUqWYUDLDiUWJ1ae1i NJKw4IJLkaVc4ErswxC5vffFEywk1iXFXFDcZ0riKWhb4av9PIK4cBdLVzx9 DS333IAoAJZgf2oG6T1zqwjxiY9Aic8C5W3nsxpk7jFmc113LFfobQryn2kP tpQgLYWHbiWHTZ9buL1ihZTHIeZZr4u9Ppk7fQZWMPIVg2a4/SNnX9/pG6+H S7Hfk+vk9q/Ex+7yMUesw2+G5M8YHxOjUrtfXLx5YVkg1GkjziwMZ/bmhUXF b0mzkf5jAbG9udyeqiQFT5L78CnOJEttk/PsB4mdeCX+LRdU8RCxM01KY3F3 Ym4qvRmEsSEOzqyIua8x2O3iKuR03CpOpjHzkHSgJdTQ5ChEbYJl2lH3nkDp LT5avSzEVceKz2XFdZOkZIVFsQIdiJQCYA71UgtA73AQrDyk+6XhZrzRaMXG nvcsAvL+EmTagwSvgJCtEqCn6a9rLAP1KlovZOLgM9kjpwp9ykOqujrmOU+A qcIwaPrUCU8xaT7il+bdJBeabNwhHYzWY3Myn7BorxKIRzUfIAvdvWfiEV/c 8R2kzAj0UCbRvVsmt68c9w/NK8EUtnNAQ0RPgR3acffNT4xxGRA70e/6hXip R56VTP7huWHS1KrMy9banYozkI7MB0HoRrIyY/NcFBgiKrvgVbTMbC4fyaPg OqXNsv5O0u0s+tM5Homu5py0ob/yAkT+8d1KHdYE+MT1TRzVukD2Ebm19FtE hsp0PeLs7wXJ3QcSeKBD67zmogP9PtiYdDXSLrRp5wVmEGTZi3x+FXpOd6/q cIjzhiFMxOuO6kzk+5S3KRyDj3+P2x3bxA42iy2dYMwBnu+TFDUOYbzhjvRS HEyizWwnLUFxCviZ63wOimJp5fXoJd0Sxi1KkXLp1HacG9hEa1DY8Z+UJzYl 2idvfd66NOV4fkgycHoZh0PzTT4vuTBOQ+E3ZVsE5z7gBcNk+cqIuwJtBQox EBdV7jMx7eMw5yzi/sEk2gNPKKUnp52HuLjxYeq2SMpWZQCdsXs/lUpEhcD9 ypXNF0NikSJQWYIJBr9jE4quzDlaWZkEqTxNZ5Ha4fNOmLHXg5oHreLt0Av7 Vz309PQQdcTIAbhoSlZ9AWNuHNh5n3d6FlNV3d3az1eB5rC2kvJhYZvnhSgX 0uq4sC5IK0rXE45Sa6E185l+ZXVsDJ70SbliZzLST75DPGY7E174Djc07oHD f4f7UlANKoZjc+DEv5Xr7ZoPGLs+Hz48ytYw4yuMoqKGZsaBjiwoFostNZoW Nz28ekyvIZ2XtSpuOD3nheYKWF6MzKDSaDZ+3D58tuyKxg3Bg6L1BALcnWCI SGm8x2ynM0ZJLAr0CQ5UiQqfQBeKay/FTi7chyu4EWTWx/2L6s9mw61kct2O YFcD+C1anGQxkjXqIDziUIllHfrR9qLCQmTFfkdu7aysD0lc2tlccn0r6ac9 v6rxgucceJSc0XXNdqExVwaVQr1TF45/pXfhD3z4Fr1EU5OT+mCrcDE4Q6YA Yjg+IuruF8+kFe3+tul8JLio5ruP3Ou1xZ7kwE32xLfMvx6iH70D/oIBcMKG ppg5Z5dIy1+QJiNe1bIT/cIEyXRwBNSbQPF/CKOisZ0lsiTzPOn0DgoAwayJ 48WHNEnL1iFIoBlAEfs8JJVpPLTHyS0e1WF/kG8S8hU6EDC7st6Uc2t/QAml lCxQLjhzAH0JYtHwvlbFKki62pEqdrUkWtJZMxIGf4kUuST/DNZwTSrYG/Ze YuxDk1p1b3DU4rdeMt6gCWOQqcfhOaWxMO0fSJG2By0aYRyxhy1VsMgQVJRk 4wzPWQMvGGWt5KwuEYzEao6A0O0o2XUVhmAG7OHaCem6+gBUdxDHuMNgeVG8 k457gbZSxxUicPEPH+6OSZYSyOCUAPTrJ3q9erSRwNiyoteT8EhkBvQaBlVB Sal1hwTiSClEkhfxcAdbP+G9xtHVOa+H7UqgiSJSM5wSzzoLqOOxaXeSwFvf z40Ut6PSEGuF0v1DgB+5cCYh7SSHmlOOpn/YL0yqFWVcIcqfdC4XL9nv9RC/ FX0LJnxdVMUiHof0SkOXnfVWYZun/M9C9TTkzZjLvmRlLvotCeBI7MC0aywX TvOEer3dNKDU9izIkSRwGUD7GdopWxkJZ86BjkM7Bn8clEkIsiSKhwtOMnl/ T4ByBqkn8Ti0Yg62AvSbmbbJMG0t6nT9VG+fdE4J+gyCIvdNQ0gsiqS8Tezx XoIJXSLNKN6TsymZYmDKkc6gLKtDGszmZQP0rDWqwrISU1A7UGEsOZz/+MP5 i9c/mLBu0ZroG4DRqYs+Iq3wtFp/KveQFm/YyQfLRDrLGCR8Tgxv4tTDADYm mRpZb11TYwlwzHyi2eIcgIFcskeMcoJa0OxKcuxf1qCOLHP2uC3gwlJCQcQE 4ohLAOuVWjP046KSKm/RuyOKFruSl4kmD7Epj9NMZ0f5M+rM5pS3FvXPbbva TUbXGdIBqMQEF/0banetyAMbjP8oNKDaKjHmWhBXyJNzbSzQ0iRRM1ZSEkJN vhx8CAEsii3pUkWOF88XeBUUsz0mVKmrAmU/ff/aagHHkQJirxe2ghNwL3RW M/QeauKwWUnS+DTz3oJPQDgOn9rEIUE4pvYcdHXJC41rpjRBTLRuFbep1MII NdQoSmYhlInEYKOZU2E8sNmQnTTq+iCScaqsVbcR9izHdsyx02FYHVXPJFQG h73M53habCgjOGGdr4RP/iyXHDil3fc+1oMepbFkzYaOcayIUGTOw76bySiE y27OKpdWR9ECCuklidOxMDluolyHQJWynEqaJl9nh2lKXazmQXN7C+YwinJN RrXaN8sCkeL30aw66V7cvmst7kc2HpYI6Sg8Sy5NSmuwwXLgepy3PnHj7i9L V8IgaaLRLXg484ga6Yt0eAvqM4f5Sj0meNTLDXCZQQaHLRuus/si024zSWYm Y9/1p+0yFwO37FVjbMh9062RDEW8bBZ0VC0S9Te+xcm+TcOZF5+U60wY9zFp 3fPjiV7ETb4L8girwFzBXbOBR3wywgTrGdG+qfszxHxpdNvFdoPwSbkXxEdN LMXK1CZEoBw0fDHVHq4JcLZ5O+SuIyUYHmfnlnz2vansbfBXTmrTfd4oXWTJ XkhDwlL1ob6Vq2K1cWWWSlmc6sMV4DnXa7jE4ZAIubtoiBwiF6cwBeTGPpxI Xo6a51jsimdq9bwxVT26KAaozcnNrMgSBFovuxB9afQxTRcgD9TUZWmeS8a5 VBXYUYTBUXjux/fhrONOjSQYJsIBkmFj5ykGyGDoo15WgPWkNPJFrnXNpl7H 2HOokuLGSE1iGNYkuiSN5JrLVMkVl+vj6oojePyS42CrorrsriaDNeDHXZhD I6B9jW2wCoJfbcNhZ8UOEh6x8oF0TwnVQyNzHLHlxDN7nhwR4od3jOSILVvb CfOTgpibF+gZYRtuO5OmjCsr9Y0uVQQvmXiPkW2zBbqiyyhjBDFzrLVJzQdY AXFbHB4PKHASC9/1PRC0ObbJ4pR25sW4bwhXBdt+g5lBnWub3Mv3h+On6brS gzYpxe/l9iROEqK6cHtd6/7cEyl15QNKDsDeJagcOSZB28R5hr7WPPxuL7bJ MA2JOEy8MakeSB07bRKEAPsOYTtUz6A7uFDFP9KgztXsEZhVwf0Pw93nW3Zt sVpmMW8hJCpqFJp4eOK1aecgnpXpxYlS4xczQ+DXqLSD4YpdJIPb8gmlGkT6 vu1ATQkOAtLmHJCxWmywJ+69MUhawltQYuxzGXLhEL4KF8kw57eRvZc6mTiC fydzj1dazi+9c5K+G49iAIDMrqFcwmwz9Kix1s/ILvFS/cwcN0lWj3wVLRB3 4uw9qPFGAVNU2Rf9jNHar6uUBrB1pP6NOVFIsFWyLPtTlv3txZvnKf91GeZS UK7Pioeh9zyJ4LZ3S+UcGBIdlPbA+TW8rzre6xfnP715IcNxgBTNvVhhK1EH ijJGiO16GVSPZVTMsypRAm2QPOv7RNiAkP7xwj1lsgNzGy+HIBxk2Q9olsGf Edc1irrA9fCoPOD6JPardbouf69ijdFasRCzp6P1zMKt4bNWN3HKa3xrhSsc LGPawQK9XT+aioe9RIjf3NaNNquenu7+2/SLqnO4Cq54xBqowlQl8YbgX2HB a64Gr8RcbIzTOEMw4pT87i+zfUFeKvsw6NOGp6PwAD6DyMIr/skw5vPIBj4P 83fcPtNJ0iEbhc92ZfbExzjNYYRyEI94X7OLily6G8BhVsA4MULHVKEOvIHr bZ9lIHafNwX2FB9GzTqWfmJBBKnZwfgqykM32gRoAKEvBr7IGHGh+xHoSquf xMtbDs7ipNSwmmTkjpAxQxyTle8bbKOlybCoTBsODvyLnPtU/CARa6/V103v xo8dl8nSyE1YQ514vYrusiu9GwAGnV0Cx9HqxbsdFmk/YUz9zAU1L/Md1ZWT DPbp90hw7TQfuHZOjAB3HyXVGOlieMhlazJDtw0+LiaEGQx9WTc6VuAC3Akn Jw4zuWGrJTJl0TJmjJzuYZKSXgYhNxncpP5MBw9IyF+QtUoR8Kgs+kQrPFyz Ci3PxdQyqcvuQXzt/Wb8Xk5lXEvD0GNAb+VmDsBM1SrTQwpuDIq/+/u22BZD yJU2uB5D+9D5IhBeKVFYom+upUqAX6kfuOWxOJ2PSrc5etkHtGK2KTX8MJVJ ApqOLlLNbrkhuHr1OFEQjppsoMDA7GXcXvzFtplLZh9jG7AOqrGjWNrOthnu ybkYte/vMT9Osw2GLU4MJsw6P+A/0uuEWUTuPnFUT8upzb2EzKBYOA1hwC9s Jtq5R9AJgAqKd+iSKwnLDIiJHaybbefwFOmpliPGDH1HSEcYUUYcwPV2PUFy Ei0p1gsiaWEh07EqWP+Wguz/eogGZVc/v+WZoz0ZCdTuLK3zwt8tt4QAg5FX oB7CaR8NFnC30oISI5IJ2wGU5i6nPN/VLibYaNKCUZEiZhyxuCm1Zwl9JYKg htjDiZzEkjFhNvYgqM/mXcyiJa+D3lahfuQBVbGyQJs3qZF4KpmPzJkzXEBw vSHLCfdshi75Vv13bU1eTrqPUv1+xBmNmA/XcsWI97Zf5QpV9xEHZ9jr4Mzu 5OAM4w7OHpB44jvgZgTEaH6DawxLIECLQG6QjKAnKP+qaHa9O5CSAbViekdh DY0BhZF46AgUz4cjbIQ6Lzh1xY/qtf1gF7KoLikA53UopcDkSvLaqO+LRii0 hCEpqFIcvYTl4dVhZYZh6oxoCP0znzO6WH/KE2ol23q0KMxUK31ENE1woTk6 YHXJIuEbPLLJyKllBtHcnhuLdVrUmV5bip/dpoTQeGUlHhSNgWilkMAwUB3v rAAWTMnstKOfmXtTWHv7/DN+i4Ky1E4KO2zDIGuCgeq5gvlZxBewmJ3wmF44 ipbOWQLtcIRqxyZmpZA9jevlthxonUkxWOilmWWH2za6Qbft1jXGk1I3Fw6i 4oJzwjjEOtBmOzffgHSP0wQJOVfdc175osgXtK/+OPDkeu5f0nZXqHMRFhSL bVR9bmrKWEqStGdse2Gof8lXFm4xX2fXYE/QZ8QlnWaqhTvw3dtlt6pjKq/p M30nUR5uIUrWNRPVHYlJalM0gyyOTdZTiYnUqLwnLeI0a8O7RNjVpEGXBTJ1 vLFJ81yHyNm32bCcRwKJ8gQmVjGdNSWy5jytA3+Djr5nHBV1OSFwUotLVgrM ZRJdB7pRXBikDi5RsM6onxlSC/9AXDfiAcVmcBZxJgvGu5yz2BAwJtY6Vx+L S26cRsSwonR+DFdUC/rgEqQ1IyAFA88prM56Y7EmnWP0ddFkbFtLxHM5fPjg COFZOT0Tw4bS7Kixrp2acB6/iw9NCGaHmF0AdY/YOjoWuY+c9y3zyryUYEOS Gidz8X/JiXIar78xH56EJ+iFCLOURqfIlXBjpSJwfvlKlqEudLl+IcRmjN7W Gm76+H7LpML4fic6UemGRxnNpRCSA+fz2ETNxz+XbX4J1h0xIe3qqMBvhtuM pVJg29zSnhIxy+ToZWHLchX5CmWFGD8OAnnZGhwt1zgYzianTSE5IXMxdOmW O12R8jUJfuoePQsR2LfzbhDTRY4aoYYCT9eRbL3UcqdbL5Rg7IXbKDxLKFwk QhTSHeGRq4nmv5kddrsNKm+YEsU9VSXRkgCna1Q4jhTCi/L0NYF5EQOBudG0 UhH1zWyUrvEUkKnBzTsKQlKYFiW30KuK5HNRPoTohX+JQIfW60ZgDVlQ/CJW wAgo4u6PIJv0RpJmOvePOJbda+eZYKoaCFPXSNIXl7iKkamKWBWK6rps6opD DZUmNHITPTitNXIozNnDvHa4JPn8nV5UUqG5pJYDTgvU9dF3AEeCrXmspx76 oTBw0AeSTFufMaCRtvggZL+mXnKOL7l7FcVQXImLYo1pXY3gvFkWEwoedpfR mCXYjxk2mgrqLRlkecv1ikhblnDy5ORz12zjyRPtrxEUdfSx70yVfV3DvW82 6FgEkYW/mbnfuESWJ08fnVCOUFNo4rKpIG+6Hew99X9HRTto2ug+YFWKI9xY XhWK4uSrMfgVOBNUOkRlD/1XfZruPuxfB5Es6YITTgSEcZhwOKZinQRheTkG Vnq4AdymODYy9NO1Klui7jkZyWzOKEk7RHzRcN37pKG0BIHOKeUOcP9uA4iL rqwsNBQs88s/t22jdSaN4jgg4VDc938R1PjLbX5pHsh0BmEI7jagjaQa+W2z jcBrt69PeB7ov8Ro2NCg9z9ro3oW0W8aNE+lg+NNBaRzVW64R8xtDWVTfO4e jrLL+k4RlNOetISjbEv879hB1reo6v4bN5IN/427yIb/9i1kU7BEBH7yXaVU LUZ3nG+9WRIHd/2SDlw1xnJb0f07UPAN1N8us2LVFl+NIDh9Su9aHGPYvpaz um9vX2vwSf8FrXPD/983ly7Pv6hp7v7t/i/pmKvq/UVSmM1Sr1awllcG1hJe jbVuarnqN6XUPf2WyJG5BC1OK4GShjwt1wibaqQPNTaXQc+jiPyRlB7NdoEm F7v37InTKewEqkLqdo45R5iZxxoV7B4Bvkyo5vC3ksMHzDGlmRcXN9tsQHkW 1Ksu2xVd1oMvxXFGq7UmWtnIBiSQA5U7alyuTbvntNQMKKlWRewKs44o6aAT fXWxJTCr0K8cWUvplKEFJrVT0hYpl7Y2wSc/p+b5ba4FHzwIA89Cf1GjXbjE ke9Tmhnqj4EYyyqwVRWrGGzTyGcvZu7ZSsssiXxm28VlgW22SpAO+Uw7y4Dg Q7QFgSFzYN2hy5vLQiw7XbE7dZurOlVfKRAf6JpbRrNXN3JToIfTLFt9U4mO 20MROSAEadE4t3dUXAlXJG0NhsbsO+AFTdm+o6RuTepgJE96KaJ2AINVfKgu HoFxIlWbnJtJ8hiUkLS/G5YCSZ5KhOokwA7/ILMi9lwFGzLHoG7LM5D+Vs63 M7GZkclGsf0kMbDX2VAxBxTWipb5Gx4oUy9MB9R7f3zBSMxR7RdpcxLSQlFf dFxnrl56IRHRr720bDaMm4Pxp07LFJU0/dkHOvuys0GzZNACZlHvisj1Ir04 pDccRAbg2Jo0NnFoZb5/wVIUI0IRoXaAVNwRKEcdrj2uV3xRIxtI8FdSs5zA zfFdjQnso4XAQ4QuAVSIKr0rOQi8nKSJzavzFN48+T4xvaRYN1TFZW3dyhwA v95p63opd5lrKfIBIiCRBfIhw0RjldrzBlgLNouk5o4jn2KAni5NhYPvftYm at4KsYcZZt5SkIrlktiGv6LReLM4sw9ZhD2yhgrN/+nSTPLmxqRZD7JUy+q9 eIpcLyRgtXG/+6P00aIjPA5TVSPpFFIQLgFVLInTFNQNNYLlj0TmOiXgPV89 QW2JCGXLBZUil6Y9GzZ/SAjCg5eRBoe+damSj1xZLhkmh8Oc4cAu87EuQQRY 6u7BEL6NmEUeeEOk6BTvNdvU+wdF1CsMwJTLlNXUGxZgDnioNIG0m7g6YLN5 Kby3iNn7JjGHx4ige2vOk8qrFg5U04RTusAsD+Yf1mcOtnoV/Ym93kna5OiV WqhS7Jm6HE1C5oimrLF33zUttcL5Y5IcxrZYJyD8VDaIPJUFUiysIjAFgTkZ 4iNxa1jz15rQgW+YsBs0qkohnUNh93LTsFAiIbykdhyO1Vgvt2EzsWl4wTLQ 2hmRjv59Tt4Sa2EC1iC67RAgWvQzDfLHOUT3NtZe4uBfxI5gFBEZ8QFGZNRa ujA/eXh6yqWoITomHWoR2wqU1dZS+gXjoL1//+bt316++O6ni29eiNZ54SP9 KRg2pYFrrzHN15B+IGwTU3aYFs3sa0CpgTz8Gi2HGyj2v8XOf9/Ta5Xvagbs NTsmdmPkuKDEwrhFGt9M7Ih2Xc/zGSqbu7TnNtHTZZzDPIF9n8MLLs2+17GL /VwwBfxAoU07SUp23PGjiF2h5vmmM9zKYo0Bnrm6fkI0h9HQBHp+3Tfr3t9r NvPjvrUn0SdshrunXYzorvjj8DK5lCrXfmx/U+LDmApPdxUMhMrC63b9zL+J BgTtqosHuouVU9ZenG+QtHfGlUamxukoST2e6O3CMIUvR7bn2jrGsJg8tSc3 CuthCQ5neOdI9xh2FWb5Q6X9GP9oiMjHkUW5jv2F3IN4HaX7D/3W2rDiHbdO z2rWGTZnHw0/agNjvMRUneCrZiMD4XTcc4zi2Q1tyDbh/Fc0G+nYcPDWqd11 lfhYMe1Y8sgobYpyA+OENMOcU924FNqc3WxRBm73V9BZxzyl5Orxh15ojprd QEej6LA1WqPYlAP61YIInzZp22cYEBdnP5yxI5UO4VgpwlLiJoTMzpcIRdtS WsIkjmp2NVDL57vt8AI2qr7cilmis1ZoCh7mNWs/NBDbgtZ7OvkowQK6VPtX Bo7ebi8vNWfMJcnsfzMmMUo6nE8QUr2OVsccAkHZBi2gowYt7gNT7Px168cF CYNzji6CgjvhqqlLVISGDcZT5aVLKjt17Z0jlqJ0X/bIRz16FYiuWIkirEck VP/ShnneNPQiiSGSsUMPnES6KMcR7SIDlt0FLLfxAArcv7rUqE3ppia4IxpK Id3QIkb8Xrv/uHuOlKiAD/03TJqIPSYkG6GdhwaHvR+f/8GZkGVsFjx3eGZR 87ARnVOoR6e2OfGt2BNBam3YV/zqPLEbelq6rkaAeW09eM0HSADUpBHzRVi1 tlsI9BXb3KfdoDEVlrpGEzYOm8o0trxjBHdGD4pBmVVbxSiEP70spX0499y5 JXtXiW3QYSGKtiE5bI1dsumZ9muw0j1N/p7DbXBpJdH1TybqrGaviZh6ZICQ eEEoZI7qtjriouCAchyUFogu+AbVOkXw0+fnyiaBOSM3lE7Y/A/0EzVlfFjK 1cekQFePQGb1KEx69rD6QYAVrHolD1EreHqO4RwpJc1D5AhoDAPRheibMaNh g1CjKIsaoJ48/c73koejSxhNQE3mo34YzMNhzJQ42ovod0FSqKknoJM3xhBF 6AhVgnxBbjPPo68Dv4JG68oDTO5th4xxJOvY1vYi+gJbdzyvF0UM6O/BF++H tWrtqZpg45suHV0742FgKdscWKqxSCkyKY/RN71tjv/axs06EW7bJI4IQprO CdLoul6BOlwUHFS4jx82ZyjGr+MWscvGR6Ej8qdfrw+utbSLndT6kKphEofE 0rCvJ2FXsL6eCuLxr3lPXax43/Nm5koHkO1YEQ1FMCZiicFvVJNQbHt2TyEZ 0HfR/xkz59n5JHnslpNp4HXVkLhMFbBKfi4lat9FfQppwPeWsoHNMaq9YiLI AiMM708zFbvQfoME8M1ooOlsJNAEpmMcK4RvIq/QT4uaP/CJ9A33fvYpel0I wDkJ+7gGynzjsP/brNA5BfZR/8xVRM7bKvuieHeS5AhbrbmhbKz3EmBhEI22 MvQfCGtUExWQZI3FUY2ZtRzSTOM0Y5N3GzjhPAkCiy+rEIH/zYro2QvqQUTO +Zf6Bkv9KUuZSz5BclG+kuWtDrdA8zvrhl8L7rUBvQ7fl9pUwfVDDoJKQdDs B3UkO/95z4GrDQi4YIzDTdSGIFy8xmYEZiINVJUjgo9EqCVFVMyzSH3szvTJ hOhzHeZmaTSQ6v8HHdvYSUXXWpuVGZYDL0z3kdoeuNIkyycEc2HvJKNTcQ+s YNTCxzZhlx3G6LB0ZEbFEDaOkOHCqCI3KGHVodtea7iPrXze1G173PqcqP6C BtFuASCpx89MA9FJzjxbYlLTT6Yfw0KxqddKXf61ZnFhunGPxmvJ2JujNtcJ VCXnuehd9Zc0jAWWdStlz5Ie9+j3IZKUVFplrnB1rwt1FWLyYN56fJQRwX+Y HwWeW3R8ua0grkOurp0ym6RBhGBChrHjVYGCIAFSQBATNKTQmbY3GKRqAiZ7 ODvKZsjOdWZyCi4vXCEp81DFPmUKycpD7VXwYjveVLdTojtOhNSRCdt9XWS8 KNRIgcl4mCNZGLTBvr2jF0216OwMiUwxh4ndATK9pR8VhyMYsIzzp+LnTR9G 112H+NQ8l0PRREHFruobkCiXsU+UBTYkjk7kzKGxayo+4GIcUN23NPzRlNrf oB/DCMzuatw2niFmJG5bsSqwn/gm7yi3mqs1nveAtBBJWYNV5yxqQviW/EEl Q8UwEEKPq6ctb8wU8+F2lXqaXeGg9pzOl0sYr69KiSUjLmUJ9cIsUNOLPVoY C7gxXbPTGnE+59sqxEefOGJUspCvyry9c1W4CvjK5WppqxQrKBjKQXaXvTo/ 4mhW3F/Bk02qpcSzdsRHdrbAUnn2JcDm9TPMkp6fvFEHqT58QEilQPckyg7r DRHQGU1ls8JSrKC//PpI73GUtShs0BIaS/PkRIahB402JJ23gjdjbA37+MII Ltcm8lnDF8r3RCacm0b6dWZn//QJle3H55OFUDc2p69vnVP7L9ulLGbFfsLm fOokBMtTcvitsfKgE26MlLUFQSp5jFRS45McAmq/A+ofUPKbQnxJPvUkBPlr a3+l7Kaq4HKN2AHOdBqfDUwJRiEGFV0OzIAWk3i7+CRYlaNEp1jdwG3U3lhR AgyFQXRC+wleS2HfEI9xTcs4jsuINY1v5RPBfSL2LvQeeJseZ+oxK6P0MQyV BQ2V6RwGDuox3IKx4CLjSTF2T6/XjOFiR3AzRAyRrG0T03JeCRkOUopYi0M7 UeCgAwVJ0O/bz83+U5oOEZEuWov70idkBh67i+debNq0n5uimUqAhSb3SoEt Dl9/++qIfRv20iRI8I+QpFRg6pfT8vnprTPOHTVbto36aEkvkGBf8FQ60n4w bqJhnNDAsXwrJpBUiVbdvy5jwdG3Ag/EyUDSHFOO9WNdeHj1I8uU3/lLMXFl qjRpEeDLLShIGmJgRpfHk+4VqnlWdVHRUblkTvdeNDvYic8amuQUaQVs0Ai/ KkljK1mSesEFhlxLKgzta7qdIXxfM0ZgUVGnK9+vptfLXMp1UVHX5/kAdsHB SVI8BSs5kwLCHlMYduzE6IkTFH0mIjCrEsRebgmiJbjACyug5y9iPsogpT3e B9cKNsTmnVe9XEQ2ifqdheVIOched/nKuceDzPZQP5T0TIbPASfqjqSzgVlb 5gpB5EgDTBnnpsgXYn5K0kh7b89TbGA8H+mafXuTVFDISmSF6k4OmxiuSQpg uSiNe+qtiMwJAKHYZGqnFNT/xvzS6UCK/N/H2DduTX2f9lcSaO/HHid+ExsP 9tq9apyYOxhruFUBHl0MsF/B49tX1ER1ig0jTUiRLigsB+O+EicRO6Y1LN4P VEdFpN+ie/8YaZqnEQjcZE2SrzLfLBT2h/0h6rcyNSjNJuoS3xfVBFM67fv3 b4SrPJLAztMnp9hJgPZZkkcmLiY9GWRUKSQRrsn9WqMLJnLt8AnYRZIzPGWk Zab87PGNLmqQqGW8y4rYYGKSAIQD/FzMOAqFu7FnFvVmR6WmVoOwtysEocpQ 5JA2ATO4f7Pt6KcTyYYkTOcflGRNXDCqFiYVJiBs8tXW5TjhAOIbwmaJFH5k 8A/p+Jdma/u2ztYDkACUNQ1ukSl4rer0mYv93JqLnmSWMruMuegYX8APmvod wuthhrdEePJevWu/XCMSSEhXwkA/ZaHeyhF52kt5VcAJyeVAbzcD54ESwl1F llmKYly2XpviGYdWUEUssW8YwaLkm5LKbAg9eMP4EKzpDn2mo53SR3MYFXkO j0QoyK/2IgbOGETIb6xQaKDdI6gOFcBjqkhEDU1y5nAAZ1SoqxmHzLE93Yq7 iQBRshbpYRIMvCR+pY8ohehtxWqDelqZrEV9e6JE3nYLvf5s9Ny/c45MX7m0 jxd258iTUILi6pL47Ku0OXI/BQd3JOcc9zfEq5175CbXlc4FRvU8taeSUm+w j2r1d54tCO0rMgn/2c/SpBxqxMK4srO0J0l2qF1O88rePppENUHEUDBg9N71 5H18a215aUddu+o93YsJTIXQ/HzT5vMX/eDxjBoXW4yWgjBV7NbqW7omVQ6x JqE3NY0HWDsjuCTNtuTW2tZDqrPSyTb4mAnogv21UgFc3kY2Kx1N1Edh3WhR 0aI6d/bF6gbxBp5HAHGunicA8bc2Zror+XVdLsgYycTNWOSNkt4YFjneg//Y ig8alX0mjgjehhcY6c1lMpUcmQ40AYU9c2ZVjBcd10sD3FTVyANHijd0rHSP jXOlskYrVNiuMtPd5SfCXOTXQV9i6UjjIMfNU3EqQ8jDi8RFzbbdmbRC5lpG HxvCpBRFMUFba1W3oyNw/Fm6V+sXGcLKtI99MzFWNokUHIuMtP01cqC4qlRb C4lt0ka5wEsiy6OfftCv6WPPEFPxIFUhhWNpN7mwlJ7SGNNlotdi4lS9SdZs VwpXoO4ZLx9SeZc2IcqRJa200m0wxbRVGKGv4Z5LgSL57ahSO/yRSXohFu4w yS+wzxrzVYH4TLZV81lLK6D7T/U5ULvndc1ft0HM/YgR7DrEl8SHqndOK/VJ FZddwICphRfVXD/7ehIoBt8vqcWr8JEO36Qe9xwlSRPfEKOOsCVcxb6nPFw1 N1B4sBPBEmSFbTQBix3+YF1wRwdQJOy4jQj4xN/3FXcNOVclnf1tg3IMOOLX yK/OWRJZsdKEEVYZn5hTObkgAk3URVqHKbOQAig0s6ZHoYcQLwqerDBLVkjl qDGSJdAgdb3gRH13Eh+ttOfwa+Qc5ji+5RYlLWVddhyrKDHZPOk67QoLqENl ve3aUkoVXDsXx1xcv1buC6f+Ue89IuwgUhZoN5+dPn2g6LsXhIpvfW2VGOJr Uoff8r8KWir6OjHDRpv44hvYhtAtlCeDVaJY8Hk18KHJLtmg1Hs5bbCrWWSx 0wsK0xu2zip1P+TOH0XlTX1HlREVCFFKf0VTDD3HBSLhvSbspHB48er1kT06 Aon+ZlB0kk49b99JjpzrZWeqd/DwTpTRzMWAeKyKjr/OuRjOVei0lhRgsozP RBBMxTEn8E9p2WzsesiqblsEdzBSDoGbRjh1BJmpKVVkfqFujpXfHKUHdimf AR5ANfUIqnrNsSt01LWEjsn5fax66z6xy0BL8bfVqgTzBMvB+gOYIpIUilGW yqpYWrk57wC2VhYBRFE2oBNKuCLkKpVXmqGmq6F9SUpO5Prk5hIB/rUo8Ciy 1yiq9pIEsHO/35SsMmG1AOvJJK0uHuRgHBVUfZQ9TS+g0+6hD1u0hMp8d6L6 NkXp4gMkYUco4ZkQQmmFkC3bm6x6baWTX9yJznbCY9jidNGZyVgInJ4SrJ/R rmdf6KNW3GDbg7ijyZfhrqMfnbR43i6eC8eWkEiNO1Ci0Ait6xJHODg6seeo QlZujwOBQYI5B5c/c/tgpbgRQQfUmxwVvndFE4Ehy00j4JBH5tIAAdmg/8NI dxNDE1YQjXGGVTmjcCuvV9uYBMXrTM2y/QmuuGAaQYQaiuwgsgdh4ynRgveW 5E2j5ZA4NmHgV8e49Kakytkag204Xkj6OMdFSOPwWu1N924hkSXYXYwpWUIl Nt2RlE7bYp9YbBmcsS+2OKWTTvXxbUn6LBg6Jfq6IiKHwN+Sj45DI9g2Fh9R nbzXGkO7+XJkx1IZQyLFxV8edzPSaumFy0aFi+rhMINh/nv8ODOhwRMOqrJv UaSd2KOrmhLDlNUcvDHFiJIBvgfl98Bg/bRU9KPaz5T7bEmBIFcMw1wSREcx 4xiH1ld29juAhmEH0D6vYn3boxN+GNN6tAPS3t7xnPqU71cPyctfNq1PnxOt qbd1Wbp1Jl+GbAjBekHY/JadTU+nJ7LJDCUqGg8MUleLT/lkjO047MKUPkpp spwADd/SjRUGSPqxur5fwre1odlgLMEjgBG+oybBA/MlPnqmnWIUlYHSzoyV wRAaWJ2jer8go5m9UjvJE1QPDuIfqtHxBRalwssamzmVbc9w32XXEff4kza9 d876rYfTz/uHfC/7S2yRIXqmj9LF/Xh/z3XDkCuu314RZgDD28ReBTJU7CdD geY4ykpxRqTG32DohzHFzLInVLJzf59OVUX9mCA7swvYRe1iwNLB35IItFuK ANlpAovsW5ugz79/LvGv/3lAfvCiOdBW3dIvbeyJSa/BTnClyygLQNOgpKuV di5i9t0mOyn2oejTASwMGKPAxcCkt2Dc7CL2PbX3sNY2ClQmdY7iOhfpbwzL Rildpbjs9yrt64U+khm105bsTvXm4uX7O4GJcqmGa0GPkd68EQ+pZguH2Pxs 4qgEG6pw3+YIjigJj6xrlBwL/Caisg7aOLvkhkQ/YQxq4MgLRD4nXbQiGHc4 hNiJQgr5apLlrAia9DvzQUEGZpZvRh06fj0RWrnQBm/ZDfXATuBj89ZijhxJ MXJGM1OgRDmq1OYaVZ8ETib1f8fSaFJZWiQTnvhLgQlm/45HJLrzAl6AjgX/ cCoT96HBzY+NTgb8YzI2snMQMVpXF7VD7E2C1WIYGOAeCU1etSvpM4YZaYp5 3GYuciHTiy3g2nda6LjBsCTdB96MbygsRyf4tk85ZncsmFy63aboGUnmhA0J 1oqZ78j2o29RUHhLL9Vd5VdgrVNKsEspB0M+vl2x2Ql3IEefpOLBbvINdZIX foo0cLVd1+IDp4hAsV3Vl5oKmf0vjZ9/5LSZRYiDS738Eu/VGLwm0LPk9Gkl rbry0MVCJWAJfFeUnwQ7Yf1uBH1Cna35gm6rg6DhNYAEFEfJ+3ut/vwxQGjF rGVI6IKb/nJlATXrNSKcJDCn+uQkm0kWeh9gpYc/okDozqbfmLdQZNole9c7 Dlx1drknI92nTEWYqpLw7MnpA92Kl9it5voP8p8eZjWGYWGqV0VlnAZoKZc+ QMIqyTajFjkWqOJTA0X5zojc8/iSdB/ggzD36rze7JiyJsIp2YbWvHpbDNV9 7vqHxa4b6wvlcE1iQJ3vf/bThnU2eIOUGRUlIchf4KsYMpe7yISJuoMgZ9ep lm+VNuoqt45IsRYz4leJIwQpKxJL9JZj6iUnH8Mhkvee+1Me5kdZPfM13mMu /Zgvh2ViWtHTx9HrZc1hjIHueg+TiGAvo9vSg5dr2hPMOHaMvGcJQOQi+6s0 Bzj1IiFpDvD+nrz8IcnzVYACV16C7ePwlXbQK1LtQyT6oFGPtFec+AKKbAc8 h+F5xDeJf6bC7tMHD55NuBXD54/xpkVA77GJH+raTo4Mfu/0wcmpDPH4MSHJ 322I0yNL0WX9qArWfaFdoQAnzyCMf/qAbxIHGp4SOzBRnGQNiCxBXWxhCfNp upxxrBNi6ac+tJhTF186NpS8YI5IEw77fc5t/CjC0MvZ5lQRq8ZS020iifNc dMppX/UyxHTLAfjwDm2ipFs968S0iIluSQwPCJ5QutvhWy7U+caBAYBBgWXx Ak9Itqfv95Yqz67rsY+MkD9DknSLa1dGPXbY0/AT6zh4a7ftppyrnQVcRGbT P0GHDG4ujQj/CmeFzswiOaCxDPoeUl2ateMDRfsjmYqeJe59qiejurDCw0Sg YCyrrUcKcxrgOsWnCKJNMLvidLaRSz2Jn4goRl4Bl6IBQnYijBulq+wjdOXi S3rtpEk2Ayi5vslmSArE1sroB6kjCu6P90LhbeRUa1Qe+9BbPoRIbvuOlBeM DZR8xb3QqWdtjRCarQ+WiRvBF2kJW9eJ8mF5Pn1tfBqdlDV1tqWu8tabQ1bx rUD9p7VlZ+o2FdnPRWGSj1Jo84EM54dWChdBdVT1jLoeixeD45WcXNIZXK4D EjgxAI4fXdU3KHFhjdPsZdGBwA3owc929Za8vqhPo0RK6tLeCB8c5CVvUO+t ty3KWoXgGULWgH6No1AJObyBbRo9lmKvHcJEfEQ3KcAwrjvLMo97ToAAnIbn A/Eg8FfStZ5qLNYzQYw8ivVt/4hlHQKPvPuyjv6Zy6J6tH/AKX36EX3aQjSO qbmh18CeYOJJxRo1m7rExqUFFsZSLuehV/xPyC0bTNYfTZLU0FTYCM/uDXDa H6CHiEPZ8rHkopcCHnqjPYyp5KOjpXPpv/2o/7bHjyEsevKKHXqX5cM4/2f0 jlb6jz/ey3XncxfE0En4SLJ7tJ7cmI/M/NIxSVfq98tYpyCtLq+dZA8FOhPQ 535SRvLJ3jLQOUnhKvV0IIISy4KgbJyC0VIeM9/5JqTygVgsgrUi6t4oqzBm aj598pDEYoKGh+12PO4Z1ryIdmRJhLWVbSZVQqJjJHF/La6SJoAwr+lBrwuj 3hpFO+oDU/cZhKtoMv1ZcpabRYw7L0FyF7HycswdbHIv2b0QsMLaTV5338Mg s83HjEpl70Sk3Z5qmD2nRPoX+nmooSflZoZDTudrtXyT1RLil6vbuXULM8cE UOx0SLFMIimNZsZuCMjliOHtZXWhx+q+95AqLpti/3IVIXZvMdNHe8sF1qe4 mSCHVsEivcE+kZac8fH91g5G6ef2WqucWS8UPgmSQUJFpQ4wx/XXUoiFF+of wER6CvpaP6swFGB6dqlXKHEaSAMI6vI9HDN+2BLcsbROPAwNpVdtLM9Nv76n mwyHD/z73CrGXba+8GTAiYI6Maj3hvIL+JM+jVkQhNBuKL7gyLY2GUh6TZSt 1Doa0WunoTIFcmmLpJPNkmurEqB93hJs+pkiJJgn213IH03QnFuxAkyMgrEB pwafj/eefGCklGaHylWfTR8dTchTdVNYrQi3E2nqarfuYyf8dDdajEavYsIv LAYHoxM6gK9jvMO6qHosTvvzvpr5Xziz129+BEocmSApjDwxMZKiW+Oj87vx PSckPhQ1iyF35pKwTgumCJkJ3R+MADAGxbIvSzg2nv2sdQ6QUklYy9bKnl9Y Z34OPBweQBULBj19+jllSeY9dzfbhA9Zhdh/euF3nN7o0YWPEdX79yDE5mPz UNYehqcUv0QOv743CbeZgCIMQ4uzclqu54qNWMhPxaC51IYw1me5yimG+j7k 8IUG/9U/4io84XbraY7iWgTfG7SXm+DhI3xiWyy2KdCjE0YX3oPm6C++V4hz t/uENcZwLCPywNf88YTH3Sr9li2+auKC9YkfRZVAKSiG/ba6KYvVgiNJSFzU SLne5H/fSvUJ3kLqxebSCqy1/MS7O4KKBqcP4UdhnNdRPptA/JHwClzWKuOq aQteUnspnVlcK4PtPMNOYJh7xjkksJNn3x2lgkQqnSR9Rt0hE8Hq0xaL4oh3 Ui4cOCiHA5mw9EVL+jAeKE9oqeXigeVYHfSFCUVmcIqaIm9dSpfbdMuiTpRl vfQXWuTX5qNOJbObMoZyvLz453/cFg6fJklgTvn9AQfn4I/GCNmJv3FsqghD zj966t5pX9USHkvTb+6iUn6rEGFYzSUWJFgi21mXEDpmvZTi3tYmYri3+HW4 A7McI3pT3vXw+3Z9z5aHO5z3SDbg7RmAw9qNaPEZJIbWFazQQbjrh0adizTc Q31gS+zoPOlyKClsqIi2+kS/D6I02+uNyja6ZslYPEod5Hu9BpRaiJafIOQG bW6rj24ryzjTiFmWaXLgGu0gTN8gtRmvQk/w+y09pLxcwran9HXVbI9ix0ps /VyFnl8CH6MK917wmroQGEa67ZckSwbt68c4mrbA1kctXf442l8sJjUYN9sF w4YT4AzRgAS0W31RDg0X7TnGand5A7EYAOs1C626HbzK3fnyFsRbSSqMeu6D 8/IopuZKm94wrPaEcaJpmEls3Sb5+R1GnoIO51LN8aqtEe2yKo41h+GIqhfk BtK2ou7ITfgCJmobtPYyL1fw1z6iCZndguQei6l7lc36T7CmlHiOVGB00ou5 3X8NfF13WMRwTk/joKwP9PTMLeKMM7KiQ9878x6D1o/dyD04jvMBpD6rEANY fUkWGMLqZ3eH1Q/jsPrJzkdg9nYI4LC/waEBfMDo+zsmCukyyqnMYYcNHfmR UhdDUL67IM0AvJMhTtyKBGlBueVdaNI69sM9PiaQdzyYswSIEhSf59w8oFj8 z4MlEHRx8KE/ben1sz9JVxt9kXCchu8pOYCT0TxuiuNNZswQZFvhwm1yo1bR ta9ONmkwRcxafoco0Br1Im6iSMsN87lZhPxYKwMvm1jcURKE+CAUyMOoFfX+ FWJaZG+QlR6fVYum+IDfu8AEzoUriZtwWk9LGHnpLsM3Eg3xZ9dL+yrNim/W pq1Sro54cqk0KQhmgCbR8EXR0No0e7WigPCKwmFU0MKN5Aw/F2WK0IQjhELh Yo+/7JEH/DI4ia2AXgmAqvwS3h0oAqSSJYHC2Qw9o8oP8iPcicpqOw/AZDiY wH9ev/2W/vvizXcHTN8HCHZ8QAdLHs9qBdYDO1AUPHUjGtDPmDiJ3Z+dik2l RB27a3LMt2Gh2yEMFo5JgBVUAfQFFmf51EZmufjAMT2Q5X4RnHRCXjCdwQSE JZ2DVgMqAkvdsD7G3NjKPfW9wEeN2GeU6i/epax36HB23/q/k66N9np0OZ0c 4a+wgXX81fR0+pB+jVlBhzFkcoJRIn7e/+HR9BFod7P+AQF7w4PB66wHg7ri gcR6tZ+H6NO8LqLjEFsjue0T5jz8PZ6v5X1hxjGwxeozVE2obQbWHiEINzpJ qil2sedTjkdMRhMnSuzqLfCOd4UvWbOPwbZzY2NOsaJrR7tLs2853ZT9jcIO v4pknSldy8UTbA18+uACDXziBZp2e9CHS5NmIMH34Pvz/kbo96nxH4WW7iMr Pb1/r9SP/G9Nh/2SbOoeB8hjUQyrKtzPJbMsOE1EAflLclbR8aV9mmYFaEQ1 069Z95fW4FqQWhsOaAKlxrptDMujPrtBZy77rpernMuKb6htlYDPMay65l2W lvgeQPBxqpzlqLIXjtAmxHvBDsH/BxOUZEnYRQEA --> </rfc>