Re: [apps-discuss] HTML5 and RFC 2854

Mykyta Yevstifeyev <evnikita2@gmail.com> Sat, 25 June 2011 11:16 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E24228006; Sat, 25 Jun 2011 04:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level:
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU8MJqfQfgL5; Sat, 25 Jun 2011 04:16:07 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1433C228005; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
Received: by fxe4 with SMTP id 4so916178fxe.27 for <multiple recipients>; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8n5LXtUencGcqFfHcL4/1l8t1tah0X/DYYEm+VKultA=; b=u7clKSfkETAsrkWieK1Falb8ODY8VoUa42h/yjVK7nXQ0wExiea79E02xXlE34OxD4 rmxE5qW21ASRcK6z9BveNfN94n/Q7gg4IYHWtOkYF1YgzB3yqDhPzTZ/GPpY27gH5vZu LhOf/Viik4Bwionv6JRa5AAoOMlkTbNpWK6pQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=uxDLrurymtWQtiGIpox0Tne59T2KYRRWNT/49TnEqpC6mvnEYrNoWFfofe74qDopII 9LkqZj6kRhhFhtR66I/Tg8vuZeuSDFM7WDlSjYNeJfqz6nG/u/FYeMKMTOC0yk6S09c7 eaBjEfRPvb+PpWVzGI1m23YY7o075TtmScL3I=
Received: by 10.223.20.210 with SMTP id g18mr6024401fab.30.1309000566038; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id e16sm2204488fak.41.2011.06.25.04.16.04 (version=SSLv3 cipher=OTHER); Sat, 25 Jun 2011 04:16:04 -0700 (PDT)
Message-ID: <4E05C3A1.9080002@gmail.com>
Date: Sat, 25 Jun 2011 14:16:49 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4E04C38A.6090505@gmail.com> <4E05AFF0.9080705@gmx.de>
In-Reply-To: <4E05AFF0.9080705@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf-types@ietf.org, Apps-discuss list <apps-discuss@ietf.org>, public-html-comments-request@w3.org
Subject: Re: [apps-discuss] HTML5 and RFC 2854
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 11:16:09 -0000

25.06.2011 12:52, Julian Reschke wrote:
> On 2011-06-24 19:04, Mykyta Yevstifeyev wrote:
>> Hello all,
>>
>> Cross-posting this to Apps-discuss and html-comments lists. The proposed
>> HTML5 specification (http://dev.w3.org/html5/spec/), which is currently
>> in Last Call, in its Section 12.1 updates the registration of text/html
>> media type. I should note that we have RFC 2854
>> (http://tools.ietf.org/html/rfc2854) which also specifies this media
>> type. Therefore the question is what should be done with this RFC.
>> Should it be retired upon approval of HTML5? Or something else?
>>
>> Mykyta Yevstifeyev
>
> HTML5 currently tries to obsolete RFC 2854; I believe this is a problem.
>
> From <http://tools.ietf.org/html/rfc4288#section-9>:
>
>    Changes should be requested only when there are serious omissions or
>    errors in the published specification.  When review is required, a
>    change request may be denied if it renders entities that were valid
>    under the previous definition invalid under the new definition.
>
> Note the second sentence; many currently valid HTML4 documents aren't 
> valid HTML5 documents anymore. Thus, a document updating the media 
> type registration for text/html will need to continue to allow 
> HTML4.01 documents as well.
Currently copying this to ietf-types@ietf.org .  I personally think 
HTML5 should be backwards-compatible with previous version as well as 
the media type defined for that version.  So, first what should be done 
is identification whether there are some issue which make create 
confusion with the aforementioned regulations of RFC 4288.  Next, if it 
doesn't, IANA should update registration of this media type with 
reference to HTML5, not RFC 2854.  RFC 2854 itself should then be moved 
to Historic in order to represent it isn't an authoritative definition 
any more.  This won't create confusion with different definitions of the 
media type.

Just my opinion.

Mykyta Yevstifeyev
>
> See related HTML WG issue: <http://www.w3.org/html/wg/tracker/issues/53>
>
> Best regards, Julian
>