Jon,
After a short discussion about the issues, the TAG will put together our collected
thoughts on the issues raised (we don't have an outline yet but expect to in the
next couple of weeks). Henry Thompson will also (likely) be in Prague. So short
answer is "yes", one or more of us will be there and will participate in the panel.
Larry
--
http://larry.masinter.net
-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Tuesday, February 08, 2011 9:24 AM
To: Noah Mendelsohn
Cc: Larry Masinter; Peterson, Jon; Thomas Roessler
Subject: Re: TAG talk at March IETF meeting
Hello,
Before our IAB call tomorrow, I wanted to ping you guys and ask if you'd made any progress on this? Even if the TAG doesn't have consensus opinion as such, it would still be great to have an individual (TAG member or no) speak on the panel to their perspective on the role of standards in the web world. People in the IETF community really do need education on this, and while we can approximate the message, I suspect someone from your side could deliver it much better.
- J
On Feb 2, 2011, at 7:44 PM, Noah Mendelsohn wrote:
> We do indeed prefer to discuss things "in public", but if there's a problem
> in this case, we can also do it off the record. I still have to work out
> finding a slot on the F2F agenda, but I'm optimistic. Thank you.
>
> Noah
>
> On 2/2/2011 8:26 PM, Larry Masinter wrote:
>> I'd like to discuss this at the W3C TAG meeting next week, but the
>> minutes and discussion topics are open. Can I send this discription
>> to the public archives?
>>
>>
>> ==============
>>
>> This is the current plenary description we've been circulating in the IAB:
>>
>>> Advancements in the design of web browsers have introduced fundamental
>>> changes to the architecture of application protocols. The widespread
>>> availability and growing sophistication of JavaScript interpreters in
>>> browsers enables web servers to push to browsers all of the application
>>> logic required to implement a client-server protocol. Consequently, many
>>> client-server applications that once required an installed client on a
>>> host computer now can rely simply on a modern browser to act as a client
>>> for the purposes of a particular application. For example, where once
>>> email clients required a custom application to access an inbox,
>>> increasingly a web browser can serve this purpose as well as the
>>> purpose-built applications of the past. Similarly, HTTP with the
>>> assistance of JavaScript can subsume the functions performed by the
>>> protocols like POP3 and IMAP. The need for Internet standards beyond
>>> HTTP to implement an email inbox application consequently diminishes -
>>> why author standards and worry about interoperability of clients and
>>> servers when the server can simply push to the client all the code it
>>> needs to be interoperable?
>>>
>>> Many client-server applications on the Internet could potential migrate
>>> to this post-standardization environment. In this environment, there is
>>> of course still a role for the IETF to play: existing working groups
>>> like HyBi and OAuth are examples of areas where standards work is still
>>> required to support this application development paradigm. Collectively,
>>> we need to identify areas where the standardization is unlikely to be
>>> relevant in the future, and focus our efforts on those areas where our
>>> application designs will remain impactful.
>>
>>