--- 1/draft-ietf-rtcweb-video-01.txt 2014-10-27 15:14:45.007869439 -0700 +++ 2/draft-ietf-rtcweb-video-02.txt 2014-10-27 15:14:45.027869915 -0700 @@ -1,18 +1,18 @@ Network Working Group A.B. Roach Internet-Draft Mozilla Intended status: Standards Track October 27, 2014 Expires: April 30, 2015 WebRTC Video Processing and Codec Requirements - draft-ietf-rtcweb-video-01 + draft-ietf-rtcweb-video-02 Abstract This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network. It specifies the video processing that is required, as well as video codecs and their parameters. Status of This Memo @@ -196,27 +196,27 @@ Encoders are encouraged to support encoding media with at least the same resolution and frame rates cited above. 5.1. VP8 If VP8, defined in [RFC6386], is supported, then the endpoint MUST support the payload formats defined in [I-D.ietf-payload-vp8]. In addition it MUST support the 'bilinear' and 'none' reconstruction filters. - In addition to the [RFC6236] mechanism, H.264 encoders MUST limit the - streams they send to conform to the values indicated by receivers in - the corresponding max-fr and max-fs SDP attributes. - TODO: There have been claims that VP8 already requires supporting both filters; if true, these do not need to be reiterated here. + In addition to the [RFC6236] mechanism, VP8 encoders MUST limit the + streams they send to conform to the values indicated by receivers in + the corresponding max-fr and max-fs SDP attributes. + 5.2. H.264 If [H264] is supported, then the device MUST support the payload formats defined in [RFC6184]. In addition, they MUST support Constrained Baseline Profile Level 1.2, and they SHOULD support H.264 Constrained High Profile Level 1.3. Implementations of the H.264 codec have utilized a wide variety of optional parameters. To improve interoperability the following parameter settings are specified: