Fwd: [IANA #1149773] Request for media type text/vtt

Hi all,

I thought I'd share this with everyone - when trying to submit
"text/vtt" as a MIME media type to the IANA, we received the below
feedback.

This means we'll have to make some small changes to the WebVTT
specification that includes the MIME media type description at
https://w3c.github.io/webvtt/#iana .

None of this has an impact on the rest of the specification.
I'll prepare a pull request for it.

Kind Regards,
Silvia.

---------- Forwarded message ---------
From: Amanda Baber via RT <iana-mime@iana.org>
Date: Thu, Aug 29, 2019 at 3:28 PM
Subject: [IANA #1149773] Request for media type text/vtt
To: <silviapfeiffer1@gmail.com>


Dear Silvia,

The IESG-designated media type experts have reviewed this request and
returned the inline comments below.

If you have any questions, please don't hesitate to contact us.

If the template needs to be revised, please edit those revisions into
the clean copy at the end of this message.

Best regards,

Amanda Baber
Lead IANA Services Specialist

=====

Review:

Looks mostly good.  A couple of questions.

> Name: Silvia Pfeiffer
> Email: silviapfeiffer1@gmail.com
>
> Media type name: text
> Media subtype name: vtt
>
> Required parameters: None
>

Should be N/A per RFC 6838 Section 5.6.

Optional parameters:
> None
>

Same.

Encoding considerations: 8bit
>
> Security considerations:
> Text track files themselves pose no immediate risk unless sensitive
> information is included within the data. Implementations, however, are
> required to follow specific rules when processing text tracks, to ensure
> that certain origin-based restrictions are honored. Failure to correctly
> implement these rules can result in information leakage, cross-site
> scripting attacks, and the like.
>

Any preferred encryption to overcome the leakage?

Interoperability considerations:
> Rules for processing both conforming and non-conforming content are
> defined in this specification.
>

Are there any older versions of this specification that are incompatible
with this one?  The specification I looked at made it clear there were
earlier versions of the specification, but I didn't look at changes between
them to find out.

Published specification:
> https://www.w3.org/TR/webvtt1/#iana-text-vtt
>
> Applications which use this media:
> Web browsers and other video players.
>
>
> Fragment identifier considerations:
> None
>
> Restrictions on usage:
> No restrictions apply
>
> Provisional registration? (standards tree only):
> None
>
> Additional information:
>
> 1. Deprecated alias names for this type: None
> 2. Magic number(s): See below in comments
> 3. File extension(s): vtt
> 4. Macintosh file type code: No specific Macintosh file type codes are
> recommended for th
> 5. Object Identifiers: None
>
> General Comments:
> WebVTT files all begin with one of the following byte sequences
> representing an optional UTF-8 BOM, the ASCII string "WEBVTT" and finally a
> space, tab, line break or the end of the file (where "EOF" means the end of
> the file):
>
> EF BB BF 57 45 42 56 54 54 0A
> EF BB BF 57 45 42 56 54 54 0D
> EF BB BF 57 45 42 56 54 54 20
> EF BB BF 57 45 42 56 54 54 09
> EF BB BF 57 45 42 56 54 54 EOF
> 57 45 42 56 54 54 0A
> 57 45 42 56 54 54 0D
> 57 45 42 56 54 54 20
> 57 45 42 56 54 54 09
> 57 45 42 56 54 54 EOF
>
> Person to contact for further information:
>
> 1. Name: Silvia Pfeiffer
> 2. Email: silviapfeiffer1@gmail.com
>
> Intended usage: Common
> This file format provides subtitles and captions to Web browser and is
> also in use by other video players.
>
> Author/Change controller: W3C

=====

Original submission:

Name: Silvia Pfeiffer
Email: silviapfeiffer1@gmail.com

Media type name: text
Media subtype name: vtt

Required parameters: None

Optional parameters:
None

Encoding considerations: 8bit


Security considerations:
Text track files themselves pose no immediate risk unless sensitive
information is included within the data. Implementations, however, are
required to follow specific rules when processing text tracks, to
ensure that certain origin-based restrictions are honored. Failure to
correctly implement these rules can result in information leakage,
cross-site scripting attacks, and the like.

Interoperability considerations:
Rules for processing both conforming and non-conforming content are
defined in this specification.

Published specification:
https://www.w3.org/TR/webvtt1/#iana-text-vtt

Applications which use this media:
Web browsers and other video players.


Fragment identifier considerations:
None

Restrictions on usage:
No restrictions apply

Provisional registration? (standards tree only):
None

Additional information:

1. Deprecated alias names for this type: None
2. Magic number(s): See below in comments
3. File extension(s): vtt
4. Macintosh file type code: No specific Macintosh file type codes are
recommended for th
5. Object Identifiers: None

General Comments:
WebVTT files all begin with one of the following byte sequences
representing an optional UTF-8 BOM, the ASCII string "WEBVTT" and
finally a space, tab, line break or the end of the file (where "EOF"
means the end of the file):

EF BB BF 57 45 42 56 54 54 0A
EF BB BF 57 45 42 56 54 54 0D
EF BB BF 57 45 42 56 54 54 20
EF BB BF 57 45 42 56 54 54 09
EF BB BF 57 45 42 56 54 54 EOF
57 45 42 56 54 54 0A
57 45 42 56 54 54 0D
57 45 42 56 54 54 20
57 45 42 56 54 54 09
57 45 42 56 54 54 EOF

Person to contact for further information:

1. Name: Silvia Pfeiffer
2. Email: silviapfeiffer1@gmail.com

Intended usage: Common
This file format provides subtitles and captions to Web browser and is
also in use by other video players.

Author/Change controller: W3C

Received on Tuesday, 10 September 2019 09:37:07 UTC