<<

Introduction to Science CSCI 109

China – Tianhe-2

Andrew Goodney Fall 2019

Lecture 9: Networks Nov. 9th, 2019 Schedule

1 Computer Networks

u Computer networks everywhere!

v Headed towards IoT (*everything* electronic on a network) u How did we get here?

2 1960’s

u 1960’s

v ”Mainframe” = $$MM v Universities and Government facilities install at designated places (UIUC, UCSD, etc.)

v Allow remote access to researchers across the country to better utilize v Mainframes – 100% busy

3 1960’s Remote Access

u Dumb Terminals and analog

Phone call

4 1960’s Problems

u Any issues with this model?

v Analog connections slow (300BPS) v Only so many phone lines

v Long distance calls were expensive

5 Digital Circuits

u Mid to late 1960’s digital circuits improve things u Also, computer-to-computer communication 64kbps digital circuit

(smaller) mainframe (smaller) mainframe

mainframe

(smaller) mainframe

6 Late 1960’s

u Terminals in office -> local main u Local mainframe -> digital circuit -> big main frame u Key observations: v Multiple users

v Computer-to-computer

7

7 Late 1960’s

u Still not ideal… u Connections are “circuit switched” (dedicated) between source and destination u What happens when no one is using the circuit? u Really only one dumb-terminal can use connection at a time u Do humans time share well? u Digital circuits still expensive u Also, computer-to-computer identified as key application

8 Design Goals

u Need a way to:

v Connect users at terminals to remote computers v Connect many users at the same time (fairly)

v Allow computer-to-computer communications

v Maximize the utilization of expensive digital links

9 Solution: the packet

u What is a packet? u Chunks of user data u And VERY IMPORTANTLY u Meta-data () about where the packet is from, and where it needs to go

10 How do packets solve the problem?

u Now we can build “packet-switched” networks = packet switch

64kbps digital circuit

11

u What do we have now? u Terminals connect to local computers u Data is broken up into packets sent to switch u Can go to other local computers u Or, switch can ”forward” packet to remote switch u Remote switch sends packet to big, expensive main frame u Main advantage: links are shared amongst all users, or computer-to-computer communication u Nothing is dedicated to one connection

12 Packet Switching Advantage

u Sharing and utilization is main advantage of packet switching example:

§ 1 Mb/s link ….. N § each user: users • 100 kb/s when “active” 1 Mbps link • active 10% of time u circuit-switching: v 10 users u packet switching: v with 35 users, probability > 10 active at same time is less than .0004 v with 50 users, P = 0.01 13 A bit more history…

u How did we make the jump to packet switching? u Idea came about late 1960’s u ARPA (Advanced Research Projects Agency) v US-DOD wanted packet switched computer-to-computer networks

v Seen as crucial to Cold War effort

u This is , packet switching is a lot like lines at amusement park/grocery store

14 Len Kleinrock/UCLA

u Len Kleinrock writes PhD thesis on queuing theory/packet switching v All theoretical, didn’t exist yet u ARAP contacts and says “Hey you seem like just the right guy, here’s a ton of money, invent the ARPANet…” u Gets faculty position at UCLA (~1963), embarks on project u With BBN, builds Interface Message Processor (IMP) (packet switch) u 50 years ago (Oct. 29th), sends first message from UCLA to Stanford

15 Interface Message Processor

Internet Museum: https://la.curbed.com/2011/10/31/10429196/internet-invented-ucla-first-message-museum

Recreated lab as it was 50 years ago. You can go visit: 3420 Boelter Hall

16 Network Terminology

u Everything on the network is either: v u sends or receives data v Packet switch u receives packets on interfaces and forwards to other switches or hosts v Communication link u Physical connection between two devices that carries data u v Packet switches “store and forward” u Receive a packet u Store it (store) u Figure out where to send it (forward)

17 Modern Networks

u How do we build modern networks? mobile network u The Internet is a network of networks! global ISP u Internet edge: v Access networks connects hosts to the regional ISP network

v Access networks connect to networks in the core u Internet Core: v Networks of networks (ISPs) connecting together institutional network 18 More Terminology

