From 7732815dcaa2d3cf5a8733ae995fb84060b2e20f Mon Sep 17 00:00:00 2001 From: Kesara Rathnayake Date: Fri, 28 Feb 2025 14:27:18 +1300 Subject: [PATCH 1/3] chore: Run yestests (pre-changes) --- tests/valid/docfile.html | 16 ++++++++-------- tests/valid/draft-miek-test.html | 15 +++++++-------- tests/valid/draft-template.html | 15 +++++++-------- tests/valid/indexes.pages.text | 16 ++++++++-------- tests/valid/indexes.prepped.xml | 8 ++++---- tests/valid/indexes.text | 6 +++--- tests/valid/indexes.v3.html | 12 ++++++------ tests/valid/manpage.txt | 10 +++++----- tests/valid/rfc7911.html | 15 +++++++-------- tests/valid/rfc99999.html | 15 +++++++-------- tests/valid/sourcecode.pages.text | 20 ++++++++++---------- tests/valid/sourcecode.prepped.xml | 8 ++++---- tests/valid/sourcecode.text | 6 +++--- tests/valid/sourcecode.v3.html | 12 ++++++------ 14 files changed, 85 insertions(+), 89 deletions(-) diff --git a/tests/valid/docfile.html b/tests/valid/docfile.html index eb75cea8..c1d325ff 100644 --- a/tests/valid/docfile.html +++ b/tests/valid/docfile.html @@ -4,15 +4,15 @@ -Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.25.0 +Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.27.0 - - + + @@ -24,7 +24,7 @@ Xml2rfc Vocabulary V3 Schema -January 2025 +February 2025 xml2rfc(1) @@ -39,7 +39,7 @@
xml2rfc(1)
Published:
- +
Author:
@@ -49,7 +49,7 @@
-

Xml2rfc Vocabulary Version 3 Schema
xml2rfc release 3.25.0

+

Xml2rfc Vocabulary Version 3 Schema
xml2rfc release 3.27.0

Abstract

@@ -371,7 +371,7 @@

The latest version of this documentation is available in HTML form at https://ietf-tools.github.io/xml2rfc/.

- This documentation applies to xml2rfc version 3.25.0.

+ This documentation applies to xml2rfc version 3.27.0.

@@ -6396,7 +6396,7 @@

The following variables are available for use in an xml2rfc - manpage Jinja2 template, as of xml2rfc version 3.25.0:

+ manpage Jinja2 template, as of xml2rfc version 3.27.0:

{{ bare_latin_tags }}:
diff --git a/tests/valid/draft-miek-test.html b/tests/valid/draft-miek-test.html index cfa130f0..d148465f 100644 --- a/tests/valid/draft-miek-test.html +++ b/tests/valid/draft-miek-test.html @@ -16,7 +16,7 @@ This version is adapted to work with "xml2rfc" version 2.x. ' name="description"> - + @@ -26,21 +26,20 @@ @@ -417,7 +416,7 @@ /* Fix PDF info block run off issue */ @media print { #identifiers dd { - float: none; + max-width: 100%; } } #identifiers .authors .author { diff --git a/tests/valid/draft-template.html b/tests/valid/draft-template.html index 676195ce..3699f3b1 100644 --- a/tests/valid/draft-template.html +++ b/tests/valid/draft-template.html @@ -11,25 +11,24 @@ Insert an abstract: MANDATORY. This template is for creating an Internet Draft. " name="description"> - + @@ -406,7 +405,7 @@ /* Fix PDF info block run off issue */ @media print { #identifiers dd { - float: none; + max-width: 100%; } } #identifiers .authors .author { diff --git a/tests/valid/indexes.pages.text b/tests/valid/indexes.pages.text index 097ee7d1..6ee1a06d 100644 --- a/tests/valid/indexes.pages.text +++ b/tests/valid/indexes.pages.text @@ -3,9 +3,9 @@ Network Working Group H. Person, Ed. -Internet-Draft January 23, 2025 +Internet-Draft February 28, 2025 Intended status: Experimental -Expires: July 27, 2025 +Expires: September 1, 2025 xml2rfc index tests @@ -26,7 +26,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 27, 2025. + This Internet-Draft will expire on September 1, 2025. Copyright Notice @@ -53,9 +53,9 @@ Table of Contents -Person Expires July 27, 2025 [Page 1] +Person Expires September 1, 2025 [Page 1] -Internet-Draft xml2rfc index tests January 2025 +Internet-Draft xml2rfc index tests February 2025 This is another section! @@ -109,9 +109,9 @@ Index -Person Expires July 27, 2025 [Page 2] +Person Expires September 1, 2025 [Page 2] -Internet-Draft xml2rfc index tests January 2025 +Internet-Draft xml2rfc index tests February 2025 E @@ -165,4 +165,4 @@ Author's Address -Person Expires July 27, 2025 [Page 3] +Person Expires September 1, 2025 [Page 3] diff --git a/tests/valid/indexes.prepped.xml b/tests/valid/indexes.prepped.xml index 9855035b..026f37a5 100644 --- a/tests/valid/indexes.prepped.xml +++ b/tests/valid/indexes.prepped.xml @@ -1,6 +1,6 @@ - - + + @@ -20,7 +20,7 @@ - +
Status of This Memo @@ -41,7 +41,7 @@ material or to cite them other than as "work in progress." - This Internet-Draft will expire on 27 July 2025. + This Internet-Draft will expire on 1 September 2025.
diff --git a/tests/valid/indexes.text b/tests/valid/indexes.text index 20b06f33..fcac8d11 100644 --- a/tests/valid/indexes.text +++ b/tests/valid/indexes.text @@ -3,9 +3,9 @@ Network Working Group H. Person, Ed. -Internet-Draft January 23, 2025 +Internet-Draft February 28, 2025 Intended status: Experimental -Expires: July 27, 2025 +Expires: September 1, 2025 xml2rfc index tests @@ -26,7 +26,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 27, 2025. + This Internet-Draft will expire on September 1, 2025. Copyright Notice diff --git a/tests/valid/indexes.v3.html b/tests/valid/indexes.v3.html index 9a259cab..4373ee09 100644 --- a/tests/valid/indexes.v3.html +++ b/tests/valid/indexes.v3.html @@ -6,7 +6,7 @@ xml2rfc index tests - + @@ -19,11 +19,11 @@ Internet-Draft xml2rfc index tests -January 2025 +February 2025 Person -Expires July 27, 2025 +Expires September 1, 2025 [Page] @@ -36,12 +36,12 @@
indexes-00
Published:
- +
Intended Status:
Experimental
Expires:
-
+
Author:
@@ -71,7 +71,7 @@

