I have to recognise that the name choice for this effort was not entirely
appropriate as it drags the spotlight on the "user interface" while leaving the
"remoting" unfairly in the shadows.
- What expertise do you see that the IETF has (and other
groups do not
have) that makes it the right body to work on this set of issues?
With the risk of repeating what Dave already mentioned, I have to point out
that in the process of remoting a ui two entities (i.e. the server and the
client) are exchanging information about display objects (i.e. widgets) over
As there are other bodies that have the experience on defining what display
objects are needed and what is their behaviour, the aim of this effort is to
develop an open, platform-independent mechanism of creating and maintaining
remote display objects and the focus should be on the network-based mechanisms
covering the connectivity, reliability, security, etc., on which the IETF has
the best experience around.
- What importance to the Internet does this work have that makes it a
correct use of IETF resources?
Broadband and wireless technology will enable more and more "smart" devices
(i.e. Internet tablets, PDAs, mobile phones, PCs, etc.) to be connected to the
Internet. Soon the proliferation of these devices will make them the most
numerous device "category" on the Internet and their users will want to
interact remotely, for various reasons, with applications that are not hosted
on the devices; thus, making this effort fit within IETF's scope "protocols and
practices for which secure and scalable implementations are expected to have
wide deployment and interoperation on the Internet, or to form part of the
infrastructure of the Internet."
Ietf mailing list