4/27/2015Slide 1 Rethinking the design of the Internet: The end to end arguments vs. the brave new world Marjory S. Blumenthal Computer Science and Telecomms.

Slides:



Advertisements
Similar presentations
Layering and the network layer CS168, Fall 2014 Sylvia Ratnasamy
Advertisements

Information-Centric Networks02b-1 Week 2 / Paper 2 Tussle in Cyberspace: Defining Tommorow’s Internet –David D. Clark, John Wroclawski, Karen R. Sollins.
Net Neutrality, What Else? Wim Nauwelaerts Partner Hunton & Williams.
1 Scalability is King. 2 Internet: Scalability Rules Scalability is : a critical factor in every decision Ease of deployment and interconnection The intelligence.
Cisco Hierarchical Network Model RD-CSY /101.
GENI: Global Environment for Networking Innovations Larry Landweber Senior Advisor NSF:CISE Joint Techs Madison, WI July 17, 2006.
1.End to end arguments in system design (1981) 2.Tussles in cyberspace: Defining Tomorrow’s Internet (2005) Nick McKeown CS244 Lecture 3 Architecture and.
Chapter 9 Designing Systems for Diverse Environments.
Tussle in cyberspace: Defining tomorrow ’ s internet (2002) D.Clark, J. Wroclawski, K. Sollins & R. Braden Presented by: Gergely Biczok (Slides in courtesy.
NewArch: A new architecture for an Internet David D. Clark, Steve Bellovin, Bob Braden, Noel Chiappa, Ted Faber, Aaron Falk Mark Handley, Scott Shenker,
EECE 411: Design of Distributed Software Applications What is a Distributed System? You know when you have one … … when the failure of a computer you’ve.
Building a Peer-to-Peer Anonymizing Network Layer Michael J. Freedman NYU Dept of Computer Science Public Design Workshop September 13,
CS 268: Active Networks Ion Stoica May 6, 2002 (* Based on David Wheterall presentation from SOSP ’99)
Privacy Chris Kelly iLaw July 5, 2002.
Chapter 1  Introduction 1 Overview  What is a secure computer system?  Concerns of a secure system o Data: Privacy, Integrity, Availability o Users:
1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University
Disrupting the Disruption: The revenge of end to end David D. Clark March 2003.
Rethink the design of the Internet CSCI 780, Fall 2005.
The Case for Network-Layer, Peer-to-Peer Anonymization Michael J. Freedman Emil Sit, Josh Cates, Robert Morris MIT Lab for Computer Science IPTPS’02March.
Tussle in cyberspace: Defining tomorrow ’ s internet D.Clark, J.Wroclawski, K.Sollins & R.Braden Presented by: Ao-Jan Su (Slides in courtesy of: Baoning.
FIT5037 Advanced Network Security --- Modern Computing and Security --- Lecture 1.
Future Research Directions Jennifer Rexford Advanced Computer Networks Tuesdays/Thursdays 1:30pm-2:50pm.
1 Network Layer: Host-to-Host Communication. 2 Network Layer: Motivation Can we built a global network such as Internet by extending LAN segments using.
The Future of Internet Research Scott Shenker (on behalf of many networking collaborators)
Principles of Information Technology
The Future of the Internet Jennifer Rexford ’91 Computer Science Department Princeton University
Terena Netwoking Conference 2009 Network core design for business continuity architectures Martí Griera - Juanan Martínez Servei d’Informàtica Universitat.
Lecture 1 Internet CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger and Daniel Zappala Lecture 1 Introduction.
Intranet, Extranet, Firewall. Intranet and Extranet.
What does it take to define an architecture? (Part 2) David D. Clark July, 2012.
Lecture 18 Page 1 CS 111 Online Design Principles for Secure Systems Economy Complete mediation Open design Separation of privileges Least privilege Least.
Univ. of TehranComputer Network1 Computer Networks Computer Networks (Graduate level) University of Tehran Dept. of EE and Computer Engineering By: Dr.
FIND experimental requirements David D. Clark. FIND Future Internet Design (FIND) is an NSF program (now folded in to NetSE) to envision the Internet.
Feb 20, 2001CSCI {4,6}900: Ubiquitous Computing1 Announcements.
Firewalls Paper By: Vandana Bhardwaj. What this paper covers? Why you need a firewall? What is firewall? How does a network firewall interact with OSI.
Networks and Hackers Copyright © Texas Education Agency, All rights reserved. 1.
Tussel in Cyberspace Based on Slides by I. Stoica.
1 An Introduction to the future of the Internet (part 1) David Clark MIT CSAIL July 2012.
IMPROUVEMENT OF COMPUTER NETWORKS SECURITY BY USING FAULT TOLERANT CLUSTERS Prof. S ERB AUREL Ph. D. Prof. PATRICIU VICTOR-VALERIU Ph. D. Military Technical.
Happy Network Administrators  Happy Packets  Happy Users WIRED Position Statement Aman Shaikh AT&T Labs – Research October 16,
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
RON: Resilient Overlay Networks David Andersen, Hari Balakrishnan, Frans Kaashoek, Robert Morris MIT Laboratory for Computer Science
Tussle in cyberspace: Defining tomorrow’s internet D.Clark, J.Wroclawski, K.Sollins, R.Braden Presenter: Baoning Wu.
Lecture 1 Internet CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger and Daniel Zappala Lecture 2 Introduction.
RON: Resilient Overlay Networks David Andersen, Hari Balakrishnan, Frans Kaashoek, Robert Morris MIT Laboratory for Computer Science
Network Architecture: Design Philosophies IS250 Spring 2010 John Chuang
QoS research in a complicated world Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
Copyright © 2002 Intel Corporation. Intel Labs Towards Balanced Computing Weaving Peer-to-Peer Technologies into the Fabric of Computing over the Net Presented.
What is the cloud ? IT as a service Cloud allows access to services without user technical knowledge or control of supporting infrastructure Best described.
Chapter 1 Introduction Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Infrastructure and Commons Brett M. Frischmann Assistant Professor of Law Loyola University Chicago School of Law.
Tussle in Cyberspace: Defining Tomorrow’s Internet Presented by: Khoa To.
Application Architecture Internet Architecture David D. Clark MIT CSAIL September 2005.
Developing a Next-Generation Internet Architecture Robert Braden, David Clark,Scott Shenker, and John Wrokclawski Presented By Ding Lizhao.
Digital Libraries1 David Rashty. Digital Libraries2 “A library is an arsenal of liberty” Anonymous.
Information-Centric Networks Section # 2.2: Internet Evolution Instructor: George Xylomenos Department: Informatics.
End-to-End Principle Brad Karp UCL Computer Science CS 6007/GC15/GA07 25 th February, 2009.
© 2012 IBM Corporation IBM Security Systems 1 © 2012 IBM Corporation Cloud Security: Who do you trust? Martin Borrett Director of the IBM Institute for.
Can we save the OPEN Internet? with focus on The Two-Port Internet Problem and what to do about it Terry Gray Designated Prophet of Doom University of.
The Fine Art of Politics in TERENA Middleware Task Forces.
A Case Study in Building Layered DHT Applications
Presented by Muhammad Abu Saqer
Software Defined Networking (SDN)
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
WHAT IS MPLS?  MPLS is a type of data-carrying protocol that manages traffic between two locations. It is mainly used in high-performing networks. 
CSE 542: Operating Systems
Architecture and Principles
Presentation transcript:

4/27/2015Slide 1 Rethinking the design of the Internet: The end to end arguments vs. the brave new world Marjory S. Blumenthal Computer Science and Telecomms Board, NRC David D. Clark M.I.T. Lab for Computer Science © Copyright 2000, David D. Clark & Marjory S. Blumenthal

4/27/2015Slide 2 Design principles of the Internet The end-to-end arguments: The lower layers of the network are not the right place to implement application-specific functions. The lower layers of the network should implement basic and general functions, and the applications should be built “above” these functions, at the edges. E.g. move functions “up and out”. This leads to the result of function migration to the end-node. The network should be “as transparent as technology permits”.

4/27/2015Slide 3 A simple view of the Internet User Router “The Internet”

4/27/2015Slide 4 Benefits of the end to end arguments User empowerment. Run what you please. Flexibility in the face of unknown applications. A network to hook computers together. Lower cost in core of network. Eliminate special “features”. Rely on edge-node equipment. More robust applications. No unexpected failures of third-party nodes. An example of “getting it wrong”: make the network reliable. Interferes with real-time telephony.

4/27/2015Slide 5 But in today’s Internet... There are “new” factors to consider: Assured operation in an untrustworthy world. More demanding applications. –Growing need for enhanced services. Less sophisticated users. –User empowerment is a user burden. –Does today’s software really empower the user? Third parties who want to intervene. New sorts of end-node devices. –Appliances, not PCs. The evolving role of the Internet Service Provider.

4/27/2015Slide 6 In the brave new world The end to end model does not empower the ISP. ISPs want to sell services, add value, and make money. –New network services (or not), protection, control of applications/content, accounting. The end to end model does not empower rights holders. The end to end model does not empower governments. Control of content, taxation, consumer protection, law enforcement. The end to end model does not empower employers. The end to end model only empowers certain application makers.

4/27/2015Slide 7 The end to end argument functions at two levels At the “network” level: Avoid putting constraining per-application functions into the core of the network. Build general purpose services. At the “application” level: Build applications in a way that makes them robust, easy to use, reliable, etc. –Simple approach: push software to the edge. –Perhaps more realistic: reason carefully about role of servers, trusted third parties, etc. Increasing concern about the goal of making money?

4/27/2015Slide 8 The end to end argument at the network level At the network level: (examples of what is happening…) More complex role for commercial ISPs –vertical integration of transport/QoS with apps. –control of what apps users can use. –filtering of unacceptable behavior. Others (e.g., employers, universities) restrict activities. –Firewalls, filters Governments propose controls in the net. –Carnivore The Internet is hard to find and control. What is the Internet?

4/27/2015Slide 9 The end to end argument at the application level At the application level: (examples of what is happening) Ease of use, mutual distrust, multi-party interactions may motivate servers and services other than at the end- points of the users. –Relays for content, trusted third parties. –How do we make these applications robust? –How do the parties know who they are talking to? Appliance and devices motivate new designs. Both ISPs and ASPs (A = Application) want to “get into the action”. ISP involvement will imply constraints on location/structure.

4/27/2015Slide 10 A simple view of the Internet User Router “The Internet”

4/27/2015Slide 11 A more complex view of the Internet Backbone (big ISP) Backbone (big ISP) Backbone (big ISP) Little ISP User Little ISP Corp Campus Little ISP User By the end to end argument, applications live at the edge. The ISP lives here. And below. The ISP does not live at the end-points. (They can try…)

4/27/2015Slide 12 Some ideas for moving forward Labels. A compromise between autonomy and visibility of action. Distinction between private and public communication. Accept that private communication is not restricted. Focus on communication “to the public”. New principles for application design. Do not force an end-node implementation. Allow the user to select an alternative. A more sophisticated form of empowerment. Tolerance for experimentation. That which is not forbidden is permitted?

4/27/2015Slide 13 Some “contradictions” in the end to end approach How can we build a trustworthy network out of edge-devices that cannot be trusted? How can we have anonymity and accountability? How can the net control unacceptable behavior and still permit unknown applications? Flexibility is critical if the Internet is to be a part of the computer world. Must find a balance among the goals.

4/27/2015Slide 14 What has really changed? A loss of trust among users. Global communication with local trust. The need to factor in economic forces. Role of commercial (and other) ISPs. The change in the nature of the user base. Less sophisticated: ease of use, protection concerns Co-evolution of technology and law. Complex cycle of evolution. Geographic differences. Change in nature of innovation. Big players. Possibility of slow ossification.