Rec. ITU-T H.264 (01/2012) 7.4.2.6 End of stream RBSP semantics The end of stream RBSP indicates that no additional NAL units shall be present in the bitstream that are subsequent to the end of stream RBSP in decoding order. The syntax content of the SODB and RBSP for the end of stream RBSP are empty. No normative decoding process is specified for an end of stream RBSP. NOTE - When an end of stream NAL unit is present, the bitstream is considered to end (for purposes of the scope of this Recommendation | International Standard). In some system environments, another bitstream may follow after the bitstream that has ended, either immediately or at some time thereafter, possibly within the same communication channel. Under such circumstances, the scope of this Recommendation | International Standard applies only to the processing of each of these individual bitstreams. No requirements are specified herein regarding the transition between such bitstreams (e.g., in regard to timing, buffering operation, etc.). 7.4.2.7 Filler data RBSP semantics The filler data RBSP contains zero or more bytes. No normative decoding process is specified for a filler data RBSP. ff byte is a byte. It is a requirement of bitstream conformance that the value of byte shall be equal to 0xFF. 7.4.2.8 Slice layer without partitioning RBSP semantics The slice layer without partitioning RBSP consists of a slice header and slice data. 7.4.2.9 Slice data partition RBSP semantics 7.4.2.9.1 Slice data partition A RBSP semantics When slice data partitioning is in use, the coded data for a single slice is divided into three separate partitions. Slice data partition A contains all syntax elements of category 2. Category 2 syntax elements include all syntax elements in the slice header and slice data syntax structures other than the syntax elements in the residual() syntax structure. slice_id identifies the slice associated with the slice data partition. The value of slice id is constrained as follows: If separate_colour_plane_flag is equal to 0, the fo