Christian Nennemann
56f2ce669c
Both drafts now live in workspace/drafts/ as siblings:
drafts/
├── act/ (ACT -01, native to parent repo)
│ ├── draft-nennemann-act-01.md kramdown-rfc source
│ ├── draft-nennemann-act-01.{xml,txt,html,pdf}
│ ├── .refcache/ bibxml cache
│ └── build.sh
├── ietf-wimse-ect/ (ECT -02, submodule, PDF added)
│ └── ...
└── README-pdf.md PDF toolchain docs
ACT kramdown-rfc conversion:
- full YAML frontmatter (title, author, refs)
- section structure matches kramdown-rfc conventions
- {{REF}} citation syntax, auto-numbered sections
- references auto-built from normative/informative blocks
- removed manual TOC (kramdown-rfc generates)
- builds cleanly: 133K XML, 89K TXT, 208K HTML, 167K PDF
PDF toolchain:
- xml2rfc --pdf via weasyprint<60 + pydyf<0.10 injected into xml2rfc pipx venv
- both build.sh scripts now produce PDF as Step 4
- README-pdf.md documents the setup for new machines
Submodule: bump ietf-wimse-ect pointer for build.sh PDF step
14 lines
679 B
XML
14 lines
679 B
XML
<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
|
|
<front>
|
|
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
|
|
<author fullname="B. Leiba" initials="B." surname="Leiba"/>
|
|
<date month="May" year="2017"/>
|
|
<abstract>
|
|
<t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name="BCP" value="14"/>
|
|
<seriesInfo name="RFC" value="8174"/>
|
|
<seriesInfo name="DOI" value="10.17487/RFC8174"/>
|
|
</reference>
|