Re: [Rfc-markdown] [netmod] too long lines from IANA module inclusion

[Carsten Bormann <[e-mail]>]

Now you made me curious.
No RFCs use RFC 8792 encoding yet (except for RFC 8792 itself), as you said.

I-Ds:

  "Grant Negotiation and Authorization Protocol", Justin Richer, Aaron
  Parecki, Fabien Imbault, 2021-10-25, <draft-ietf-gnap-core-protocol-08.txt>

(Using this for JSON text.)

  "Problem Details for HTTP APIs", Mark Nottingham, Erik Wilde, Sanjay Dalal,
  2021-10-13, <draft-ietf-httpapi-rfc7807bis-01.txt>

(Using this for JSON text containing a json-schema.org description.)

  "HTTP Message Signatures", Annabelle Backman, Justin Richer, Manu Sporny,
  2021-08-13, <draft-ietf-httpbis-message-signatures-06.txt>

(Using this for examples of Signature-Input, Signature.)

  draft-ietf-netconf-crypto-types-21.txt, draft-ietf-netconf-http-client-server-08.txt, draft-ietf-netconf-https-notif-09.txt, draft-ietf-netconf-keystore-23.txt, draft-ietf-netconf-netconf-client-server-24.txt, draft-ietf-netconf-notification-capabilities-21.txt, draft-ietf-netconf-restconf-client-server-24.txt, draft-ietf-netconf-ssh-client-server-26.txt, draft-ietf-netconf-tls-client-server-26.txt, draft-ietf-netconf-trust-anchors-16.txt, draft-ietf-netmod-yang-instance-file-format-21.txt)

(Tons of netconf drafts, apparently using this mainly for XML examples — I didn’t check all of those.)

  "Conveying a Certificate Signing Request (CSR) in a Secure Zero Touch
  Provisioning (SZTP) Bootstrapping Request", Kent Watsen, Russ Housley, Sean
  Turner, 2021-12-03, <draft-ietf-netconf-sztp-csr-12.txt>

(As mentioned, for a YANG tree, HTTP requests, JSON text.)

  "A Layer 2 VPN Network YANG Model", samier barguil, Oscar de Dios, Mohamed
  Boucadair, Luis Munoz, 2021-11-22, <draft-ietf-opsawg-l2nm-12.txt>

(YANG JSON instances, again.)

  "A Layer 3 VPN Network YANG Model", samier barguil, Oscar de Dios, Mohamed
  Boucadair, Luis Munoz, Alejandro Aguado, 2021-10-08,
  <draft-ietf-opsawg-l3sm-l3nm-18.txt>

(Overly long HTTP requests.)

  "Structured Data for Filtered DNS", Dan Wing, Tirumaleswar Reddy.K, Neil
  Cook, Mohamed Boucadair, 2021-10-13,
  <draft-wing-dnsop-structured-dns-error-page-01.txt>

(JSON.)

  "List Pagination for YANG-driven Protocols", Kent Watsen, Qin WU, Olof
  Hagsand, Hongwei Li, Per Andersson, 2021-10-25,
  <draft-wwlh-netconf-list-pagination-00.txt>

  "NETCONF Extensions to Support List Pagination", Kent Watsen, Qin WU, Olof
  Hagsand, Hongwei Li, Per Andersson, 2021-10-25,
  <draft-wwlh-netconf-list-pagination-nc-02.txt>

  "RESTCONF Extensions to Support List Pagination", Kent Watsen, Qin WU, Olof
  Hagsand, Hongwei Li, Per Andersson, 2021-10-25,
  <draft-wwlh-netconf-list-pagination-rc-02.txt>

(HTTP requests, some XML.)

And, crucially for an implementer, no ‘\\’ wrapping, except (unnecessarily!) in draft-ietf-netconf-ssh-client-server-21.txt (apparently fixed in later versions.)

The form

   =============== NOTE: '\' line wrapping per RFC 8792 ================

(15 equals signs left, 16 equals signs right) seems to be the favorite lead-in; however, draft-wing-dnsop-structured-dns-error-page-01.txt had a version indented by 2 characters that has 14+15 accordingly.  About 5 % 10+11, apparently before RFC 8792 was published so there was less space.)

Examples from the HTTP ecosystem (GNAP, HTTPAPI, HTTPBIS) didn’t have any “===“ decoration, though.  (Why the heck was this left open as a choice for the author?  I like “%%%” decoration instead, should I use that as a personal fashion statement?)

Grüße, Carsten