rfc9896.original.xml   rfc9896.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.2. <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 2.5.
3) --> 9) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
-editorial-rswg-svgsinrfcs-04" category="info" submissionType="editorial" obsole -editorial-rswg-svgsinrfcs-04" category="info" submissionType="editorial" number
tes="7996" tocInclude="true" sortRefs="true" symRefs="true" version="3"> ="9896" obsoletes="7996" tocInclude="true" sortRefs="true" symRefs="true" versio
<!-- xml2rfc v2v3 conversion 3.30.2 --> n="3">
<!-- xml2rfc v2v3 conversion 3.31.0 -->
<link href="https://datatracker.ietf.org/doc/draft-editorial-rswg-svgsinrfcs-0
4" rel="prev"/>
<front> <front>
<title>SVGs in RFCs</title> <title>SVGs in RFCs</title>
<seriesInfo name="Internet-Draft" value="draft-editorial-rswg-svgsinrfcs-04" /> <seriesInfo name="RFC" value="9896"/>
<author initials="A." surname="Rossi" fullname="Alexis Rossi"> <author initials="A." surname="Rossi" fullname="Alexis Rossi">
<organization>RFC Series Consulting Editor</organization> <organization>RFC Series Consulting Editor</organization>
<address> <address>
<email>rsce@rfc-editor.org</email> <email>rsce@rfc-editor.org</email>
</address> </address>
</author> </author>
<author initials="N." surname="Brownlee" fullname="Nevil Brownlee"> <author initials="N." surname="Brownlee" fullname="Nevil Brownlee">
<organization/> <organization/>
<address> <address>
<email>nevil.brownlee@gmail.com</email> <email>nevil.brownlee@gmail.com</email>
skipping to change at line 39 skipping to change at line 40
<address> <address>
<email>jmahoney@staff.rfc-editor.org</email> <email>jmahoney@staff.rfc-editor.org</email>
</address> </address>
</author> </author>
<author initials="M." surname="Thomson" fullname="Martin Thomson"> <author initials="M." surname="Thomson" fullname="Martin Thomson">
<organization/> <organization/>
<address> <address>
<email>mt@lowentropy.net</email> <email>mt@lowentropy.net</email>
</address> </address>
</author> </author>
<date year="2025" month="September" day="17"/> <date year="2025" month="November"/>
<keyword>Internet-Draft</keyword> <keyword>SVG</keyword>
<abstract> <abstract>
<?line 58?> <?line 55?>
<t>This document sets policy for the inclusion of SVGs in the definitive version <!-- [rfced] Abstract
s of RFCs and relevant publication formats. It contains policy requirements from
RFC 7996 and removes all requirements related to using a specific SVG profile o a) The Abstract does not explicitly mention that this document obsoletes RFC
r specific implementation code. It also makes the RFC Publication Center (RPC) r 7996. See the checklist in the "Abstract" section of
esponsible for implementation decisions regarding SVGs.</t> https://authors.ietf.org/required-content. Please review and let us know how
you would like to update.
b) This sentence mentions the RPC being responsible for implementation
decisions. Other instances in the document mention the RPC being responsible
for decisions about both tooling and implementation. Are any updates needed?
Original:
It also makes the RFC Publication Center (RPC) responsible for
implementation decisions regarding SVGs.
Perhaps:
It also makes the RFC Publication Center (RPC) responsible for
decisions about SVG tooling and implementation.
-->
<!-- [rfced] Abstract/Introduction: Is "sets" the best word choice here? Would
"defines" or something else be better? Also, will all readers know what the
"definitive versions of RFCs and relevant publication formats" are? Would
adding a citation or clarification in the Introduction be helpful? If so,
please provide the appropriate citation or text.
Original:
This document sets policy for the inclusion of SVGs in the definitive
versions of RFCs and relevant publication formats.
...
This document sets policy for the inclusion of SVGs (Scalable Vector
Graphics) in the definitive versions of RFCs and relevant publication
formats.
-->
<t>This document sets policy for the inclusion of SVGs in the definitive version
s of RFCs and relevant publication formats. It contains policy requirements from
RFC 7996 but removes all requirements related to using a specific SVG profile o
r implementation code. It also makes the RFC Production Center (RPC) responsible
for implementation decisions regarding SVGs.</t>
</abstract> </abstract>
<note removeInRFC="true">
<name>About This Document</name>
<t>
The latest revision of this draft can be found at <eref target="https://
github.com/alexisannerossi/id-svgsinrfcs/blob/main/svgsinrfcs.md"/>.
Status information for this document may be found at <eref target="https
://datatracker.ietf.org/doc/draft-editorial-rswg-svgsinrfcs/"/>.
</t>
<t>
Discussion of this document takes place on the
RSWG Editorial Stream Working Group mailing list (<eref target="mailto:r
swg@rfc-editor.org"/>),
which is archived at <eref target="https://mailarchive.ietf.org/arch/bro
wse/rswg/"/>.
</t>
<t>Source for this draft and an issue tracker can be found at
<eref target="https://github.com/alexisannerossi/id-svgsinrfcs"/>.</t>
</note>
</front> </front>
<middle> <middle>
<?line 62?> <?line 95?>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t>This document sets policy for the inclusion of SVGs (Scalable Vector Gr <t>This document sets policy for the inclusion of Scalable Vector Graphics
aphics) in the definitive versions of RFCs and relevant publication formats. It (SVGs) in the definitive versions of RFCs and relevant publication formats. It
contains policy requirements taken from <xref target="RFC7996"/> and removes all contains policy requirements taken from <xref target="RFC7996"/> but removes all
requirements related to using a specific SVG profile or specific implementation requirements related to using a specific SVG profile or implementation code.</t
code.</t> >
<t>SVG has been developed by W3C, the World Wide Web Consortium <xref targ <t>SVG has been developed by the World Wide Web Consortium (W3C); see <xre
et="SVG"/>.</t> f target="SVG"/>.</t>
<t>The RFC Publication Center (RPC) is responsible for making SVG tooling <t>The RFC Production Center (RPC) is responsible for making decisions abo
and implementation decisions. They may want to use the content of <xref target=" ut SVG tooling and implementation. The RPC may use the content of <xref target="
RFC7996"/> as a starting point for those decisions, but they are not bound by <x RFC7996"/> as a starting point for those decisions, but they are not bound by <x
ref target="RFC7996"/> and they may change elements of the implementation as nee ref target="RFC7996"/>. In addition, the RPC may change elements of the implemen
ded to support the RFC authoring community as long as those changes are aligned tation as needed to support the RFC authoring community as long as those changes
with the policy requirements in this document.</t> are aligned with the policy requirements in this document.</t>
</section> </section>
<section anchor="policy-requirements"> <section anchor="policy-requirements">
<name>Policy Requirements</name> <name>Policy Requirements</name>
<t>SVG tooling and implementation decisions are made or overseen by the RP <!-- [rfced] Section 2: In the text below, how may we update "This include
C, and must adhere to the policy requirements in this document.</t> s"?
It is not clear what "This" refers to.
Original:
* Images and diagrams in RFCs should be successfully rendered and
understood by the widest audience possible. To that end, the RPC
may prohibit the use of SVG features that are known to lack
support on common devices, that do not render on small or low-
resolution screens, or that could make diagrams less
comprehensible for any significant readership. This includes:
- SVGs must not contain pointers to external resources.
- SVGs must not contain executable script.
- SVGs should be as accessible as possible to people with visual
disabilities, ...
Perhaps:
* Images and diagrams in RFCs should be successfully rendered and
understood by the widest audience possible. To that end, the RPC
may prohibit the use of SVG features that are known to lack
support on common devices, that do not render on small or low-
resolution screens, or that could make diagrams less
comprehensible for any significant readership. In particular:
- SVGs must not contain pointers to external resources.
- SVGs must not contain executable script.
- SVGs should be as accessible as possible to people with visual
disabilities, ...
Or:
* Images and diagrams in RFCs should be successfully rendered and
understood by the widest audience possible. To that end, the RPC
may prohibit the use of SVG features that are known to lack
support on common devices, that do not render on small or low-
resolution screens, or that could make diagrams less
comprehensible for any significant readership. For instance:
- SVGs must not contain pointers to external resources.
- SVGs must not contain executable script.
- SVGs should be as accessible as possible to people with visual
disabilities, ...
-->
<!-- [rfced] Section 2: FYI, we have updated the sentence below to clarify that
SVGs should be consistent with the content of the RFC (rather than the text
output file of the RFC).
Original:
At minimum, SVGs should be consistent with the text.
Current:
At minimum, SVGs should be consistent with the descriptions
in the text of the RFC.
-->
<!-- [rfced] Section 2: This sentence mentions that decisions about SVG
tooling and implementation are "made or overseen" by the RPC. The document
mentions several times that the RPC is responsible for making decisions, but
this is the only mention of "overseen" in the document. Please review and let
us know if any updates are needed.
Original:
SVG tooling and implementation decisions are made or overseen by the
RPC, and must adhere to the policy requirements in this document.
-->
<!-- [rfced] Section 2: We updated "rfcxml" to "RFCXML" in the first sentence
below per RFC 9720. Would it be helpful to also include a citation to RFC 9720
or other applicable reference here?
Original:
* Authors may include multiple versions of images or diagrams in
rfcxml. Publication formats should present the versions best
suited to each format. In many cases, that will be an SVG.
Perhaps:
* Authors may include multiple versions of images or diagrams in
RFCXML [RFC9720]. Publication formats should present the versions best
suited to each format. In many cases, that will be an SVG.
-->
<t>Decisions about SVG tooling and implementation are made or overseen by the RP
C and must adhere to the policy requirements in this document:</t>
<ul spacing="normal"> <ul spacing="normal">
<li> <li>
<t>SVGs may be included in RFCs to help explain a concept more clearly , but should not be the only representation of that concept. A good faith effort should be made to assure that descriptions of concepts - which might include pr otocols, formats, or system architectures - are fully represented in the text of the RFC. At minimum, SVGs should be consistent with the text.</t> <t>SVGs may be included in RFCs to help explain a concept more clearly , but they should not be the only representation of that concept. A good-faith e ffort should be made to ensure that descriptions of concepts -- which might incl ude protocols, formats, or system architectures -- are fully represented in the text of the RFC. At minimum, SVGs should be consistent with the descriptions in the text of the RFC.</t>
</li> </li>
<li> <li>
<t>SVGs must not include animation or interactive features. SVGs shoul d include only limited reactive design elements (scaling, dark/light mode, and p erhaps minor adjustments to allow for variations in display technology). The int ent of this is to ensure that the diagram's meaning is not altered.</t> <t>SVGs must not include animation or interactive features. SVGs shoul d include only limited reactive design elements (scaling, dark/light mode, and p erhaps minor adjustments to allow for variations in display technology). The int ent of this is to ensure that the diagram's meaning is not altered.</t>
</li> </li>
<li> <li>
<t>Images and diagrams in RFCs should be successfully rendered and und erstood by the widest audience possible. To that end, the RPC may prohibit the u se of SVG features that are known to lack support on common devices, that do not render on small or low-resolution screens, or that could make diagrams less com prehensible for any significant readership. This includes: <t>Images and diagrams in RFCs should be successfully rendered and und erstood by the widest audience possible. To that end, the RPC may prohibit the u se of SVG features that are known to lack support on common devices, that do not render on small or low-resolution screens, or that could make diagrams less com prehensible for any significant readership. This includes:
</t> </t>
<ul spacing="normal"> <ul spacing="normal">
<li> <li>
<t>SVGs must not contain pointers to external resources.</t> <t>SVGs must not contain pointers to external resources.</t>
</li> </li>
<li> <li>
<t>SVGs must not contain executable script.</t> <t>SVGs must not contain executable script.</t>
</li> </li>
<li> <li>
<t>SVGs should be as accessible as possible to people with visual disabilities, including those who have color blindness, those who need to scale or change fonts, and those who use screen reading software. The RPC will refer t o the W3C Accessibility Guidelines <xref target="WAI"/> when making decisions re garding accessibility.</t> <t>SVGs should be as accessible as possible to people with visual disabilities, including those who have color blindness, those who need to scale or change fonts, and those who use screen-reading software. The RPC will refer t o the W3C Accessibility Guidelines <xref target="WAI"/> when making decisions re garding accessibility.</t>
</li> </li>
</ul> </ul>
</li> </li>
<li> <li>
<t>Authors may include multiple versions of images or diagrams in rfcx ml. Publication formats should present the versions best suited to each format. In many cases, that will be an SVG.</t> <t>Authors may include multiple versions of images or diagrams in RFCX ML. Publication formats should present the versions best suited to each format. In many cases, that will be an SVG.</t>
</li> </li>
<li> <li>
<t>SVG vocabulary and implementation may change over time. Changes are not required to remain backwards-compatible, although maintaining compatibility where possible is encouraged.</t> <t>SVG vocabulary and implementation may change over time. Changes are not required to remain backwards compatible, although maintaining compatibility where possible is encouraged.</t>
</li> </li>
</ul> </ul>
<t>The RPC is authorized to place constraints on SVG usage in RFCs for bot h technical and editorial reasons <t>The RPC is authorized to place constraints on SVG usage in RFCs for bot h technical and editorial reasons
in order to ensure that published RFCs meet the above policy in order to ensure that published RFCs meet the above policy
and to provide consistency across the RFC series. and to provide consistency across the RFC Series.
The RPC must document the acceptable usage of SVGs, and all changes to tooling o The RPC must document the acceptable usage of SVGs, and all changes to decisions
r implementation decisions must be widely communicated to the RFC author communi about SVG tooling and implementation must be widely communicated to the RFC aut
ty using mailing lists or other means.</t> hor community using mailing lists or other means.</t>
</section> </section>
<section anchor="implementation-guidance"> <section anchor="implementation-guidance">
<name>Implementation Guidance</name> <name>Implementation Guidance</name>
<t>The RPC is expected to solicit community input before making decisions and to publicly explain their reasoning.</t> <t>The RPC is expected to solicit community input before making decisions and to publicly explain their reasoning.</t>
<t>Documentation produced by the RPC should describe what technical and ed <t>Documentation produced by the RPC should describe the technical and edi
itorial constraints apply to SVGs torial constraints that apply to SVGs
and provide RFC authors with guidance on how to produce diagrams that meet these and provide RFC authors with guidance on how to produce diagrams that meet those
constraints.</t> constraints.</t>
<t>The RPC's implementation should strive to allow SVGs produced by widely used drawing tools. <t>The RPC's implementation should strive to allow SVGs produced by widely used drawing tools.
Where possible, implementation decisions should focus on specifying what is disa llowed, rather than attempting to specify exactly what is allowed.</t> Where possible, implementation decisions should focus on specifying what is disa llowed rather than attempting to specify exactly what is allowed.</t>
<t>The RPC should periodically review and revise their practices.</t> <t>The RPC should periodically review and revise their practices.</t>
</section> </section>
<section anchor="security-considerations"> <section anchor="security-considerations">
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document has no security considerations.</t> <t>This document has no security considerations.</t>
</section> </section>
<section anchor="iana-considerations"> <section anchor="iana-considerations">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This document has no IANA actions.</t> <t>This document has no IANA actions.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references anchor="sec-informative-references"> <references anchor="sec-informative-references">
<name>Informative References</name> <name>Informative References</name>
<reference anchor="RFC7996"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.799
<front> 6.xml"/>
<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
diagrams that may appear in RFCs -- and considers some of the issues concerning
the creation and use of such diagrams.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7996"/>
<seriesInfo name="DOI" value="10.17487/RFC7996"/>
</reference>
<reference anchor="SVG" target="https://www.w3.org/TR/SVG/"> <reference anchor="SVG" target="https://www.w3.org/TR/SVG/">
<front> <front>
<title>Scalable Vector Graphics</title> <title>Scalable Vector Graphics (SVG) 2</title>
<author> <author>
<organization>W3C</organization> <organization>W3C</organization>
</author> </author>
<date>n.d.</date> <date/>
</front> </front>
</reference> </reference>
<reference anchor="WAI" target="https://www.w3.org/WAI/standards-guideline s/"> <reference anchor="WAI" target="https://www.w3.org/WAI/standards-guideline s/">
<front> <front>
<title>W3C Accessibility Standards Overview</title> <title>W3C Accessibility Standards Overview</title>
<author> <author>
<organization>W3C</organization> <organization>W3C</organization>
</author> </author>
<date>n.d.</date> <date/>
</front> </front>
</reference> </reference>
</references> </references>
<?line 232?>
<!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed. Updates of this nature typically
result in more precise language, which is helpful for readers.
Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
-->
</back> </back>
<!-- ##markdown-source: <!-- ##markdown-source:
H4sIAAAAAAAAA71YTY/cNhK961cQzmHtxbTaiBcbuE+enewaE8COMWNkjgtK H4sIAEhnJmkAA+1a/W/bxhn+nX/FTf1hcSHRqbuti1Y08dylcNF8IMnqDUVR
olrMUKSWpFrTCfzf91WRUqvHHse7hxyMsSSSVfXeqw/2ZrMpoo5G7cTtL2+D nMijeDXJ4+6OUtQg//ue970jRUm2G9sdOhQF4tii7t7vj+fe42w2S7z2lZqL
0Fbc/OsqFI2rrezxtvGyjRvV6Oi8lmbjw7TfhMM+aOvbOmxe/q04KDuqXSHE 199+5YRuxKunZy7JTdbIGk9zKws/U7n2xmpZzaxbL2dutXS6sUXmZg//lDRd
3rtx2Imb27u3eIrHAfv/Oe8Ut9Er2Ys75++13Yu3tBjLeqnNTtCxb3BgtlQ6 vVB2Lh799dFfEudlk/8gK9Ngs7edSlZz8WliFs5Uyis3F589wjLdWv7a+ZOH
v8c36etuJ7oYh7DbbmklvdEHVWoVW1q0pRfbyrspqC0dsiU/dOzGaieeSaMe Dx89PEky6efgXpjEdYtaO6dN82bTgsjAO8mlx+eThyd/nn3ySXKpNmtj83ki
dJDWKu9C0FvdrFx/hpVGRhUiVs420taydv32q5u3lXEVeWS3p5dl3zwrQpS2 ZiR7ksjOl8bis5jhR4AauJ2m4pUBNX4SVDqt1FvtRo+NXcpG/yQ9eM5Jf/Fa
+bc0ziL66EdVHHbiVeGq4IyCtZ344fXrvxd68Pw5xO9fvnz98vviftqJaxuV Wa2cODON6yqvm6X4B0vBy1UtdTUX1mXqCWwQjZOCyi7r56n4uzXrplJqxP25
typufiTUi1rCNW1bV4Sx6jWccPYjo7rwUdyr4+R8A/g3xGAhx9g5T2xs8E9g Wulq94sd/mMWDa1NF3HtkyU9TTNT7/L5OhXPZAmDb0Zsvlay2Xl8qORLa/Iu
OyxeluKGYuA3iddLjm71GmBKq3+TEUZ2JAJxq7xWQVw5G0YTibNEJi9XM2+1 o8/iTDVe7Wj3Yx32PoFDiyK9Sc9nqXhTmtqZZsT/mbSw284X16pZ+yeVWUME
+py3len3pfgH2LFGqZX19+qgzfmHM/trE5bWllVe+2ZPb4mgczs/leKd7AD6 a9pN2iifJI2xNRau1DxJEgqL4aMg2SmG6E/4PVDa+j5ymouLT8/4Yx/emazk
cWXmJyXt2evPg/zgXTPW9CyuFMG/Nv1rn/a+AaltW34tznel+Ni5Pji7sv9O olLiW5VBDfGVlW2pMycegMiROAlrpV0qBGLpfevmx8fr9Tpdf0oqH795dYyF
euB29uHJMPv4xrgJLng3HEuIoCis8z0WHpBcRUE6WB4F+U46ov+C9nTSifts x7wsBGIhK0cOvDg9/1Ah8FGcZplC5C10pf1GvKZ8kTZ34sVK2ZVW658TBOyO
aSfuXl3x45zjtTSyMkr8omqEgSSUQ6frkNZIv1fxlG/TNJXTK86yjzdbWKHc Xb9rtux0rirdKHcoWjKbzYRcOG9lBpt+/gd8/A6eVPn34nR4LI/gJTU8ELlB
uru8/lZjeBSXda2gsEobHY8oAcgN6Zsgfj4of9Bq+iPDMLcN867NftSNMtqq 5DfGC/W2rXQGwTeihnMoTnwpPf5D9qBAdPRUDJlNfknIMSnSR2GVElmpsstK
sC2KzWYjZBWilzWw+thBzahaYw8IRVAxiMEZXR8FYBOxU6CpNiOlkHDtUuzo O091hR5Mei4T4VQIPVMkvZLBfi7VyhesqlX/6bRV+SwziM/Gp+JlpaRTwiqy
Q6NabTUBK+AVrQi0hOqggGXhlVEHiVOHscKJTJ1IZIRSXEdROxtRCRaLXv1n lIARBHiLzonLxqxFadbJxnRibboK3+hLiGFE15JRUgTSglSF8I7CvclUr5dj
1F6RJ0G03vWsNKIrn9e7AxJLGnO+FIZQjxoRnYCjyDcpwqBq3eqaHBaDd60G 4V69PBMLRclulWvxVFO4IPSErttK0VqO3SRXmab65FLxAhstpQEcArf2eg7W
eQhoea/7wfD25FbtGsU+SRMcaus97FCMLPWV+0nr4vnNh6sXsBsGBK1JGITW 2RruGvoJ0R8Iwlum82JhfAnJTUWLScldAVJxahWeb6JqcJdSucofJ8kLq5e6
ozMbmEqoeLUHD+QZ4VcmDnrdNEYVxXdUvpZs+v8Yef6UQF/8OWRFAGYTZb// kRUH4bkXiAMjanmpooqU9t0CbpWjvBcPINrRvtZEYZfvSE6rlgg/Eo/aBmz7
nlPs06c/h7WioNWdDKJSilA/KOMGHFwdKZUuOHx0T9OIO6SBuFMV12aHGjOS UtlSwou/DN99g4DJTfZAoH9xTXwfn1NZiXVuLs6dmDjl3YTFWiiEJjURRKrR
v9j+6VNJwP8B3zp8RjmUkmlFHACGwkDQTymBip06YtdRTAQ2x67YQ8KXCAcp iAc4Uz0WFxQ+ySRXBeXVBJksnKkV4h7sFTILG/HPQ4XH6CbOTMVaVxWUrqCM
ZxAGwiVyQdwDe40lSQcuqNPBF6IaI51zRPNXwrooKjdaBuExI3F2oe6k3Suh zJWN8bgO6aIiLU0VTCDNg2qm4F7LCllVqZVEwLQjK4WqBwHkViqZs9WlQGKG
TGYEplle587DA6tUk5gK4zAAuCU3UjUj19BZ+tFStcIGdPE9/U1eJjuBPZNG VZAuq6TVRb+tD8Kx5iRxqaq26KrH4ryAPtOkDbnUWrNCDeEtssWnFs3Wqx0G
7y3OmjAw8ClfkhNrdpUFJWXJh7TwZrUwUf8twLPtXjYsJ0cZQFoBOBzIB6iE Xr316V50vdkpA2RU0cJD2YZThqjpJqs6F5J8gBecHoM1iNCtDZLSrjRN7yrF
dvcYK4RsOoXFCPZ/cO+vKQ8J1SonKCGWx0I6rFNmEOphMEgiUAq6azVE0TvY g71eQHT6dnB0KOOHC0iEBhk5Jn8RI93BQpSDVDQlSlPPMVZTksSJwpqa05Iq
qo2S3hwTiaFzI7TKFCZpOGvIgwHiWyJjrmSczynFpdg714hWErCqbYmlfFSV tlggx/CNWSFfQxSPloIR4iHnUupC8LkWCYqA48REyBQaxjwolJAgV+l15WAf
Q4cXMoSRgqOtjQq110Oca0E+KmAimlA7OlSofRfnYCgfo6udgdZyXbjg3DyG fVxdDW5Rgqjb1TrPUVSTj3ai//Z+uAks3C9GPtxFHvZqgqPevYug5/37/6mv
qHoeOXVE8cHxdALh3Y5m7XjCgwKK6iHOagM+cB5AoDz1Y3+RgDx5XlO6BU6N koQWldKhXigy9kpVpgW9xYYVvjAWjfWCysWFWjA+NsB5XS0eANoc/Q2WVRAW
RTO0v1wwJ9IIrdlRzAl9Bgk1mfIXnY4KX6sku1ee2Zi3McpG95ocxcid9gAk RN6/T8nqN/tauwN3I0hI7Fs2AEYw1F9riaboIvoIoIE8MrYflINRPOPTJQyv
CPaUI88DKi3UdiHQWu+3hiHqUYeSggblOzkEigbGZfMrnMsl0lEJdBNn70Fi sSQEgXFqy3jKhgadDZVfBkSQpGFTjMjBjY2gokxyTIc+T3JkpWyWCg0j+gZy
CE3AA5JGB8gCWlR1Z51x++MLLhTsvM1IQW+aT1H2RCFXdi33XvZ/gVGMbZQI cKDt2l323Zt85rq2hUGHJAmIiOQE6q+7hhAjNuB0taTfQeTAx7GYstLLBrTW
WEd4SIPQVUNAXfeSExAe5uXLlWUFdRh56phpsw1t500j/T9EEljOmQmllJJl mhAEqFwVWBy9o3xIKV9ehoWvRgv3WurriNhO5qQzEae2gEgBeJ8S9mKt1yqi
bLSCbJAngasiHHfJN+y/mNOLEwMC6jDRJK+p7KXutdCStpFw7i2GVorVyPp+ EjHhpOO8ytFGHycIeB2gZYbWY0N75FUTCFhQ2/Rmv818DDxRS9YPxs+1XFpZ
qTlc8Pue0/qg4elF1rHjcJPDtCr01GwAM+De4GBnRpYD5I6sT7LNyUORU7c/ DwdV4UrGemhvrmNgjQ5Xkb4N2jAMgU0Rj3f0xCGIhmheI44BAGSXa0aDLZ0I
wWKAANmBaDu1qvTSHgVJgfoQlW4ohDDp9EBcETtJR4FGu8fSzM0z1W/sYh4f EYgp2ooJWBdkBqdGOqQk0qgEgg+OongLtVsUSvrOcpXDZnII4YCGXFvJ7DJS
6NIiqSsGN3rEU35lp3pQ9Ri5xaesXS0+MUjdIk+Ohp9mWsjgoByKY8qigw4j 6L3MWVfXXNVWgB9uGvblho0UdKBVrqZER4zC0rNIBFxM1bFDXGaRrdjNUSyp
TEN5kmdMTWimCEhBqW5PHcqWPFAOGiCArmgbzJCM+/ydWgM3BqQFF9fcVFr4 rJBNqN5uDVbBNnErmLZWlWqUdgQmHUKHUUTjexhT6jaNPbb3Iw5kgcpMhHZV
HS5yv5kXE+mJBIaPLAXXxgmcJ8GTVCbNk0ILLnMN/nwgfrsMtOhumHXR2Saw 4xAfnBqKWUip4EycIfAXXMnidhY6pj+7X71VWee5/EIz3fqDLVunUzLH81TF
NbfjL01ecn0A5cQlt65Us+ca0NOFjUBaz0g6JQ9iW+cOLjUPvSnF2biQC+PM n3ofEvNWGaRayIWVdp2sIh1CmNpJPoJpMjuBiR0I+3vU/epRhxrTUpHOOqDb
SC58HMRyYkV5E0adZx8Umi7vw2HXFAOUVsuw6JsBIXIt0Z3rnji4WlYjLvbH 327UvbC/B9z/R8A9NduT/G823g5PyqO2/vTf51Nq4KVc9V08Z98PAxNu9sQ1
LzW+VXunboerRQ+Ir1aNOKUMdzX2w9N9Ci0RGTfxpYFyAIdBPBdUShDRvqNf HDk37IhkT9yMAJ1j7DXgkBEY68HNAyt5egISWziRAO21AF4BpQ6Lj/ZgwakH
HViPuePzgkTJxF1z0RsSAnUBugZ2zTxcgV28zzPDb8kuKl+dqjxuJJrHEI4T 1G903dXTfWNdxT2eX886i2jzdyCADGInMSQVyXDGZgS0FfNn7Hvt8Imy4RDx
YsHWpUpRClaO6j8VSeBtOOzlQk+Cwl0x4L4HppoknnWp5Lk2dDDK5/VKJV5k JtcjXk66SY3opWwwdPpAbkz6lEcaB0zcQ7xkYOaA6S1C1eu6T+AetH4AHGdU
BYBymy9Yro4q1YFGxaX3YAKQNf2csQw+gS/55RIXJ+wytfPBNXVTztgUSh7W nDB61OEsZ5rRfBCWmGyF2RuGXTO9S/rpnS52ZlqMuhkZ70PCmw8DY0uCxL6N
U1JQhZrnIpJ5nmG+dotgE1UqvSjQeeCq5yH6fCRbzWNpuqbbMv0FCJHFDDCB oomIDnSeMgFOTpnT9Idi+8Nx843evtjm0ATfvq2rCVGfIE7+9eybwTyFRrke
EvWMwPPV9bldSjGJyn5GHeYXtPic8QSZjitD2g4jedg6HrYepeKMLacL/J9n oiIJGdYiLyhHHn128jANox+h/WiKQ5T4VB1x2XgihK/6vQlpzlkmW5rmcr1h
IbihfaYPO+DLjxnG5MjAdyPVrKa1Ob/SBEOQcDN8QhlrbclhgGm4QUww3TPX rM0hyPOuQ8B9Ggax3AN6+jVdhFChGZ90dWhZNMLcdqy+crPKqKsvDw+/fbah
J+hCKpH7DADpsUPfTrogV051gJU1SymcyfikeXTmR5xm97GURoxlMuBivg43 PpPibIeBLk3lhhai42lWyayMuwM2qClWMoRT3054BEfFsqEAOcRzv4hSwXfi
M42y2dAPihOXZigFh9+dpdvF06rJtlpgyqmV7lJHOopRozkWXYAcUGjYXrIs O/wm837/66nHofflrY7JN+UDF4B75AIa5sex08G+C9WbOB8gDIhR7PK1AjVA
EBim1IjJbojJ6rwRvGE0Msdld966yvG5+iFFXEOE8DhBP1vkGyG6j8q8Dzyc SYU2Uy0KsQEvPhJWm9GxOxqRT95qW2usimaVfcmJYICJpeJULAF+ZoWk2q2K
cfODBm/R5DxJiS5oCN6nIenxpZguexYezavrs9U4ieR8+f7y247hlbJe9tLl giDItriz+mTwxnWkYSi9o+IOepGUE8jrdanhmVovSz9EDWCRN5mp4JrocMYk
nMpg8V/JvQsQ5RUAAA== boOmUcPIWQm3ZgEh0Q0M+PRwLYoezHJVA7lXY7quKX28h0GGmgE+w4yX4YzM
eJrVA7x0R4R+G7uh0jUHLyBU2ANJgKy2444HLpMUiFORS3t5XLEJa5OrUHPb
kJ2kLAGz/EcIF+deVNmoCFIDWkmaRvfaAc8geBCwKisbU5nl5ij0OT1CF7E3
7fqYbRXS+Y9gqqA6ciSOI2TlCUWToe4Jwm8Fv69C3/fB3fdE3HeB2rcF2Xuj
BCrMd4PX1++8AlgPi+8MqfeQdNCAIiiM4NalCaAZVQEWQENo8gbEp6PvCcvw
jA9pwRU4zgcLyO1CTmwXk9ODE2ZkPuLkTOHX8Pl22MktgZt5X6kP75e/Gu6H
xbt3F6fn79+DvmoO56zbcbocE6CcuF/njD3zjp3yXj2SvS5WBrCHhgibq3ri
aFJLLZFxcSrORjPVkDLhJprksPTaAvomMm7NN/eUAyCG4JlSKYFGS7QMrKF4
jMNbXhBcsubeOsQbEgJ1AXEN2+X90Dyg8Tj+/SnwReXLQhPwlog7ymBSsHPY
OlQpSsFwgUxFEvauWO3hNRrKRwciiaayn4fgGZdKvqxwJZgyvVqp4BdAjFUP
BhIOVzNcHg6tCThBZha6Dce88C5NOujFCTtcxTDhjNotZ2xQJd6EhaSgCtWP
uMHxdjcDgdsiVGHU6jhGz/pLkt1B+2jKHm5P6P0U+k3vMHBcByxN7cPx1Px8
lxtlG40PdrwIwAM0EJPf8CsVI0a6oePuQhWGwdn+7Uc0M2cO5O/BE8TQNnoS
OyDLl9GiQZCWb1y2FzckSky1gBgiorouRsZRFpoNjg8bEoUcw97vXb81nwsV
cxmNQOFZhmlBFGdbFphmjCy+w9jy26YAGvWeN6MKWEqIYwAKXNvHKkdvo4rm
9Abbmis1ggTEL3ayb3r94THyKmBXzrRwj7YhUnxxQeAXTYEEIBg0mmVIDxzY
+sC03wfXAShVm2Fz3DnK+L4WImFMTk5hcDGclenPcLUF17cM1cKk6SM6dXaW
oolu5KC7DZBp/96TLvYaQ6/ehNXZzmp6QwYRffr89MPI8EqZDXvp/pWK4t6J
ePfQz28BnYe7VrjwG+R1h5SfCAIuA55njImmJZLXfoOywF1MfD5+G2r3jbRj
R+v4ZahjmhqfHH+keyY/VJHJF8n+C0Nx5DC+QYsjByH+GecQPaZsGHsJv2mD
axK0LDRBqrt8gEELy8g/PbdpPDtga39mp9Ic0RAM9tz4WHFR/CNWQUiFE09R
ySXLRq+ncBvdDsP7M5IegjRxPra+YGYCo3TNyR20DxW+Iv8i+S9IHarK8ykA
AA==
--> -->
</rfc> </rfc>
 End of changes. 22 change blocks. 
131 lines changed or deleted 261 lines changed or added

This html diff was produced by rfcdiff 1.48.