Great, I am currently implementing an internal part of this API: calculating and propagating timestamps. How it would be reported to user application is not really decided. For now we will live with a work around. I doubt that this API will be implemented with quarter. Eventually we should transition to using this API.

 Issue 695223  has been merged into this issue.

Is it possible to add to specification 3 more timestamps? The capture time and two timestamps for possible in-network RTP processor. The latter two will have application-specific meaning.

This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

Per the discussion in blink-dev (see https://groups.google.com/a/chromium.org/d/topic/blink-dev/Kk4lCaCBaZU/discussion) it would be better to implement this feature as an extension to Performance Timeline API.