rfc9120xml2.original.xml   rfc9120.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.37 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]> ]>
<?rfc toc="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
<?rfc tocdepth="4"?> -iab-arpa-authoritative-servers-01" number="9120" updates="3172" obsoletes="" su
<?rfc sortrefs="yes"?> bmissionType="IAB" category="info" consensus="true" xml:lang="en" tocInclude="tr
<?rfc symrefs="yes"?> ue" tocDepth="4" sortRefs="true" symRefs="true" version="3">
<rfc ipr="trust200902" docName="draft-iab-arpa-authoritative-servers-01" categor
y="info" updates="3172">
<!-- xml2rfc v2v3 conversion 3.9.1 -->
<front> <front>
<title abbrev="Nameservers for the .arpa Domain">Nameservers for the Address and Routing Parameter Area ("arpa") Domain</title> <title abbrev="Nameservers for the .arpa Domain">Nameservers for the Address and Routing Parameter Area ("arpa") Domain</title>
<seriesInfo name="RFC" value="9120"/>
<author initials="K." surname="Davies" fullname="Kim Davies"> <author initials="K." surname="Davies" fullname="Kim Davies">
<organization abbrev="IANA">Internet Assigned Numbers Authority</organizat ion> <organization showOnFrontPage="false">Internet Assigned Numbers Authority</organ ization>
<address> <address>
<postal> <postal>
<street>PTI/ICANN</street> <street>12025 Waterfront Drive</street> <street>PTI/ICANN</street>
<street>12025 Waterfront Drive</street>
<city>Los Angeles</city> <city>Los Angeles</city>
<region>CA</region>
<code>90094</code> <code>90094</code>
<country>United States of America</country> <country>United States of America</country>
</postal> </postal>
<email>kim.davies@iana.org</email> <email>kim.davies@iana.org</email>
</address> </address>
</author> </author>
<author initials="J." surname="Arkko" fullname="Jari Arkko"> <author initials="J." surname="Arkko" fullname="Jari Arkko">
<organization abbrev="Ericsson">Ericsson Research</organization> <organization showOnFrontPage="false">Ericsson Research</organization>
<address> <address>
<postal> <postal>
<street>02700 Kauniainen</street> <street>02700 Kauniainen</street>
<country>Finland</country> <country>Finland</country>
</postal> </postal>
<email>jari.arkko@ericsson.com</email> <email>jari.arkko@ericsson.com</email>
</address> </address>
</author> </author>
<date year="2021" month="October"/>
<date year="2021" month="July" day="12"/> <keyword>root zone</keyword>
<keyword>IANA</keyword>
<keyword>Internet-Draft</keyword> <keyword>top-level domain</keyword>
<keyword>root nameservers</keyword>
<keyword>DNS</keyword>
<keyword>ARPA</keyword>
<abstract> <abstract>
<t>This document describes revisions to operational practices to separate
<t>This document describes revisions to operational practices to separate the function of the "arpa" top-level domain in the DNS from its historical
function of the “arpa” top-level domain in the DNS from its historical
operation alongside the DNS root zone.</t> operation alongside the DNS root zone.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction" numbered="true" toc="default">
<section anchor="introduction" title="Introduction"> <name>Introduction</name>
<t>The "arpa" top-level domain <xref target="RFC3172" format="default"/> i
<t>The “arpa” top-level domain <xref target="RFC3172"/> is designated as an s designated as an
“infrastructure domain” to support techniques defined by Internet "infrastructure domain" to support techniques defined by Internet
standards. Zones under the “arpa” domain provide various mappings, such standards. Zones under the "arpa" domain provide various mappings, such
as IP addresses to domain names and E.164 numbers to URIs. It also as IP addresses to domain names and E.164 numbers to URIs. It also
contains special use names such as “home”, which is a non-unique name contains special-use names such as "home", which is a nonunique name
used in residential networks.</t> used in residential networks.</t>
<t>Historically, the “arpa” zone has been hosted on almost all of the <t>Historically, the "arpa" zone has been hosted on almost all of the
root nameservers, and <xref target="RFC3172"/> envisages the “arpa” domain to be root nameservers (NSs), and <xref target="RFC3172" format="default"/> envisages
“sufficiently critical that the operational requirements for the root the "arpa" domain to be
nameservers apply to the operational requirements of the “arpa” servers”. To "sufficiently critical that the operational requirements for the root
date, this has been implemented by serving the “arpa” domain directly on servers apply to the operational requirements of the "arpa" servers". To
date, this has been implemented by serving the "arpa" domain directly on
a subset of the root server infrastructure.</t> a subset of the root server infrastructure.</t>
<t>This bundling of root nameserver and "arpa" nameserver operations has e
<t>This bundling of root nameserver and “arpa” nameserver operations has entwine ntwined
d management of the zones' contents and their infrastructures. As a result,
management of the zones’ contents and their infrastructure. As a result, some proposals under consideration by the IETF involving the "arpa" zone
some proposals under consideration by the IETF involving the “arpa” zone
have been discarded due to the risk of conflict with operations associated have been discarded due to the risk of conflict with operations associated
with managing the content of the root zone, or administering the root with managing the content of the root zone or administering the root
nameservers.</t> nameservers.</t>
<t>The separation described in this document resolves the operational impa
<t>The separation described in this document resolves operational impacts cts
of synchronizing edits to the root zone and the “arpa” zone by of synchronizing edits to the root zone and the "arpa" zone by
eliminating the current dependency and allowing more tailored operations eliminating the current dependency and allowing more tailored operations
based on the unique requirements of each zone.</t> based on the unique requirements of each zone.</t>
</section>
</section> <section anchor="requirements-for-the-arpa-zone" numbered="true" toc="defaul
<section anchor="requirements-for-the-arpa-zone" title="Requirements for the “ar t">
pa” zone"> <name>Requirements for the "arpa" Zone</name>
<t>The "arpa" domain continues to play a role in critical Internet
<t>The “arpa” domain continues to play a role in critical Internet
operations, and this change does not propose weakening operational operations, and this change does not propose weakening operational
requirements described in <xref target="RFC3172"/> for the domain. Future operat requirements described in <xref target="RFC3172" format="default"/> for the doma
ional in. Future operational
requirements for the “arpa” domain are encouraged to follow strong requirements for the "arpa" domain are encouraged to follow strong
baseline requirements such as those documented in <xref target="RFC7720"/>.</t> baseline requirements such as those documented in <xref target="RFC7720" format=
"default"/>.</t>
<t>Changes to the administration of the “arpa” zone do not alter the <t>Changes to the administration of the "arpa" zone do not alter the
management practices of other zones delegated within the “arpa” management practices of other zones delegated within the "arpa"
namespace. For example, “ip6.arpa” would continue to be managed in namespace. For example, "ip6.arpa" would continue to be managed in
accordance with <xref target="RFC5855"/>.</t> accordance with <xref target="RFC5855" format="default"/>.</t>
</section>
</section> <section anchor="transition-process" numbered="true" toc="default">
<section anchor="transition-process" title="Transition Process"> <name>Transition Process</name>
<t>The process will dedicate new hostnames to the servers that are authori
<t>The process will dedicate new hostnames to the servers authoritative for tative for
the “arpa” zone, but will initially serve the “arpa” zone from the same the "arpa" zone, but it will initially serve the "arpa" zone from the same
hosts.</t> hosts.</t>
<t>Once completed, subsequent transitional phases could include using
<t>Once completed, subsequent transitional phases could include using new hosts to replace or augment the existing root nameserver hosts and
new hosts to replace or augment the existing root nameserver hosts, and separating the editing and distribution of the "arpa" zone from
separation of the editing and distribution of the “arpa” zone from
necessarily being connected to the root zone. Any future management necessarily being connected to the root zone. Any future management
considerations regarding how such changes may be performed are beyond considerations regarding how such changes may be performed are beyond
the scope of this document.</t> the scope of this document.</t>
<section anchor="dedicated-nameserver-hostnames" numbered="true" toc="defa
<section anchor="dedicated-nameserver-hostnames" title="Dedicated nameserver hos ult">
tnames"> <name>Dedicated Nameserver Hostnames</name>
<t>Consistent with the use of the "arpa" namespace itself to host namese
<t>Consistent with the use of the “arpa” namespace itself to host name rvers for other delegations in the "arpa" zone <xref target="RFC5855" format="de
servers for other delegations in the “arpa” zone (<xref target="RFC5855"/>), thi fault"/>, this
s document specifies a new namespace of "ns.arpa", with the
document specifies a new namespace of “ns.arpa”, with the nameserver set for the "arpa" zone to be initially labeled as follows:</t>
nameserver set for the “arpa” zone to be initially labelled as follows:</t> <artwork name="" type="" align="left" alt=""><![CDATA[
<figure><artwork><![CDATA[
a.ns.arpa a.ns.arpa
b.ns.arpa b.ns.arpa
c.ns.arpa c.ns.arpa
... ...
]]></artwork></figure> ]]></artwork>
<t>Dedicated hostnames eliminate a logical dependency that requires the
<t>Dedicated hostnames eliminate a logical dependency that requires the coordinated editing of the nameservers for the "arpa" zone and the root
coordinated editing of the nameservers for the “arpa” zone and the root zone. This component of this transition does not require that the underlying
zone. This component of this transition does not require the underlying hosts that provide "arpa" name service (that is, the root nameservers) be
hosts that provide “arpa” name service (that is, the root nameservers) be altered. The "arpa" zone will initially map the new hostnames to the
altered. The “arpa” zone will initially map the new hostnames to the
same IP addresses that already provide service under the respective same IP addresses that already provide service under the respective
hostnames within root-servers.net.</t> hostnames within "root-servers.net".</t>
<t>Because these nameservers are completely within the "arpa" zone, they
<t>Because these nameservers are completely within the “arpa” zone, they
will require glue records in the root zone. This is consistent with will require glue records in the root zone. This is consistent with
current practice and requires no operational changes to the root zone.</t> current practice and requires no operational changes to the root zone.</t>
</section>
</section> <section anchor="separation-of-infrastructure" numbered="true" toc="defaul
<section anchor="separation-of-infrastructure" title="Separation of infrastructu t">
re"> <name>Separation of Infrastructure</name>
<t>After initially migrating the "arpa" zone to use hostnames that are n
<t>After initially migrating the “arpa” zone to use hostnames that are not share ot shared
d
with the root zone, the underlying name service is expected to evolve such that with the root zone, the underlying name service is expected to evolve such that
it no longer directly aligns to a subset of root nameserver instances. With no it no longer directly aligns with a subset of root nameserver instances. With no
shared infrastructure between the root nameservers and the “arpa” nameservers, f shared infrastructure between the root nameservers and the "arpa" nameservers, f
uture uture
novel applications for the “arpa” zone may be possible.</t> novel applications for the "arpa" zone may be possible.</t>
<t>Any subsequent change to the parties providing name service for the
<t>Any subsequent changes to the parties providing name service for the zone is considered a normal management responsibility and would be
zone is considered a normal management responsibility, and would be performed in accordance with <xref target="RFC3172" format="default"/>.</t>
performed in accordance with <xref target="RFC3172"/>.</t> </section>
<section anchor="zone-administration" numbered="true" toc="default">
</section> <name>Zone Administration</name>
<section anchor="zone-administration" title="Zone administration"> <t>Publication of the "arpa" zone file to the authoritative "arpa" names
ervers is currently undertaken alongside the root zone maintenance functions.
<t>Publication of the “arpa” zone file to the authoritative “arpa” name Upon the separation of the "arpa" infrastructure from the root nameserver
servers is currently undertaken alongside the root zone maintenance functions. infrastructure, publication of the "arpa" zone no longer necessarily needs
Upon the separation of the “arpa” infrastructure from the root nameserver to be technically linked or interrelated to the root zone publication
infrastructure, publication of the “arpa” zone no longer necessarily needs
to be technically linked or inter-related to the root zone publication
mechanisms.</t> mechanisms.</t>
</section>
</section> <section anchor="conclusion-of-process" numbered="true" toc="default">
<section anchor="conclusion-of-process" title="Conclusion of process"> <name>Conclusion of Process</name>
<t>Full technical separation of operations of the "arpa" zone and root z
<t>Full technical separation of operations of the “arpa” zone and root zone one
minimally requires the following to be satisfied:</t> minimally requires the following to be satisfied:</t>
<ul spacing="normal">
<t><list style="symbols"> <li>The "arpa" zone no longer shares any hostnames in its nameserver s
<t>The “arpa” zone no longer shares any hostnames in its NS-set with the root et with the root
zone;</t> zone.</li>
<t>The hosts that provide authoritative name service are not the same hosts <li>The hosts that provide authoritative name service are not the same
hosts
as the root nameservers, do not share any IPv4 or IPv6 addresses with the as the root nameservers, do not share any IPv4 or IPv6 addresses with the
root servers, and are sufficiently separately provisioned such root servers, and are sufficiently provisioned separately such
that any unique “arpa” zone requirements can be deployed without affecting that any unique "arpa" zone requirements can be deployed without affecting
how root zone service is provided;</t> how root zone service is provided.</li>
<t>The editorial and publication process for the “arpa” zone has any common <li>The editorial and publication process for the "arpa" zone removes any common
dependencies with the root zone process removed, so that the “arpa” zone dependencies with the root zone process so that the "arpa" zone
can be managed, edited and provisioned wholly independently of the can be managed, edited, and provisioned wholly independently of the
root zone.</t> root zone.</li>
</list></t> </ul>
<t>Such separation is ultimately sought to allow for novel uses of
<t>Such separation is ultimately sought to allow for novel uses of the "arpa" zone without the risk of inadvertently impacting root zone and root
the “arpa” zone without the risk of inadvertantly impacting root zone and root
server operations. It is recognized that achieving this state requires a server operations. It is recognized that achieving this state requires a
deliberative process involving significant coordination to ensure impacts deliberative process involving significant coordination to ensure impacts
are minimized.</t> are minimized.</t>
</section>
</section>
<section anchor="iana-considerations" numbered="true" toc="default">
<name>IANA Considerations</name>
</section> <t>IANA shall coordinate the creation of the "ns.arpa" namespace and
</section>
<section anchor="iana-considerations" title="IANA Considerations">
<t>The IANA shall coordinate the creation of the “ns.arpa” namespace and
populate it with address records that reflect the IP addresses of the populate it with address records that reflect the IP addresses of the
contemporary root servers documented within “root-servers.net” as its contemporary root servers documented within "root-servers.net" as its
initial state. The namespace may either be provisioned directly within initial state. The namespace may be provisioned either directly within
the “arpa” zone (as an empty non-terminal), or through establishing the "arpa" zone (as an empty nonterminal) or through establishing
a dedicated “ns.arpa” zone, according to operational requirements.</t> a dedicated "ns.arpa" zone, according to operational requirements.</t>
<t>IANA will initially migrate the 12 NS records for the "arpa" zone
<t>The IANA will initially migrate the 12 NS records for the “arpa” zone to point to their respective new entries in the "ns.arpa" domain.</t>
to point to their respective new entries in the “ns.arpa” domain.</t> <t>When these actions are complete, the IAB and IANA will consult
and coordinate with all relevant parties on activity to reduce
<t>Subsequently, the IAB and IANA will consult and coordinate with all relevant or eliminate reliance upon the root zone and root server
parties on activity to reduce or eliminate reliance upon root zone infrastructure serving the "arpa" zone. Such
and root server infrastructure for serving the “arpa” zone. Such changes will be performed in compliance with <xref target="RFC3172" format="defa
changes will be performed in compliance with <xref target="RFC3172"/> and shall ult"/> and shall be
be conducted with all due care and deliberation to mitigate potential conducted with all due care and deliberation to mitigate potential
impacts on critical infrastructure.</t> impacts on critical infrastructure.</t>
</section>
</section> <section anchor="security-considerations" numbered="true" toc="default">
<section anchor="security-considerations" title="Security Considerations"> <name>Security Considerations</name>
<t>The security of the "arpa" zone is not necessarily impacted by any
<t>The security of the “arpa” zone is not necessarily impacted by any
aspects of these changes. Robust practices associated with administering aspects of these changes. Robust practices associated with administering
the content of the zone (including signing the zone with DNSSEC) as well the content of the zone (including signing the zone with DNSSEC) as well
as its distribution will continue to be necessary.</t> as its distribution will continue to be necessary.</t>
</section>
</section>
</middle> </middle>
<back> <back>
<references>
<references title='Normative References'> <name>References</name>
<references>
<reference anchor='RFC3172' target='https://www.rfc-editor.org/info/rfc3172'> <name>Normative References</name>
<front> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<title>Management Guidelines &amp; Operational Requirements for the Address and FC.3172.xml"/>
Routing Parameter Area Domain (&quot;arpa&quot;)</title> </references>
<author fullname='G. Huston' initials='G.' role='editor' surname='Huston'><organ <references>
ization/></author> <name>Informative References</name>
<date month='September' year='2001'/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<abstract><t>This memo describes the management and operational requirements for FC.5855.xml"/>
the address and routing parameter area (&quot;arpa&quot;) domain. This documen <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
t specifies an Internet Best Current Practices for the Internet Community, and r FC.7720.xml"/>
equests discussion and suggestions for improvements.</t></abstract> </references>
</front>
<seriesInfo name='BCP' value='52'/>
<seriesInfo name='RFC' value='3172'/>
<seriesInfo name='DOI' value='10.17487/RFC3172'/>
</reference>
</references>
<references title='Informative References'>
<reference anchor='RFC5855' target='https://www.rfc-editor.org/info/rfc5855'>
<front>
<title>Nameservers for IPv4 and IPv6 Reverse Zones</title>
<author fullname='J. Abley' initials='J.' surname='Abley'><organization/></autho
r>
<author fullname='T. Manderson' initials='T.' surname='Manderson'><organization/
></author>
<date month='May' year='2010'/>
<abstract><t>This document specifies a stable naming scheme for the nameservers
that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS. These zones contain
data that facilitate reverse mapping (address to name). This memo documents an
Internet Best Current Practice.</t></abstract>
</front>
<seriesInfo name='BCP' value='155'/>
<seriesInfo name='RFC' value='5855'/>
<seriesInfo name='DOI' value='10.17487/RFC5855'/>
</reference>
<reference anchor='RFC7720' target='https://www.rfc-editor.org/info/rfc7720'>
<front>
<title>DNS Root Name Service Protocol and Deployment Requirements</title>
<author fullname='M. Blanchet' initials='M.' surname='Blanchet'><organization/><
/author>
<author fullname='L-J. Liman' initials='L-J.' surname='Liman'><organization/></a
uthor>
<date month='December' year='2015'/>
<abstract><t>The DNS root name service is a critical part of the Internet archit
ecture. The protocol and deployment requirements for the DNS root name service
are defined in this document. Operational requirements are out of scope.</t></a
bstract>
</front>
<seriesInfo name='BCP' value='40'/>
<seriesInfo name='RFC' value='7720'/>
<seriesInfo name='DOI' value='10.17487/RFC7720'/>
</reference>
</references> </references>
<section numbered="false" anchor="members" toc="default">
<name>IAB Members at the Time of Approval</name>
<t>Internet Architecture Board members at the time this document was
approved for publication were:</t>
<ul empty="true" indent="3" spacing="compact">
<li><t><contact fullname="Jari Arkko"/></t></li>
<li><t><contact fullname="Deborah Brungard"/></t></li>
<li><t><contact fullname="Ben Campbell"/></t></li>
<li><t><contact fullname="Lars Eggert"/></t></li>
<li><t><contact fullname="Wes Hardaker"/></t></li>
<li><t><contact fullname="Cullen Jennings"/></t></li>
<li><t><contact fullname="Mirja Kühlewind"/></t></li>
<li><t><contact fullname="Zhenbin Li"/></t></li>
<li><t><contact fullname="Jared Mauch"/></t></li>
<li><t><contact fullname="Tommy Pauly"/></t></li>
<li><t><contact fullname="David Schinazi"/></t></li>
<li><t><contact fullname="Russ White"/></t></li>
<li><t><contact fullname="Jiankang Yao"/></t></li>
</ul>
</section>
<section numbered="false" anchor="acknowledgments" toc="default">
<section numbered="false" anchor="acknowledgments" title="Acknowledgments"> <name>Acknowledgments</name>
<t>Thank you <contact fullname="Alissa Cooper"/>, <contact fullname="Miche
<t>Thank you Alyssa Cooper, Michelle Cotton, Lars-Johan Liman, Wes Hardaker, lle Cotton"/>, <contact fullname="Lars-Johan Liman"/>, <contact fullname="Wes Ha
Ted Hardie, Paul Hoffman, Russ Housley, Oscar Robles-Garay, Duane rdaker"/>,
Wessels and Suzanne Woolf for providing review and feedback.</t> <contact fullname="Ted Hardie"/>, <contact fullname="Paul Hoffman"/>, <contact f
ullname="Russ Housley"/>, <contact fullname="Oscar Robles-Garay"/>, <contact ful
</section> lname="Duane Wessels"/>, and <contact fullname="Suzanne Woolf"/> for providing r
eview and feedback.</t>
</section>
</back> </back>
<!-- ##markdown-source:
H4sIAGJy7GAAA31ZXW8bNxZ9568glIdNFpLW8SbNVosF6sZJ47brGnGKAH1Z
UDOUxPWInJIcO0qR/e177iVnhiMrLVDEGnHI+3HOuZdXi8VCRBMbvZLXaq+D
9vfaB7lxXsadlhd17XUIUtlavnddNHYrb5THyqi9vPBayacz5Vs1eyYv3V4Z
K9R67fX96e2WtLRfWLvKYs1K1l5t4sKo9YK+Xqgu7pw3UUVzrxd5i8XZcyFC
hB3/UY2zeCv6TgthWs9/hnh+dvbt2bm4e1jJKwvrrI6LS9pZVCqupLEbJ7q2
VlGHlfz781fnQrRmJaSMrlrJgw7pz1q3cbeSL/ApOB+93oT+23DYlx9FMpS2
WOB/iSPw3U9LeanuDa+QMjn4k9mXD53fjjbKixDM1upaXnf7NQXrIvt/4MV9
OK8uri/4QYBNOq74b/pvIW8+XP3t6vXF9XXx7Pn52flL+RHe+o13NspLj2jy
ggpbr+TPDifZrW6yUZWrYem3COKL/Lmz0WPhr9ZEWHcbKXLSbeTFXntTKV6l
kclmJe/Mflmzg98ZZdUSHk6j8uMSYLm7c0VQflTeFA85KG+wcQjOyveAjvLV
bhKC/tuvhOHs/NXZmfxJddYAXtpO3XhrbAP0lFb/FxYAkbDgO523XlZuL3iN
sM7vGYJ0xvu3rwkyK0Ewmj5/+Y+XL/Ofr16dn9GfQiwWC5gNG1UVhfiwM0EC
7t1eIxO1DpU3awQTXplgnA0AnnSt9tjXWdXIlt4zleYvgm7BuKjFprMVLaAk
EJsS8bCkXTT6Xjc4goiFiPPXl9e3ErnfSxODhAXRUdoaMRwkiUnbYGo9rPfO
RfkZ/FomH/amrhvQ7Anh1bu6YwPIo68f/8cfOVpfvkjyWxO+FWFIkZCIGWLo
FWKDzTqv82szdrVrW5BORl3trPm90/T6xhA71oeBMkkHlK/DUv4GW4PsbK19
GZNsSuvdPbl3j0y7Lsi9altIWJjjJIAL9lzdSJU0LgU7v0gQTar3Zvn8mxfS
Zm5ixa/vr3DuVUT0ghMVuIUXggytrgxS1wWd36YjyOXZzu31bC4fdgYPEBEl
rbOLjh3ktQIv1ZQ22AFzbaSN4OiD83cBmXg3JK85zEs3KVNyhzPWWlu5c4Gi
zInd42/802SsCE6sHSV5zs6VqdIWYFRbCsOjOMLttRaz0G02pjIwsDlIYDiS
SViuIr9TItjr3zvjNQF+lH8yQhRGSKQDO2H3P319Cvf87mwpPzhBck4RQVSH
MJh92/CbCTW0nsrWY69qnFCRK0C0QrrWAXKcD+N4paPkFK/LzOc1QNfQxnjj
KLoc23xW8XRwMBkLCx8I2mIPydyyxf3plNfwF0ng4gjQfnhuHtmC6gE4ATZd
E+ciAGiE+dYFgDOzApsQqDLlERA64OrNh7fY6941x7Gho8VO3esUzNqECkxD
KGuANWfKm3BHpmLrTWOqKB9M3JXuKWgp2IAMCP6KPewPyl5NIk2nzlEDQMa9
sYA7BDkvPwbNMqlPVkXyqRfUOilfqbWIDFykulWACwCBvAYBA8LBVjvUR/OZ
jtM1SWXvZG9XH/0J6dYHoRsDW1Uc/Oq8T/reakTeVgd+EyR0D7Rm7yB2EIsG
/9ZFtMRahURb2iXLwjEBtIJ2ZGF+gvJ4gl1lAkuBzminsBvbJZlrG3Ug4LhG
U9AGLg8SO5o3z/4jrNVOoWPAhtjEIjoJalo+aHWnLXNhDLOYuDDJUSk7vfXJ
yqV823FR+OpGR95m5xReQcRd58GkmjzcOIo7tQmocRxikPUorr1Co98KegBN
YSMV9C9fEPLX7PmAjR6lGYBTgWJ81I4jpJqYClNJ8rG640WHL30iPILU6C1X
SmJNLuNp18QA4Bacf4sQ6E+KZG4uZ6b9ZpkOfnBdUw95TqKdqMcuCVVVztfK
VjoRll2k9oVdfCI/eAWpYI9uvIN9IeGoTR/wEuoJpABIiShc+oErTip2OTCD
sJc9POVMHAVoDv2MaUdEkgpek6RaPwol9zC8OZVKOpI04BdyA90agoCAzZN8
gzmIbxz8oFYKUgv7Ko6NsVXToR/oAsAqeg/Yeq/BCWxJGtRtOU90pv6ENBOy
jyWeX2RuiEKKMhJISOglYk5NODHw9itIIfdgCkUYXQqisNb0KtKIhzGBeaJH
EH17kJvEkxFWYiL01FxuIdy01Y54QFCvMor3ik6RoBg1s9SYeZL7g4MzHOgK
9Eu2FmJKGHkiL3P+6+Ng8EcwhawILPAMMta0oI88H9BMzaluNuQkbZLaofLa
mPiRmcGOTXiRYvi0gPKz1A+IoQZwZ7YxmhsvpHw8GzbNbEjsmQ/mFsVGUkdw
Ql8zt0bkNmqtmya1uEl5wkqI/9F/dJtQy3wMfViXH6ryw3K5zO+IMcwjx/qC
A/2RjduyYBfFhvuwrG/cxAERjhDA2/SQzHmwJ27npYN9zePqm1DHXQ8xDp/6
8o0nI9vGwpCtyAUNmGwORLhMNrKz78wLPKRODWl5yitMmI+4L8x9Rq0o66qu
yaip3UeKgoY/uXtCrATpydEFgA5WjdeqPgwm9maNlwysBqZI2sS4aZZsMrcf
WixRScGa73WliAJ4NUwjT7zrNQzWPlL9LJV4cBDsWR/YbcM9Aun5QIhCIDhV
nK0JGUXfovQViNM8QMZOL6HVtOaVV0PowO1E9KZtqRAXm8iN85AHs/Vjp3TE
JIpNkRzOAXwkIIUd/spN5FGzOMXWFEFwXX9qB/nU1OfqpIG0vTCRnKXbL2lL
fw1QDS6q7G95GzgWflz2ItVQXAI/klnWiWTlURAA0/hALfQpEB/3lJObWZJ2
YR1dqumKRErA0neKqb2YuxDMuqHsUHkoyuFRHpG2SGKY4P0odPkI5vwAoZrI
xvdWvwcyil6GqEAr1qYx8ZB6xdSHgKVjgaEW7VT3kZrAhKjfWHcmnZUQN926
d/9k8TTNcCuZ9hxFYId6Qu4kBiDbjJ1IjevRHGRs/Km1BHnY5n74gt7j1zb3
6o8Lfz71CAlDB3MEAzFdN5ftn3s7YrbsF6zWdRCpIqXBSZVqkrF3dK8gyIKN
C68bdaqfKE8Ve01wMWEfUlJQztEyhWxQ27eFbzuI0XDYUSCKi+AJJ1hyhrMF
pXvP9palKxdRFgx2LGDDgCJeo6z+9ZHqj4FhKhK9DoWk0EwMhef6dkGcnogJ
yi7t8E+a2qV9TxSpKbImdOmFqu9P0+vYTYWTxJ/3NwM2lO28url/QVnCv98U
tWhoR2Q5jMjXMXp3Mo3ph4RNrluUMeSax1wya6o99LfLMnaTG1GlLEUbXUXj
Dvke4tCoq82GCp6lsS61k2MCC8nN4aqLYFLXgcgBImR1Ce/+UnFK0nYqZRCl
cc/j3qHLMUVgSgTnzeAGRJNuA24cS5U7Y6/sYr4XzdlEEjeyr4jcw84RKI3t
z+ZB0abMSCqG8PWWCkvBAcSiayJgzfkIrtvuIpcVvpKSx0nbu8B3wOO70RD1
ctaCNq6+J8FiQ9IIY7iXTIglHo2beFxpAjcMW2s+kwgwIqqd0XkAhK8DjfhH
GiqBrhtXdp9g38d4nBrRXBeNNQKKItO3muQ/lVwbSPn6UQvhlZlOh/Nlk37P
kK8nV5Z02+QvwA4IzNi/pgEL+rKJNPa9e9HS032sdW1HUgfSJ7BkUg0NU+6U
Nw0wncZhZROYk8xjKjS7XvnDhIHloCB3bLPjrm9G/IfmiNwCpdimdnU0lkq3
NnzBWesJ+oaeJB3wCCFPmSES9sUDT5Mh8HQ3aJ7xFC3uPIFOahwLyoUdMVcN
d/e6CF1qplJxznL7tUHsskjQcZ/N/V1K0/NzSb8k5Fifmk7RAMoZG3MpMr7o
qLlVx2ne6PGqN1ibp0QClOv7m34kfnXxPVNgNI9aF/CQnxZQSpDgZrrR9wCv
6FsimpyTEehk0kig7tJEYLx54R3D/UBHTcBAPjFUtZMzY47CiUF06tZJPkTf
pbHlk8s5z+5wRzAneyf2juki1jxbpd9oMjLZS5rbVqnW1HJkdKLpHgmkiRPy
EdPvDiJTloIxjAUfTcCp/0crRYE6xeHQf3mi/pt0RSw7mHRkGtdD94ViMPRM
xO0gB2cp37t1F8oJ2jhp7qlezI/FiXFzok8aBA0ilrMyiC/9Fnb75vUzYvED
LvYisXk6y+kxVk7beq8O+feztaruKFoX1Z11D42uebIUxB+r9IuSrv8126gm
6NkXipyyd/LgOnnRHLALQktUnMt/m2pH4wU8iNHZufxZ+bD40WG9/BllBk8+
IhbvFPrrO7wgPiAc9MmA2jeqa+Q7t9nwuvcddPCd60KjwZtfaLhPQW10WPyA
8oVnl50Cnj+SFjbpnnLbfVYWkfnoXLNhKI93B/oJE4SlZRv0oeQvXBf/BxBJ
gaBXIAAA
</rfc> </rfc>
 End of changes. 42 change blocks. 
310 lines changed or deleted 197 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/