draft-ietf-rtcweb-video-01.txt		draft-ietf-rtcweb-video-02.txt
	Network Working Group A.B. Roach		Network Working Group A.B. Roach
	Internet-Draft Mozilla		Internet-Draft Mozilla
	Intended status: Standards Track October 27, 2014		Intended status: Standards Track October 27, 2014
	Expires: April 30, 2015		Expires: April 30, 2015
	WebRTC Video Processing and Codec Requirements		WebRTC Video Processing and Codec Requirements
	draft-ietf-rtcweb-video-01		draft-ietf-rtcweb-video-02
	Abstract		Abstract
	This specification provides the requirements and considerations for		This specification provides the requirements and considerations for
	WebRTC applications to send and receive video across a network. It		WebRTC applications to send and receive video across a network. It
	specifies the video processing that is required, as well as video		specifies the video processing that is required, as well as video
	codecs and their parameters.		codecs and their parameters.
	Status of This Memo		Status of This Memo
	skipping to change at page 5, line 24		skipping to change at page 5, line 24
	Encoders are encouraged to support encoding media with at least the		Encoders are encouraged to support encoding media with at least the
	same resolution and frame rates cited above.		same resolution and frame rates cited above.
	5.1. VP8		5.1. VP8
	If VP8, defined in [RFC6386], is supported, then the endpoint MUST		If VP8, defined in [RFC6386], is supported, then the endpoint MUST
	support the payload formats defined in [I-D.ietf-payload-vp8]. In		support the payload formats defined in [I-D.ietf-payload-vp8]. In
	addition it MUST support the 'bilinear' and 'none' reconstruction		addition it MUST support the 'bilinear' and 'none' reconstruction
	filters.		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		TODO: There have been claims that VP8 already requires supporting
	both filters; if true, these do not need to be reiterated here.		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		5.2. H.264
	If [H264] is supported, then the device MUST support the payload		If [H264] is supported, then the device MUST support the payload
	formats defined in [RFC6184]. In addition, they MUST support		formats defined in [RFC6184]. In addition, they MUST support
	Constrained Baseline Profile Level 1.2, and they SHOULD support H.264		Constrained Baseline Profile Level 1.2, and they SHOULD support H.264
	Constrained High Profile Level 1.3.		Constrained High Profile Level 1.3.
	Implementations of the H.264 codec have utilized a wide variety of		Implementations of the H.264 codec have utilized a wide variety of
	optional parameters. To improve interoperability the following		optional parameters. To improve interoperability the following
	parameter settings are specified:		parameter settings are specified:
End of changes. 3 change blocks.
	5 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/