time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

- This Internet-Draft will expire on July 27, 2025.

+ This Internet-Draft will expire on September 1, 2025.

- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
+ Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[IDGUIDE]
-Housley, R., "Guidelines to Authors of Internet-Drafts", , <https://www.ietf.org/id-info/guidelines.html>.
+Housley, R., "Guidelines to Authors of Internet-Drafts", , <https://www.ietf.org/id-info/guidelines.html>.
[INTRO-TO-V3]
-Levkowetz, H., "Introduction to xml2rfc Version 3", , <https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html>.
+Levkowetz, H., "Introduction to xml2rfc Version 3", , <https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html>.
[LINKRELATIONS]
-IANA, "Link Relations", <https://www.iana.org/assignments/link-relations/link-relations.xhtml>.
+IANA, "Link Relations", <https://www.iana.org/assignments/link-relations/link-relations.xhtml>.
[RFC2026]
-Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, , <https://www.rfc-editor.org/info/rfc2026>.
+Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, , <https://www.rfc-editor.org/info/rfc2026>.
[RFC2397]
-Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, , <https://www.rfc-editor.org/info/rfc2397>.
+Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, , <https://www.rfc-editor.org/info/rfc2397>.
[RFC3339]
-Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, , <https://www.rfc-editor.org/info/rfc3339>.
+Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, , <https://www.rfc-editor.org/info/rfc3339>.
[RFC3966]
-Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, , <https://www.rfc-editor.org/info/rfc3966>.
+Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, , <https://www.rfc-editor.org/info/rfc3966>.
[RFC3986]
-Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, , <https://www.rfc-editor.org/info/rfc3986>.
+Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, , <https://www.rfc-editor.org/info/rfc3986>.
[RFC5234]
-Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, , <https://www.rfc-editor.org/info/rfc5234>.
+Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, , <https://www.rfc-editor.org/info/rfc5234>.
[RFC6068]
-Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, , <https://www.rfc-editor.org/info/rfc6068>.
+Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, , <https://www.rfc-editor.org/info/rfc6068>.
[RFC6087]
-Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, , <https://www.rfc-editor.org/info/rfc6087>.
+Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, , <https://www.rfc-editor.org/info/rfc6087>.
[RFC7322]
-Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, , <https://www.rfc-editor.org/info/rfc7322>.
+Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, , <https://www.rfc-editor.org/info/rfc7322>.
[RFC7669]
-Levine, J., "Assigning Digital Object Identifiers to RFCs", RFC 7669, DOI 10.17487/RFC7669, , <https://www.rfc-editor.org/info/rfc7669>.
+Levine, J., "Assigning Digital Object Identifiers to RFCs", RFC 7669, DOI 10.17487/RFC7669, , <https://www.rfc-editor.org/info/rfc7669>.
[RFC7841]
-Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., "RFC Streams, Headers, and Boilerplates", RFC 7841, DOI 10.17487/RFC7841, , <https://www.rfc-editor.org/info/rfc7841>.
+Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., "RFC Streams, Headers, and Boilerplates", RFC 7841, DOI 10.17487/RFC7841, , <https://www.rfc-editor.org/info/rfc7841>.
[RFC7991]
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI 10.17487/RFC7991, , <https://www.rfc-editor.org/info/rfc7991>.
+Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI 10.17487/RFC7991, , <https://www.rfc-editor.org/info/rfc7991>.
[RFC7996]
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
+Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
[RFC7997]
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
+Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
[RFC7998]
-Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3 Preparation Tool Description", RFC 7998, DOI 10.17487/RFC7998, , <https://www.rfc-editor.org/info/rfc7998>.
+Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3 Preparation Tool Description", RFC 7998, DOI 10.17487/RFC7998, , <https://www.rfc-editor.org/info/rfc7998>.
[RNC]
-Clark, J., "RELAX NG Compact Syntax", <https://www.oasis-open.org/committees/relax-ng/compact-20021121.html>.
+Clark, J., "RELAX NG Compact Syntax", <https://www.oasis-open.org/committees/relax-ng/compact-20021121.html>.

