As I said in a previous thread, it would be useful to have the canonical version of RFCs also do that, not just manuscripts, i.e., for RFC 9750:
----
<abstract pn="section-abstract">
<t indent="0" pn="section-abstract-1">
The Messaging Layer Security (MLS) protocol (RFC 9420) provides a group key
agreement protocol for messaging applications.
MLS is designed to protect against eavesdropping, tampering, and message
forgery, and to provide forward secrecy (FS) and post-compromise security (PCS).
</t>
----
instead of:
----
<abstract pn="section-abstract">
<t indent="0" pn="section-abstract-1">The Messaging Layer Security (MLS)
protocol (RFC 9420)
provides a group key agreement protocol for messaging applications.
MLS is designed to protect against eavesdropping, tampering, and message
forgery, and to provide forward secrecy (FS) and post-compromise security
(PCS).
</t>
----
That also would simplify reviewing diffs during AUTH48 for people who insist on
not using markdown[1], and so will have to do that on RFCXML.
(and I hope that the RFC editor will not try to impose using GitHub during
AUTH48. Git is fine[2]).
[1] markdown did not fit my requirements to write I-Ds, so I wrote my own
asciidoctor backend for RFCXML.
[2] Git is the diamond under the steaming pile of dung that is GitHub.
On 4/23/25 7:48 AM, Carsten Bormann wrote:
> On 23. Apr 2025, at 16:13, Michael Richardson <mcr+i...@sandelman.ca> wrote:
>>
>> What would also help would be if everyone started every new sentence on a
>> newline. It doesn't matter if they wrap the sentence into multiple lines,
>> but having a new sentence on a newline simplies git diff.
>
> Indeed, that is generally the consensus people arrive at when they are using
> markdown and git for significant document work.
>
>> I wonder how to socialize this wider. Maybe it's worth a three minute
>> plenary talk, but my guess is that the people we want to reach don't come to
>> the plenary.
>
> First thing, I need to fix my XML to markdown converter to consistently do
> that!
>
> (Do we have other “manuscript style” issues that we want to capture somewhere?
> For now, I have set up:
>
> https://github.com/cabo/kramdown-rfc/wiki/Manuscript-Style
> )
>
> Grüße, Carsten
>
--
Marc Petit-Huguenin
Email: m...@petit-huguenin.org
Blog: https://medium.com/@petithug
Profile: https://www.linkedin.com/in/petithug
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ rfc-interest mailing list -- rfc-interest@rfc-editor.org To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