u Access networks are Local Area Networks (LANs)

v Host (desktops, laptops, servers) v Switches

v Routers u Routers are special packet switches that bridge (connect) multiple LANs, or from LAN to WAN u WAN = v Connects from LAN to network core

19 More Terminology

u Network Core

v LANs and WAN connections from access networks to ISPs v And between ISPs

20 How do we build modern networks

u First look at access networks

v How do we connect hosts (pc, laptop, server, phones) to the network

21 LANs

u In 2018 (almost?) all LANs are built with Ethernet technologies u Homes, businesses, university campus u Built with

v (“Ethernet cable”) v Wifi

v v Power lines u Wide range of speeds v 10M, 100M, 1G, 10G, 40G, 100G

22 Home Network

devices

to/from headend or central office

Cable, DSL , or fiber wireless access , firewall, NAT point (100->1000 Mbps) wired Ethernet (100 Mbps or 1G) 23 Institutional Network

institutional link to ISP (Internet) institutional router

Ethernet institutional mail, switch web servers

u typically used in companies, universities, etc v 10 Mbps, 100Mbps, 1Gbps, 10Gbps, 40G, 100G transmission rates v today, end systems typically connect into Ethernet switch

24

u Wireless access to phones, etc u Provided by cellular operators u 2G (dead?), , , now 5G u Speeds vary

v 100’s kilobits/s (2G) v 5G 300Mbps+ to Internet

25 WAN Links

u How to connect access networks to the core?

26 DSL

central office network

DSL splitter modem DSLAM

ISP voice, data transmitted at different frequencies over DSL access dedicated line to central office multiplexer u (DSL)

v Uses existing phone lines v 10 - 100Mbps

v Homes and small businesses

27

cable headend …

cable splitter cable modem modem CMTS termination system data, TV transmitted at different frequencies over shared cable ISP distribution network v HFC: hybrid fiber coax § asymmetric: up to 1Gbps downstream transmission rate, <20 Mbps upstream transmission rate v network of cable, fiber attaches homes to ISP router § homes share access network to cable headend § unlike DSL, which has dedicated access to central office v Homes and small business 28 Fiber Optical WAN Links

u Institutional networks, ISP to ISP u Laser light on optical fiber u Speeds 100M to 100G u Some homes!

v ATT Fiber, Google Home, other lucky people!

29 Physical Links

u Communication links can be made up of different physical media, with different properties

30 Twisted Pair

u Twisted Pair: two copper wires twisted around each other u Examples: old phone lines, CAT5(6,7) Ethernet cables u : 100M to 2.5G per pair u Usually multiple pairs per cable

31

u Coaxial cable: center conductor surrounded by insulation then tubular shield u Carries frequency u “CableTV” (cable modem) wires in your house, DS3 other similar telco services u 100M to 10G per cable

32 Fiber Optic Cable u Extremely thin glass cables called strands u Laser light used to transmit data u Can carry multiple wavelengths at once (i.e. multiple ”colors”) u Essentially unlimited bandwidth per strand u Typically 1G to 100G per wavelength u 96 wavelengths per strand u Short distance: Ethernet on campus u Long distance, undersea u Propagates at 60% speed of light

33 Wireless

u Also known as radio waves u Connects through free space (no wires) u Wi-fi, cellular, satellite, specialized services u Bandwidth depends on frequency, channel width, , etc. (kilobits to gigabits)

v 900MHz, 2.4GHz, 5GHz, 60GHz u Propagation affected by walls, buildings, trees, ground, water, other transmission sources u Some free-space laser links exist, not very common

34 Internet structure

u Keep saying “network of networks” u What do we mean? u Basic goal of Internet “end to end” communication v Any host can talk to any host u End systems connect to Internet via access ISPs (Internet Service Providers) v Residential, business and university ISPs u Access ISPs in turn must be interconnected. v So that any two hosts can send packets to each other u Resulting network of networks is very complex v Evolution was driven by economics and national policies u Let’s take a stepwise approach to describe current Internet structure

