type is equal to 14 or 20 and for which svc_extension_flag is equal to 0. The value of svc_extension_flag shall be equal to 0 for coded video sequences conforming to one or more profiles specified in Annex H. Decoders conforming to one or more profiles specified in Annex H shall ignore (remove from the bitstream and discard) NAL units for which nal_unit_type is equal to 14 or 20 and for which SVC_extension_flag is equal to 1. rbsp_byte[ i ] is the i-th byte of an RBSP. An RBSP is specified as an ordered sequence of bytes as follows. The RBSP contains an SODB as follows: If the SODB is empty (i.e., zero bits in length), the RBSP is also empty. Otherwise, the RBSP contains the SODB as follows: 1) The first byte of the RBSP contains the (most significant, left-most) eight bits of the SODB; the next byte of the RBSP contains the next eight bits of the SODB, etc., until fewer than eight bits of the SODB remain. 2) rbsp_trailing_bits() are present after the SODB as follows: The first (most significant, left-most) bits of the final RBSP byte contains the remaining bits of the SODB (if any). ii) The next bit consists of a single rbsp_stop_one_bite equal to 1. iii) When the rbsp_stop_one_bit is not the last bit of a byte-aligned byte, one or more rbsp_alignment_zero_bit is present to result in byte alignment. One or more cabac_zero word 16-bit syntax elements equal to 0x0000 may be present in some RBSPs after the rbsp_trailing_bits() at the end of the RBSP. Syntax structures having these RBSP properties are denoted in the syntax tables using an '_rbsp" suffix. These structures shall be carried within NAL units as the content of the rbsp_byte[ i ] data bytes. The association of the RBSP syntax structures to the NAL units shall be as specified in Table 7-1. Rec. ITU-T H.264 (01/2012) NOTE 6 - When the boundaries of the RBSP are known, the decoder can extract the SODB from the RBSP by concatenating the bits of the bytes of the RBSP and discarding the rbsp_stop_one_bit, which is the last (least significant, right-most) bit eq