The MPEG committee have defined the ``Delivery Multimedia Integration Framework'', to provide the multiplexing and synchronisation services necessary for the various MPEG coding schemes.
THe DMIF specification compares the overall design to FTP. There is a DMIF Application Interface (DAI) and the DMIF Network Interface (DNI). The application uses the DAI to establish a session, and the DMIF layer maps this through to the DNI to signal the appropriate network resources. How this happens is very application pattern dependent. For example, an application for local storage is quite different from one for remote interaction. Network channels are called transmuxes and a general model of mapping elementar MPEG streams onto these channels is defined, together with a specific mapping for low latency, low overhead (i.e. multiple streams per network channel) is offered in the TransMux channel model in the standard.
Other models are possible, but not specified - for example, a stream per channel in keeping with the IETF model would be feasible. This could then be mapped to an RTP flow, perhaps multicast and perhaps reserved using RSVP. This is currently being explored for remote retrieval using RTSP and for interactive use in the relevant IETF workign groups.