As has been mentioned before in this thread the AVT working group is currently evaluating draft-ietf-avt-rtp-mpeg4-es-05.txt. The IESG received the following liaison statement from ISO/IEC JTC1/SC29/WG11 (MPEG).
We (the Transport Area Directors) would like to hear from SG16 (or at least the people on this list and anyone else who cares to comment) if they have any comments on this liaison statement or advice to us about what we should do at this time.
Allison Mankin & Scott Bradner
----------
INTERNATIONAL ORGANISATION FOR STANDARDISATION ORGANISATION INTERNATIONALE DE NORMALISATION ISO/IEC JTC1/SC29/WG11 CODING OF MOVING PICTURES AND AUDIO
ISO/IEC JTC 1/SC 29/ WG 11 N3694 October 2000, La Baule
Title: Liaison Statement to IETF on MPEG-4 on IP Source: WG11 Status: Approved
WG11 has progressed in the development of a framework for the carriage of MPEG-4 content over IP networks, and we have included the recent version, N3718, for your information.
WG11 understands that for the carriage of MPEG-4 elementary streams over IP networks, there is an Internet-Draft <draft-ietf-avt-rtp-mpeg4-es-05.txt> eligible for promotion to a standards track RFC. However, there is no consensus yet on the payload formats for the carriage of various MPEG-4 streams in WG11. For instance, there are still strong concerns that the payload format for MPEG-4 audio specified in <draft-ietf-avt-rtp-mpeg4-es-05.txt>, while adequate for a range of applications, is not appropriate for general use. That is, <draft-ietf-avt-rtp-mpeg4-es-05.txt> may not be used in the context of MPEG-4 over IP framework in the future. WG11 would prefer to find a design for a single RTP payload format that would suffice for the carriage of all MPEG-4 content over IP networks.
Therefore, WG11 is concerned about promotion of <draft-ietf-avt-rtp-mpeg4-es-05.txt> to standards track RFC because of possible interoperability problems between different types of terminals using MPEG-4 content. WG11 recommends that IETF suspend promotion to standards track RFC of all IETF drafts related to the carriage of MPEG-4 content over IP networks and wait for WG11 to finalize its current work on a generic solution that includes framework and payload formats for the carriage of MPEG-4 content over IP networks.
WG11 commits to the following schedule:
Draft of framework at La Baule meeting Finalization of framework by December 1st, 2000 Finalization of generic payload format by December 1st, 2000 Finalization of video payload format by December 1st, 2000 Finalization of audio payload format by January 2001 Finalization of FlexMux payload format by January 2001
WG11 is aware that the ITU-T wishes to move forward with the adoption of an RTP payload specification for MPEG-4 Elementary Streams into the H.323 suite Recommendations. Therefore, in a companion liaison statement to ITU-T SG 16, WG11 has requested that ITU-T either delay the decision for the affected H.323 suite Recommendations or allow an interim revision without incurring a long delay such as two years.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com