id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1119	Undefined HRD syntax elements and variables	vdrugeon	yk	"In Annex C, it seems that some syntax elements and variables are checked without being always defined. 

In C.1 General step 9: ""When the PT SEI message associated with AU 0 has pt_cpb_alt_timing_info_present_flag equal to 1, …"". But pt_cpb_alt_timing_info_present_flag is not always signalled. So adding an inference for this syntax element may be necessary.

In C.2.2 and C.2.3, the variable DefaultInitCpbParamsFlag is checked without necessarily being defined, since it is defined in C.1 only when pt_cpb_alt_timing_info_present_flag is equal to 1. Either the value of pt_cpb_alt_timing_info_present_flag should be added as condition before checking the value of DefaultInitCpbParamsFlag or there should be a default value of DefaultInitCpbParamsFlag specified when pt_cpb_alt_timing_info_present_flag is equal to 0.

Is the second condition in the definition of the numbers n2 and n3 correct: ""The associated BP SEI message has bp_alt_cpb_params_present_flag equal to 1""? Why is bp_alt_cpb_params_present_flag rather than pt_cpb_alt_timing_info_present_flag considered given that pt_cpb_alt_timing_info_present_flag seems to be the syntax element used everywhere else when using alternate timings?

In C.2.3, the PT SEI syntax elements cpb_alt_initial_removal_delay_delta, cpb_alt_initial_removal_offset_delta, cpb_delay_offset and dpb_delay_offset are mentioned. These syntax elements do not exist. The prefix ""pt_nal"" or ""pt_vcl"" is missing.
"	defect	closed	minor		spec		fixed		ksuehring bbross XiangLi fbossen jvet@…