3
0
Fork
You've already forked spec
0

Reformat to xml2rfc (RFC 7991) #1

Merged
pukkamustard merged 15 commits from ietf-rfc-xml into main 2022年02月08日 13:45:13 +01:00

This reformats the specification document to the IETF xml2rfc format (see RFC 7991).

This is a good format for formal specifications and is used by the IETF and by GNUnet's LSD (https://lsd.gnunet.org/).

Removes dependency on AsciiDoc (which is quite heavy). In place we now rely on the Python xml2rfc tool.

This is the second reformat of the specification (first one was from Org-mode to AsciiDoc). We unfortunately loose Git history. I tried hard not to introduce any changes to the spec while reformating. Content-wise this is almost equivalent to version 0.3.0.

Figure has not yet been reformated. SVG as exported by graphviz can not be used in a RFC XML document as it does not conform with SVG Tiny. I will manually port the figure later.

This reformats the specification document to the IETF xml2rfc format (see [RFC 7991](https://datatracker.ietf.org/doc/html/rfc7991)). This is a good format for formal specifications and is used by the IETF and by GNUnet's LSD (https://lsd.gnunet.org/). Removes dependency on AsciiDoc (which is quite heavy). In place we now rely on the Python xml2rfc tool. This is the second reformat of the specification (first one was from Org-mode to AsciiDoc). We unfortunately loose Git history. I tried hard not to introduce any changes to the spec while reformating. Content-wise this is almost equivalent to version 0.3.0. Figure has not yet been reformated. SVG as exported by graphviz can not be used in a RFC XML document as it does not conform with [SVG Tiny](https://www.w3.org/TR/SVGTiny12/). I will manually port the figure later.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eris/spec!1
Reference in a new issue
eris/spec
No description provided.
Delete branch "ietf-rfc-xml"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?