The application/smil and application/smil+xml Media Types
draft-hoschka-smil-media-type-13

[Note]: 'Back on ballot to confirm the IESG is okay with a late change related to SMIL versions.  The substantive change is that SMIL is now being registered as OBSOLETE' added by Ted Hardie

[Ballot comment]
Reviewed by Scott Brim, Gen-ART

I (Harald) do not choose to cast a DISCUSS, but want to call attention to these comments from the review:

Overall I see no technical problems but a
couple procedural ones, which I would bring up.  If they are considered
acceptable then I believe the draft is ready to go:

- RFC3023 says:

    "Registrations for new XML-based media types under top-level types
    other than "text" SHOULD, in specifying the charset parameter and
    encoding considerations, define them as: "Same as [charset parameter
    / encoding considerations] of application/xml as specified in RFC
    3023."

  but this draft says:

    "charset

    All of the considerations described in RFC3023 also apply to the
    SMIL media type."

  Is that close enough?  It parallels how RFC3023 wants you to treat
  security considerations, but that may not be a good thing.

- Missing newline:

  "To: ietf-types@iana.org Subject: Registration of MIME media type
  application/smil+xml"

- (There are a couple word choices I would change if I were editor, but
  the intent is clear in all cases.)

[Ballot discuss]
Needs a security considerations section.  The easiest solution is to
  place the text that is in the application/smil registration in the
  security considerations section.  Then, refer to the new section from
  both the application/smil and the application/smil+xml registrations.