rfc9121xml2.original.xml   rfc9121.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.5.24 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]> ]>
<?rfc sortrefs="yes"?> <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.5.24 -->
<?rfc symrefs="yes"?>
<rfc ipr="trust200902" docName="draft-davies-int-historic-05" category="info" up <!-- [rfced] As this document is moving RFCs 1528 and 1706 to Historic, should i
dates="1528, 1706"> t obsolete those RFCs (rather than update them)?
<front>
<title abbrev="Infrastructure .int domains">Deprecating infrastructure "int"
domains</title>
Original:
Updates: 1528, 1706 (if approved)
-->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-davies-int-historic-05" number="9121" submissionType="IETF"
category="info" consensus="true" updates="1706" obsoletes="1528" xml:lang="en"
tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.15.3 -->
<front>
<title abbrev="Infrastructure .int domains">Deprecating Infrastructure "int"
Domains</title>
<seriesInfo name="RFC" value="9121"/>
<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 abbrev="IANA">Internet Assigned Numbers Authority</organizat ion>
<address> <address>
<postal> <postal>
<street>PTI/ICANN</street> <street>12025 Waterfront Drive</street> <extaddr>PTI/ICANN</extaddr>
<street>12025 Waterfront Drive</street>
<city>Los Angeles</city> <city>Los Angeles</city>
<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="A." surname="Baber" fullname="Amanda Baber"> <author initials="A." surname="Baber" fullname="Amanda Baber">
<organization abbrev="IANA">Internet Assigned Numbers Authority</organizat ion> <organization abbrev="IANA">Internet Assigned Numbers Authority</organizat ion>
<address> <address>
<postal> <postal>
<street>PTI/ICANN</street> <street>12025 Waterfront Drive</street> <extaddr>PTI/ICANN</extaddr>
<street>12025 Waterfront Drive</street>
<city>Los Angeles</city> <city>Los Angeles</city>
<code>90094</code> <code>90094</code>
<country>United States of America</country> <country>United States of America</country>
</postal> </postal>
<email>amanda.baber@iana.org</email> <email>amanda.baber@iana.org</email>
</address> </address>
</author> </author>
<date year="2023" month="April"/>
<date year="2022" month="November" day="28"/> <!-- [rfced] Please insert any keywords (beyond those that appear in the title)
for use on https://www.rfc-editor.org/search. -->
<keyword>Internet-Draft</keyword>
<abstract> <abstract>
<t>This document deprecates the use of any "int" domain names that were
<t>The document deprecates the use of any “int” domain names that were designated for infrastructure purposes by the IETF, and it identifies
designated for infrastructure purposes by the IETF, and identifies them for removal from the "int" top-level domain. Any implementations
them for removal from the “int” top-level domain. Any implementation that involve these domains are now deprecated. This
that involves these domains should be considered deprecated. This document also changes the status of RFC 1528 and RFC 1706 to
document also requests moving the status of RFC 1528 and RFC 1706 to Historic.</t>
historic.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="introduction" numbered="true" toc="default">
<section anchor="introduction" title="Introduction"> <name>Introduction</name>
<t>The "int" top-level domain <xref target="RFC1591" format="default"/> is
<t>The “int” top-level domain <xref target="RFC1591"/> is a specialized domain a specialized domain
designated for intergovernmental organizations, which are organizations designated for intergovernmental organizations, which are organizations
established by international treaties between or among national established by international treaties between or among national
governments.</t> governments.</t>
<t>Historically, the "int" domain was also used for purposes related to In
<t>Historically, the “int” domain was also used for Internet infrastructure ternet infrastructure. This practice ended in 2001 when the "arpa" domain was
related purposes. This practice ended in 2001 when the “arpa” domain was
declared the appropriate home for infrastructural identifier spaces declared the appropriate home for infrastructural identifier spaces
<xref target="RFC3172"/>. In conjunction with this change, the eligibility for “ int” <xref target="RFC3172" format="default"/>. In conjunction with this change, the eligibility for "int"
domains was limited to only intergovernmental treaty organizations.</t> domains was limited to only intergovernmental treaty organizations.</t>
<t>The documented uses of infrastructural identifiers in the "int" domain
<t>The documented uses of infrastructural identifiers in the “int” domain were largely experimental and are now, in practice, obsolete. This document
were largely experimental and are now in practice obsolete. This document changes the status of related specifications to Historic, and it
requests moving the related specifications to historic status, along removes any associated delegations from the "int" zone in the
with removing any associated delegations from the “int” zone in the
domain name system.</t> domain name system.</t>
</section>
</section> <section anchor="historical-infrastructural-uses" numbered="true" toc="defau
<section anchor="historical-infrastructural-uses" title="Historical infrastructu lt">
ral uses"> <name>Historical Infrastructural Uses</name>
<t>The following domains were used for infrastructural identifier purposes
<t>The following domains were used for infrastructural identifier purposes
that are now considered historic. Although each of these names was that are now considered historic. Although each of these names was
either delegated or documented at one time, the parties administering either delegated or documented at one time, the parties administering
them have long since stopped using them.</t> them have long since stopped using them.</t>
<section anchor="atmaint" numbered="true" toc="default">
<section anchor="atmaint" title="atma.int"> <name>atma.int</name>
<t>The atma.int domain was experimentally defined to implement address
<t>The atma.int domain was experimentally defined to implement address
lookups for Asynchronous Transfer Mode (ATM), including ATM End System lookups for Asynchronous Transfer Mode (ATM), including ATM End System
Addresses (AESAs). <xref target="ANS"/></t> Addresses (AESAs) <xref target="ANS" format="default"/>.</t>
</section>
</section> <section anchor="ip4int" numbered="true" toc="default">
<section anchor="ip4int" title="ip4.int"> <name>ip4.int</name>
<t>The ip4.int domain was described as providing an alternative to the
<t>The ip4.int domain was described as providing an alternative to
in-addr.arpa domain for mapping host IPv4 addresses to host names. The in-addr.arpa domain for mapping host IPv4 addresses to host names. The
in-addr.arpa domain zone continues to be administered for this purpose in-addr.arpa domain zone continues to be administered for this purpose
<xref target="RFC1035"/>.</t> <xref target="RFC1035" format="default"/>.</t>
</section>
</section> <section anchor="ip6int" numbered="true" toc="default">
<section anchor="ip6int" title="ip6.int"> <name>ip6.int</name>
<t>The ip6.int domain was originally delegated for mapping host IPv6 add
<t>The ip6.int domain was originally delegated for mapping host IPv6 addresses resses
to host names. It was subsequently removed from the “int” zone, having to host names. It was subsequently removed from the "int" zone, having
been replaced by ip6.arpa for this purpose <xref target="RFC4159"/>.</t> been replaced by ip6.arpa <xref target="RFC4159" format="default"/>.</t>
</section>
</section> <section anchor="nsapint" numbered="true" toc="default">
<section anchor="nsapint" title="nsap.int"> <name>nsap.int</name>
<t>The nsap.int domain name was specified to experimentally map Open
<t>The nsap.int domain name was specified to experimentally map Open
Systems Interconnection (OSI) Network Service Access Points to domain Systems Interconnection (OSI) Network Service Access Points to domain
names <xref target="RFC1706"/>.</t> names <xref target="RFC1706" format="default"/>.</t>
</section>
</section> <section anchor="rdiint" numbered="true" toc="default">
<section anchor="rdiint" title="rdi.int"> <name>rdi.int</name>
<t>The rdi.int domain name experimentally mapped OSI Inter-Domain Routin
<t>The rdi.int domain name experimentally mapped OSI Inter-Domain Routing g
Protocol’s Routing Domain Identifiers <xref target="ISO10747"/> to the domain na Protocol's Routing Domain Identifiers <xref target="ISO10747" format="default"/>
me to the domain name
system.</t> system.</t>
</section>
</section> <section anchor="regint" numbered="true" toc="default">
<section anchor="regint" title="reg.int"> <name>reg.int</name>
<t>The reg.int domain name hosted an experimental mechanism for publishi
<t>The reg.int domain name hosted an experimental mechanism for publishing ng
IANA registration values in the domain name system.</t> IANA registration values in the domain name system.</t>
</section>
</section> <section anchor="tpcint" numbered="true" toc="default">
<section anchor="tpcint" title="tpc.int"> <name>tpc.int</name>
<t>The tpc.int domain name hosted an experimental remote printing
<t>The tpc.int domain name hosted an experimental remote printing
service that served as a gateway between Internet mail and facsimile service that served as a gateway between Internet mail and facsimile
transmission <xref target="RFC1528"/>.</t> transmission <xref target="RFC1528" format="default"/>.</t>
</section>
</section> </section>
</section> <section anchor="updates-to-other-rfc-series-documents" numbered="true" toc=
<section anchor="updates-to-other-rfc-series-documents" title="Updates to other "default">
RFC Series documents"> <name>Updates to Other RFC Series Documents</name>
<section anchor="rfc-1528" numbered="true" toc="default">
<section anchor="rfc-1528" title="RFC 1528"> <name>RFC 1528</name>
<t>The specification for tpc.int <xref target="RFC1528" format="default"
<t>The specification for tpc.int <xref target="RFC1528"/> should be deemed histo /> is Historic,
ric
as it no longer functions as described in the document.</t> as it no longer functions as described in the document.</t>
</section>
</section> <section anchor="rfc-1706" numbered="true" toc="default">
<section anchor="rfc-1706" title="RFC 1706"> <name>RFC 1706</name>
<t>The specification for nsap.int <xref target="RFC1706" format="default
<t>The specification for nsap.int <xref target="RFC1706"/> should be deemed hist "/> is Historic,
oric
as it no longer functions as described in the document.</t> as it no longer functions as described in the document.</t>
</section>
</section> </section>
</section> <section anchor="iana-considerations" numbered="true" toc="default">
<section anchor="iana-considerations" title="IANA Considerations"> <name>IANA Considerations</name>
<t>IANA has removed the historical "int"
<t>The IANA shall coordinate the removal of any of the historical “int” domains discussed in this document.</t>
domains discussed in this document that are still delegated in the </section>
“int” zone.</t> <section anchor="security-considerations" numbered="true" toc="default">
<name>Security Considerations</name>
</section> <t>Some old systems might have one or more subdomains of these names
<section anchor="security-considerations" title="Security Considerations">
<t>Some old systems might have one or more subdomains of these names
hardwired and expect a positive response for at least the second-level hardwired and expect a positive response for at least the second-level
domain. This is, of course, true for any name in the DNS and should not domain. This is, of course, true for any name in the DNS and should not
be the sole basis to retain obsolete names.</t> be the sole basis for retaining obsolete names.</t>
<t>Existing applications should eliminate any reliance upon these <t>Existing applications should eliminate any reliance upon these
zones for their historic purpose. The operator of the “int” domain zones. The operator of the "int" domain
should be cautious about any potential re-use of these domains for should be cautious about any potential re-use of these domains for
intergovernmental treaty organizations.</t> intergovernmental treaty organizations.</t>
</section>
</section> <section anchor="additional-information" numbered="true" toc="default">
<section anchor="additional-information" title="Additional Information"> <name>Additional Information</name>
<t>This document is the result of a comprehensive inventory of .int domain
<t>This document is the result of an comprehensive inventory conducted by s
the IANA team of .int domains to accurately establish and record their to accurately establish and record their
purpose based on historical documentation. As part of this inventory, purpose based on historical documentation. As part of this inventory,
the domains delegated for infrastructure identifier related purposes IANA studied the domains delegated for purposes related to infrastructure identi
were studied. Query patterns in the DNS for these domains were analyzed fiers. Query patterns in the DNS for these domains were analyzed
and judged to be insignificant, and preliminary outreach was conducted and judged to be insignificant; preliminary outreach
to the contacts for the associated domains. The assessment concluded to the contacts for the associated domains was conducted. The assessment conclud
that these domains are highly likely to be obsolete and this document is ed
intended to formalize that assessment.</t> that these domains are very likely obsolete. This document formalizes that asses
sment.</t>
<t>There are a small number of existing “int” domains nominally for
“international databases” that are not defined by any standards
documentation, and are assigned to entities rather than for an
identifier purpose. While they would not qualify for a “int” domain
under current criteria, their disposition is beyond the scope of this
memo.</t>
</section>
<t>There are a small number of nominal "int" domains for
"international databases" that are not defined by any standards
documentation. They are assigned to entities rather than for
identifier purposes. Their dispositions are beyond the scope of this
memo.
</t>
</section>
</middle> </middle>
<back> <back>
<references>
<name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.103
5.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.152
8.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.159
1.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.170
6.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.317
2.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.415
9.xml"/>
<references title='Informative References'> <reference anchor="ISO10747" target="https://www.iso.org/standard/21417.ht
ml">
<reference anchor='RFC1035' target='https://www.rfc-editor.org/info/rfc1035'> <front>
<front> <title>Information technology - Telecommunications and information exc
<title>Domain names - implementation and specification</title> hange between systems - Protocol for exchange of inter-domain routeing informati
<author fullname='P. Mockapetris' initials='P.' surname='Mockapetris'><organizat on among intermediate systems to support forwarding of ISO 8473 PDUs
ion/></author> </title>
<date month='November' year='1987'/> <author>
<abstract><t>This RFC is the revised specification of the protocol and format us <organization>ISO/IEC</organization>
ed in the implementation of the Domain Name System. It obsoletes RFC-883. This </author>
memo documents the details of the domain name client - server communication.</t> <date year="1994" month="October"/>
</abstract> </front>
</front> <seriesInfo name="ISO/IEC" value="10747:1994"/>
<seriesInfo name='STD' value='13'/> </reference>
<seriesInfo name='RFC' value='1035'/>
<seriesInfo name='DOI' value='10.17487/RFC1035'/>
</reference>
<reference anchor='RFC1528' target='https://www.rfc-editor.org/info/rfc1528'>
<front>
<title>Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Tec
hnical Procedures</title>
<author fullname='C. Malamud' initials='C.' surname='Malamud'><organization/></a
uthor>
<author fullname='M. Rose' initials='M.' surname='Rose'><organization/></author>
<date month='October' year='1993'/>
<abstract><t>This memo describes a technique for &quot;remote printing&quot; usi
ng the Internet mail infrastructure. In particular, this memo focuses on the ca
se in which remote printers are connected to the international telephone network
. This memo defines an Experimental Protocol for the Internet community. It doe
s not specify an Internet standard.</t></abstract>
</front>
<seriesInfo name='RFC' value='1528'/>
<seriesInfo name='DOI' value='10.17487/RFC1528'/>
</reference>
<reference anchor='RFC1591' target='https://www.rfc-editor.org/info/rfc1591'>
<front>
<title>Domain Name System Structure and Delegation</title>
<author fullname='J. Postel' initials='J.' surname='Postel'><organization/></aut
hor>
<date month='March' year='1994'/>
<abstract><t>This memo provides some information on the structure of the names i
n the Domain Name System (DNS), specifically the top-level domain names; and on
the administration of domains. This memo provides information for the Internet c
ommunity. This memo does not specify an Internet standard of any kind.</t></abs
tract>
</front>
<seriesInfo name='RFC' value='1591'/>
<seriesInfo name='DOI' value='10.17487/RFC1591'/>
</reference>
<reference anchor='RFC1706' target='https://www.rfc-editor.org/info/rfc1706'>
<front>
<title>DNS NSAP Resource Records</title>
<author fullname='B. Manning' initials='B.' surname='Manning'><organization/></a
uthor>
<author fullname='R. Colella' initials='R.' surname='Colella'><organization/></a
uthor>
<date month='October' year='1994'/>
<abstract><t>This document defines the format of one new Resource Record (RR) fo
r the DNS for domain name-to-NSAP mapping. The RR may be used with any NSAP addr
ess format. This memo provides information for the Internet community. This me
mo does not specify an Internet standard of any kind.</t></abstract>
</front>
<seriesInfo name='RFC' value='1706'/>
<seriesInfo name='DOI' value='10.17487/RFC1706'/>
</reference>
<reference anchor='RFC3172' target='https://www.rfc-editor.org/info/rfc3172'>
<front>
<title>Management Guidelines &amp; Operational Requirements for the Address and
Routing Parameter Area Domain (&quot;arpa&quot;)</title>
<author fullname='G. Huston' initials='G.' role='editor' surname='Huston'><organ
ization/></author>
<date month='September' year='2001'/>
<abstract><t>This memo describes the management and operational requirements for
the address and routing parameter area (&quot;arpa&quot;) domain. This documen
t specifies an Internet Best Current Practices for the Internet Community, and r
equests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='52'/>
<seriesInfo name='RFC' value='3172'/>
<seriesInfo name='DOI' value='10.17487/RFC3172'/>
</reference>
<reference anchor='RFC4159' target='https://www.rfc-editor.org/info/rfc4159'>
<front>
<title>Deprecation of &quot;ip6.int&quot;</title>
<author fullname='G. Huston' initials='G.' surname='Huston'><organization/></aut
hor>
<date month='August' year='2005'/>
<abstract><t>This document advises of the deprecation of the use of &quot;ip6.in
t&quot; for Standards Conformant IPv6 implementations. This document specifies
an Internet Best Current Practices for the Internet Community, and requests disc
ussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='109'/>
<seriesInfo name='RFC' value='4159'/>
<seriesInfo name='DOI' value='10.17487/RFC4159'/>
</reference>
<reference anchor="ISO10747" target="https://www.iso.org/standard/21417.html">
<front>
<title>Protocol for exchange of inter-domain routeing information among inte
rmediate systems to support forwarding of ISO 8473 PDUs</title>
<author >
<organization></organization>
</author>
<date year="1994" month="October"/>
</front>
<seriesInfo name="ISO/IEC" value="10747:1994"/>
</reference>
<reference anchor="ANS" target="https://www.broadband-forum.org/technical/downlo
ad/af-saa-0069.000.pdf">
<front>
<title>ATM Name Service Specification Version 1.0</title>
<author >
<organization></organization>
</author>
<date year="1996" month="November"/>
</front>
<seriesInfo name="ATM Forum" value="AF-SAA-0069.000"/>
</reference>
<reference anchor="ANS" target="https://www.broadband-forum.org/technical/
download/af-saa-0069.000.pdf">
<front>
<title>ATM Name System Specification Version 1.0</title>
<author>
<organization>The ATM Forum Technical Committee</organization>
</author>
<date year="1996" month="November"/>
</front>
<seriesInfo name="ATM Forum" value="af-saa-0069.000"/>
</reference>
</references> </references>
<section numbered="false" anchor="acknowledgments" toc="default">
<section numbered="false" anchor="notes-for-removal-before-publication" title="N <name>Acknowledgments</name>
otes (for removal before publication)"> <t>This document was compiled with help from Ted Hardie and Michelle
<t>I-D source is maintained at: https://github.com/kjd/draft-davies-int-historic
</t>
</section>
<section numbered="false" anchor="acknowledgments" title="Acknowledgments">
<t>This document was compiled with help from Ted Hardie and Michelle
Cotton, with additional input from Jari Arkko, John Klensin, Warren Cotton, with additional input from Jari Arkko, John Klensin, Warren
Kumari, Pete Resnick, George Michaelson and Toerless Eckert.</t> Kumari, Pete Resnick, George Michaelson, and Toerless Eckert.</t>
</section>
</section>
</back> </back>
<!-- ##markdown-source:
H4sIAJJdhWMAA91Z0W7bOhJ951cQ6cO2QOTYuWnTBFhgvU26N7e3abZOt48L
WqItNpKoS1Jx3aL/vmeGlCwn6eK+7MsWKGpJFHlm5syZGTXLMhFMqPS5vNCt
07kKpllL06yc8sF1eeiclgemCQeysLUyjRdquXT6/lxe7S+aYFG/RorC5o2q
sW3h1Cpkhbo32mdYkpXGB+tMnk1fCh9UU/xbVbbBSuykhWkd//LheDo9mx6L
uw2dFLRrdMguaDMBkOcE0UrRtYUK2p/L2cvj14dydjp9JVpzLqT01gWnV3i0
1Z6ut/XuUnWhtI6WZfgrsRkevJvIC4bJtyL6d6Ye37RuvUMj596bdaMLed3V
S+28nPO2Jmx58eCn+fWcb8BXWodz/k1/Mnlze3V09WZ+fT26NzueHr+Un2GW
WzkLn144c695QY6tz+XvFic1a10lULktgPQM7jpJ110THBZ+akwAukUgF0m7
kvNaw/GKV2kEqjqXd6aexOD8zahGTWDhvlfmE/l3BetGTpnXiJoa3f7/c4ti
EydLMnHnGOKcq5Ei95rgfnz7Zjb95WX/Ewwcfp7N+p9gZPr5y+z0OP08wQr6
ebX4MJuenpxG41MiHtw4G2xuK4nTpP6alwpmEVBDLs5ijklnu6BTskZUtgFu
y3ewrtaFgYUgvg+69jJY6bu2RVrQvhvlCnoZuwKEfH1y+ou8ufjkDyIS5dYI
iSxDaP350dFms5kYb8kJR5yzePvoeHYyO52Uoa74HUpE5OHZ2Uk2m8bAwq3a
E7w+uDjq6OryDZax1bQYT+bXi30HzG/fy2tQTS60uzc5/m11blYmj0b+C6Si
f2eT6c/hLp1VxRJQM1jb1Qw96LxssEt1VNhNU2HBkVplXqlsOn11NplOp5O2
WO1b8yqbzX5iDeN8S7sfICneZov5fNhIiCzLwHWQW+VBiNtSQxzzrtakkklq
Qb+A+53n6Kpmu6e0nG20QgW50U6LQlNiKSIvMeOBSLeda63HC8st73p1efv2
EJsW0hQ4FO5DYuBBzS87Xdt7BYo5W/PyeHKwbVbpe10lDBNEB7BM3VaaoHMA
BEMyzb2t7qMJXg/K70vbVYVcaiRc43G0A9zB4AIb3qICiMEXqvIWaP7otA9e
AhSxkgCBZ6Hj/ETCsL6zMXyBpAJU0ZeSSfR2bYqi0kI8Iy1ytoBjCC37/mnz
5PfvKV1//JDGSyU9MU1V5huh5jWP3Y7kWtt7iB17pCL5U435xr7xh3JTmryU
CiHZeyBgoFpWxpfYCDHifRp+hj2ggfhJ0dNho3WDd1My90vE7kwPg39Ntquq
2h6OIpgM2ygfXQtyRdyDPu/zRjhdsW09fyYcINkSbyn3dFPgKbZEQZ7BOGDj
05Rr1fg4+CmvFEWbHqu2dbZ1rEClRSo/YiyMHojp4HeVg58cDxLKHz8mQEwc
+tI1HEe5MaHE3sAWFTFarSuzNktToQbwGewF0bOR3FCZmgUfAmibavtEANn5
2/1wTfZzFu93PpaLn1vhyU0PQyEod2VFEoXD9dcWOpLOJT4TTxq7oTcHl9ul
t5UOOoWixyCeSpM+fH4skaz2fXakTIIWoM9aC3Yjpz9tQaKjvLe54V0KlM91
2uKBNHxDk5bsEyOBSvVlQmm34+QjJ5HzokdXtqrshs4egkQOGnj6X0jSUzQK
UO+5kc4MgiDnFXqObl1KrZCMiFpUqSipxFYNN2DLZDDexdGjYGN/sjcgVJFn
rXKcn6qoTYNjEEU4k/W0VPcIMOUqykNOymXblgmTgsTeeYY9a0VdcvRDfzXO
2DE7QJZCr0wTmTsoMAAUTnsvKmvvutazz+Z+2+Ql2iILxbx1qvEr2PYeHZB8
jiL14hBezauOKz4VrUsQb8FxE/O4HSx7Pr9czP2LCUQRFfnHD8Zs2pMd5HQx
RgxxzJ1ZksdIM0CqItIKbEv6BudAq02TEfIJyUa/AUGvoRT0Rml9kFc39ye9
gTqSmG5z1CgZ9JPbMDPBAowuXXwL1WcXp8QrVo7EoKgz1LxBZ5Kdr8Z2vnpo
J1i1Nk2KSk+Zp/C/2uEXD/BfBd7Kd0tPidwEbMaJSFs9TrZDIhaRbEn1wOm2
gkTG0gF87ICHdsV6Rt1lb1fjVbszrL8adxgRU1SPyLUHLISF8kOrG7FInSRX
Evi70VGYn39YXL2Q1yhc1t0NPds8h6B7eWNxHgclyWFMwRgA1PEeKNrRHc50
sQfzMSrKMRwd8WQXce1HtMXktL6J/ovvb8m04mqk19+/9y04GgBgDKUeHyp2
4gaEej1CGC/2EFKsKRGafZWvNdUr42Pj1XbcAxBEmoBoI0NNInsSHRkxOFWR
p1X2mQxtvgOSLv4MEOIayjGqcsMu8ilSrKZ0EbNYSWL3Rm2HXmRoHWg44qq1
UrlHWUW3FUhtauO5I0/t1PFrKt9UET7F+ZxrL+sttW8L7qQHtfVsVN/kRav2
qlmkebJzdMSo1yw0xHGn/wJmGOSdZVnGsavURHi5p1mDoyOSyQ4JfUj4CZIh
iUYc/p9A4RFZvknlLXWRDIof+BKJAN2zNMlRnxXbgdjXp3kiFr4BDB5EfRka
pML4vPO+BzDqNuRQZH0wOGgne6kJ2CkVg13ovKMh/xHgBbV/Fs7pJ9HarMsQ
qyYpN4mopWO6ZY9qv16LEuPmxjimdMGczoFMQvEMlxfIbYujYpMJ0JVGAxGH
CA2dKmLPL/qRhpsqg4YIx+S2c55KvOvS6/AaJ1EKyMX1gk9NAW5sgB7HvdGj
yaXyhuntdKD861u3pPlCXH6F77kktm01tGdpN029KceOjkUrZxQ1EB2siQ4Q
5F6fdF4bt2vqkuJzVZS2JXdjUYr3Xv85msgUhJBaBLWEJPKZLRQBasDqkKVB
dH+gw9niT7bMnPJoKEwaaq52XyaIt2NyGZ/o6rsqRLYiFjXGRAwYnoKK+RIL
rdtSaadZjmufCD39g1Y1vbj33RGBUDl4CJdSs91PXBxBTKBIlehH0RdMxI96
v2acIj1IBo5W0nPzFz1DzOmBHYqdSvsHbcGD4XzUxD6ct+J84AO6MxqP/9lp
mNyqQJLrxyxMJBiFht9U8PQW46ogG790xToW8SV5kAZXFq8mxE8BrUuUwxmg
gOPumBqAwcciVUHqpzCODNzbmxLi+ZF7ilodz0HFO9Rl0iakHftgSUlKZD7i
Upk7Ck9EOWQM4QsPSMLM4wEUi5lMNJonaRoOjrMa+YL+Sl+TMDb89ZGipvsU
3PuOjVSuU0dHFD/Yn8dRthRxwx/I0bARhpYcXRilT/8xbPdBgzc4HEY71X8M
pb4KFOAZAvSkWoiNm6Q54vGUM5GfSxRY8uJWbnrxkX90cMEqzrpqP9E7OMpJ
sN9xMCDGKLTqMCkHlD4KJshu6DvD1jZxVvc59KOnt6hRQdIHlaXK7yilry3V
8Ofj70ZLvbL80WnZi9oL8f08+lwXfz1YqcrrA8wQV9kFlLJzkDWcSjhJJ3nC
2n2wW2MY65YTCMDR3Zfi6Kf/Z8D6kt9h6qt0sY7Nw5On7otNJHjdwp1F/IxQ
6qqNPfctbv1KH0MjAd+bHM/Q17yxIVAgebnaaZppWkgnv/qbckbO3d2dPZS/
2bKR7yrSLrz0WVEMxLuuxpJDeUP0/qh9Y/K7Q/kPDdXUfJLSlaevtjj41mpX
UcN8md9pR5T+D4NnTTycGQAA
</rfc> </rfc>
 End of changes. 38 change blocks. 
345 lines changed or deleted 180 lines changed or added

This html diff was produced by rfcdiff 1.48.