rfc8875xml2.original.xml   rfc8875.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.3.3 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
]>
<?rfc toc="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"
<?rfc sortrefs="yes"?> docName="draft-ietf-git-github-wg-configuration-07" number="8875"
<?rfc symrefs="yes"?> obsoletes="" updates="" submissionType="IETF" category="info"
consensus="true" xml:lang="en" tocInclude="true" sortRefs="true"
symRefs="true" version="3">
<rfc ipr="trust200902" docName="draft-ietf-git-github-wg-configuration" category ="info"> <!-- xml2rfc v2v3 conversion 2.44.0 -->
<front> <front>
<title abbrev="WG GitHub Admin">Working Group GitHub Administration</title> <title abbrev="WG GitHub Admin">Working Group GitHub Administration</title>
<seriesInfo name="RFC" value="8875"/>
<author initials="A." surname="Cooper" fullname="Alissa Cooper"> <author initials="A." surname="Cooper" fullname="Alissa Cooper">
<organization>Cisco</organization> <organization>Cisco</organization>
<address> <address>
<email>alcoop@cisco.com</email> <email>alcoop@cisco.com</email>
</address> </address>
</author> </author>
<author initials="P." surname="Hoffman" fullname="Paul Hoffman"> <author initials="P." surname="Hoffman" fullname="Paul Hoffman">
<organization>ICANN</organization> <organization>ICANN</organization>
<address> <address>
<email>paul.hoffman@icann.org</email> <email>paul.hoffman@icann.org</email>
</address> </address>
</author> </author>
<date month="August" year="2020" />
<date year="2020" month="April" day="13"/>
<area>General</area> <area>General</area>
<workgroup>GIT Working Group</workgroup> <workgroup>GIT Working Group</workgroup>
<keyword>Internet-Draft</keyword>
<abstract> <!-- [rfced] Please insert any keywords (beyond those that appear in the
title) for use on https://www.rfc-editor.org/search. -->
<t>The use of GitHub in IETF working group processes is increasing. <keyword>example</keyword>
<abstract>
<t>The use of GitHub in IETF working group processes is increasing.
This document describes uses and conventions for working This document describes uses and conventions for working
groups which are considering starting to use GitHub. It does not groups that are considering starting to use GitHub. It does not
mandate any processes, and does not require changes to the processes mandate any processes and does not require changes to the processes
used by current and future working groups not using GitHub.</t> used by current and future working groups not using GitHub.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction" numbered="true" toc="default">
<section anchor="introduction" title="Introduction"> <name>Introduction</name>
<t>Many IETF working groups and participants make use of GitHub in differe
<t>Many IETF working groups and participants make use of GitHub in different way nt ways as part of
s as part of
their work on IETF documents. Some others are interested in having their working groups their work on IETF documents. Some others are interested in having their working groups
use GitHub to facilitate the development of working group documents, but they ar e use GitHub to facilitate the development of working group documents, but they ar e
unfamiliar with how to get started or they are unclear about which conventions t unfamiliar with how to get started or unclear about which conventions to follow.
o follow. Some other working groups use or plan to use other code-repository services
Some other working groups use or plan to use other code such as GitLab and Bitbucket, which have
repository services such as GitLab and Bitbucket, which have
different properties than GitHub.</t> different properties than GitHub.</t>
<t>This document specifies a set of administrative processes and conventio
<t>This document specifies a set of administrative processes and conventions for ns for IETF working
IETF working
groups to use if they choose as a working group to use GitHub to facilitate thei r work. The specifications in this document are not directed at working groups o r individuals that are groups to use if they choose as a working group to use GitHub to facilitate thei r work. The specifications in this document are not directed at working groups o r individuals that are
already using GitHub to do IETF work. Practices vary among existing working grou ps and already using GitHub to do IETF work. Practices vary among existing working grou ps, and
some of them are not consistent with the conventions proposed here: that is fine . The goal some of them are not consistent with the conventions proposed here: that is fine . The goal
of the specifications in this document is not to require uniformity in current p ractice, but to of the specifications in this document is not to require uniformity in current p ractice, but to
help working groups get started using GitHub in a reviewed and validated way if help working groups get started using GitHub in a reviewed and validated way, if
desired.</t> desired.</t>
</section>
</section> <section anchor="administrative-process-and-conventions" numbered="true" toc
<section anchor="administrative-process-and-conventions" title="Administrative P ="default">
rocess and Conventions"> <name>Administrative Process and Conventions</name>
<t>This section specifies an administrative process and conventions to sup
<t>This section specifies an administrative process and conventions to support port
the creation and management of GitHub organizations for working groups and singl e-document the creation and management of GitHub organizations for working groups and singl e-document
repositories in a uniform way. The steps may be done manually by the IETF Secret ariat or repositories in a uniform way. The steps may be done manually by the IETF Secret ariat, or
they may be automated. See they may be automated. See
&lt;https://github.com/richsalz/ietf-gh-scripts&gt; and &lt;<eref target="https://github.com/richsalz/ietf-gh-scripts"/>&gt; and
&lt;https://github.com/martinthomson/i-d-template&gt; for working examples of au &lt;<eref target="https://github.com/martinthomson/i-d-template"/>&gt; for worki
tomation ng examples of automation
that is in use in some working groups.</t> that is in use in some working groups.</t>
<t>In this document the question of whether processes should be manual or
<t>In this document the question of whether processes should be manual or automa automated is
ted is
deliberately left unspecified, since these are implementation details that the I ETF Secretariat and Tools Team will address.</t> deliberately left unspecified, since these are implementation details that the I ETF Secretariat and Tools Team will address.</t>
<t>Most of the conventions below are drawn from <xref
<t>Most of the conventions below are drawn from <xref target="I-D.ietf-git-using target="RFC8874" format="default"/>.</t>
-github"/>.</t> <section anchor="creation" numbered="true" toc="default">
<name>Creation of GitHub Organizations</name>
<section anchor="creation" title="Creation of GitHub Organizations"> <t>This document specifies that there be a facility in the IETF Datatrac
ker
<t>This document specifies that there be a facility in the IETF Datatracker (&lt;<eref target="https://datatracker.ietf.org/"/>&gt;) interface to allow an a
(&lt;https://datatracker.ietf.org/&gt;) interface to allow an area director or w rea director (AD) or
orking working group chair to request the creation of a GitHub organization for a
group chair to request the creation of a GitHub organization for a particular wo particular working
rking group. Ideally, this facility would appear both as part of the working group
group. Ideally, this facility would appear both as part of the working group cha chartering UI and the working group page UI.</t>
rtering UI <t>When an area director or working group chair makes a request to creat
as well as the working group page UI.</t> e a GitHub
<t>When an area director or working group chair makes a request to create a GitH
ub
organization, the following process would be initiated:</t> organization, the following process would be initiated:</t>
<ol spacing="normal" type="1">
<t><list style="numbers"> <li>Create a GitHub organization for the working group.</li>
<t>Create a GitHub organization for the working group.</t> <li>Name the organization in the format ietf-wg-&lt;wgname&gt;...</li>
<t>Name the organization as ietf-wg-&lt;wgname&gt;</t> <li anchor="S3">Initialize the organization by designating the IETF Se
<t>Initialize the organization by designating the IETF Secretariat and the are cretariat and the area directors
a directors in the working group's area as owners. If the responsible AD for the working gro
in the working group’s area as owners. If the responsible AD for the working gro up is from
up is from another area, that AD will be an owner as well.</li>
another area, that AD will be an owner as well.</t> <li anchor="S4">Initialize the organization with a team that has admin
<t>Initialize the organization with a team that has administrator access. This istrator access. This team will
team will consist of the working group chairs and working group secretary, if one exists.<
consist of the working group chairs and working group secretary, if one exists.< /li>
/t> </ol>
</list></t> <t>After the organization is created, the URL for the organization would
be added to the
<t>After the organization is created, the URL for the organization would be adde working group's page in the Datatracker.</t>
d to the <t>Steps <xref target="S3" format="counter"/> and <xref target="S4" form
working group’s page in the Datatracker.</t> at="counter"/> above imply that the GitHub identities of the organization owners
and
<t>Steps 3 and 4 above imply that the GitHub identities of the organization owne
rs and
administrators are known. Recording GitHub identities in the Datatracker (see administrators are known. Recording GitHub identities in the Datatracker (see
&lt;https://trac.tools.ietf.org/tools/ietfdb/ticket/2548&gt;) would facilitate t his. The &lt;<eref target="https://trac.tools.ietf.org/tools/ietfdb/ticket/2548"/>&gt;) w ould facilitate this. The
person requesting the organization would need to be notified if the GitHub ident ities of person requesting the organization would need to be notified if the GitHub ident ities of
any of the people meant to be owners or administrators were not available.</t> any of the people meant to be owners or administrators were not available.</t>
</section>
</section> <section anchor="migration-of-an-existing-organization" numbered="true" to
<section anchor="migration-of-an-existing-organization" title="Migration of an E c="default">
xisting Organization"> <name>Migration of an Existing Organization</name>
<t>If a working group already has an organization, it would be useful to
<t>If a working group already has an organization, it would be useful to be able be able
to make it have the same management as one would get with going through the to make it have the same management as one would get by going through the
steps in <xref target="creation"/>. That is, it would be good to be able to run steps in <xref target="creation" format="default"/>. That is, it would be good
steps 3 and to be able to run Steps <xref target="S3" format="counter"/> and <xref target="S
4 from <xref target="creation"/> so that the rest of the activities in this sect 4" format="counter"/> from <xref target="creation"
ion, such as format="default"/> so that the rest of the activities in this section, such as
personnel changes, work the same way as for organizations that were created as personnel changes, work the same way as for organizations that were created as
specified herein.</t> specified herein.</t>
</section>
</section> <section anchor="personnel-changes" numbered="true" toc="default">
<section anchor="personnel-changes" title="Personnel Changes"> <name>Personnel Changes</name>
<t>When there are personnel changes in the area or the working group, th
<t>When there are personnel changes in the area or the working group, those chan ose changes would be
ges would be
reflected in the GitHub organization. reflected in the GitHub organization.
There should be an ability in the Datatracker to specify that there were personn There should be an ability in the Datatracker to specify that personnel
el changes.</t> changes have occurred.</t>
</section>
</section> <section anchor="working-group-closing" numbered="true" toc="default">
<section anchor="working-group-closing" title="Working Group Closing"> <name>Working Group Closing</name>
<t>When a working group is closed, the team with administrative access w
<t>When a working group is closed, the team with administrative access would be ould be removed, and
removed and
the owner list would be returned to the Secretariat and current ADs at the time of closing. the owner list would be returned to the Secretariat and current ADs at the time of closing.
The organization summary and the repositories within the organization would be u pdated to The organization summary and the repositories within the organization would be u pdated to
indicate that they are no longer under development. indicate that they are no longer under development.
Later, the owner list could become just the Secretariat, or might include others Later, the owner list could become just the Secretariat, or it might include oth ers
chosen by the Secretariat or the IESG.</t> chosen by the Secretariat or the IESG.</t>
</section>
</section> <section anchor="repo_create" numbered="true" toc="default">
<section anchor="repo_create" title="Creation of Document Repository"> <name>Creation of Document Repository</name>
<t>There are many different scenarios and configurations where it might
<t>There are many different scenarios and configurations where it might be usefu be useful to have
l to have
automation or established administrative conventions for repositories within WG automation or established administrative conventions for repositories within WG
organizations, such as:</t> organizations, such as:</t>
<ul spacing="normal">
<t><list style="symbols"> <li>Creating a new repository for an individual draft (at the discreti
<t>Creating a new repository for an individual draft (at the discretion of the on of the WG chair);</li>
WG chair);</t> <li>Creating a new repository for an already adopted working group dra
<t>Creating a new repository for an already-adopted working group draft;</t> ft;</li>
<t>Migrating an existing document repository into the WG organization; and</t> <li>Migrating an existing document repository into the WG organization
<t>Creating a new repository that contains multiple drafts.</t> ; and</li>
</list></t> <li>Creating a new repository that contains multiple drafts.</li>
</ul>
<t>As an incremental step, this document specifies that there be a facility in t <t>As an incremental step, this document specifies that there be a facil
he Datatracker ity in the Datatracker
interface to allow an administrator of an ietf-wg-&lt;wgname&gt; organization to request interface to allow an administrator of an ietf-wg-&lt;wgname&gt; organization to request
the creation of a new repository within that organization for a single document. The the creation of a new repository within that organization for a single document. The
document authors would be identified as collaborators. The repository name would be the document authors would be identified as collaborators. The repository name would be the
draft name. Ideally, the repository would be configured with a skeleton draft fi le, draft name. Ideally, the repository would be configured with a skeleton draft fi le,
default CONTRIBUTING, LICENSE, and README files, and continuous integration supp ort, in default CONTRIBUTING, LICENSE, and README files, and continuous integration supp ort, in
the vein of &lt;https://github.com/martinthomson/i-d-template&gt;. the vein of &lt;<eref target="https://github.com/martinthomson/i-d-template"/>&g t;.
Performing this step would automatically inform the IETF Secretariat that this r epository should Performing this step would automatically inform the IETF Secretariat that this r epository should
be backed up as described in <xref target="backup"/>.</t> be backed up as described in <xref target="backup" format="default"/>.</t>
</section>
</section> <section anchor="listing-related-repositories" numbered="true" toc="defaul
<section anchor="listing-related-repositories" title="Listing Related Repositori t">
es"> <name>Listing Related Repositories</name>
<t>The IETF Datatracker should allow users to add links to repositories
<t>The IETF Datatracker should allow users to add links to repositories (for Git (for GitHub and
Hub and
other repository services) on working group, document, and user pages. other repository services) on working group, document, and user pages.
At the time of this writing this feature was under development.</t> At the time of this writing, this feature was under development.</t>
</section>
</section> </section>
</section> <section anchor="working-group-process" numbered="true" toc="default">
<section anchor="working-group-process" title="Working Group Process"> <name>Working Group Process</name>
<t><xref target="RFC8874" format="default"/> contains discussion of the di
<t><xref target="I-D.ietf-git-using-github"/> contains discussion of the differe fferent possible ways that a
nt possible ways that a
working group can use GitHub and the large number of decisions associated with d oing so. working group can use GitHub and the large number of decisions associated with d oing so.
This section specifies a basic set of administrative policies for working groups to follow This section specifies a basic set of administrative policies for working groups to follow
and the administrative support needed to carry out those policies.</t> and the administrative support needed to carry out those policies.</t>
<section anchor="contributions" numbered="true" toc="default">
<section anchor="contributions" title="Contributions"> <name>Contributions</name>
<t>At a minimum, every repository created in a working group organizatio
<t>At a minimum, every repository created in a working group organization needs n needs to
to
incorporate into its CONTRIBUTING file the boilerplate text at incorporate into its CONTRIBUTING file the boilerplate text at
&lt;https://trustee.ietf.org/license-for-open-source-repositories.html&gt; from the IETF &lt;https://trustee.ietf.org/license-for-open-source-repositories.html&gt; from the IETF
license file for open source repositories. The CONTRIBUTING file can contain oth er license file for open-source repositories. The CONTRIBUTING file can contain oth er
information as well (see information as well (see
&lt;https://github.com/ietf/repo-files/tree/master/contributing-samples&gt; for examples).</t> &lt;https://github.com/ietf/repo-files/tree/master/contributing-samples&gt; for examples).</t>
<t>It would be useful if the user data in the Datatracker could list (at
<t>It would be useful if the user data in the Datatracker could list (at a minim a minimum) the
um) the
GitHub account of the user so that their contributions could be tracked more eas ily.</t> GitHub account of the user so that their contributions could be tracked more eas ily.</t>
<t>Some working groups choose to have more than one draft in a repositor
<t>Some working groups choose to have more than one draft in a repository, parti y, particularly
cularly
for drafts that are tightly linked with significant cross-references. for drafts that are tightly linked with significant cross-references.
In such a case, the README for the repository needs to say that clearly so that In such a case, the README for the repository needs to say so clearly, so that
a participant understands that changes might be made to multiple drafts at once. </t> a participant understands that changes might be made to multiple drafts at once. </t>
</section>
</section> <section anchor="backup" numbered="true" toc="default">
<section anchor="backup" title="Backing Up and Archiving GitHub Content"> <name>Backing Up and Archiving GitHub Content</name>
<t>IETF working group mailing lists are automatically backed up by the I
<t>IETF working group mailing lists are automatically backed up by the IETF Secr ETF Secretariat, and
etariat, and
the archives are publicly available. All official interactions in a WG must be a rchived.</t> the archives are publicly available. All official interactions in a WG must be a rchived.</t>
<t>Working group GitHub content also needs to be backed up and
<t>Working group GitHub content needs to publicly archived. This document specifies using the Git protocol
also be backed up and publicly archived. This document specifies using the git p <xref target="git-protocol" format="default"/> itself for both of these tasks.</
rotocol t>
<xref target="git-protocol"/> itself for both of these tasks.</t> <t>Every IETF working group repository on GitHub will have a mirror repo
sitory of the same
<t>Every IETF working group repository on GitHub will have a mirror repository o
f the same
name on a server maintained by the IETF Secretariat. Every hour, a service will use the name on a server maintained by the IETF Secretariat. Every hour, a service will use the
“git fetch” command on every GitHub repository that is being tracked. The mirror "git fetch" command on every GitHub repository that is being tracked. The mirror
repository will allow anyone to read the repository.</t> repository will allow anyone to read the repository.</t>
<t>Note that this system will not back up GitHub issues or pull requests
<t>Note that this system will not back up GitHub issues or pull requests. .
These should be backed up as well; the GitHub API allows for this. These should be backed up as well; the GitHub API allows for this.
The IETF Secretariat should back up those at the same time as it is backing up t he GitHub The IETF Secretariat should back up those at the same time as it is backing up t he GitHub
repositories.</t> repositories.</t>
<t>The steps in <xref target="repo_create" format="default"/> inform the
<t>The steps in <xref target="repo_create"/> inform the IETF Secretariat which r IETF Secretariat which repositories should be backed up.
epositories should be backed up.
Working group chairs and area directors should also be able to request that the IETF Working group chairs and area directors should also be able to request that the IETF
Secretariat back up additional repositories that are related to IETF working gro ups.</t> Secretariat back up additional repositories that are related to IETF working gro ups.</t>
</section>
</section> </section>
</section> <section anchor="security-considerations" numbered="true" toc="default">
<section anchor="security-considerations" title="Security Considerations"> <name>Security Considerations</name>
<t>An attacker who can change the contents of Internet-Drafts, particularl
<t>An attacker who can change the contents of Internet Drafts, particularly late y late in a working
in a working group's process, can possibly cause unnoticed changes in protocols that are even
group’s process, can possibly cause unnoticed changes in protocols that are even tually
tually
adopted.</t> adopted.</t>
<t>There is a risk of data loss due to centralization of data in one servi
<t>There is a risk of data loss due to centralization of data in one service. ce.
This is recognized, and mitigated by the plan described in <xref target="backup" This is recognized and mitigated by the plan described in <xref target="backup"
/>.</t> format="default"/>.</t>
</section>
</section> <section anchor="iana-considerations" numbered="true" toc="default">
<section anchor="iana-considerations" title="IANA Considerations"> <name>IANA Considerations</name>
<t>This document has no IANA actions.</t>
<t>This document has no IANA actions.</t> </section>
</section>
</middle> </middle>
<back> <back>
<references title='Informative References'> <references>
<name>Informative References</name>
<reference anchor="git-protocol" target="https://git-scm.com/book/en/v2/Git-on-t
he-Server-The-Protocols#The-Git-Protocol">
<front>
<title>Git on the Server - The Protocols</title>
<author >
<organization></organization>
</author>
<date year="n.d."/>
</front>
</reference>
<reference anchor="I-D.ietf-git-using-github">
<front>
<title>Working Group GitHub Usage Guidance</title>
<author initials='M' surname='Thomson' fullname='Martin Thomson'>
<organization />
</author>
<author initials='B' surname='Stark' fullname='Barbara Stark'>
<organization />
</author>
<date month='March' day='19' year='2020' />
<abstract><t>This document provides a set of guidelines for Working Groups that <reference anchor="git-protocol" target="https://git-scm.com/book/en/v2/Gi
choose to use GitHub for their work. Note to Readers Discussion of this docume t-on-the-Server-The-Protocols#The-Git-Protocol">
nt takes place on the GitHub@ietf mailing list (ietf-and-github@ietf.org), which <front>
is archived at https://mailarchive.ietf.org/arch/search?email_list=ietf-and-git <title>Git on the Server - The Protocols</title>
hub. Source for this draft and an issue tracker can be found at https://github. <author surname="Chacon" initials="S">
com/ietf-gitwg/using-github.</t></abstract> <organization/>
</author>
<author surname="Straub" initials="B">
<organization/>
</author>
<date>2014</date>
</front>
<seriesInfo name="in" value="Pro Git" />
</reference>
</front> <reference anchor="RFC8874" target="https://www.rfc-editor.org/info/rfc8874">
<front>
<title>Working Group GitHub Usage Guidance</title>
<seriesInfo name='Internet-Draft' value='draft-ietf-git-using-github-06' /> <author initials="M" surname="Thomson" fullname="M. Thomson">
<format type='TXT' <organization />
target='http://www.ietf.org/internet-drafts/draft-ietf-git-using-github- </author>
06.txt' /> <author initials="B" surname="Stark" fullname="B. Stark">
</reference> <organization />
</author>
<date month="August" year="2020" />
</front>
<seriesInfo name="RFC" value="8874" />
<seriesInfo name="DOI" value="10.17487/RFC8874"/>
</reference>
</references> </references>
</back> </back>
<!-- ##markdown-source:
H4sIAC2wlF4AA51a748btxH9zr+CsIE0BiRd6qRAe/7QXM6uc4DjGLYDfyiK
gNqlJPZ2yc1yV4ps+H/vmyG5S0o6J2jRFmeJv2b45s2boZbLpahdZVWrr2Xd
q82wNHrYLLdmoP/txvXysF1Wzm7MduzVYJwVgxkajP7g+ntjt/Jl78ZOvjTD
j+Na3tStscYPcahar3u9x9iXxQBRqUFvXX+8lsZunBCm66/l0I9+ePrNN//4
5qlQvVbX8qW2uleNOGCrLW2Dj+7elzuLe33E9/W1vLOD7q0els/JDiH8oGz9
q2qcxWmP2ovOXMt/D65aSO/6odcbj7+OLf3xHyHUOOxcfy3kUkj8x1h/LW9W
8ta5Tvf8UfDSTWO8V/nnrt8qaz6yydfy1vjK8ee6Vaa5lqqpMPb7ij5fVa4V
xRZvVvJHt9m0ymZ7vFFjU3xcbnF3e/P6db5Fh/GrXRj/vamUtSvMgF/h3b7F
rL2GYZJutesdXOCaa54f7/IRbkc6K4edlu90v9e9XMr3+MebONo/CsNVv9UD
xu+GofPXV1e0oq9aMutq7dz9lbZX+6dXWG7p7BLLLcNySyy2nBZ7TP+iMemT
R0Isl0up1oScCndHe49eS7dJwDFW3r14/y95iJfPeJCwptLeay8N/msrwMbj
2xUWwAdA9thqO8ha+6o3awwbaSxwIYHpPb6CP72Ek9K6gtf18rAz1U4ChjTQ
m1r3tCkg1Q/0x+D4eOFsK3mHLRwWtm4QuIIa8MYmx/l4C94zjZG9/m00tPZO
2S0+w3Lk+mm4wOK1XB9lNfY9GUCzN+MwYk7hgLDc6DkcwmGCK1tT140W4jGF
Re/qseKAFD/Rsc4dGXzSkXWV6ZQdvGzV/YU7qM1mo/lIB3XELM+TMEbAABPc
SEjiLZL//Uq+cy1Wwpjes1cNBav2A8zEqju1Z69OS8wHE7OfyU0bVZnGDORg
8lit97pxHV8yzlmCY9p+IdfjQOOPtLcY7Ua1WEVhL3Cc3LkDLQ1khwvGmQCI
NFyOtmo0xqq1wyoBGDl66FSuadxhJWYrT93Ljuxl1yibwBPGVa7Woted82YA
I0qPeDFAgfQjAdCT7a/Umu/nBzOsx+peD4t4DPhNi/lKgB9w0mAIUUDWjIgy
GnynK7OhUQrbseNUxtv7DIgXQyWHT4qXaJPZBL9VO+fwT0VblJdSRM75jcb7
XzH7xINWKuxtiKByQ+h2CP81Yqmia1PDqd9xXGNrszf1qBp2C08TqgFV1Mci
dOg0tZvNW4H+wEZ8G3uFu1Gtw2D9OxxFs84jSHgGADuhnY7HDAKoU9AQ3gi4
uU/p2hwFPPAAMuYzwsyNsTr4YeuQBMOqf+gTEygBpiSSGa2hLGCGI41OjNJF
02JsOLHTTXdqUh4ShaewkMIGe6MP5HaAZK8aQ7xXEzEQDsC52L1eEQfdlPB6
E+DF825nR0Sces1clcPUPgDQM3jCbD92HdK7YC/jknktGgdiVludqCIakifW
IhHkvEiWN3qZfDyHKx2OXRF9TLZH6A66Iw49yjVYChKEtgcEmyPROp2NYfZO
44hwsMGVu15w7MRJ0COuJYeCPLUWXzXDsyzrQplx0u1BA141H6+CbNstKdF1
g/9qOzxjRD4wr+VEBsXTemevzLJeDroFOw2aZ+aO0L8rfANLiSfCoVgGRpjC
fo58XBiBv3Qfbv/uFKFk/G8juJ8uhkh7p5kJZ9LxOzc2NTkhOI2ieHIH9hS1
bpDNgQUNfzZ6gxRoE1zqBd1XxWxCFETJhs5Pewcw1PC4SWRw8Sro0t87KBX5
XivcqmkaILBGwiKLfnJ+iEFegG+NVHTgDaGkD1ZuetfKT5/+ebd8vppUNYdR
1NafP1N0PJa3CaYzLn8ucPnpcULy54fJPJmD/Qk+iViPgSOilc8VnIDQv4d2
/TrHRj1/wYclAXlFWHgScjVW0xReqmEjLdmpIvPiek4VFEkbcHmkIVy2LOKR
oHQpBBl4KgqRsVEnq0Jp1ZqCaBEwNZl4YMCorqNEvUZmzZQJ71wmIRwOnMaS
7pc7gaEHTTfsLwztwBkYhIv6sNP2S4bL3HBST545MlrvgvF6slvkdi945yAj
aKnEb4cUCCC/wRD8r4X46yogRn/Bh2eGwICnK/ka5QV/V0yA4YxPlHoEicOW
qhC6eyG+hct568Z8vDATXEY8jwlDFHCXg4m+KPzmRURlcci/+DAKB3IH1H4Q
jnfh/hB6HaXRdaPlzfPLJnLSRMwJZYO2orUWIS4wh6OYIsOGxWW8d3jmuy9b
yVlbyYG4gFfbkbCZMxJhtqL7Iu7HIYZEGiKm/gdRaPqQYcovfPQeYI5ESsmD
NQdxz80GuD0/ITYN8KoDkn55+2ryUWlKAhToDFwaCg9xegkM+nhBGWNg/3ec
177lQ39Hkngf6PU4s2mSCDXxIovRaH1xkHC/nKIKT4by4N7i+5V8qyuU9rnu
mBc9P5782p8kSvpiNRCRz5zG/+R0Wa+vwDKQ01dP//bd3wPXBf8UmtTwtWoB
aY1cmSI6wf2Cd60Onl2z/OOcFIXxRd8IKsmiizrtkKpkq5Ud4hLRUYSx0k8H
HfWl2iOdKURGyCY/mW0/s6yVL5JezXMK8vLmTJsnUczwtrIkKDPM4EHC34xN
PCDtLPAnF4xm4KIkSFUim0x1UVRbHVchaclxtXXBlTjBlrWxCNoJ9/vp05T2
PtMdsOAoT7J1rs7OwQlntFF+MUzFdykRz4tBqsx4pTI0+Z808T7D1yxHF6kg
iziwuknl+yJUvZPJJIBVEJOlvOQt+dpisNJyk25h+W9suMQ30ya3YZOYf0J+
pxA5O0aKCGbQS/xI1EBVWRqfnAg9u2lCARWXuJBVqKVCW8/ajFLhulAYeSyS
EmfLZmag5oW+dPJgctlQvG0cKaWUds+ZvmqoZgp0FwmXWLqsEwItz3DpdQvG
4oqFC4SQCBqi6GzMMPZ2IsezXJYqqJvnXkYIDSaUfVU4NPuqZAY/ti2XkDEZ
FiUEnTy68DJZj10orVCmUTVbBWJSc08DPCAbFKcwZrQ1/j9rjKzEK4zvg6cy
g6u4ekWy/b9jlGiZtQtCUWu2u4Faa81Ypw6OqAhHNlUyZRETRcC7l+fa9nkS
rW/nfsenx+SKX0NAsLpNAG+JF+fmhq+0xR5uKvrmljS162gWiCEct6AobpLM
hQsdEREPtjB+R1AoEXPa7Lh0UR9eFuLNT9wAcSalXEajgVaFZHCQWXuH9a3N
ehKh6y6/jkiqjSdnRofRJx9eBqHw5NmfXTzS+FLVruOCvOyK0X5prZgraDE7
Nzam4iJbG0WAS+fJjQ9V5h+djMEK16Lwgl/bsRkM5Tk+C8saH7wC27lOa5jB
FyeV45+vdfIy54HypZBvIVNeFsFlTM4VTdlh4IrmxOoprjkwzqqc0FaYzAsq
Y25u8XtEXgKwaOBMgexSoVaA/ApaIPQcsp0t56E0k5JqgBl9XhRRxaxpQoou
Ak/Qvv5eN3qg4pnX2ZhGL1CGbxSuUt7+/Pr927sffnl/9/rlQr66u33x+t2L
0PJ+++Lm+U8veHxsghMKjB3d6LmwTFoltm2Q3S07do9USE79v/oXK4H8yU0v
lhaUxQGnVCVGKqi4GxOeSC5XLhFlmJ43aDkBCnhpTfiqJQknPz0x1EG40Hdj
lwr8VzGw3uqGefxtRirhseO0OE95NuAVZNZzcwuqHeRt733AYUZNXxOmYt6m
iAwV0IXG8hPJmaXQBQl04YZoNy4BEJk3ZYJjZxx6M0yO3QD//CwBH1xIPdT9
KxN7bP4J8eXOyMwWRImj9xklZh1v50NNyK8RobsrTqosZfOOc0rADT1lSTu2
a83hX4NaPLO+8t5VJrQyCfw1C1TvVg+2J4EEb6qHeumuMRUNu9BcnJ4OxFQk
l5NjVHBJERRJpXpcpuP3DBJzafmYbeE0oHCM/VTcnpK0YDu2C4l7wdQMEkmF
mnOBVdAV7e6D+EA91hHp6JAQzOCL6OdAZ0PWDn/1HJGQZ7/jIMNJaQbFofVc
l8EMbb1ewk1L12m79G7sK73MUb7aDW0TGpQk6VPQijg37M66GwvIsEARJoEo
z09MIImACxpnfjoN/RFuEJ3VlxkhkR1XtNWSuQ72aQ2Wgo39VTXdCgDuQzd1
arOm9uoT6pWe11ixcOSYpB7dJa0dlByLOtIR05U/YeZPwK8wzE6VDi+YlUGm
l1UOnkkeyrBLLVuHMKf31eZIjYDzZm969YmaK0zghygq+0LiiA8HCYKLrNXX
HAX5I2iC6aUG1ANFR21e0F4KSeo48SMI7Kl6cABQwoxQUSDc2ajHcK1ehyyX
8lDUp3mqjOBG7ZZ0Cj33YcfoHaHyh9FAcvzbgnjIVE5N0rNVNTvhROZQseBw
whCpP8Cp3H/smJJu+mpn9lmngyKZGO7T45hKgI7z9296/qd/0d2HzkmZ3eYU
9cCrw2IqhRSfQIdVuhHyuMICc29B3iAC3AZeN5BnLKpUNT1CKdKFLRUR62kp
evv5UBw32lZF2ybXC9V4ruGzlErv0dMp0oLyoeZ3eJ0iOxCTMv3IATkm/80D
sgoISzcbxgG3iUM0EGiVvycSfcEkecHVGWRceloNPUUGOwVd37si5aYnO4gu
wYqMuIQTsaYOsWG+CQ/9l+5mJcNhoARQvamUwcOmlNIouh+RvRs9VLtH8GtL
vz6gbQLXx1OeCnFDbxXsrxDagRXD+UWhX6krHhXzkYKYVYc6KWGJDl67uSSl
JHkE8cWHE2pR0b3KGQDG+1FzT6sbMSIKas91s897DIXEIg5+lvcnbt7cheP5
GNgmLHGu5NKK8RghdcaSi3s2LHCoDx68E4OTh6btime/VZBtWasqL2M/f1FW
hrf7Qr1dsHh1EjtZt7jspM9S0Zd9sOnhJXvmEvlBkjugKg1FsmrKU00c3Efd
OrhLvx3hJ16sO/ZUgd3G38uopEGA+WEIieqwcyHVMmWmBzTiAm4Sp19wSf4F
ly+Tg2yC6pilipja1UFSLnjtKAmhbhTFyGipB1vh8FmbLBFCZqKmqp8faEWs
m1epGWH4Icf4e9aJlIMb7CHrkd0M5YEwaqa+9mZK0xQwMWajduRKonJIXh+p
dcWv0vD8lp0bWYB/IvJwNUG/6Ll5fXPm5pIYqYNrXRgZWTr+MIiWwir/A/Aa
Hh35JwAA
</rfc> </rfc>
 End of changes. 52 change blocks. 
331 lines changed or deleted 203 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/