[EXTENSION] File Type codes (+ PDF)

[punctuations]

Extension Kind

New Flags bit assignment

Motivation

Use the reserved bits (5-6) to define PDF transfers.

Proposed Wire Format

N/A

Semantics and Behaviour

When the bit for PDF is set the client SHOULD identify that the packet is the data of a pdf file and thus should treat it as such.

Backwards Compatibility

Modifies existing framing — breaking change, needs new ALPN (jtp/2)

Alternatives Considered

Since the current jtp/1 specifies that if bits 5-6 are set in the file type codes then they may choose to identify the packet as malformed and reject the request, this change would change that behaviour in that if the bit is set it is not a malformed request, but instead a different file type.

Implementation Notes

No response

Checklist

• I have read the current RFC and this does not duplicate an existing feature.
• I have considered the impact on resource limits (Section 11 of the RFC).
• I have considered the security implications (Section 13 of the RFC).