35 Internet Structure u To enable end-to-end communication, all access nets (millions) must interconnect… how? access access … net net … access net access access net net access access net net …

access access net net

access net access net

access

net

access … … net access access net access net net 36 Internet Structure u Naïve solution: direct connect every ISP together!

access access … net net … access net access access net net … … access access net net connecting each access ISP …

… …

… to each other directly doesn’t access access net scale: O(N2) connections. net

access net access net

access

net

… access … … net access access net access net net 37 Internet Structure u Solution: One global ISP connects access nets hierarchically u Not possible, never happened… access access … net net … access net access access net net access access net net …

… global

access access net ISP net

access net access net

access

net

access … … net access access net access net net 38 Internet Structure

Internet exchange point access access … net net … access net access access net net IXP access access net net ISP A …

… access IXP access net ISP B net

access ISP C net access net

access peering link

net

access … … net access access net access net net 39 Internet Structure

u Regional ISPs arose to connect access nets (schools, businesses, homes) to the Internet u Regional ISPs connected together at IXPs (Internet Exchange Points) for mutual economic benefit u Specialized regional networks connect some access networks together v Educational: Los Nettos (socal .edu)

v Metro area networks: City chartered networks to lower connection costs for businesses

40 Network of Networks

access access … net net … access net access access net net IXP access access net net ISP A …

… access IXP access net ISP B net

access ISP C net access net

access

net regional net

access … … net access access net access net net

41 Hierarchical View

Tier 1 ISP Tier 1 ISP Google

IXP IXP IXP

Regional ISP Regional ISP

access access access access access access access access ISP ISP ISP ISP ISP ISP ISP ISP u at center: small # of well-connected large networks

v “tier-1” commercial ISPs (e.g., Level 3, Sprint, AT&T, NTT), national & international coverage

v content provider network (e.g, Google): private network that connects it data centers to Internet, often bypassing tier-1, regional ISPs 42 Communicating on the Internet

u Material so far is how we build packet switched networks u From another perspective: how does data get to the other side?

43 Protocols

u All communication on networks is moderated by one or more protocols u Human protocols: v ”What time is it?” “Excuse me, where is…”

v Introductions, small talk, etc. u Network Protocols

v Machine to machine u Network protocols: define the format and order of messages sent and received between network devices, and the actions to be taken upon message transmission or receipt

44 Protocols a human protocol and a protocol:

Hi TCP connection request Hi TCP connection response Got the time? Get http://www.awl.com/kurose-ross 2:00 time

45 Getting Data Across the Internet

u From the programmers perspective, the network is a black- box u A set of components that provide an API to get data from app to server and back

GET http://www.usc.edu/

46 How to provide that service?

u To get from device to server and back

v Data must be packetized

v Traverse access network à ISP à ISP à ISP à access network à server (and back)

v Travel across heterogeneous network types, physical layers u Does (should?) the programmer worry about any of this? u No! It just works. u What is the solution? u A series of abstractions!

47 Flying Analogy

u First an analogy

ticket (purchase) ticket (complain)

baggage (check) baggage (claim)

gates (load) gates (unload)

runway takeoff runway landing

airplane airplane routing airplane routing

48 Flying Analogy

u Goal: get from one city to the other

