HTTP3 is a named reference, but the other HTTP RFCs are referenced only by RFC number. That makes some sense for the older HTTP RFCs which are being obsoleted by this document, but I'd expect at least H2 and H3 to have parity.
The text was updated successfully, but these errors were encountered:
Personally, I like the anchor names, provided they give readers more mental context for what they're being referred to. Obviously it doesn't matter for things like "TLS 1.3 ([TLS])", but are more useful in things like "esoteric concept; see Section foobar of [BAZ]."
HTTP3 is a named reference, but the other HTTP RFCs are referenced only by RFC number. That makes some sense for the older HTTP RFCs which are being obsoleted by this document, but I'd expect at least H2 and H3 to have parity.
The text was updated successfully, but these errors were encountered: