PRIORITY extension

• From: <K.Morgan@iaea.org>
• Date: Sat, 12 Jul 2014 20:46:55 +0000
• To: <ietf-http-wg@w3.org>
• Message-ID: <422C4CC5-8406-41A3-931E-4347C594D34B@iaea.org>

As far as I can tell, everything in h2-13 related to PRIORITY is completely optional (please correct me if I'm wrong).

I've repeatedly seen arguments against adding anything optional to the spec. So why does PRIORITY get a pass? If it's truly optional, it could easily be moved to a separate RFC as an extension.

So, why not move PRIORITY to an extension? It would make the main spec smaller and cleaner.

This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.

Received on Saturday, 12 July 2014 20:47:27 UTC