Reconnections Workshop: Some topics to pursue

1. Reconnections Workshop:Some topics to pursue (Or “a few sticky ideas from day one”) 10/26/2005

2. (Silent) failure is not an option

3. Application diagnostics are important. The ability to correlate diagnostics from multiple applications can be invaluable.

4. If you have strong (any?) detection and response capabilities, maybe you don’t need as much prevention.

5. Real notes from a real meeting at UPenn, earlier this month. • First the group shared thoughts on the underlying problems causing security problems at Penn. Each NPTF member voted to indicate the relative importance of the problems:

6. How Open? (1 of 2)Why don’t people seem to want “Open/Highly Available networks?”Why do they want “unlisted numbers?” - They’ve learned to be afraid -

7. How Open? (2 of 2)TEG: Selective isolationismCN: Zones of connectivityRH: Universal communications vs communities of interest. We win when we can combine them.DC: Want e2e transparency when communicating with trusted parties

8. The role of identity and trust in network design

9. Concentrate on the apps and the OS, not (only) the network(or “e2e and transparency is still goodness”)

10. Ease of network reconfiguration is important(Application and policy requirements may change often)

11. Manage full networks (or full systems), rather than network elements.

12. What happens when the entire Internet becomes “firewall friendly” (by running on port 80)?

13. We probably have failed to understand social and financial pressures(It’s the economy, stupid?)

14. Your items here.