ticket (purchase) ticket (complain) ticket baggage (check) baggage (claim baggage

gates (load) gates (unload) gate runway (takeoff) runway (land) takeoff/landing airplane routing airplane routing airplane routing airplane routing airplane routing

departure intermediate air-traffic arrival airport control centers airport layers: each layer implements a service v via its own internal-layer actions v relying on services provided by layer below 49 Why Layers

u Explicit structure eases system design in highly complex system v Adds structure to the design process u Modularity

v Each layer provides a service to the layer above, essentially abstracting the connection details away v Layers can be updated and improved as long as services offered don’t change

v Each layer ABSTRACTS the connection between devices at that layer u Ease for application programmers v Minimum amount to learn

v Use the API provided by upper layers, let the rest sort it out 50 Data flow through layers

abstract connection Packet flow

51 Packet Headers u Each layer adds a header as a packet flows down u Header contains the information necessary for that layer to do its job u Header is removed as data flows up

52 Closer look at the layers

Typically software layers

Typically hardware layers

53 TCP/IP

u TCP/IP Most famous protocol suite u TCP v Layer 4 protocol v Guarantees in-order delivery of packets u Either they get to the other side in order u Or both hosts know a packet was lost v Offers ”data stream” abstraction to layers above u IP () v Layer 3 protocol v All “Internet” traffic is IP traffic v Handles addressing (IP addresses) and routing of packets across the Internet v No guarantees, packets routed best effort v Offers host-to-host packet service to layers above 54 Network Performance

u Performance Metrics for Networks u Bandwidth - ”how fast is my network” v How much data (bits) can I get to the other side per second v Applies to communication links, as well as across the network u – “How slow is my network” v How long does it take for data to get from one side to the other v Measured in time: s, ms, us u Loss – “How bad is my network” v Fraction of packets that get dropped (don’t make it to the other side) v Needs to be <<1% for good network operation u Throughput – “How good is my network” v Considering how bandwidth, latency, loss combine with a protocol to measure how much data is actually delivered per unit time v This is what applications see 55 Original Internet Design Goals

u “the Internet” came out of (D)ARPA projects in the 1960’s, 70’s and 80 u Primary driver was to enable computer-to-computer communications, even under nuclear attack

56 Original Internet Design Goals

u Paper in 1988: “The Design Philosophy of the DARPA Internet Protocols” (David Clark, 1988). u In PRIORITY order

u 1. Continue despite loss of network infrastructure (degrade, but still function under attack)

u 2. Support multiple types of communication services (many different applications)

u 3. Accommodate a variety of networks (e.g. early networks were not all Ethernet, today’s networks use Ethernet at layer 2, layer 1 is very different)

u 4. Permit distributed management of Internet resources (no one entity is required for network to function)

u 5. Cost effective

u 6. Host attachment should be easy (only local changes required to add host)

u 7. Resource accountability (security) 57 What about now?

u Many of these goals made the Internet as we know it possible. u Especially the middle 4:

u Support multiple types of communication services (many different applications)

u Accommodate a variety of networks (e.g. early networks were not all Ethernet, today’s networks use Ethernet at layer 2, layer 1 is very different)

u Permit distributed management of Internet resources (no one entity is required for network to function)

u Cost effective

58 What about now?

u However, some make things interesting u 4. Permit distributed management of Internet resources

u Originally indented to make the network resilient in a military scenario

u Now: basically no one is in charge v 7. Resource accountability

u If you read the paper, they basically never got to this

u This is why is such a disaster, it wasn’t designed in originally

u Network agents implicitly trusted, this still causes problems, see re: BGP attacks

59 Back to Internet History

60 Growth of the Internet

61 Switch to TCP/IP (layer 4 protocol)

u ARPANet switches to TCP/IP – still in use!

62 USC/ISI u Information Sciences Institute v Part of USC under Viterbi v Researchers, grad students, undergrads v In beautiful MDR u Became prominent in developing early Internet protocols v IP u “The internet protocol provides for transmitting blocks of data called from sources to destinations, where sources and destinations are hosts identified by fixed length addresses.” v ICMP v v Simple Mail Transport Protocol u ICANN nee IANA v Internet Assigned Numbers Authority -> ICANN

v (USC basically ran the Internet) 63 Takeaways

u Networks allow computers to communicate (exchange data) u Data is broken into packets (small chunks) and sent over shared circuits (packet switching) by switches and routers u Internet is a network-of-networks – No one owner/regulator u The Internet provides an API for a service (networking) that lets app developers write software (abstraction) u Services are implemented with protocols that are stacked in layers (more abstraction) u TCP/IP is the core protocol on which most is based u Security was not an important design feature when the Internet was invented – we’re still paying for this now u Bandwidth, latency, loss, are the important network performance metrics u USC/ISI has been involved in inventing the modern Internet since (not quite) the beginning (e.g DNS, IANA, ICANN) 64