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" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 3.2. <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
3) --> -editorial-rswg-svgsinrfcs-04" category="info" submissionType="editorial" number
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft ="9896" obsoletes="7996" tocInclude="true" sortRefs="true" symRefs="true" versio
-editorial-rswg-svgsinrfcs-04" category="info" submissionType="editorial" obsole n="3">
tes="7996" tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.30.2 -->
<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 38
<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="December"/>
<keyword>Internet-Draft</keyword> <keyword>SVG</keyword>
<abstract> <abstract>
<?line 58?>
<t>This document sets policy for the inclusion of SVGs in the definitive version <t>This document defines policy for the inclusion of Scalable Vector Graphics (S
s of RFCs and relevant publication formats. It contains policy requirements from VGs) in the definitive versions of RFCs and relevant publication formats. It con
RFC 7996 and removes all requirements related to using a specific SVG profile o tains policy requirements from RFC 7996 but removes all requirements related to
r specific implementation code. It also makes the RFC Publication Center (RPC) r using a specific SVG profile or implementation code. It also makes the RFC Produ
esponsible for implementation decisions regarding SVGs.</t> ction Center (RPC) responsible for decisions about SVG tooling and implementatio
n.</t>
<t>This document obsoletes RFC 7996.</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?>
<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 defines policy for the inclusion of Scalable Vector Graph
aphics) in the definitive versions of RFCs and relevant publication formats. It ics (SVGs) in the definitive versions of RFCs and relevant publication formats d
contains policy requirements taken from <xref target="RFC7996"/> and removes all efined in <xref target="RFC9720"/>. It contains policy requirements taken from <
requirements related to using a specific SVG profile or specific implementation xref target="RFC7996"/> but removes all requirements related to using a specific
code.</t> SVG profile or implementation 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 C, and must adhere to the policy requirements in this document.</t> <t>Decisions about SVG tooling and implementation are made by the RPC 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. In particular:
</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 <xref target="RFC9720"/>. Publication formats should present the versions be st 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.972
<front> 0.xml"/>
<title>SVG Drawings for RFCs: SVG 1.2 RFC</title> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.799
<author fullname="N. Brownlee" initials="N." surname="Brownlee"/> 6.xml"/>
<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>
</back> </back>
<!-- ##markdown-source:
H4sIAAAAAAAAA71YTY/cNhK961cQzmHtxbTaiBcbuE+enewaE8COMWNkjgtK
olrMUKSWpFrTCfzf91WRUqvHHse7hxyMsSSSVfXeqw/2ZrMpoo5G7cTtL2+D
0Fbc/OsqFI2rrezxtvGyjRvV6Oi8lmbjw7TfhMM+aOvbOmxe/q04KDuqXSHE
3rtx2Imb27u3eIrHAfv/Oe8Ut9Er2Ys75++13Yu3tBjLeqnNTtCxb3BgtlQ6
v8c36etuJ7oYh7DbbmklvdEHVWoVW1q0pRfbyrspqC0dsiU/dOzGaieeSaMe
dJDWKu9C0FvdrFx/hpVGRhUiVs420taydv32q5u3lXEVeWS3p5dl3zwrQpS2
+bc0ziL66EdVHHbiVeGq4IyCtZ344fXrvxd68Pw5xO9fvnz98vviftqJaxuV
typufiTUi1rCNW1bV4Sx6jWccPYjo7rwUdyr4+R8A/g3xGAhx9g5T2xs8E9g
OyxeluKGYuA3iddLjm71GmBKq3+TEUZ2JAJxq7xWQVw5G0YTibNEJi9XM2+1
+py3len3pfgH2LFGqZX19+qgzfmHM/trE5bWllVe+2ZPb4mgczs/leKd7AD6
cWXmJyXt2evPg/zgXTPW9CyuFMG/Nv1rn/a+AaltW34tznel+Ni5Pji7sv9O
euB29uHJMPv4xrgJLng3HEuIoCis8z0WHpBcRUE6WB4F+U46ov+C9nTSifts
aSfuXl3x45zjtTSyMkr8omqEgSSUQ6frkNZIv1fxlG/TNJXTK86yjzdbWKHc
uru8/lZjeBSXda2gsEobHY8oAcgN6Zsgfj4of9Bq+iPDMLcN867NftSNMtqq
sC2KzWYjZBWilzWw+thBzahaYw8IRVAxiMEZXR8FYBOxU6CpNiOlkHDtUuzo
Q6NabTUBK+AVrQi0hOqggGXhlVEHiVOHscKJTJ1IZIRSXEdROxtRCRaLXv1n
1F6RJ0G03vWsNKIrn9e7AxJLGnO+FIZQjxoRnYCjyDcpwqBq3eqaHBaDd60G
eQhoea/7wfD25FbtGsU+SRMcaus97FCMLPWV+0nr4vnNh6sXsBsGBK1JGITW
ozMbmEqoeLUHD+QZ4VcmDnrdNEYVxXdUvpZs+v8Yef6UQF/8OWRFAGYTZb//
nlPs06c/h7WioNWdDKJSilA/KOMGHFwdKZUuOHx0T9OIO6SBuFMV12aHGjOS
v9j+6VNJwP8B3zp8RjmUkmlFHACGwkDQTymBip06YtdRTAQ2x67YQ8KXCAcp
ZxAGwiVyQdwDe40lSQcuqNPBF6IaI51zRPNXwrooKjdaBuExI3F2oe6k3Suh
TGYEplle587DA6tUk5gK4zAAuCU3UjUj19BZ+tFStcIGdPE9/U1eJjuBPZNG
7y3OmjAw8ClfkhNrdpUFJWXJh7TwZrUwUf8twLPtXjYsJ0cZQFoBOBzIB6iE
dvcYK4RsOoXFCPZ/cO+vKQ8J1SonKCGWx0I6rFNmEOphMEgiUAq6azVE0TvY
qo2S3hwTiaFzI7TKFCZpOGvIgwHiWyJjrmSczynFpdg714hWErCqbYmlfFSV
Q4cXMoSRgqOtjQq110Oca0E+KmAimlA7OlSofRfnYCgfo6udgdZyXbjg3DyG
qHoeOXVE8cHxdALh3Y5m7XjCgwKK6iHOagM+cB5AoDz1Y3+RgDx5XlO6BU6N
RTO0v1wwJ9IIrdlRzAl9Bgk1mfIXnY4KX6sku1ee2Zi3McpG95ocxcid9gAk
CPaUI88DKi3UdiHQWu+3hiHqUYeSggblOzkEigbGZfMrnMsl0lEJdBNn70Fi
CE3AA5JGB8gCWlR1Z51x++MLLhTsvM1IQW+aT1H2RCFXdi33XvZ/gVGMbZQI
WEd4SIPQVUNAXfeSExAe5uXLlWUFdRh56phpsw1t500j/T9EEljOmQmllJJl
bLSCbJAngasiHHfJN+y/mNOLEwMC6jDRJK+p7KXutdCStpFw7i2GVorVyPp+
qTlc8Pue0/qg4elF1rHjcJPDtCr01GwAM+De4GBnRpYD5I6sT7LNyUORU7c/
wWKAANmBaDu1qvTSHgVJgfoQlW4ohDDp9EBcETtJR4FGu8fSzM0z1W/sYh4f
6NIiqSsGN3rEU35lp3pQ9Ri5xaesXS0+MUjdIk+Ohp9mWsjgoByKY8qigw4j
TEN5kmdMTWimCEhBqW5PHcqWPFAOGiCArmgbzJCM+/ydWgM3BqQFF9fcVFr4
HS5yv5kXE+mJBIaPLAXXxgmcJ8GTVCbNk0ILLnMN/nwgfrsMtOhumHXR2Saw
NbfjL01ecn0A5cQlt65Us+ca0NOFjUBaz0g6JQ9iW+cOLjUPvSnF2biQC+PM
SC58HMRyYkV5E0adZx8Umi7vw2HXFAOUVsuw6JsBIXIt0Z3rnji4WlYjLvbH
LzW+VXunboerRQ+Ir1aNOKUMdzX2w9N9Ci0RGTfxpYFyAIdBPBdUShDRvqNf
HViPuePzgkTJxF1z0RsSAnUBugZ2zTxcgV28zzPDb8kuKl+dqjxuJJrHEI4T
YsHWpUpRClaO6j8VSeBtOOzlQk+Cwl0x4L4HppoknnWp5Lk2dDDK5/VKJV5k
BYBymy9Yro4q1YFGxaX3YAKQNf2csQw+gS/55RIXJ+wytfPBNXVTztgUSh7W
U1JQhZrnIpJ5nmG+dotgE1UqvSjQeeCq5yH6fCRbzWNpuqbbMv0FCJHFDDCB
EvWMwPPV9bldSjGJyn5GHeYXtPic8QSZjitD2g4jedg6HrYepeKMLacL/J9n
IbihfaYPO+DLjxnG5MjAdyPVrKa1Ob/SBEOQcDN8QhlrbclhgGm4QUww3TPX
J+hCKpH7DADpsUPfTrogV051gJU1SymcyfikeXTmR5xm97GURoxlMuBivg43
M42y2dAPihOXZigFh9+dpdvF06rJtlpgyqmV7lJHOopRozkWXYAcUGjYXrIs
EBim1IjJbojJ6rwRvGE0Msdld966yvG5+iFFXEOE8DhBP1vkGyG6j8q8Dzyc
cfODBm/R5DxJiS5oCN6nIenxpZguexYezavrs9U4ieR8+f7y247hlbJe9tLl
nMpg8V/JvQsQ5RUAAA==
</rfc> </rfc>
 End of changes. 23 change blocks. 
139 lines changed or deleted 55 lines changed or added

This html diff was produced by rfcdiff 1.48.