-
```
There are cases where 72 characters (the default line length) is still too wide
(notably when including RNCs into IETF RFCs in plain text format).
It would be awesome if the default line length …
-
```
There are cases where 72 characters (the default line length) is still too wide
(notably when including RNCs into IETF RFCs in plain text format).
It would be awesome if the default line length …
-
```
There are cases where 72 characters (the default line length) is still too wide
(notably when including RNCs into IETF RFCs in plain text format).
It would be awesome if the default line length …
-
From John Mattsson: "For 5G use cases, I would strongly like the document to also cover use of SLH-DSA in RFC 2986 (PKCS #10), RFC 4210 (CMP), and RFC 6090 (OCSP)."
-
```
There are cases where 72 characters (the default line length) is still too wide
(notably when including RNCs into IETF RFCs in plain text format).
It would be awesome if the default line length …
-
Here is a compilation of up-to-date RFCs related to IMAP:
* 2177 - IDLE Extension: https://tools.ietf.org/html/rfc2177
* 2342 - NAMESPACE Extension: https://tools.ietf.org/html/rfc2342
* 2971 - I…
-
It looks like some RFCs use different markup from others, leading to the RFC fetcher to fail to extract the title.
For example, https://datatracker.ietf.org/doc/html/rfc3986 uses
```
Uniform Reso…
-
`type_task` | by nick.delregno@verizon.com
___
The IETF uses surveys for a variety of purposes, from confirming interoperable implementations for RFC progression to surveys of industry impleme…
-
Can you add the support of new SIP RFCs?
-
The spec seemingly doesn't specify exactly what the rules should be for URL-encoding federation URLs.
Synapse seems to query-encode both path and query elements. Dendrite path-encodes path elements…