1. � MPEG-4 on IP Framework draft-singer-mpeg4-ip-00 MPEG M6150 Joint IETF/MPEG submission, IETF to ‘standardize’ David Singer singer@apple.com Apple Computer, USA Joint IETF/MPEG submission, IETF to ‘standardize’ David Singer singer@apple.com Apple Computer, USA

2. � 2MPEG-4 on IP Why? and What? Common framework for ANY part, or all, of MPEG-4 Common framework for ANY part, or all, of MPEG-4 agree on that which can be agreed on…agree on that which can be agreed on… intended to be non-controversialintended to be non-controversial collation of ideas and practicescollation of ideas and practices Enhance interoperability Enhance interoperability Document and assign MIME types Document and assign MIME types Refer to and use only existing drafts and specifications Refer to and use only existing drafts and specifications

3. � 3MPEG-4 on IP Areas Covered Use of RTP Use of RTP common features of payload formatscommon features of payload formats Unicast and MulticastUnicast and Multicast Use of SDP Use of SDP Use of RTSP Use of RTSP MIME names for MPEG-4 files and data structures MIME names for MPEG-4 files and data structures

4. � 4MPEG-4 on IP Areas NOT covered RTP payload formats (there are several already) RTP payload formats (there are several already) Or their names (RTPMAP names) Or their names (RTPMAP names)

5. � 5MPEG-4 on IP RTP mapping Send in decode order Send in decode order 1 st frame in each packet, allow interleave1 st frame in each packet, allow interleave Timescales the same Timescales the same Timestamp is the presentation time (Composition time stamp) Timestamp is the presentation time (Composition time stamp) Use RTP synchronization (map OCR or FCR to NTP) Use RTP synchronization (map OCR or FCR to NTP)

6. � 6MPEG-4 on IP RTP payload formats One, simple, base-level scheme ought to be available One, simple, base-level scheme ought to be available carry any Mpeg-4 streamcarry any Mpeg-4 stream possibly non-optimallypossibly non-optimally any receiver ought to be able to handle itany receiver ought to be able to handle it it’s good if senders can be persuaded to send itit’s good if senders can be persuaded to send it One scheme only for Flexmux One scheme only for Flexmux handles the many-small-PDUs problemhandles the many-small-PDUs problem

7. � 7MPEG-4 on IP RTP Payloads needed Encourage development of new schemes Encourage development of new schemes Media-aware packetizationMedia-aware packetization Error resilience and protection Error resilience and protection either use existing and developing IETF techniqueseither use existing and developing IETF techniques or do custom formats, if more applicableor do custom formats, if more applicable –(combined source/channel coding)

8. � 8MPEG-4 on IP SDP Use—IOD 0 or 1 MPEG session in an SDP session 0 or 1 MPEG session in an SDP session would be good to loosen this restrictionwould be good to loosen this restriction If an IOD is needed, find by If an IOD is needed, find by URL giving locationURL giving location or DESCRIBE in RTSP, if no location givenor DESCRIBE in RTSP, if no location given global attribute a=mpeg4-iod[:location] global attribute a=mpeg4-iod[:location] two round trips, different ‘accept’ values, in SDP two round trips, different ‘accept’ values, in SDP location is data:, http: etc. location is data:, http: etc.

9. � 9MPEG-4 on IP SDP Use—Stream Mapping Mapping Elementary Stream IDs (MPEG) to RTP session Mapping Elementary Stream IDs (MPEG) to RTP session single streamsingle stream FlexMuxFlexMux For single streams, attrribute a=mpeg4- esid For single streams, attrribute a=mpeg4- esid For flexmux, part of For flexmux, part of a=mpeg4-flexmuxinfo:locatioona=mpeg4-flexmuxinfo:locatioon

10. � 10MPEG-4 on IP RTSP Usage Care with sessions, which are dependent/independent streams Care with sessions, which are dependent/independent streams Care with tearing down streams and losing session ID Care with tearing down streams and losing session ID Dual round-trip IF IOD is needed noted already Dual round-trip IF IOD is needed noted already

11. � 11MPEG-4 on IP MIME names The MPEG-4 format when used as a file (e.g. HTTP) The MPEG-4 format when used as a file (e.g. HTTP) The IOD, over RTSP/DESCRIBE or file access The IOD, over RTSP/DESCRIBE or file access FlexMux Info (mapping, structure) FlexMux Info (mapping, structure) Not payload names for RTPMAP Not payload names for RTPMAP they are in the I-Ds or RFCs that document those payload formatsthey are in the I-Ds or RFCs that document those payload formats

12. � 12MPEG-4 on IP Issues MIME name for the standard file format: MIME name for the standard file format: MPEG4 or MP4?MPEG4 or MP4? Video, audio, or application?Video, audio, or application? Indicating terminal buffering needed? Indicating terminal buffering needed? At most 1 MPEG session in SDP At most 1 MPEG session in SDP (Ignorance)? (Ignorance)? file format for elementary streamsfile format for elementary streams Multicast URLsMulticast URLs Flexmux tables?Flexmux tables?

13. � 13MPEG-4 on IP Next steps (MPEG has reviewed once) (MPEG has reviewed once) Form next draft based on IETF and MPEG comments Form next draft based on IETF and MPEG comments probably also email discussionprobably also email discussion AHG meeting in September AHG meeting in September MPEG meeting in October MPEG meeting in October