182158b5c0
* fix: Also extract document names from XML seriesInfo attributes The old code only looked in the anchor string for the document names of references, which doesn't work if the anchor uses a mnemonic. This caused lots of missed references for many documents. * No need to import lxml anymore * Add tests * Handle xinclude to bibxml URLs * Wrap line * Apply suggestion from @rjsparks * Undo erroneous additions * Address suggestion from @rjsparks
239 lines
13 KiB
XML
239 lines
13 KiB
XML
<?xml version='1.0'?>
|
|
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
|
|
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="exp" submissionType="independent" ipr="trust200902" docName="draft-test-references-00" version="3">
|
|
<front>
|
|
<title>Test Draft with References</title>
|
|
<author fullname="Alfred Person" initials="A." surname="Person" role="editor">
|
|
<address>
|
|
<address>
|
|
<email>aperson@example.com</email>
|
|
</address>
|
|
</address>
|
|
</author>
|
|
</front>
|
|
<middle>
|
|
<section>
|
|
<name>First Section</name>
|
|
<t>
|
|
Text here.
|
|
<xref target="RFC0001">RFC0001</xref>
|
|
<xref target="RFC0255">RFC0255</xref>
|
|
<xref target="bcp6">BCP6</xref>
|
|
<xref target="RFC1207">FYI7</xref>
|
|
</t>
|
|
</section>
|
|
</middle>
|
|
<back>
|
|
<references>
|
|
<name>Normative References</name>
|
|
<reference anchor="RFC0001" target="https://www.rfc-editor.org/info/rfc1">
|
|
<front>
|
|
<title>Host Software</title>
|
|
<author initials="S." surname="Crocker" fullname="S. Crocker">
|
|
<organization/>
|
|
</author>
|
|
<date year="1969" month="April"/>
|
|
</front>
|
|
<seriesInfo name="RFC" value="1"/>
|
|
<seriesInfo name="DOI" value="10.17487/RFC0001"/>
|
|
</reference>
|
|
<reference anchor="MNEMONIC" target="https://www.rfc-editor.org/info/rfc2">
|
|
<front>
|
|
<title>Cloud Software</title>
|
|
<author initials="D." surname="Crocker" fullname="D. Crocker">
|
|
<organization/>
|
|
</author>
|
|
<date year="1969" month="April"/>
|
|
</front>
|
|
<seriesInfo name="RFC" value="2"/>
|
|
<seriesInfo name="DOI" value="10.17487/RFC0002"/>
|
|
</reference>
|
|
</references>
|
|
<references>
|
|
<name>Informative References</name>
|
|
<xi:include href='https://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-teas-pcecc-use-cases-00.xml'/>
|
|
<xi:include href='https://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-teas-pcecc-use-cases.xml'/>
|
|
<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-sipcore-multiple-reasons-00.xml" />
|
|
<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-sipcore-multiple-reasons.xml" />
|
|
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml9/reference.BCP.0014.xml" />
|
|
<reference anchor='RFC0255' target='https://www.rfc-editor.org/info/rfc255'>
|
|
<front>
|
|
<title>Status of network hosts</title>
|
|
<author initials='E.' surname='Westheimer' fullname='E. Westheimer'>
|
|
<organization/>
|
|
</author>
|
|
<date year='1971' month='October'/>
|
|
</front>
|
|
<seriesInfo name='RFC' value='255'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC0255'/>
|
|
</reference>
|
|
<reference anchor="CONSISTENCY">
|
|
<front>
|
|
<title>Key Consistency and Discovery</title>
|
|
<author fullname="Alex Davidson" initials="A." surname="Davidson">
|
|
<organization>Brave Software</organization>
|
|
</author>
|
|
<author fullname="Matthew Finkel" initials="M." surname="Finkel">
|
|
<organization>The Tor Project</organization>
|
|
</author>
|
|
<author fullname="Martin Thomson" initials="M." surname="Thomson">
|
|
<organization>Mozilla</organization>
|
|
</author>
|
|
<author fullname="Christopher A. Wood" initials="C. A." surname="Wood">
|
|
<organization>Cloudflare</organization>
|
|
</author>
|
|
<date day="17" month="August" year="2022"/>
|
|
<abstract>
|
|
<t> This document describes the key consistency and correctness
|
|
requirements of protocols such as Privacy Pass, Oblivious DoH, and
|
|
Oblivious HTTP for user privacy. It discusses several mechanisms and
|
|
proposals for enabling user privacy in varying threat models. In
|
|
concludes with discussion of open problems in this area.
|
|
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name="Internet-Draft" value="draft-wood-key-consistency-03"/>
|
|
</reference>
|
|
<referencegroup anchor="bcp6">
|
|
<reference anchor='RFC1930' target='https://www.rfc-editor.org/info/rfc1930'>
|
|
<front>
|
|
<title>Guidelines for creation, selection, and registration of an Autonomous System (AS)</title>
|
|
<author initials='J.' surname='Hawkinson' fullname='J. Hawkinson'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='T.' surname='Bates' fullname='T. Bates'>
|
|
<organization/>
|
|
</author>
|
|
<date year='1996' month='March'/>
|
|
<abstract>
|
|
<t>This memo discusses when it is appropriate to register and utilize an Autonomous System
|
|
(AS), and lists criteria for such. This document specifies an Internet Best Current
|
|
Practices for the Internet Community, and requests discussion and suggestions for
|
|
improvements.
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name='BCP' value='6'/>
|
|
<seriesInfo name='RFC' value='1930'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC1930'/>
|
|
</reference>
|
|
<reference anchor='RFC6996' target='https://www.rfc-editor.org/info/rfc6996'>
|
|
<front>
|
|
<title>Autonomous System (AS) Reservation for Private Use</title>
|
|
<author initials='J.' surname='Mitchell' fullname='J. Mitchell'>
|
|
<organization/>
|
|
</author>
|
|
<date year='2013' month='July'/>
|
|
<abstract>
|
|
<t>This document describes the reservation of Autonomous System Numbers (ASNs) that are for
|
|
Private Use only, known as Private Use ASNs, and provides operational guidance on their
|
|
use. This document enlarges the total space available for Private Use ASNs by
|
|
documenting the reservation of a second, larger range and updates RFC 1930 by replacing
|
|
Section 10 of that document.
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name='BCP' value='6'/>
|
|
<seriesInfo name='RFC' value='6996'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC6996'/>
|
|
</reference>
|
|
<reference anchor='RFC7300' target='https://www.rfc-editor.org/info/rfc7300'>
|
|
<front>
|
|
<title>Reservation of Last Autonomous System (AS) Numbers</title>
|
|
<author initials='J.' surname='Haas' fullname='J. Haas'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='J.' surname='Mitchell' fullname='J. Mitchell'>
|
|
<organization/>
|
|
</author>
|
|
<date year='2014' month='July'/>
|
|
<abstract>
|
|
<t>This document reserves two Autonomous System Numbers (ASNs) at the end of the 16-bit and
|
|
32-bit ranges, described in this document as "Last ASNs", and provides
|
|
guidance to implementers and operators on their use. This document updates Section 10 of
|
|
RFC 1930.
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name='BCP' value='6'/>
|
|
<seriesInfo name='RFC' value='7300'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC7300'/>
|
|
</reference>
|
|
</referencegroup>
|
|
</references>
|
|
<references>
|
|
<name>Mysterious References</name>
|
|
<!-- Unrecognized references section name -->
|
|
<reference anchor='RFC1207' target='https://www.rfc-editor.org/info/rfc1207'>
|
|
<front>
|
|
<title>FYI on Questions and Answers: Answers to commonly asked "experienced Internet user"
|
|
questions
|
|
</title>
|
|
<author initials='G.S.' surname='Malkin' fullname='G.S. Malkin'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='A.N.' surname='Marine' fullname='A.N. Marine'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='J.K.' surname='Reynolds' fullname='J.K. Reynolds'>
|
|
<organization/>
|
|
</author>
|
|
<date year='1991' month='February'/>
|
|
<abstract>
|
|
<t>This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by
|
|
the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is
|
|
to document the most commonly asked questions and answers in the Internet. This memo
|
|
provides information for the Internet community. It does not specify any standard.
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name='FYI' value='7'/>
|
|
<seriesInfo name='RFC' value='1207'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC1207'/>
|
|
</reference>
|
|
</references>
|
|
<references title="Malformed Normative References">
|
|
<!-- title attribute was for references title was removed for v3, but should be recognized -->
|
|
<reference anchor='RFC4086' target='https://www.rfc-editor.org/info/rfc4086'>
|
|
<front>
|
|
<title>Randomness Requirements for Security</title>
|
|
<author initials='D.' surname='Eastlake 3rd' fullname='D. Eastlake 3rd'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='J.' surname='Schiller' fullname='J. Schiller'>
|
|
<organization/>
|
|
</author>
|
|
<author initials='S.' surname='Crocker' fullname='S. Crocker'>
|
|
<organization/>
|
|
</author>
|
|
<date year='2005' month='June'/>
|
|
<abstract>
|
|
<t>Security systems are built on strong cryptographic algorithms that foil pattern analysis
|
|
attempts. However, the security of these systems is dependent on generating secret
|
|
quantities for passwords, cryptographic keys, and similar quantities. The use of
|
|
pseudo-random processes to generate secret quantities can result in pseudo-security. A
|
|
sophisticated attacker may find it easier to reproduce the environment that produced the
|
|
secret quantities and to search the resulting small set of possibilities than to locate the
|
|
quantities in the whole of the potential number space.
|
|
</t>
|
|
<t>Choosing random quantities to foil a resourceful and motivated adversary is surprisingly
|
|
difficult. This document points out many pitfalls in using poor entropy sources or
|
|
traditional pseudo-random number generation techniques for generating such quantities. It
|
|
recommends the use of truly random hardware techniques and shows that the existing hardware
|
|
on many systems can be used for this purpose. It provides suggestions to ameliorate the
|
|
problem when a hardware solution is not available, and it gives examples of how large such
|
|
quantities need to be for some applications. This document specifies an Internet Best
|
|
Current Practices for the Internet Community, and requests discussion and suggestions for
|
|
improvements.
|
|
</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name='BCP' value='106'/>
|
|
<seriesInfo name='RFC' value='4086'/>
|
|
<seriesInfo name='DOI' value='10.17487/RFC4086'/>
|
|
</reference>
|
|
</references>
|
|
</back>
|
|
</rfc>
|