Anyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...
#RFC #IETF #HyperText
Karsten Schmidt
npub13t…wn30g
2025-02-26 10:19:04 UTC
Author Public Key
npub13t480fdgej2k3fjk5e7sqhqks7wnlgldmpwsec7772z4pyr3yumq2wn30gSeen on
wss://relay.mostr.pubPublished at
2025-02-26 10:19:04 UTCEvent JSON
{
"id": "638510e2405295eaf6be4f4350be9d52f5646a08cfb65468d1f297e03bf8669e",
"pubkey": "8aea77a5a8cc9568a656a67d005c16879d3fa3edd85d0ce3def2855090712736",
"created_at": 1740565144,
"kind": 1,
"tags": [
[
"t",
"rfc"
],
[
"t",
"ietf"
],
[
"t",
"hypertext"
],
[
"proxy",
"https://mastodon.thi.ng/users/toxi/statuses/114069677313552098",
"activitypub"
]
],
"content": "Anyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...\n\n#RFC #IETF #HyperText",
"sig": "457831b164434ff771a445b1b9473b0b637950b06912b589acd1daae375e8126ae92a16eef0f03e3cef21ae3654e3a939074282a7575969f57b28aacbc2ad5e0"
}