Re: [apps-discuss] Last Call for HTML5 in the W3C

Dzonatas Sol <dzonatas@gmail.com> Fri, 17 June 2011 22:11 UTC

Return-Path: <dzonatas@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 53BC411E8130 for <apps-discuss@ietfa.amsl.com>; Fri, 17 Jun 2011 15:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.408
X-Spam-Level:
X-Spam-Status: No, score=-5.408 tagged_above=-999 required=5 tests=[AWL=-1.809, 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 9fg3BbfN8rpq for <apps-discuss@ietfa.amsl.com>; Fri, 17 Jun 2011 15:11:14 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7DB11E812F for <apps-discuss@ietf.org>; Fri, 17 Jun 2011 15:11:14 -0700 (PDT)
Received: by pzk5 with SMTP id 5so2416724pzk.31 for <apps-discuss@ietf.org>; Fri, 17 Jun 2011 15:11:14 -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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bE8Ds6Y0+LEwJCE9aMlp04IpYks4q3XHoP7711t4TP8=; b=oeHL3Qg1ptR9s3IgbshAwEnVAdDtfL6jhI7KH5CehUguAYhOpm8g/nY1cx5PvWUaci WAsFk9afk4v30+Y6WwNfw87ePgP0IGjtpPdI0MBgSt9zLaT9nkD7vO5981OnpWzThMae x9JRHb2JBq0Kp5+4wEZYRqi1Gk/pMRi8+ZfoI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=CnluZU66JRegAJBZtFGKIip4zSX3HrShywAvSOkgfDVlK+0LoT4AVQyLfE4tukcF2B BV9w8gp2NyraWoDFL+di+QI2Aguouc9KExtHUAl+6M9q6J6Eo5kRvqFXfu2Jt8QkJ0++ hIqoIsoOwKiXS0eFPNm3+p1NDk9S4LGWjxA9k=
Received: by 10.143.20.20 with SMTP id x20mr383494wfi.131.1308348674121; Fri, 17 Jun 2011 15:11:14 -0700 (PDT)
Received: from [192.168.0.50] (adsl-70-133-70-225.dsl.scrm01.sbcglobal.net [70.133.70.225]) by mx.google.com with ESMTPS id p5sm1701988pbk.36.2011.06.17.15.11.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Jun 2011 15:11:13 -0700 (PDT)
Message-ID: <4DFBD0C5.50208@gmail.com>
Date: Fri, 17 Jun 2011 15:10:13 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110505 Icedove/3.0.11
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <ED845ED2-A05F-42B1-B17A-E8B3A6F07D7B@mnot.net>
In-Reply-To: <ED845ED2-A05F-42B1-B17A-E8B3A6F07D7B@mnot.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] Last Call for HTML5 in the W3C
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: Fri, 17 Jun 2011 22:11:15 -0000

That is the API perspective. That would also make the ABI perspective 
regard HTTP status codes 200, 201, 202, and 203 as standard input, 
output, error, and one bit "control flow" where TLS does not exist in 
SI/SO modes.

Note that "network order" considers top three bits, yet that is not 
clear about top three of each byte or the thee most significant bits of 
the last byte. That standard creates this kind of mask:
100000001000000011111000

Can we just default something like the OAuth MAC header to that code to 
signify that mask is known? Then, check /.well-known/ for that bitstream?

We can then determine the queue direction.

On 06/17/2011 01:45 PM, Mark Nottingham wrote:
> [ with my IETF/W3C Liaison hat on ]
>
> The W3C has announced a Last Call on the HTML5 specification; see:
>   http://www.w3.org/2011/02/htmlwg-pr.html
>
> The IETF has been encouraged to provide feedback, especially regarding HTML's use of and interface with IETF technologies.
>
> For background on Last Call in their process, see:
>   http://www.w3.org/2005/10/Process-20051014/tr.html#last-call
>
> and the specification itself:
>   http://www.w3.org/TR/html5/
> paying special attention to the 'status of this document' section for information about the Last Call and how to provide feedback.
>
> See also their LC FAQ:
>   http://www.w3.org/2011/05/html5lc-faq.html
>
> Cheers,
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>    


-- 
--- http://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering
Ag-Biotech, Virtual Reality, Consultant