MIME Type Registration for MPEG-4
RFC 4337

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'MIME Type Registration for MPEG-4' to 
         Proposed Standard 

The IESG has approved the following document:

- 'MIME Type Registration for MPEG-4 '
   <draft-lim-mpeg4-mime-04.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Allison Mankin.

A URL of this Internet-Draft is:

Technical Summary
   This specification defines the standard MIME types associated with MP4 
   files. The document also recommends use of registered MIME types 
   according to the type of contents.  There are five types, audio/mp4,
   video/mp4, application/mp4, application/mpeg4-iod, and 
   application/mpeg-iod-xmt.   IOD is the Initial Object Descriptor,
   and the last two are binary and textual formatted bodies to carry them.

 Working Group Summary
  Although this is not a working group document, there was extensive
  discussion and review by the Audio Video Transport Working Group,
  based on their expertise in media types and mpeg4 in the net,
  and the result was several significant revisions to address concerns.
  A media review was solicited on the ietf-types list and did not raise
  any comments.  There were no comments during the IETF Last
  Call period.
Protocol Quality
 The specification notes that there are multiple interoperating implementations
  of these media types.  Allison Mankin is the sponsoring Area Director for 
  this specification, and Colin Perkins and Magnus Westerlund gave it its pre-
  publication review and care.

Note to RFC Editor

  Please expand IOD to Initial Object Descriptor in both sections 3.4. and 3.5

Sections 3.1, 3.2, 3.3, 3.4 and 3.5:
Security considerations:     See section 5 of RFC XXXX
Security considerations:     See section 4 of RFC XXXX
[this document's security considerations are in section 4 now]