diff --git a/tests/valid/draft-miek-test.html b/tests/valid/draft-miek-test.html index d148465f..4554f999 100644 --- a/tests/valid/draft-miek-test.html +++ b/tests/valid/draft-miek-test.html @@ -480,6 +480,10 @@ margin-bottom: 0.25em; } +.references .link { + display: inline-block; +} + /* index */ .index ul { margin: 0 0 0 1em; @@ -2489,7 +2493,7 @@

[VIM]
-Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
+Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
@@ -2500,11 +2504,11 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
[RFC4641]
-Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
+Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
diff --git a/tests/valid/draft-miek-test.v3.html b/tests/valid/draft-miek-test.v3.html index fd270824..d88acf91 100644 --- a/tests/valid/draft-miek-test.v3.html +++ b/tests/valid/draft-miek-test.v3.html @@ -16,7 +16,7 @@ This version is adapted to work with "xml2rfc" version 2.x. ' name="description"> - + @@ -1301,7 +1301,7 @@

[VIM]
-Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
+Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
@@ -1312,11 +1312,11 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
[RFC4641]
-Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
+Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
diff --git a/tests/valid/draft-template.html b/tests/valid/draft-template.html index 3699f3b1..35b5a4bc 100644 --- a/tests/valid/draft-template.html +++ b/tests/valid/draft-template.html @@ -469,6 +469,10 @@ margin-bottom: 0.25em; } +.references .link { + display: inline-block; +} + /* index */ .index ul { margin: 0 0 0 1em; @@ -2098,7 +2102,7 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
@@ -2109,35 +2113,35 @@

[DOI_10.1145_2975159]
-Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., Vahdat, A., and Association for Computing Machinery (ACM), "Jupiter rising", Communications of the ACM, vol. 59, no. 9, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
+Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., Vahdat, A., and Association for Computing Machinery (ACM), "Jupiter rising", Communications of the ACM, vol. 59, no. 9, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
[DOMINATION]
-Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
+Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
[I-D.iab-xml2rfc]
-Hoffman, P. E., "The "xml2rfc" Version 3 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfc-04, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfc-04>.
+Hoffman, P. E., "The "xml2rfc" Version 3 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfc-04, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfc-04>.
[I-D.iab-xml2rfcv2]
-Reschke, J., "The 'XML2RFC' version 2 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfcv2-00, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfcv2-00>.
+Reschke, J., "The 'XML2RFC' version 2 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfcv2-00, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfcv2-00>.
[I-D.narten-iana-considerations-rfc2434bis]
-Alvestrand, H. T. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://datatracker.ietf.org/doc/html/draft-narten-iana-considerations-rfc2434bis-09>.
+Alvestrand, H. T. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://datatracker.ietf.org/doc/html/draft-narten-iana-considerations-rfc2434bis-09>.
[RFC2629]
-Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
+Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
[RFC3552]
-Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
+Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
[SHARING]
-Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
+Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
diff --git a/tests/valid/draft-template.v3.html b/tests/valid/draft-template.v3.html index dcf61d0e..db12e514 100644 --- a/tests/valid/draft-template.v3.html +++ b/tests/valid/draft-template.v3.html @@ -11,7 +11,7 @@ Insert an abstract: MANDATORY. This template is for creating an Internet Draft. " name="description"> - + @@ -910,7 +910,7 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
@@ -921,35 +921,35 @@

[DOI_10.1145_2975159]
-Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., Vahdat, A., and Association for Computing Machinery (ACM), "Jupiter rising", Communications of the ACM, vol. 59, no. 9, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
+Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., Vahdat, A., and Association for Computing Machinery (ACM), "Jupiter rising", Communications of the ACM, vol. 59, no. 9, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
[DOMINATION]
-Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
+Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
[I-D.iab-xml2rfc]
-Hoffman, P. E., "The "xml2rfc" Version 3 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfc-04, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfc-04>.
+Hoffman, P. E., "The "xml2rfc" Version 3 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfc-04, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfc-04>.
[I-D.iab-xml2rfcv2]
-Reschke, J., "The 'XML2RFC' version 2 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfcv2-00, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfcv2-00>.
+Reschke, J., "The 'XML2RFC' version 2 Vocabulary", Work in Progress, Internet-Draft, draft-iab-xml2rfcv2-00, , <https://datatracker.ietf.org/doc/html/draft-iab-xml2rfcv2-00>.
[I-D.narten-iana-considerations-rfc2434bis]
-Alvestrand, H. T. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://datatracker.ietf.org/doc/html/draft-narten-iana-considerations-rfc2434bis-09>.
+Alvestrand, H. T. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://datatracker.ietf.org/doc/html/draft-narten-iana-considerations-rfc2434bis-09>.
[RFC2629]
-Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
+Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
[RFC3552]
-Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
+Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
[SHARING]
-Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
+Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
diff --git a/tests/valid/draft-v3-features.v3.html b/tests/valid/draft-v3-features.v3.html index c6078663..bd7fce54 100644 --- a/tests/valid/draft-v3-features.v3.html +++ b/tests/valid/draft-v3-features.v3.html @@ -13,7 +13,7 @@ This document tests features introduced in xml2rfc v3 vocabulary. " name="description"> - + @@ -4972,7 +4972,7 @@

Best Current Practice 45, <https://www.rfc-editor.org/info/bcp45>.
At the time of writing, this BCP comprises the following:
- Eggert, L. and S. Harris, "IETF Discussion List Charter", BCP 45, RFC 9245, DOI 10.17487/RFC9245, , <https://www.rfc-editor.org/info/rfc9245>.
+ Eggert, L. and S. Harris, "IETF Discussion List Charter", BCP 45, RFC 9245, DOI 10.17487/RFC9245, , <https://www.rfc-editor.org/info/rfc9245>.
[DUP]
@@ -4991,24 +4991,24 @@

[RFC7991]
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, , <https://www.rfc-editor.org/rfc/rfc7991>.
+Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, , <https://www.rfc-editor.org/rfc/rfc7991>.
[RFC7996]
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
+Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
[STD78]
Internet Standard 78, <https://www.rfc-editor.org/info/std78>.
At the time of writing, this STD comprises the following:
- Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, DOI 10.17487/RFC5343, , <https://www.rfc-editor.org/info/rfc5343>.
+ Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, DOI 10.17487/RFC5343, , <https://www.rfc-editor.org/info/rfc5343>.
- Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, DOI 10.17487/RFC5590, , <https://www.rfc-editor.org/info/rfc5590>.
+ Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, DOI 10.17487/RFC5590, , <https://www.rfc-editor.org/info/rfc5590>.
- Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, , <https://www.rfc-editor.org/info/rfc5591>.
+ Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, , <https://www.rfc-editor.org/info/rfc5591>.
- Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, , <https://www.rfc-editor.org/info/rfc6353>.
+ Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, , <https://www.rfc-editor.org/info/rfc6353>.
[STPETER]
@@ -5018,7 +5018,7 @@

[SVG11]
-Ferraiolo, J., 藤沢, 淳 (Fujisawa, J.), and D. Jackson, "Scalable Vector Graphics (SVG) 1.1 Specification", W3C Recommendation REC-SVG11-20030114, , <http://www.w3.org/TR/2003/REC-SVG11-20030114/>. +Ferraiolo, J., 藤沢, 淳 (Fujisawa, J.), and D. Jackson, "Scalable Vector Graphics (SVG) 1.1 Specification", W3C Recommendation REC-SVG11-20030114, , <http://www.w3.org/TR/2003/REC-SVG11-20030114/>. Latest version available at http://www.w3.org/TR/SVG11/. @@ -5031,7 +5031,7 @@

[XML]
-Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, , <http://www.w3.org/TR/2008/REC-xml-20081126/>. +Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, , <http://www.w3.org/TR/2008/REC-xml-20081126/>. Latest version available at http://www.w3.org/TR/xml. diff --git a/tests/valid/elements.v3.html b/tests/valid/elements.v3.html index effebf93..6b843120 100644 --- a/tests/valid/elements.v3.html +++ b/tests/valid/elements.v3.html @@ -15,7 +15,7 @@ - + @@ -1789,15 +1789,15 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.

[RFC7997]
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", IAB, RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
+Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", IAB, RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.

[RFC8174]
-Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
+Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
@@ -1813,15 +1813,15 @@

[I-D.levkowetz-xml2rfc-v3-implementation-notes]
-Levkowetz, H., "Implementation notes for RFC7991,", Work in Progress, Internet-Draft, draft-levkowetz-xml2rfc-v3-implementation-notes-13, , <https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13>.
+Levkowetz, H., "Implementation notes for RFC7991,", Work in Progress, Internet-Draft, draft-levkowetz-xml2rfc-v3-implementation-notes-13, , <https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13>.
[RFC5083]
-Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, DOI 10.17487/RFC5083, , <https://www.rfc-editor.org/info/rfc5083>.
+Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, DOI 10.17487/RFC5083, , <https://www.rfc-editor.org/info/rfc5083>.
[RFC5652]
-Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, , <https://www.rfc-editor.org/info/rfc5652>.
+Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, , <https://www.rfc-editor.org/info/rfc5652>.
@@ -1834,11 +1834,11 @@

[RFC2634]
-Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC 2634, DOI 10.17487/RFC2634, , <https://www.rfc-editor.org/info/rfc2634>.
+Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC 2634, DOI 10.17487/RFC2634, , <https://www.rfc-editor.org/info/rfc2634>.
[RFC5035]
-Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, DOI 10.17487/RFC5035, , <https://www.rfc-editor.org/info/rfc5035>.
+Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, DOI 10.17487/RFC5035, , <https://www.rfc-editor.org/info/rfc5035>.
@@ -1851,27 +1851,27 @@

[RFC2045]
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, , <https://www.rfc-editor.org/info/rfc2045>.
+Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, , <https://www.rfc-editor.org/info/rfc2045>.
[RFC2046]
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, , <https://www.rfc-editor.org/info/rfc2046>.
+Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, , <https://www.rfc-editor.org/info/rfc2046>.
[RFC2047]
-Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, , <https://www.rfc-editor.org/info/rfc2047>.
+Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, , <https://www.rfc-editor.org/info/rfc2047>.
[RFC2049]
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, DOI 10.17487/RFC2049, , <https://www.rfc-editor.org/info/rfc2049>.
+Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, DOI 10.17487/RFC2049, , <https://www.rfc-editor.org/info/rfc2049>.
[RFC4289]
-Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, DOI 10.17487/RFC4289, , <https://www.rfc-editor.org/info/rfc4289>.
+Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, DOI 10.17487/RFC4289, , <https://www.rfc-editor.org/info/rfc4289>.
[RFC6838]
-Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, , <https://www.rfc-editor.org/info/rfc6838>.
+Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, , <https://www.rfc-editor.org/info/rfc6838>.
@@ -1883,7 +1883,7 @@

[AUTHORS]
-Πυθαγόρας ὁ Σάμιος (Samos, P. O.), Doe, J., Bergström, A., and J. Doe, "Lots of authors", RFC 7539, DOI 10.17487/RFC7539, , <https://www.rfc-editor.org/rfc/rfc7539>.
+Πυθαγόρας ὁ Σάμιος (Samos, P. O.), Doe, J., Bergström, A., and J. Doe, "Lots of authors", RFC 7539, DOI 10.17487/RFC7539, , <https://www.rfc-editor.org/rfc/rfc7539>.
[DATE-RANGE]
@@ -1907,7 +1907,7 @@

[RFC0952]
-Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC0952, , <https://www.rfc-editor.org/info/rfc952>.
+Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC0952, , <https://www.rfc-editor.org/info/rfc952>.

diff --git a/tests/valid/rfc7911.html b/tests/valid/rfc7911.html index 190192fe..e2b7cb03 100644 --- a/tests/valid/rfc7911.html +++ b/tests/valid/rfc7911.html @@ -473,6 +473,10 @@ margin-bottom: 0.25em; } +.references .link { + display: inline-block; +} + /* index */ .index ul { margin: 0 0 0 1em; @@ -1607,19 +1611,19 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271]
-Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
+Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
[RFC4760]
-Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, , <https://www.rfc-editor.org/info/rfc4760>.
+Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, , <https://www.rfc-editor.org/info/rfc4760>.
[RFC5492]
-Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, DOI 10.17487/RFC5492, , <https://www.rfc-editor.org/info/rfc5492>.
+Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, DOI 10.17487/RFC5492, , <https://www.rfc-editor.org/info/rfc5492>.
@@ -1638,15 +1642,15 @@

