Hello TAPS, We have a slot on the agenda this week for covering TAPS mappings for QUIC. Ahead of that discussion, I’ve posted this short draft to show how this could look.
Best, Tommy > Begin forwarded message: > > From: [email protected] > Subject: New Version Notification for draft-taps-quic-mapping-00.txt > Date: March 19, 2022 at 4:06:56 PM PDT > To: Tommy Pauly <[email protected]> > > > A new version of I-D, draft-taps-quic-mapping-00.txt > has been successfully submitted by Tommy Pauly and posted to the > IETF repository. > > Name: draft-taps-quic-mapping > Revision: 00 > Title: A Transport Services Mapping for QUIC > Document date: 2022-03-19 > Group: Individual Submission > Pages: 5 > URL: https://www.ietf.org/archive/id/draft-taps-quic-mapping-00.txt > Status: https://datatracker.ietf.org/doc/draft-taps-quic-mapping/ > Html: > https://www.ietf.org/archive/id/draft-taps-quic-mapping-00.html > Htmlized: https://datatracker.ietf.org/doc/html/draft-taps-quic-mapping > > > Abstract: > This document defines a Transport Services API mapping for QUIC > streams. > > Discussion Venues > > This note is to be removed before publishing as an RFC. > > Discussion of this document takes place on the QUIC Working Group > mailing list ([email protected]), which is archived at > https://mailarchive.ietf.org/arch/browse/quic/. > > Source for this draft and an issue tracker can be found at > https://github.com/tfpauly/draft-taps-quic-mapping. > > > > > The IETF Secretariat > >
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
