- Request For Comments is a fascinating topic to me - They are most famously used by the [[IETF]] - History - [50 Years of RFCs](https://www.rfc-editor.org/history/fifty-years-of-rfcs/) - [RFC 8700 - 50 Years of RFCs](https://tools.ietf.org/html/rfc8700) - Someday I want to design a general RFC system for business that can be used for designing SOPs - At Wasson we've run into the issue of scaling documentation procedures - RADAR has had a similar issue with a fast growing team - Tooling - [mmark](https://github.com/mmarkdown/mmark) "is a powerful markdown processor written in Go, geared towards writing IETF documents" - [kramdown](https://github.com/cabo/kramdown-rfc2629) - Both use [xml2rfc](xml.resource.org) - The problems: - A lot of the tools are dedicated for use by the IETF - For example, the IPR clauses are only usable for representing IETF copyright notices - Author guidance - The following resources are made available by the IETF for authors: - Templates: https://tools.ietf.org/tools/templates/ - Draft submission tool: https://datatracker.ietf.org/idst/upload.cgi - The draft tool also includes a [Note Well](https://datatracker.ietf.org/submit/note-well/) page that states "This is a reminder of IETF policies in effect on various topics such as patents or code of conduct. It is only meant to point you in the right direction. Exceptions may apply. The IETF's patent policy and the definition of an IETF "contribution" and "participation" are set forth in BCP 79; please read it carefully." - IETF meetings have newcomer pages, eg [IETF 106](https://www.ietf.org/how/meetings/106/newcomers/) - The [idnits tool](https://tools.ietf.org/tools/idnits/) checks submissions for "nits" - [BCP78](https://tools.ietf.org/html/bcp78) describes the rights that authors grant the IETF to make RFCs usable by the community while still granting the IETF the necessary rights. - [The publication process](https://www.rfc-editor.org/pubprocess/) describes the process - - Mirroring (eg rfcs.dev) - There's an ability to retrieve the RFCs [in bulk](https://www.rfc-editor.org/retrieve/) - Independent Submission Editor - There exists an independent submission path for documents that don't follow the IETF path: https://www.rfc-editor.org/about/independent/ -