[RFC3345]
-McPherson, D., Gill, V., Walton, D., and A. Retana, "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345, DOI 10.17487/RFC3345, , <https://www.rfc-editor.org/info/rfc3345>.
+McPherson, D., Gill, V., Walton, D., and A. Retana, "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345, DOI 10.17487/RFC3345, , <https://www.rfc-editor.org/info/rfc3345>.
[RFC4272]
-Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, DOI 10.17487/RFC4272, , <https://www.rfc-editor.org/info/rfc4272>.
+Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, DOI 10.17487/RFC4272, , <https://www.rfc-editor.org/info/rfc4272>.
[RFC4724]
-Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, DOI 10.17487/RFC4724, , <https://www.rfc-editor.org/info/rfc4724>.
+Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, DOI 10.17487/RFC4724, , <https://www.rfc-editor.org/info/rfc4724>.
[STOP-OSC]
diff --git a/tests/valid/rfc7911.v3.html b/tests/valid/rfc7911.v3.html index dfab84b5..2dedb503 100644 --- a/tests/valid/rfc7911.v3.html +++ b/tests/valid/rfc7911.v3.html @@ -16,7 +16,7 @@ that each path is identified by a Path Identifier in addition to the address prefix. " name="description"> - + @@ -419,19 +419,19 @@

[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.

[RFC4271]
-Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
+Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
[RFC4760]
-Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, , <https://www.rfc-editor.org/info/rfc4760>.
+Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, , <https://www.rfc-editor.org/info/rfc4760>.
[RFC5492]
-Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, DOI 10.17487/RFC5492, , <https://www.rfc-editor.org/info/rfc5492>.
+Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, DOI 10.17487/RFC5492, , <https://www.rfc-editor.org/info/rfc5492>.
@@ -450,15 +450,15 @@

[RFC3345]
-McPherson, D., Gill, V., Walton, D., and A. Retana, "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345, DOI 10.17487/RFC3345, , <https://www.rfc-editor.org/info/rfc3345>.
+McPherson, D., Gill, V., Walton, D., and A. Retana, "Border Gateway Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345, DOI 10.17487/RFC3345, , <https://www.rfc-editor.org/info/rfc3345>.
[RFC4272]
-Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, DOI 10.17487/RFC4272, , <https://www.rfc-editor.org/info/rfc4272>.
+Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, DOI 10.17487/RFC4272, , <https://www.rfc-editor.org/info/rfc4272>.
[RFC4724]
-Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, DOI 10.17487/RFC4724, , <https://www.rfc-editor.org/info/rfc4724>.
+Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, DOI 10.17487/RFC4724, , <https://www.rfc-editor.org/info/rfc4724>.
[STOP-OSC]
diff --git a/tests/valid/rfc9001.canonical.html b/tests/valid/rfc9001.canonical.html index e2dff47f..e640192b 100644 --- a/tests/valid/rfc9001.canonical.html +++ b/tests/valid/rfc9001.canonical.html @@ -11,7 +11,7 @@ This document describes how Transport Layer Security (TLS) is used to secure QUIC. " name="description"> - + @@ -2478,55 +2478,55 @@

[AEAD]
-McGrew, D., "An Interface and Algorithms for Authenticated Encryption", RFC 5116, DOI 10.17487/RFC5116, , <https://www.rfc-editor.org/info/rfc5116>.
+McGrew, D., "An Interface and Algorithms for Authenticated Encryption", RFC 5116, DOI 10.17487/RFC5116, , <https://www.rfc-editor.org/info/rfc5116>.

[AES]
-"Advanced encryption standard (AES)", National Institute of Standards and Technology report, DOI 10.6028/nist.fips.197, , <https://doi.org/10.6028/nist.fips.197>.
+"Advanced encryption standard (AES)", National Institute of Standards and Technology report, DOI 10.6028/nist.fips.197, , <https://doi.org/10.6028/nist.fips.197>.
[ALPN]
-Friedl, S., Popov, A., Langley, A., and E. Stephan, "Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301, , <https://www.rfc-editor.org/info/rfc7301>.
+Friedl, S., Popov, A., Langley, A., and E. Stephan, "Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301, , <https://www.rfc-editor.org/info/rfc7301>.
[CHACHA]
-Nir, Y. and A. Langley, "ChaCha20 and Poly1305 for IETF Protocols", RFC 8439, DOI 10.17487/RFC8439, , <https://www.rfc-editor.org/info/rfc8439>.
+Nir, Y. and A. Langley, "ChaCha20 and Poly1305 for IETF Protocols", RFC 8439, DOI 10.17487/RFC8439, , <https://www.rfc-editor.org/info/rfc8439>.
[HKDF]
-Krawczyk, H. and P. Eronen, "HMAC-based Extract-and-Expand Key Derivation Function (HKDF)", RFC 5869, DOI 10.17487/RFC5869, , <https://www.rfc-editor.org/info/rfc5869>.
+Krawczyk, H. and P. Eronen, "HMAC-based Extract-and-Expand Key Derivation Function (HKDF)", RFC 5869, DOI 10.17487/RFC5869, , <https://www.rfc-editor.org/info/rfc5869>.
[QUIC-RECOVERY]
-Iyengar, J., Ed. and I. Swett, Ed., "QUIC Loss Detection and Congestion Control", RFC 9002, DOI 10.17487/RFC9002, , <https://www.rfc-editor.org/info/rfc9002>.
+Iyengar, J., Ed. and I. Swett, Ed., "QUIC Loss Detection and Congestion Control", RFC 9002, DOI 10.17487/RFC9002, , <https://www.rfc-editor.org/info/rfc9002>.
[QUIC-TRANSPORT]
-Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, , <https://www.rfc-editor.org/info/rfc9000>.
+Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, , <https://www.rfc-editor.org/info/rfc9000>.
[RFC2119]
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC4086]
-Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, DOI 10.17487/RFC4086, , <https://www.rfc-editor.org/info/rfc4086>.
+Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, DOI 10.17487/RFC4086, , <https://www.rfc-editor.org/info/rfc4086>.
[RFC8174]
-Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
+Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[SHA]
-Dang, Q., "Secure Hash Standard", National Institute of Standards and Technology report, DOI 10.6028/nist.fips.180-4, , <https://doi.org/10.6028/nist.fips.180-4>.
+Dang, Q., "Secure Hash Standard", National Institute of Standards and Technology report, DOI 10.6028/nist.fips.180-4, , <https://doi.org/10.6028/nist.fips.180-4>.
[TLS-REGISTRIES]
-Salowey, J. and S. Turner, "IANA Registry Updates for TLS and DTLS", RFC 8447, DOI 10.17487/RFC8447, , <https://www.rfc-editor.org/info/rfc8447>.
+Salowey, J. and S. Turner, "IANA Registry Updates for TLS and DTLS", RFC 8447, DOI 10.17487/RFC8447, , <https://www.rfc-editor.org/info/rfc8447>.
[TLS13]
-Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, , <https://www.rfc-editor.org/info/rfc8446>.
+Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, , <https://www.rfc-editor.org/info/rfc8446>.
@@ -2537,31 +2537,31 @@

