Naming convention for a virtual network ...

Having come up with a couple of solid (and open to improvement) ideas for the addressing of the simulated internet on the internet. I do need to stop and think (quite a bit) about the domain naming convention we should use.

Just 'connecting' is not enough, we will need destinations and cul-de-sacs, places to explore and places to discover. Naming conventions often open up the world of ideas, telling those in the system what may be out there. A clue to the traps and treats in store.

Soon there will be a couple of simple activities, I don't think they will be complex, something that will be in the realms of build, connect, find. The hidden cul-de-sac will be a client with some 'servers' each containing the pieces of a very simple puzzle.

So whilst I will think on about the puzzle, the naming convention, well as it is simulated and we can do what we want (within reason), anything that relates to the world of the simulated internet on the internet and its core could be on a .packet top level domain.

This was we could have ...

  • usa.packet
  • uk.packet
  • france.packet
  • germany.packet

with examples such as

  • www.uk.packet
  • mail.uk.packet
  • dns.uk.packet
  • tftp.uk.packet

We could happily give a subdomain different levels of control, so uk.packet could be extended to ..

  • openuniversity.uk.packet
  • localcollege.uk.packet
  • localschool.uk.packet
  • myuniversity.uk.packet
And then could be extended with ...
  • www.openuniversity.uk.packet
  • mail.openuniversity.uk.packet
  • etc

And so on ...

Better ideas are always open for inclusion.

Comments

Popular posts from this blog

Simulation vs emulation vs virtualisation ....

You can't free a fish from water ...

Slow are the wheels that maketh the #Linux NAL ...