[IDONS] MechanismSoftwareClient :: pdf :: context view

inbound links:
Client side

Client side

Pseudo code if(user!=me) { goto ignore_it; }

Depends on requirements from name resolution policy.

The hard part: there is no user interface at this time, which allows the user to select, which resolution to use, in case a DNS lookup would return multiple, different sets of A records from different authorities.

Ideas (to be moved to [[Solutions]] (or requirements?):

Subscription Reputation Support

Trust preferences in names:

  1. Tier 1 would consist of servers in data-centers around the world, connected to each other using p2p to transfer changed records.
  2. Tier 2 would consist of registrar servers that communicate with tier 1 to update records or set domains to ip addresses.
  3. Tier 3 would be client side and connect to Tier 1 servers to resolve domains, which would not require hacking of already existing systems.

The whole client side could be understood as a "vhost" feature under the users control.

Last modification: Sun, 19 Dec 2010 17:09:24 +0100

Author(s): jfw,

Document number A5afeb39445695358a1d5cf9425159a3a (version 434) delivered to public at Wed, 23 Sep 2020 11:24:44 +0200

short comments

add comment