[AEBounds]
-Luykx, A. and K. Paterson, "Limits on Authenticated Encryption Use in TLS", , <https://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf>.
+Luykx, A. and K. Paterson, "Limits on Authenticated Encryption Use in TLS", , <https://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf>.
[ASCII]
-Cerf, V., "ASCII format for network interchange", STD 80, RFC 20, DOI 10.17487/RFC0020, , <https://www.rfc-editor.org/info/rfc20>.
+Cerf, V., "ASCII format for network interchange", STD 80, RFC 20, DOI 10.17487/RFC0020, , <https://www.rfc-editor.org/info/rfc20>.
[CCM-ANALYSIS]
-Jonsson, J., "On the Security of CTR + CBC-MAC", Selected Areas in Cryptography, SAC 2002, Lecture Notes in Computer Science, vol 2595, pp. 76-93, DOI 10.1007/3-540-36492-7_7, , <https://doi.org/10.1007/3-540-36492-7_7>.
+Jonsson, J., "On the Security of CTR + CBC-MAC", Selected Areas in Cryptography, SAC 2002, Lecture Notes in Computer Science, vol 2595, pp. 76-93, DOI 10.1007/3-540-36492-7_7, , <https://doi.org/10.1007/3-540-36492-7_7>.
[COMPRESS]
-Ghedini, A. and V. Vasiliev, "TLS Certificate Compression", RFC 8879, DOI 10.17487/RFC8879, , <https://www.rfc-editor.org/info/rfc8879>.
+Ghedini, A. and V. Vasiliev, "TLS Certificate Compression", RFC 8879, DOI 10.17487/RFC8879, , <https://www.rfc-editor.org/info/rfc8879>.
[GCM-MU]
-Hoang, V., Tessaro, S., and A. Thiruvengadam, "The Multi-user Security of GCM, Revisited: Tight Bounds for Nonce Randomization", CCS '18: Proceedings of the 2018 ACM SIGSAC Conference on Computer and Communications Security, pp. 1429-1440, DOI 10.1145/3243734.3243816, , <https://doi.org/10.1145/3243734.3243816>.
+Hoang, V., Tessaro, S., and A. Thiruvengadam, "The Multi-user Security of GCM, Revisited: Tight Bounds for Nonce Randomization", CCS '18: Proceedings of the 2018 ACM SIGSAC Conference on Computer and Communications Security, pp. 1429-1440, DOI 10.1145/3243734.3243816, , <https://doi.org/10.1145/3243734.3243816>.
[HTTP-REPLAY]
-Thomson, M., Nottingham, M., and W. Tarreau, "Using Early Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, , <https://www.rfc-editor.org/info/rfc8470>.
+Thomson, M., Nottingham, M., and W. Tarreau, "Using Early Data in HTTP", RFC 8470, DOI 10.17487/RFC8470, , <https://www.rfc-editor.org/info/rfc8470>.
[HTTP2-TLS13]
-Benjamin, D., "Using TLS 1.3 with HTTP/2", RFC 8740, DOI 10.17487/RFC8740, , <https://www.rfc-editor.org/info/rfc8740>.
+Benjamin, D., "Using TLS 1.3 with HTTP/2", RFC 8740, DOI 10.17487/RFC8740, , <https://www.rfc-editor.org/info/rfc8740>.
[IMC]
@@ -2569,23 +2569,23 @@

