rfc8888v3.txt		rfc8888.txt
	skipping to change at line 210 ¶		skipping to change at line 210 ¶
	FMT=11 indicating that this is a congestion control feedback packet,		FMT=11 indicating that this is a congestion control feedback packet,
	and with the SSRC set to that of the sender of the RTCP packet.		and with the SSRC set to that of the sender of the RTCP packet.
	Section 6.1 of [RFC4585] requires the RTCP header to be followed by		Section 6.1 of [RFC4585] requires the RTCP header to be followed by
	the SSRC of the RTP flow being reported upon. Accordingly, the RTCP		the SSRC of the RTP flow being reported upon. Accordingly, the RTCP
	header is followed by a report block for each SSRC from which RTP		header is followed by a report block for each SSRC from which RTP
	packets have been received, followed by a Report Timestamp.		packets have been received, followed by a Report Timestamp.
	Each report block begins with the SSRC of the received RTP stream on		Each report block begins with the SSRC of the received RTP stream on
	which it is reporting. Following this, the report block contains a		which it is reporting. Following this, the report block contains a
	16-bit packet metric block for each RTP packet with sequence number		16-bit packet metric block for each RTP packet that has a sequence
	in the range begin_seq to begin_seq+num_reports inclusive (calculated		number in the range begin_seq to begin_seq+num_reports inclusive
	using arithmetic modulo 65536 to account for possible sequence number		(calculated using arithmetic modulo 65536 to account for possible
	wrap-around). If the number of 16-bit packet metric blocks included		sequence number wrap-around). If the number of 16-bit packet metric
	in the report block is not a multiple of two, then 16 bits of zero		blocks included in the report block is not a multiple of two, then 16
	padding MUST be added after the last packet metric block, to align		bits of zero padding MUST be added after the last packet metric
	the end of the packet metric blocks with the next 32-bit boundary.		block, to align the end of the packet metric blocks with the next
	The value of num_reports MAY be 0, indicating that there are no		32-bit boundary. The value of num_reports MAY be 0, indicating that
	packet metric blocks included for that SSRC. Each report block MUST		there are no packet metric blocks included for that SSRC. Each
	NOT include more than 16384 packet metric blocks (i.e., it MUST NOT		report block MUST NOT include more than 16384 packet metric blocks
	report on more than one quarter of the sequence number space in a		(i.e., it MUST NOT report on more than one quarter of the sequence
	single report).		number space in a single report).
	The contents of each 16-bit packet metric block comprise the R, ECN,		The contents of each 16-bit packet metric block comprise the R, ECN,
	and ATO fields as follows:		and ATO fields as follows:
	Received (R, 1 bit): A boolean that indicates whether the packet was		Received (R, 1 bit): A boolean that indicates whether the packet was
	received. 0 indicates that the packet was not yet received and		received. 0 indicates that the packet was not yet received and
	the subsequent 15 bits (ECN and ATO) in this 16-bit packet metric		the subsequent 15 bits (ECN and ATO) in this 16-bit packet metric
	block are also set to 0 and MUST be ignored. 1 indicates that the		block are also set to 0 and MUST be ignored. 1 indicates that the
	packet was received and the subsequent bits in the block need to		packet was received and the subsequent bits in the block need to
	be parsed.		be parsed.
End of changes. 1 change blocks.
	12 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/