The larger thesis
The INternet FileSystem maps the DNS or other network namespaces
into the host filesystem,
one may conceptually
and expect to be able list the contents with
browse them with, say
More usefully, perhaps,
one could use this unification of the network and filesystem namespaces
to cross-compile, remote-deploy "applets" by simply copying them
and setting appropriate permissions etc.
The scheme sounds a bit like
but notice that
even Plan9 stopped short of unifying
the network namespace.
as far as I can figure out,
there seems to be no way to think of the DNS
as the primary global addressing mechanism
other forms of address,
The problem is three-fold:
INFS is an experimental step to address the third aspect.
The existence of a manually coordinated IP space
was assumed in the design of the DNS,
it prevents the DNS from being operated
without IP (or an equivalent addressing mechanism).
This is better explained in my thesis.
If a DNS-like namespace can be had
as a primary addressing mechanism,
without incurring penalties elsewhere,
the need for a globally coordinated IP gets questioned,
that would be too fundamental an issue.
It is hard to think so fundamentally differently
without a model or a prototype to work with.
Even with INFS itself,
there's clearly a Pandora's box of
user interface and network application redesign
opportunities waiting to be opened,
which will take much work
and need tons of discussion.
I am more immediately concerned with
To get the basic idea across and to set the ball rolling,
you still need to say
to see the SSH header,
echo -e "GET / HTTP/1.0\n\n" | rw ./tcp:80
to dump index.html.
reduction of overall code footprint and context switches,
general IPv6/v4 transparency for applications,
and weaning applications and uses from IP addresses,
so that we may introduce self-management of IP addresses
on network, provider and Internet scales.