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
838 B
XML
14 lines
838 B
XML
<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
|
|
<front>
|
|
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
|
|
<author fullname="S. Bradner" initials="S." surname="Bradner"/>
|
|
<date month="March" year="1997"/>
|
|
<abstract>
|
|
<t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. 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="14"/>
|
|
<seriesInfo name="RFC" value="2119"/>
|
|
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
|
|
</reference>
|