 Two approaches are described. The first is designed to support maximum interoperability with MPEG System environments. The second is designed to provide maximum compatibility with other RTP- encapsulated media streams and future IETF conference-control work. RFC 2343: Describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. Bundling has advantages for this payload type particularly in video-on-demand applications. This payload type may be used when its advantages are important enough to sacrifice the modularity of having separate audio and video streams. RFC 2354: Summarizes a range of possible techniques for the repair of continuous media streams subject to packet loss. The techniques discussed include redundant transmission, retransmission, interleaving, and forward error correction. The range of applicability of these techniques is noted, together with the protocol requirements and dependencies. RFC 2429: Specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. Because the 1998 version of H.263 is a superset of the 1996 syntax, this format can also be used with the 1996 version of H.263, and is recommended for this use by new implementations. This format does not replace RFC 2190, which continues to be used by existing implementations, and may be required for backward compatibility in new implementations. RFC 2431: Specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in RTP. Each RTP packet contains all or a portion of one scan line as defined by ITU Recommendation BT.601-5, and includes fragmentation, decoding, and positioning information. RFC 2435: Describes the RTP payload format for JPEG video streams. The packet format is optimized for Real-Time video streams where codec parameters rarely change from frame to frame. RFC 2508: Describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead o