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 be helpful in the Introduction? 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 Publication Center (RPC) responsibl
e 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 Publication Center (RPC) is responsible for making decisions ab
and implementation decisions. They may want to use the content of <xref target=" out 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 <
ref target="RFC7996"/> and they may change elements of the implementation as nee xref target="RFC7996"/>. In addition, the RPC may change elements of the impleme
ded to support the RFC authoring community as long as those changes are aligned ntation as needed to support the RFC authoring community as long as those change
with the policy requirements in this document.</t> s 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 another 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 H4sIAEUSHGkAA+1a/W/bxhn+nX/FTf1hcSHRqbOti1Y08dylcNF8IMnqDUVR
olrMUKSWpFrTCfzf91WRUqvHHse7hxyMsSSSVfXeqw/2ZrMpoo5G7cTtL2+D nMijeDXJ4+6OUtTA//ue970jRUlxEtsdOhQF4tii7t7vj+fe42w2S7z2lZqL
0Fbc/OsqFI2rrezxtvGyjRvV6Oi8lmbjw7TfhMM+aOvbOmxe/q04KDuqXSHE V9997YRuxMsnZy7JTdbIGk9zKws/U7n2xmpZzaxbL2dutXS6sUXmZvf/lDRd
3rtx2Imb27u3eIrHAfv/Oe8Ut9Er2Ys75++13Yu3tBjLeqnNTtCxb3BgtlQ6 vVB2Lh7+9eFfEudlk/8oK9Ngs7edSlZz8SAxC2cq5ZWbi88fYpluLX/t/Mn9
v8c36etuJ7oYh7DbbmklvdEHVWoVW1q0pRfbyrspqC0dsiU/dOzGaieeSaMe +w/vnySZ9HNwL0ziukWtndOmeb1pQWTgneTS4/PJ/ZM/zz77LLlUm7Wx+TwR
dJDWKu9C0FvdrFx/hpVGRhUiVs420taydv32q5u3lXEVeWS3p5dl3zwrQpS2 M5I9SWTnS2PxWczwI0AN3E5T8dKAGj8JKp1W6o12o8fGLmWjf5YePOekv3il
+bc0ziL66EdVHHbiVeGq4IyCtZ344fXrvxd68Pw5xO9fvnz98vviftqJaxuV rFZOnJnGdZXXzVL8g6Xg5aqWupoL6zL1GDaIxklBZZf1s1T83Zp1Uyk14v5M
typufiTUi1rCNW1bV4Sx6jWccPYjo7rwUdyr4+R8A/g3xGAhx9g5T2xs8E9g rXS1+8UO/zGLhtami7j28ZKeppmpd/l8k4qnsoTBNyM23yjZ7Dw+VPKFNXmX
OyxeluKGYuA3iddLjm71GmBKq3+TEUZ2JAJxq7xWQVw5G0YTibNEJi9XM2+1 0WdxphqvdrT7qQ57H8OhRZG+T8+nqXhdmtqZZsT/qbSw284X16pZ+8eVWUME
+py3len3pfgH2LFGqZX19+qgzfmHM/trE5bWllVe+2ZPb4mgczs/leKd7AD6 a9pN2iifJI2xNRau1DxJEgqL4aMg2SmG6E/4PVDa+j5ymouLB2f8sQ/vTFZy
cWXmJyXt2evPg/zgXTPW9CyuFMG/Nv1rn/a+AaltW34tznel+Ni5Pji7sv9O USnxncqghvjayrbUmRP3QORInIS10i4VArH0vnXz4+P1ep2uH5DKx69fHmPh
euB29uHJMPv4xrgJLng3HEuIoCis8z0WHpBcRUE6WB4F+U46ov+C9nTSifts MS8LgVjIypEDL07PP1YIfBSnWaYQeQtdab8RryhfpM2deL5SdqXV+kOCgN2x
aSfuXl3x45zjtTSyMkr8omqEgSSUQ6frkNZIv1fxlG/TNJXTK86yjzdbWKHc 63fNlp3OVaUb5Q5FS2azmZAL563MYNMv/oCP38OTKv9BnA6P5RG8pIYHIjeI
uru8/lZjeBSXda2gsEobHY8oAcgN6Zsgfj4of9Bq+iPDMLcN867NftSNMtqq /MZ4od60lc4g+EbUcA7FiS+lx3/IHhSIjp6KIbPJLwk5JkX6KKxSIitVdllp
sC2KzWYjZBWilzWw+thBzahaYw8IRVAxiMEZXR8FYBOxU6CpNiOlkHDtUuzo 56mu0INJz2UinAqhZ4qkVzLYz6Va+YJVteo/nbYqn2UG8dn4VLyolHRKWEWW
Q6NabTUBK+AVrQi0hOqggGXhlVEHiVOHscKJTJ1IZIRSXEdROxtRCRaLXv1n EjCCAG/ROXHZmLUozTrZmE6sTVfhG30JMYzoWjJKikBakKoQ3lG4N5nq9XIs
1F6RJ0G03vWsNKIrn9e7AxJLGnO+FIZQjxoRnYCjyDcpwqBq3eqaHBaDd60G 3MsXZ2KhKNmtci2eagoXhJ7QdVspWsuxm+Qq01SfXCqeY6OlNIBD4NZez8E6
eQhoea/7wfD25FbtGsU+SRMcaus97FCMLPWV+0nr4vnNh6sXsBsGBK1JGITW W8NdQz8h+gNBeMt0XiyMLyG5qWgxKbkrQCpOrcLzTVQN7lIqV/mjJHlu9VI3
ozMbmEqoeLUHD+QZ4VcmDnrdNEYVxXdUvpZs+v8Yef6UQF/8OWRFAGYTZb// suIgPPcCcWBELS9VVJHSvlvArXKU9+IeRDva15oo7PIdyWnVEuFH4lHbgG1f
nlPs06c/h7WioNWdDKJSilA/KOMGHFwdKZUuOHx0T9OIO6SBuFMV12aHGjOS KFtKePGX4btvEDB5nz0Q6F9eE9/H51RWYp2bi3MnJk55N2GxFgqhSU0EkWo0
v9j+6VNJwP8B3zp8RjmUkmlFHACGwkDQTymBip06YtdRTAQ2x67YQ8KXCAcp 4gHOVI/EBYVPMslVQXk1QSYLZ2qFuAd7hczCRvzzUOERuokzU7HWVQWlKygj
ZxAGwiVyQdwDe40lSQcuqNPBF6IaI51zRPNXwrooKjdaBuExI3F2oe6k3Suh c2VjPK5DuqhIS1MFE0jzoJopuNeyQlZVaiURMO3ISqHqQQC5lUrmbHUpkJhh
TGYEplle587DA6tUk5gK4zAAuCU3UjUj19BZ+tFStcIGdPE9/U1eJjuBPZNG FaTLKml10W9bkB5VW3RVH45jGzwS5wXUmSZtSKXWmhVKCK+TLT616LVe7dD3
7y3OmjAw8ClfkhNrdpUFJWXJh7TwZrUwUf8twLPtXjYsJ0cZQFoBOBzIB6iE 6o1P94Lr9U4VIJuKFg7KNpwxRE03WdW5kOMDuuDsGIxBhG5sj5R2pWl6Wynu
dvcYK4RsOoXFCPZ/cO+vKQ8J1SonKCGWx0I6rFNmEOphMEgiUAq6azVE0TvY 7bUCotN3g6NDGT9eQCI0yMgh+YsY6RYWohSkmilRmXqOsZiSJE4U1tSclVSw
qo2S3hwTiaFzI7TKFCZpOGvIgwHiWyJjrmSczynFpdg714hWErCqbYmlfFSV xQIphm/MCukagni0FIwQDzlXUhdiz7XIT8Qb5yVCptAw5kGdhAS5Su9YDW5Q
Q4cXMoSRgqOtjQq110Oca0E+KmAimlA7OlSofRfnYCgfo6udgdZyXbjg3DyG gqjb1TrPUVSTT3Zi/uaOeB9YuFuQfLyPPAzWBE+9fRtBz9XV/9RZSUKLSulQ
qHoeOXVE8cHxdALh3Y5m7XjCgwKK6iHOagM+cB5AoDz1Y3+RgDx5XlO6BU6N RBQZe6Uq04LeYsMKXxiLxnpB9eJCLRgfG+C8rhb3AG2O/gbLKggLIldXKVn9
RTO0v1wwJ9IIrdlRzAl9Bgk1mfIXnY4KX6sku1ee2Zi3McpG95ocxcid9gAk A87W7sDfCBOS+4YdgCEMNdhaoiu6CD8CaiCXjA0I7WAVzwB1CctrLAlRYJza
CPaUI88DKi3UdiHQWu+3hiHqUYeSggblOzkEigbGZfMrnMsl0lEJdBNn70Fi Mp6ypUFnQ/WXEREkadgWI3LwYyOoKpMc06HRkxxZKZulQseIzoEcHGm7hpd9
CE3AA5JGB8gCWlR1Z51x++MLLhTsvM1IQW+aT1H2RCFXdi33XvZ/gVGMbZQI +yanua5tYdEhTQIkIjkB++uuIciIDTheLel3EDnwcSymrPSyAa21JggBKu+K
WEd4SIPQVUNAXfeSExAe5uXLlWUFdRh56phpsw1t500j/T9EEljOmQmllJJl LA7fUUKklDAvwsKXo4V7PfVVhGwnc9KZiFNjQKgAvU8JfLHWaxVhiZhw1nFi
bLSCbJAngasiHHfJN+y/mNOLEwMC6jDRJK+p7KXutdCStpFw7i2GVorVyPp+ 5eijjxJEvA7YMkPzsaE/8qoJBCyob3qz32g+BaCoJesH4+daLq2sh5OqcCWD
qTlc8Pue0/qg4elF1rHjcJPDtCr01GwAM+De4GBnRpYD5I6sT7LNyUORU7c/ PTQ91zGyRt+rSN8GfRiGwKYIyDt64hBEQzivEchAALLLNcPBlo6ECMQUjcUE
wWKAANmBaDu1qvTSHgVJgfoQlW4ohDDp9EBcETtJR4FGu8fSzM0z1W/sYh4f sAsyg1MjHVISeVQCwgdHUbyF6i0KJX1nuc5hMzmEgEBDrq1kdhkp9F7mtKtr
6NIiqSsGN3rEU35lp3pQ9Ri5xaesXS0+MUjdIk+Ohp9mWsjgoByKY8qigw4j Lmsr4A83Dftyw0YKOtAqV1OmI0Zh6VkkAi6m6tghLrNIV+zmKJZUV8gmVHG3
TEN5kmdMTWimCEhBqW5PHcqWPFAOGiCArmgbzJCM+/ydWgM3BqQFF9fcVFr4 Bqtgm7gVTFurSjVKO0KTDqHDMKLxPY4pdZvGLtv7ESeyQGUmQsOqcYoPTg3V
HS5yv5kXE+mJBIaPLAXXxgmcJ8GTVCbNk0ILLnMN/nwgfrsMtOhumHXR2Saw LKRUcCYOEfgLrmRxOwsd0w/uV29U1nmuv9BMt/5gy9bplMzxQFXxp96HxLxV
NbfjL01ecn0A5cQlt65Us+ca0NOFjUBaz0g6JQ9iW+cOLjUPvSnF2biQC+PM BqkWcmGlXSerSIcgpnaSz2CazE5wYgfD/h51v3rUoca0VKSzDvD2txt1z+3v
SC58HMRyYkV5E0adZx8Umi7vw2HXFAOUVsuw6JsBIXIt0Z3rnji4WlYjLvbH Aff/EXBPzPYo/5uNt8Oj8qitP/n3+ZQaeClXfRfP2ffDxISbPXENZ84NOyLZ
LzW+VXunboerRQ+Ir1aNOKUMdzX2w9N9Ci0RGTfxpYFyAIdBPBdUShDRvqNf EzcjQOcYew04ZATGenBzz0oen4DEFk4kQHstgFeAqcPioz1YcOqB9Rtdd/V0
HViPuePzgkTJxF1z0RsSAnUBugZ2zTxcgV28zzPDb8kuKl+dqjxuJJrHEI4T 31jv4h5PsGedRbT5WxBABrGTGJKKRPRHAEZAWzE/YN9rp0+UDYeIN7ke8XLS
YsHWpUpRClaO6j8VSeBtOOzlQk+Cwl0x4L4HppoknnWp5Lk2dDDK5/VKJV5k TWpEL2WDoeMHcmPSpzzSOGDiHuIlAzMHUG8Rql7XfQL3oPUj4Dij4oTRow6n
BYBymy9Yro4q1YFGxaX3YAKQNf2csQw+gS/55RIXJ+wytfPBNXVTztgUSh7W OdOMBoSwxGQrzN407JrxXdKP73SxM9Ri1M3IeB8Svv8wMLYkSOzbKJqI6EDn
U1JQhZrnIpJ5nmG+dotgE1UqvSjQeeCq5yH6fCRbzWNpuqbbMv0FCJHFDDCB KRPg5JQ5jX8otj8eN7/X2xfbHJrg2zd1NSHqE8TJv55+O5in0CjXQ1QkIcNa
EvWMwPPV9bldSjGJyn5GHeYXtPic8QSZjitD2g4jedg6HrYepeKMLacL/J9n 5AXlyMPPT+6nYfYjtB/PdkCJz9URl41HQviq35tw0TOcZwyxOfJ4znWIs0/D
IbihfaYPO+DLjxnG5MjAdyPVrKa1Ob/SBEOQcDN8QhlrbclhgGm4QUww3TPX AJZLf0+2pgsQqi/jE64OnYpGl9tG1Rds1hTl9MXhobdPMpRl0pfVH+jSNG7o
J+hCKpH7DADpsUPfTrogV051gJU1SymcyfikeXTmR5xm97GURoxlMuBivg43 HDqeYpXMyrg7QIKaQiRDFPVdhEdvVCMbiotDGPeLKBVcJr7Hb7LqD7+eehxx
M42y2dAPihOXZigFh9+dpdvF06rJtlpgyqmV7lJHOopRozkWXYAcUGjYXrIs X93odPy+NOC8v0MKoE9+Ghsc7LtQvYnzAbmAGIUsXydQ35NUXzPVov4a8OKT
EBim1IjJbojJ6rwRvGE0Msdld966yvG5+iFFXEOE8DhBP1vkGyG6j8q8Dzyc YLUZnbajEfnArbYlxqpoVtlXmogBmFgqTsUSmGdWSCrZqigIeWxrOqtPBm9c
cfODBm/R5DxJiS5oCN6nIenxpZguexYezavrs9U4ieR8+f7y247hlbJe9tLl RxqGijuq6aAXSTmBdF6XGp6p9bL0Q9QADXmTmQquiQ5nKOI26BU1jJyVcGsW
nMpg8V/JvQsQ5RUAAA== gBHdvIBPj9Ki6MEs7+obd+pH1/WiT/egx1AqwGcY7jKKkRlPsXpcl+6I0G9j
N1S65uAFcgp7IAkA1XbKcc9lkgJxKnJpL48rNmFtchVKbRuyk5Sl0pT/BOHi
vIsKGtU+6jsrSWPoXjvAGAQPAlZlZWMqs9wchfamR6AitqRdH7OtQjr/EUwV
VEeOxCmErDyBZzLUHbH3jVD3u0D3XeD2HYH2bRD2TbH13gSBCvPtUPX1O9+B
p4fFt0bSewA6aEARFCZv69IErIyqAAugITR5A+LT0fcEYXi0h7TgChzHggXk
diEntovJ6cEJMzIfcXKm8Gv4fDvj5JbAzbyv1If3yl8P98Li7duL0/OrK9BX
zeF4dTtGl2MClBN365yxZ96yU96pR7LXxcpkckGzg827euJoQEstkeFwKs5G
o9SQMuEGmuSw9LoC+iYybs039pQDIIbgmVIpgUZLtAysoXiMM1teEFyy5t46
xBsSAnUBcQ3b5f2wPIDwOPX9OfBF5ctCE/CWiDvKYFKwc9g6VClKwXBxTEUS
9q5Y7eH1GcpHByKJprKfh+AZl0q+pHAlmDK9WqngF0CMVQ8GEg5XM9waDq0J
OEFmFroNp7vwDk066MUJO1zBMOGM2i1nbFAlXoGFpKAK1U+2wfFmFwKB2yJU
YdTqOD3P+suR3fn6aLgebk3ovRT6Te8ucFwHAE3tw/Gw/HyXG2UbTQ12vAjA
AzQQk9/wqxQjRrqhU+5CFYbB2f6lRzQzZw7k78ETxNA2ehI7IMtX0aJBkJbv
vLYXNiRKTLWAGCKiui5GxlEWmk3bgj1EIcew93vXb83nQsVcRiNQeJZhSBDF
2ZYFphkji68utvy2KYBGvefNqAKWEuIYgALX9rHK0duoojm9ubbmSo0gAfGL
neybXn9mjLwK2JUzLdyfbYgU31cQ+EVTIAEIBo1GGNIDB7Y+MO33wXUAStVm
2Bx3jjK+r4VIGJOTUxhcDEdk+jPcaMH1LUO1MGD6hA6bnaVoops46G4DZNq/
76QLvcbQKzdhdbazmt6MQUSfPjv9ODK8UmbDXrp3paK4dxDePevz2z/n4Y4V
LvwWed0h5SeCgMuA5xljommJ5JXfoCxwFxNfjN+C2n0T7djROn4J6piGxSfH
n+ieyY9VZPJlsv+iUJw0jC/O4qRBiH/G8UOPKRvGXsJv2uCaBC0LTZDqLh9g
0MIy8k/PbRrPDtjaH9WpNEc0BIM9Mz5WXBT/iFUQUuHEU1RyybLRayncRrcz
8P6MpIcgTZyPrS+YmcAo3W5yB+1Dha/Gv0z+CziAZT/rKQAA
--> -->
</rfc> </rfc>
 End of changes. 22 change blocks. 
131 lines changed or deleted 260 lines changed or added

This html diff was produced by rfcdiff 1.48.