[governance] Stephanie's - User input to Internet architecture work

yehudakatz at mailinator.com yehudakatz at mailinator.com
Mon Mar 10 10:37:05 EDT 2008


Stephanie's - User input to Internet architecture work
[ http://lists.cpsr.org/lists/arc/governance/2008-03/msg00160.html ]

>...  So, next step is, 
-snip-
Such a document could list user requirements such as:

* no provider lock-in. If there is a market of providers, then user's
choice is a necessity to avoid oligopolies. Technical solutions that
limit the ability of the user to switch providers are
bad. Counter-example, an architecture where all IP addresses would be
PA (Provider-Aggregeatable) would create a serious lock-in (although
not an 100 % lock-in since renumbering your machines is still
possible, while painful).

* freedom to create and deploy new applications, even applications
which were not planned at the beginning. Counter-example: I've
recently seen a proposal for a "future Internet" based on
applications, with an architecture centered around a small set if
usages (and, since "the code is the law", such an architecture would
probably prevent innovation).

* freedom to be called as well as calling. There are other uses of the
Internet than browsing the Web. Some of these uses require the ability
of the ordinary user to be the responder of a communication, not only
the initiator. This should be possible on personal machines, without
renting a dedicated box. Counter-example: NAT seriously threatens
that. There is a high risk that, a few years from now, the typical
individual user connection, and may be the SOHO as well, will be with
private addresses only.

- adding -

* (4) to safeguard the open marketplace of ideas on the Internet by 
adopting and enforcing baseline protections to guard against 
unreasonable discriminatory favoritism for, or degradation of, 
content by network operators based upon its source, ownership, or 
destination on the Internet.
[ibid #4:  “Internet Freedom Preservation Act 2008” (HR 5353) 
Reps. Ed Markey and Chip Pickering]

* Applying SEC Trade rules & penalties to DNS Exchanges and
Trading Systems. 
(Domain-Trading; normative and alternate methoods,
i.e.: Insider Trading Rules, etc...)

* Universal Pricing for Domain Purchases, Renewals, and Trades.
(A constant-value unit (k) / fixed exchange-price-point)

For example:
A European Register charges in Euros, US registers charges Dollars
for dns services. the 'rate' of the cost for the Domain would be constant,
regardless of the present value of the Euro or the Dollar.

As it now Domain cost are subject to currency valuations.
i.e.: the Euro is now stronger than the Dollar, so Europeans buy domains 
and services from US companies at a bargain/discount. 
Wherein Americans pay normative cost for domestic dns services and a 
premium for European dns services. User's choices are now encumbered by 
their base currency, limiting their selection to local and exchange rates,
respective to the cost.

--
____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, send any message to:
     governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
     http://lists.cpsr.org/lists/info/governance



More information about the Governance mailing list