rfc9328v3.txt		rfc9328.txt
	skipping to change at line 2029 ¶		skipping to change at line 2029 ¶
	The value of the parameter is a comma-separated (',') list of		The value of the parameter is a comma-separated (',') list of
	base64 encoding (Section 4 of [RFC4648]) representations of SEI		base64 encoding (Section 4 of [RFC4648]) representations of SEI
	NAL units, as specified in [VSEI].		NAL units, as specified in [VSEI].
	| Informative note: Intentionally, no list of applicable or		| Informative note: Intentionally, no list of applicable or
	| inapplicable SEI messages is specified here. Conveying		| inapplicable SEI messages is specified here. Conveying
	| certain SEI messages in sprop-sei may be sensible in some		| certain SEI messages in sprop-sei may be sensible in some
	| application scenarios and meaningless in others. However, a		| application scenarios and meaningless in others. However, a
	| few examples are described below:		| few examples are described below:
			|
	1. In an environment where the bitstream was created from film-		| In an environment where the bitstream was created from film-
	based source material, and no splicing is going to occur		| based source material, and no splicing is going to occur
	during the lifetime of the session, the film grain		| during the lifetime of the session, the film grain
	characteristics SEI message is likely meaningful, and sending		| characteristics SEI message is likely meaningful, and
	it in sprop-sei, rather than in the bitstream at each entry		| sending it in sprop-sei, rather than in the bitstream at
	point, may help with saving bits and allows one to configure		| each entry point, may help with saving bits and allows one
	the renderer only once, avoiding unwanted artifacts.		| to configure the renderer only once, avoiding unwanted
			| artifacts.
	2. Examples for SEI messages that would be meaningless to be		|
	conveyed in sprop-sei include the decoded picture hash SEI		| Examples for SEI messages that would be meaningless to be
	message (it is close to impossible that all decoded pictures		| conveyed in sprop-sei include the decoded picture hash SEI
	have the same hashtag) or the filler payload SEI message (as		| message (it is close to impossible that all decoded pictures
	there is no point in just having more bits in SDP).		| have the same hashtag) or the filler payload SEI message (as
			| there is no point in just having more bits in SDP).
	max-lsr:		max-lsr:
	The max-lsr MAY be used to signal the capabilities of a receiver		The max-lsr MAY be used to signal the capabilities of a receiver
	implementation and MUST NOT be used for any other purpose. The		implementation and MUST NOT be used for any other purpose. The
	value of max-lsr is an integer indicating the maximum processing		value of max-lsr is an integer indicating the maximum processing
	rate in units of luma samples per second. The max-lsr parameter		rate in units of luma samples per second. The max-lsr parameter
	signals that the receiver is capable of decoding video at a higher		signals that the receiver is capable of decoding video at a higher
	rate than is required by the highest level.		rate than is required by the highest level.
	| Informative note: When the OPTIONAL media type parameters		| Informative note: When the OPTIONAL media type parameters
End of changes. 1 change blocks.
	14 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.48.