HTTP Live Streaming
RFC 8216

Received changes through RFC Editor sync (created alias RFC 8216, changed abstract to 'This document describes a protocol for transferring unbounded streams of multimedia data.  It specifies the data format of the files and the actions to be taken by the server (sender) and the clients (receivers) of the streams.  It describes version 7 of this protocol.', changed pages to 60, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-08-31, changed ISE state to Published RFC)

(Via drafts-eval@iana.org): IESG/Authors/RFC ISE:

The IANA Services Operator has completed its review of draft-pantos-http-live-streaming-21. If any part of this review is inaccurate, please let us know.

We have one question about this document.

When the RFC Independent Stream Editor notifies us that the actions requested in this document can be performed, we will replace the current template for media type registration application/vnd.apple.mpegurl with the template contained in this document.

There is one issue, though: in the future, we may create a "file extension" column at https://www.iana.org/assignments/media-types, which would be populated by extracting data from the "file extension" fields in registration templates.

Can the file extension information in this template be placed in a field labeled "File extension(s):", as in RFC 6838?

Thank you,

Amanda Baber
Lead IANA Services Specialist