close
Warning:
Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
Nov 4, 2010, 11:55:42 PM (14 years ago)
- Author:
-
wlehr
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v2
|
v3
|
|
10 | 10 | |
11 | 11 | The goal of the economic/policy research is to help ensure that the architecture to the greatest extent possible implements the design principles of '''Commercializability''' and '''Regulability''' |
| 12 | These two design principles focus on how the M1st architecture relates to the larger socio-economic context or ecosystem. |
| 13 | |
| 14 | '''Commercializability''': economic viability considerations. |
| 15 | * is the architecture economically viable in a reasonable market/industry context? |
| 16 | * is it efficient (cost minimizing, welfare maximizing)? |
| 17 | * is its implementation and operation incentive compatible? what are incentives of ISPs to adopt/deploy architecture? |
| 18 | * what are implications of architecture for industry/value chain dynamics? |
| 19 | * what is a plausible deployment scenario? |
| 20 | |
| 21 | '''Regulability''': social governance considerations |
| 22 | * is architecture consistent with core social/policy goals? |
| 23 | * is it pro-competitive, privacy-preserving, fair? |
| 24 | * is it amenable to regulation? enforcement? |
| 25 | * how would adoption of the architecture impact policy debates like ''Network Neutrality''? technical neutrality in regulatory policy? |
| 26 | * what are implications for RF spectrum management? |
| 27 | * what policy reforms (regulations, institutional/market design) might re-enforce the architectures performance or viability along important design dimensions (e.g., trust, observability, etc.)? |
12 | 28 | |
13 | 29 | |