Maybe this is also interesting for taps as a reference...
On 10.08.20, 22:35, "QUIC on behalf of Dirkjan Ochtman" <quic-boun...@ietf.org
on behalf of dirk...@ochtman.nl> wrote:
On Fri, Aug 7, 2020 at 12:57 AM Martin Duke <martin.h.d...@gmail.com> wrote:
> On this subject, (speaking as individual) I think it would be useful to
define a QUIC application API. SCTP did one
(https://datatracker.ietf.org/doc/rfc6458/) and the idea that an application
would have to be written separately for each quic implementation is silly.
For what it's worth, for the hyper library (the most popular HTTP
library in the Rust ecosystem) we're trying to define a set of Rust
traits (abstract interfaces) that cover the basic QUIC API insofar as
H3 support needs it.
https://github.com/hyperium/h3/blob/master/design/PROPOSAL.md#4-public-api
Kind regards,
Dirkjan
_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
