Hi Christian, We have an experimental project that uses your timestamp mechanism. Therefore we are interested in your draft.
Cheers, Yunfei On Sun, Aug 28, 2022 at 1:51 PM Christian Huitema <[email protected]> wrote: > This new version of the QUIC timestamp draft is mostly a simple update to > keep the draft from expiring. I did develop the "use case" section a bit, > but as we discussed during the IETF 115 meeting I don't want to invest too > much time there unless other WG participants express interest. > > -- Christian Huitema > > > -------- Forwarded Message -------- > Subject: New Version Notification for draft-huitema-quic-ts-08.txt > Date: Sun, 28 Aug 2022 13:44:54 -0700 > From: [email protected] > To: Christian Huitema <[email protected]> <[email protected]> > > > A new version of I-D, draft-huitema-quic-ts-08.txt > has been successfully submitted by Christian Huitema and posted to the > IETF repository. > > Name: draft-huitema-quic-ts > Revision: 08 > Title: Quic Timestamps For Measuring One-Way Delays > Document date: 2022-08-28 > Group: Individual Submission > Pages: 11 > URL: https://www.ietf.org/archive/id/draft-huitema-quic-ts-08.txt > Status: https://datatracker.ietf.org/doc/draft-huitema-quic-ts/ > Htmlized: https://datatracker.ietf.org/doc/html/draft-huitema-quic-ts > Diff: https://www.ietf.org/rfcdiff?url2=draft-huitema-quic-ts-08 > > Abstract: > The TIMESTAMP frame can be added to Quic packets when one way delay > measurements are useful. The timestamp is set to the number of > microseconds from the beginning of the node's epoch to the time at > which the packet is sent. The draft defines the "enable_timestamp" > transport parameter for negotiating the use of this extension frame, > and the TIMESTAMP frame. > > > > The IETF Secretariat > > >
