[ietf-types] Update to text/html registration

"Michael[tm] Smith" <mike@w3.org> Tue, 07 August 2012 11:16 UTC

Return-Path: <mike@jay.w3.org>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A1C4421F8674 for <ietf-types@ietfa.amsl.com>; Tue, 7 Aug 2012 04:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.489
X-Spam-Status: No, score=-9.489 tagged_above=-999 required=5 tests=[AWL=1.109, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9mw2vjLrO3El for <ietf-types@ietfa.amsl.com>; Tue, 7 Aug 2012 04:16:52 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org []) by ietfa.amsl.com (Postfix) with ESMTP id DD31D21F8671 for <ietf-types@ietf.org>; Tue, 7 Aug 2012 04:16:52 -0700 (PDT)
Received: from localhost ([] helo=MikeSmith.local) by jay.w3.org with esmtp (Exim 4.69) (envelope-from <mike@jay.w3.org>) id 1SyhmN-0000eB-9o; Tue, 07 Aug 2012 07:16:52 -0400
Date: Tue, 07 Aug 2012 20:16:49 +0900
From: "Michael[tm] Smith" <mike@w3.org>
To: ietf-types@ietf.org
Message-ID: <20120807111647.GB67292@sideshowbarker>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/0488deb39a35+poontang (2012-05-24 22:02:57+09:00)
Subject: [ietf-types] Update to text/html registration
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2012 11:16:53 -0000

Please update the registration for the text/html media type to reference
the HTML5 specification instead of RFC 2854.


Type name:

Subtype name:

Required parameters:
  No required parameters

Optional parameters:
    The charset parameter may be provided to definitively specify the
    document's character encoding, overriding any character encoding
    declarations in the document. The parameter's value must be the name of
    the character encoding used to serialize the file, must be a valid
    character encoding name, and must be an ASCII case-insensitive match
    for the preferred MIME name for that encoding. [IANACHARSET]

Encoding considerations:
  8bit (see the section on character encoding declarations)

Security considerations:
  Entire novels have been written about the security considerations that
  apply to HTML documents. Many are listed in this document, to which the
  reader is referred for more details. Some general concerns bear
  mentioning here, however:

  HTML is scripted language, and has a large number of APIs (some of which
  are described in this document). Script can expose the user to potential
  risks of information leakage, credential leakage, cross-site scripting
  attacks, cross-site request forgeries, and a host of other problems.
  While the designs in this specification are intended to be safe if
  implemented correctly, a full implementation is a massive undertaking
  and, as with any software, user agents are likely to have security bugs.

  Even without scripting, there are specific features in HTML which, for
  historical reasons, are required for broad compatibility with legacy
  content but that expose the user to unfortunate security problems. In
  particular, the img element can be used in conjunction with some other
  features as a way to effect a port scan from the user's location on the
  Internet. This can expose local network topologies that the attacker
  would otherwise not be able to determine.

  HTML relies on a compartmentalization scheme sometimes known as the
  same-origin policy. An origin in most cases consists of all the pages
  served from the same host, on the same port, using the same protocol.

  It is critical, therefore, to ensure that any untrusted content that
  forms part of a site be hosted on a different origin than any sensitive
  content on that site. Untrusted content can easily spoof any other page
  on the same origin, read data from that origin, cause scripts in that
  origin to execute, submit forms to and from that origin even if they are
  protected from cross-site request forgery attacks by unique tokens, and
  make use of any third-party resources exposed to or rights granted to
  that origin.

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

Published specification:
  This HTML5 specification is the relevant specification. Labeling a
  resource with the text/html type asserts that the resource is an HTML
  document using the HTML syntax.

Applications that use this media type:
  Web browsers, tools for processing Web content, HTML authoring tools,
  search engines, validators.

Additional information:
  Magic number(s):
    No sequence of bytes can uniquely identify an HTML document. More
    information on detecting HTML documents is available in the Media Type
    Sniffing specification.

    File extension(s):
      "html" and "htm" are commonly, but certainly not exclusively, used as
      the extension for HTML documents.

    Macintosh file type code(s):

Person & email address to contact for further information:
   Michael[tm] Smith <mike@w3.org>

Intended usage:

Restrictions on usage:
  No restrictions apply.

  Ian Hickson <ian@hixie.ch>

Change controller:

Fragment identifiers used with text/html resources either refer to the
indicated part of the document or provide state information for in-page

Michael[tm] Smith http://people.w3.org/mike