2009
DOI: 10.1007/978-3-642-03700-9_11
|View full text |Cite
|
Sign up to set email alerts
|

On Designing for Tussle: Future Internet in Retrospect

Abstract: Abstract. Over the past decades, the fundamental principles of the Internet architecture have not significantly changed. However, Internet evolution and its effects on participants' interests have triggered the need for re-defining these design principles. "Design for Tussle" is an aspiration for future network designs, which enables the involved stakeholders to express their possibly conflicting socio-economic preferences on service instances. We performed a series of case studies examining whether establishe… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2009
2009
2012
2012

Publication Types

Select...
3
1
1

Relationship

3
2

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…Using proven design principles and architectural guidelines of the Internet [13,14], like the classic end-to-end principle [15] and refinements such as "design for tussle" [16,17], helps in designing protocols that are feasible for each relevant stakeholder. Although following such principles does not ensure the success of a certain protocol, they are important for the long-term evolution of the Internet [18]. For communication to take place, protocols have to be agreed upon.…”
Section: Protocol Development Processmentioning
confidence: 99%
“…Using proven design principles and architectural guidelines of the Internet [13,14], like the classic end-to-end principle [15] and refinements such as "design for tussle" [16,17], helps in designing protocols that are feasible for each relevant stakeholder. Although following such principles does not ensure the success of a certain protocol, they are important for the long-term evolution of the Internet [18]. For communication to take place, protocols have to be agreed upon.…”
Section: Protocol Development Processmentioning
confidence: 99%
“…It is obvious that the need for designing a tussle-aware FI has emerged to enhance deployment, stability and interoperability of new solutions. Although there are plenty of counter-examples of adopted protocols/architectures that do not follow the Design for Tussle principle, tussle-aware protocols and architectures are expected to have better chances for adoption/success in the long-term [3].…”
Section: Introductionmentioning
confidence: 99%
“…Even if a good technical design is not the most important success factor, tussle-aware protocol designs have better chances at deployment in the long-term [24].…”
Section: Good Technical Designmentioning
confidence: 99%