RFC 3426:General Architectural and Policy Consider...
RFC-Ref

General Architectural and Policy Considerations


1. Introduction
2. Relationship to "Architectural Principles of the Internet"
3. Questions
4. Justifying the Solution
4.1. Case study: Integrated and Differentiated Services
5. Interactions between Layers
5.1. Discussion: The End-to-End Argument
5.2. Case study: Endpoint Congestion Management
5.3. Case study: Layering Applications on Top of HTTP
6. Long-term vs. Short-term Solutions
6.1. Case study: Traversing NATs
7. Looking at the whole picture vs. making a building block
7.1. Case Study: The Session Initiation Protocol (SIP)
8. Weighing architectural benefits against architectural costs
8.1. Case Study: Performance-enhancing proxies (PEPs)
8.2. Case Study: Open Pluggable Edge Services (OPES)
9. General Robustness Questions
9.1. Discussion: Designing for Robustness
9.2. Case Study: Explicit Congestion Notification (ECN)
10. Avoiding Tragedy of the Commons
10.1. Case Study: End-to-end Congestion Control
11. Balancing Competing Interests
11.1. Discussion: balancing competing interests
12. Designing for Choice vs. Avoiding Unnecessary Complexity:
12.1. Discussion: the importance of choice
13. Preserving evolvability?
13.1. Discussion: evolvability
13.2. Discussion: overloading
13.3. Discussion: complexity, robustness, and fragility
14. Internationalization
14.1. Discussion: internationalization
15. Deployability
15.1. Discussion: deployability
16. Conclusions
17. Acknowledgements
18. Informative References
19. Security Considerations
20. IANA Considerations
21. Authors' Addresses
22. Full Copyright Statement
23. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org