My research group, as well as everyone who currently uses PlanetLab (and
presumably the future GENI platform, if it comes to pass) faces a
different deployment scenario than what the operational folks are used
to. Setting up anycast might be possible, but is operationally very very
difficult for
what do you think of as expensive?
Anything that has 1000% or higher markup. There is also another kind of
expense: solving the SiteFinder problem took a lot of time, public
outcry and moral outrage from a large group of people. It would have
been nice to just scoot over to a competitor. These
Hi Stephane,
On Tue, 2006-11-28 at 11:41 +0100, Stephane Bortzmeyer wrote:
let's assume two registries R1 and R2
manage the namespace .example. A customer C1 wants to create
foobar.example and asks to registry R1. A customer C2 wants to create
foobar.example and asks to registry R2. There is
Stephane,
It is not artificial, it is the way it has to work. You cannot have
multiple registries for one TLD, period. No more than you can have
perpetual motion.
Be careful about making statements about impossibility without an
associated impossibility proof. History is full of people who
But I'll do this only if asked.
Consider it done.
Ok, here is a rough protocol sketch. For simplicity, I'll gloss over
non-critical details, e.g. timeout handling. Bear with the notation,
we'll end up with something neat at the end:
- assume that R1 and R2 pick random numbers r1 and r2
Hi Ed,
The one weakness I see in the presentation of CoDoNS is one that is
common amongst academic exercises. While it treats a technical
problem in a formally defined say, it suffers from the assume
frictional surfaces syndrome. This disease is not fatal, it is more
like the flu,
Stephane Phillip,
I'm thinking of writing a short report that summarizes the invaluable
discussion here and beefing up the system sketch. I think we now agree
that it is possible to have multiple operators manage names in a single,
shared namespace without recourse to a centralized
Hi,
Let me expand on how DNSSEC coupled with a cooperative, p2p architecture
for DNS can help enable competition among TLDs. The short summary is:
- CoDoNS+DNSSEC enable any server to securely serve any name,
which makes it possible, should the community decide to
pursue it,
Henrik == Henrik Levkowetz [EMAIL PROTECTED] writes:
Henrik Hi Sam, on 2006-10-20 19:43 Sam Hartman said the
Henrik following:
I was unable to find a text mode browser that can work with
your nomination pages to nominate candidates.
Henrik w3m should work now - I replaced
