Distributed OS: Winter 2011: Difference between revisions
| Line 24: | Line 24: | ||
*recognize that "bad" behavior is always possible. "good" behavior is enforced through incentives and sanctions. | *recognize that "bad" behavior is always possible. "good" behavior is enforced through incentives and sanctions. | ||
*rules will change. Even rules for rule changes will change. Need a "living document" governing how rules are chosen and enforced. | *rules will change. Even rules for rule changes will change. Need a "living document" governing how rules are chosen and enforced. | ||
==Scenarios== | |||
===Stopping DDoS=== | |||
===Stopping phishing=== | |||
===Limiting the spread of malware=== | |||
===Bandwidth hogs=== | |||
Revision as of 19:13, 18 January 2011
Readings
January 13, 2011: CCR (two papers)
January 18, 2011: OceanStore and Pond
Internet Governance
Problems to Solve
- Attack computers with almost no consequences
- DDoS
- botnets
- capture and analyze private traffic
- distribute malware
- tampering with traffic
- Unauthorized access to data and resources
- Impersonate computers, individuals, applications
- Fraud, theft
- regulate behavior
Design Principles
- subjects of governance: programs and computers
- bind programs and computers to humans & human organizations, but recognize binding is imperfect
- recognize that "bad" behavior is always possible. "good" behavior is enforced through incentives and sanctions.
- rules will change. Even rules for rule changes will change. Need a "living document" governing how rules are chosen and enforced.