[NAN]
-Bellare, M., Ng, R., and B. Tackmann, "Nonces Are Noticed: AEAD Revisited", Advances in Cryptology - CRYPTO 2019, Lecture Notes in Computer Science, vol 11692, pp. 235-265, DOI 10.1007/978-3-030-26948-7_9, , <https://doi.org/10.1007/978-3-030-26948-7_9>.
+Bellare, M., Ng, R., and B. Tackmann, "Nonces Are Noticed: AEAD Revisited", Advances in Cryptology - CRYPTO 2019, Lecture Notes in Computer Science, vol 11692, pp. 235-265, DOI 10.1007/978-3-030-26948-7_9, , <https://doi.org/10.1007/978-3-030-26948-7_9>.

[QUIC-HTTP]
-Bishop, M., Ed., "Hypertext Transfer Protocol Version 3 (HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-quic-http-34, , <https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-34>.
+Bishop, M., Ed., "Hypertext Transfer Protocol Version 3 (HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-quic-http-34, , <https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-34>.
[RFC2818]
-Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/RFC2818, , <https://www.rfc-editor.org/info/rfc2818>.
+Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/RFC2818, , <https://www.rfc-editor.org/info/rfc2818>.
[RFC5280]
-Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, , <https://www.rfc-editor.org/info/rfc5280>.
+Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, , <https://www.rfc-editor.org/info/rfc5280>.
[ROBUST]
-Fischlin, M., Günther, F., and C. Janson, "Robust Channels: Handling Unreliable Networks in the Record Layers of QUIC and DTLS 1.3", , <https://eprint.iacr.org/2020/718>.
+Fischlin, M., Günther, F., and C. Janson, "Robust Channels: Handling Unreliable Networks in the Record Layers of QUIC and DTLS 1.3", , <https://eprint.iacr.org/2020/718>.
diff --git a/tests/valid/rfc99999.html b/tests/valid/rfc99999.html index 0d06b7d4..78ec8556 100644 --- a/tests/valid/rfc99999.html +++ b/tests/valid/rfc99999.html @@ -466,6 +466,10 @@ margin-bottom: 0.25em; } +.references .link { + display: inline-block; +} + /* index */ .index ul { margin: 0 0 0 1em; @@ -1330,7 +1334,7 @@

[RFC99998]
-Doe, J., "Prime Directive", RFC 99998, DOI 10.17487/RFC99998, , <https://www.rfc-editor.org/info/rfc99998>.
+Doe, J., "Prime Directive", RFC 99998, DOI 10.17487/RFC99998, , <https://www.rfc-editor.org/info/rfc99998>.
diff --git a/tests/valid/rfc99999.v3.html b/tests/valid/rfc99999.v3.html index ee7a9579..7d5478ac 100644 --- a/tests/valid/rfc99999.v3.html +++ b/tests/valid/rfc99999.v3.html @@ -9,7 +9,7 @@ - + @@ -142,7 +142,7 @@

[RFC99998]
-Doe, J., "Prime Directive", RFC 99998, DOI 10.17487/RFC99998, , <https://www.rfc-editor.org/info/rfc99998>.
+Doe, J., "Prime Directive", RFC 99998, DOI 10.17487/RFC99998, , <https://www.rfc-editor.org/info/rfc99998>.