me or complementary reference field pair that has the lowest LongTermPicNum value and proceeding through in ascending order to the long-term reference entry that has the highest LongTermPicNum value. 3. When the reference picture list RefPicList1 has more than one entry and RefPicList1 is identical to the reference picture list RefPicListO, the first two entries RefPicList1[ and RefPicList1[ are switched. NOTE 2 - A non-paired reference field is not used for inter prediction of frames (independent of the value of MbaffFrameFlag). 8.2.4.2.4 Initialisation process for reference picture lists for B slices in fields This initialisation process is invoked when decoding a B slice in a coded field. When this process is invoked, there shall be at least one reference field (which can be a field of a reference frame) that is currently marked as "used for reference" (i.e., as "used for short-term reference" or "used for long-term reference") and is not marked as "non-existing". When decoding a field, each field of a stored reference frame is identified as a separate reference picture with a unique index. The order of short-term reference pictures in the reference picture lists RefPicList0 and RefPicList1 depend on output order, as given by PicOrderCnt(). When pic_order_cnt_type is equal to 0, reference pictures that are marked as "non-existing" as specified in clause 8.2.5.2 are not included in either RefPicList0 or RefPicList1. NOTE 1 - When gaps_in_frame_num_value_allowed_flagi is equal to 1, encoders should use reference picture list modification to ensure proper operation of the decoding process (particularly pic_order_cnt_type is equal to 0, in which case PicOrderCnt() is not inferred for "non-existing" frames). NOTE 2 - When decoding a field, there are effectively at least twice as many pictures available for referencing as there would be when decoding a frame at the same position in decoding order. Three ordered lists of reference frames, refFrameList0ShortTerm, refFrameList1ShortTerm and refFrameListLongTerm, are de