One thing I would like to see in the document (probably in the error resilience section, 3.2.5) is an explicit requirement to support independently-decodable subframes that can be MTU-targeted by an encoder. This is very important for error resilience for RTP-packetized streams. (See RFC 2736, to which an informative reference probably wouldn’t be out of order.)
> On Aug 4, 2016, at 5:18 PM, Adam Roach <[email protected]> wrote: > > [as chair] > > NETVC participants: > > We would like to start a two-week working group last call on the codec > requirements document: > > https://tools.ietf.org/html/draft-ietf-netvc-requirements-02 > > All working group participants are encouraged to carefully read the document > and comment on the mailing list -- even something simple like "I have > reviewed the document and believe it is in good shape" is helpful. > > I'll also note that the question as to whether we request publication of this > document as an RFC is still open. As part of this last call, please indicate > whether you believe such publication would be of value. If we do not request > publication, we will instead announce a document freeze at some point after > the end of WGLC (roughly, the amount of time typically between end of WGLC > and publication request). > > Thanks! > > /a > > _______________________________________________ > video-codec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/video-codec > _______________________________________________ video-codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/video-codec
