- From: Dan Jenkins <dan@nimblea.pe>
- Date: Fri, 1 Nov 2024 08:04:32 +0000
- To: Harald Alvestrand <hta@google.com>
- Cc: "public-webrtc@W3.org" <public-webrtc@w3.org>
- Message-ID: <CADK8cqU_8u67XjaYjB_d4ZmHzxEqQTVESFVeaV_3TVNPhMHp8w@mail.gmail.com>
Hi Harald, What’s the best way of making my support known? It’s a hugely useful extension Dan *Dan Jenkins* Founder @ Nimble Ape / Everycast Labs / CommCon Nimble Ape: nimblea.pe Everycast Labs: everycastlabs.uk // broadcastbridge.app CommCon: commcon.xyz On Wed, 30 Oct 2024 at 09:46, Harald Alvestrand <hta@google.com> wrote: > Hello fellow WG members! > > As some of you know well, Google has been experimenting with an RTP > extension called abs-capture-timestamp, documented here: > > > https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/rtp-hdrext/abs-capture-time > > Following earlier WG discussions, we've decided to pursue standardization > in the IETF of this functionality, and have asked the AVTCORE WG ( > avt@ietf.org) to adopt the functionality based on the following draft: > > https://datatracker.ietf.org/doc/draft-alvestrand-avtcore-abs-capture-time/ > > This will be discussed on Monday of next week, in the IETF meeting in > Dublin. > So far, the list has been very quiet - no comments on the draft, no > expressions of support or opposition. There's a serious risk that this > draft may be rejected by the AVTCORE WG because of a lack of documented > interest from other parties than the proposer. > > So - if you have seen this thing before, and are interested in seeing it > go forward in a standardized way (which MAY lead to changes!!!), please > find a way to express support for adopting the draft in the WG before > Monday! > > Harald > > >
Received on Friday, 1 November 2024 08:04:49 UTC