DOC PREVIEW
Berkeley COMPSCI 268 - Future Internet Architectures

This preview shows page 1-2-3-4-5 out of 15 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 15 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CS 268: Future Internet ArchitecturesKey QuestionHow to Answer this QuestionTusslesDesign PrinciplesModularize along Tussle BoundariesDesign for ChoiceDesign ImplicationsEconomicsExamplesTrustOpennessImportant Side DiscussionsInternet as Public UtilitySlide 15CS 268: Future Internet ArchitecturesIon StoicaApril 28, [email protected] 2Key QuestionHow can we as researchers/engineers influence the evolution of the Internet [email protected] 3How to Answer this QuestionUnderstand the new realities and try to predict where the Internet is heading to The two papers-The days when all players had a common goal are gone, and that the new environment where different players have often conflicting goals is here to stay-Internet should provide only one basic service: connectivity for which there is no business model, hence treat the Internet as a publicly supported & controlled [email protected] 4TusslesThe process by which players with different interests act to achieve those interestsAccept the reality that the players have often conflict interests and try to leverage or at least accommodate [email protected] 5Design PrinciplesDesign for variation in outcome not for a particular outcome-Modularize the design along tussle boundaries-Design for [email protected] 6Modularize along Tussle BoundariesFunctions that are within a tussle space should be logically separated from functions outside of that spaceExamples-DNS, [email protected] 7Design for ChoiceDesign protocols such that to allow parties to express preferences about the parties they interact withExamples-Mail [email protected] 8Design ImplicationsDesign open interfaces – allow different parties to compete providing the same interfaceDesirable properties of open interfaces-Visible exchange of value  allow parties with compatible interests (e.g., provider/customer) to achieve equilibrium-Exposure of cost of choice  allow parties to make “intelligent” choices -Visible (or not) of choices made  realize that choices made public can be different from choices made in secret-Tools to isolate and resolve faults/[email protected] 9Economics Goal: create premises for investmentDrivers of investment: greedy and fear-Greedy: invest in the hope to maximize revenues-Fear driven by the competition, which in turn is driven by the ability of customers to have [email protected] 10ExamplesLock-in from IP addressing-Solution: made it easy for a host to change addresses and use multiple addressesValue pricing-Solution: aid consumers to bypass the controls of the producers Residential broadband access-Solution: design residential access facility that supports competition. Who is going to deploy this facility?Competitive wide area access-Solution: allow consumers to control the path of their packets at the level of providers. Need payment [email protected] 11TrustUsers should be able to choose with whom to interact, and the level of transparency they offer to other usersQuestion: who is controlling the policy? Users or network administrators? We cannot fully address this question but we should -Provide maximum flexibility to users in setting policies-Allow users to select third party entities to mediate the interaction (e.g., PKI)Recognize that technical solutions are note enough!-E.g., how to avoid [email protected] 12OpennessWe need to strive for open interfaces  lead to competition, innovationIn Internet this means simple service, i.e., transparent packet carriage  allow to deploy new protocols without having to modify the [email protected] 13Important Side DiscussionsMechanisms vs. policiesThe role of identityThe future of end-to-end [email protected] 14Internet as Public UtilityAssumption: Internet should provide basic connectivity  no business model for thisConclusions/Solutions: -Evolve internet into a publicly supported & controlled utility (e.g., postal system, power grid distribution, public roads)-Grant monopoly subject to regulatory contracts•Universal service  reach everyone•Common carriage  common interface•No bundled [email protected]


View Full Document

Berkeley COMPSCI 268 - Future Internet Architectures

Documents in this Course
Lecture 8

Lecture 8

33 pages

L-17 P2P

L-17 P2P

50 pages

Multicast

Multicast

54 pages

Load more
Download Future Internet Architectures
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Future Internet Architectures and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Future Internet Architectures 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?