[quicwg/base-drafts] HTTP/3 priorities interact poorly with application frontend(AFE) priorities (#2740)

ianswett <notifications@github.com> Tue, 21 May 2019 23:19 UTC

Date: Tue, 21 May 2019 16:19:55 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2QRTX65JJOLSINVJ526G5BXEVBNHHBVIVBWU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2740@github.com>
Subject: [quicwg/base-drafts] HTTP/3 priorities interact poorly with application frontend(AFE) priorities (#2740)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce4879b36551_1a603f8435ccd960471671"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HJ5Aq1uC888xXfIEh4bKnbn8an8>

AFEs commonly want to specify priorities, but load balancers connect to multiple AFEs for a given connection, so the AFE is not aware of the existing request priority structure.

An AFE may want to indicate that a request is high or low priority, but in the existing HTTP/3(and HTTP/2) scheme, the load balancer would be responsible for translating that into the priority tree.  The only correct option is to understand how all clients use HTTP/2 priorities and update the priority of the response accordingly.

Ideally a load balancer would not have to convert priorities on a user-agent basis in HTTP/3.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2740

[quicwg/base-drafts] HTTP/3 priorities interact p… ianswett
Re: [quicwg/base-drafts] HTTP/3 priorities intera… Mike Bishop