lecture 1 - introduction - networks and...

21
Lecture 1 - Introduction Networks and Security Jacob Aae Mikkelsen IMADA September 2, 2013 September 2, 2013 1 / 82 Outline Goals today Get ”feel” and terminology More depth and details later in the course Approach: Use Internet as example September 2, 2013 2 / 82 Outline 1 What is the Internet? 2 What is a protocol? 3 Network edge 4 Network core 5 performance: loss, delay, throughput 6 Protocol layers, service models 7 security 8 history September 2, 2013 3 / 82 What is the Internet? Nuts-and-bolts description What is the Internet? September 2, 2013 4 / 82 Notes Notes Notes Notes

Upload: ngomien

Post on 19-Jun-2018

214 views

Category:

Documents


0 download

TRANSCRIPT

Lecture 1 - IntroductionNetworks and Security

Jacob Aae Mikkelsen

IMADA

September 2, 2013

September 2, 2013 1 / 82

Outline

Goals today

Get ”feel” and terminology

More depth and details later in the course

Approach: Use Internet as example

September 2, 2013 2 / 82

Outline

1 What is the Internet?

2 What is a protocol?

3 Network edge

4 Network core

5 performance: loss, delay, throughput

6 Protocol layers, service models

7 security

8 history

September 2, 2013 3 / 82

What is the Internet?

Nuts-and-bolts description

What is the Internet? September 2, 2013 4 / 82

Notes

Notes

Notes

Notes

What is the Internet?

millions of connected computing devices:I hosts = end systemsI running network apps

What is the Internet? September 2, 2013 5 / 82

What is the Internet?

communication linksI fiber, copper, radio, satelliteI transmission rate: bandwidth

What is the Internet? September 2, 2013 6 / 82

What is the Internet?

Packet switches: forward packets (chunks of data)I routers and switches

What is the Internet? September 2, 2013 7 / 82

What is the Internet?

What is the Internet? September 2, 2013 8 / 82

Notes

Notes

Notes

Notes

What is the Internet?

Internet: “network of networks”I Interconnected ISPs

protocols control sending, receiving of msgsI e.g., TCP, IP, HTTP, Skype, 802.11

Internet standards

RFC Request for commentsIETF Internet Engineering Task Force

Infrastructure that provides services to applications:I Web, VoIP, email, games, e-commerce, social nets, . . .

provides programming interface to appsI hooks that allow sending and receiving app programs to “connect” to

Internet provides service options, analogous to postal service

What is the Internet? September 2, 2013 9 / 82

What’s a protocol?

A protocol define format, order of messages sent and received amongnetwork entities, and actions taken on message transmission and/or receipt

What is a protocol? September 2, 2013 10 / 82

What’s a protocol?

What is a protocol? September 2, 2013 11 / 82

The network edge

Network edge September 2, 2013 12 / 82

Notes

Notes

Notes

Notes

The network edge

The edge of the network contains the components we are most familiarwith

Computers

Smartphones

Other devices used on a day to day basis

Typically called hosts, but also divided into

Clients

Servers (often in data centers)

Network edge September 2, 2013 13 / 82

The network edge

How do we connect end systems to edge routers

Residential access nets

Institutional access networks (school, company)

Mobile access networks

Keep in mind

Bandwidth (bits per second) of access network?

Shared or dedicated?

Network edge September 2, 2013 14 / 82

Access net: DSLDigital Subscriber Line

Network edge September 2, 2013 15 / 82

Access net: DSL

Use existing telephone line to central office DSLAMI Data over DSL phone line goes to InternetI Voice over DSL phone line goes to telephone net

<2.5 Mbps upstream transmission rate (typically <1 Mbps)

<24 Mbps downstream transmission rate (typically <10 Mbps)

Network edge September 2, 2013 16 / 82

Notes

Notes

Notes

Notes

Access net: Cable network

Network edge September 2, 2013 17 / 82

Access net: Cable network

Network edge September 2, 2013 18 / 82

Access net: Cable network

Digital Subscriber Line

Frequency division multiplexing : different channels transmitted indifferent frequency bands

HFC: hybrid fiber coaxI asymmetric: up to 30Mbps downstream transmission rate, 2 Mbps

upstream transmission rate

network of cable, fiber attaches homes to ISP routerI homes share access network to cable headendI unlike DSL, which has dedicated access to central office

Network edge September 2, 2013 19 / 82

Access net: Home network

Network edge September 2, 2013 20 / 82

Notes

Notes

Notes

Notes

Enterprice access networks (Ethernet)

Network edge September 2, 2013 21 / 82

Enterprice access networks (Ethernet)

typically used in companies, universities, etc

10 Mbps, 100Mbps, 1Gbps, 10Gbps transmission rates

today, end systems typically connect into Ethernet switch

Network edge September 2, 2013 22 / 82

Wireless access networks

Shared wireless access network connects end system to router via basestation aka ”access point”

Wireless LANs

Within building (100 ft)

802.11b/g (WiFi)

11, 54 Mbps transmission rate

Wide-area wireless access

Provided by telco (cellular)operator, 10’s km

Between 1 and 10 Mbps

3G, 4G: LTE

Network edge September 2, 2013 23 / 82

Host: Sends packets of data

Host sending function:

takes application message

breaks into smaller chunks, known as packets, of length L bits

transmits packet into access network at transmission rate R

link transmission rate, aka link capacity, aka link bandwidth

link transmission rate, aka link capacity, aka link bandwidth

packettransmission delay

=time needed totransmit L-bitpacket into link

= L(bits)R(bits/sec)

Network edge September 2, 2013 24 / 82

Notes

Notes

Notes

Notes

Physical media

bit: propagates between transmitter/receiver pairs

physical link: what lies between transmitter and receiver

guided media: signals propagate in solid media: copper, fiber, coax

unguided media: signals propagate freely, e.g., radio

twisted pair (TP)I two insulated copper wiresI Category 5: 100 Mbps, 1 Gpbs EthernetI Category 6: 10Gbps

Network edge September 2, 2013 25 / 82

Physical media: coax

Coaxial cable

two concentric copper conductors

bidirectional

broadbandI multiple channels on cableI HFC

Network edge September 2, 2013 26 / 82

Physical media: Fiber

Fiber optic cable

glass fiber carrying light pulses, each pulse a bit

High-speed operationI High-speed point-to-point transmission (e.g., 10’s-100’s Gpbs

transmission rate)

low error rateI Repeaters spaced far apartI Immune to electromagnetic noise

Network edge September 2, 2013 27 / 82

Physical media: Radio

signal carried in electromagnetic spectrum

no physical ”wire”

bidirectional

propagation environment effects:I reflectionI obstruction by objectsI interference

Network edge September 2, 2013 28 / 82

Notes

Notes

Notes

Notes

Physical media: Radio

Radio link types:

terrestrial microwave e.g. up to 45 Mbps channels

LAN (e.g., WiFi) 11Mbps, 54 Mbps

wide-area (e.g., cellular) 3G cellular: few Mbps

satellite Kbps to 45Mbps channel (or multiple smaller channels)270 msec end-end delaygeosynchronous versus low altitude

Network edge September 2, 2013 29 / 82

Network core

Network core September 2, 2013 30 / 82

Network core

Mesh of interconnected routers

Packet-switching: hosts break application-layer messages intopackets

I Forward packets from one router to the next, across links on path fromsource to destination

I Each packet transmitted at full link capacity

Network core September 2, 2013 31 / 82

Packet-switching

Store-and-forward

Takes L/R seconds to transmit (push out) L-bit packet into link at Rbps

Store and forward: entire packet must arrive at router before it canbe transmitted on next link

End-end delay = 2L/R (assuming zero propagation delay)

Network core September 2, 2013 32 / 82

Notes

Notes

Notes

Notes

Packet-switching

Queueing delay and loss

If arrival rate (in bits) to link exceeds transmission rate of link for aperiod of time:

I Packets will queue, wait to be transmitted on linkI Packets can be dropped (lost) if memory (buffer) fills up

Network core September 2, 2013 33 / 82

Routing and forwarding

Routing

Determines source-destination route taken by packets.Uses routing algorithms

Forwarding

Move packets from router’s input to appropriate router output

Network core September 2, 2013 34 / 82

Routing and forwarding

Network core September 2, 2013 35 / 82

Circuit switching

End-end resources allocated to,reserved for ”call” between sourceand dest:

In diagram, each link has fourcircuits.

I Call gets 2nd circuit in toplink and 1st circuit in rightlink.

Dedicated resources: no sharingI circuit-like (guaranteed)

performance

circuit segment idle if not usedby call (no sharing)

Commonly used in traditionaltelephone networks

Network core September 2, 2013 36 / 82

Notes

Notes

Notes

Notes

Circuit switching: FDM vs. TDM

Network core September 2, 2013 37 / 82

Packet- vs. Circuit-switching

packet switching allows more users to use network!

example:

1 Mb/s link

each user:I 100 kb/s when “active”I active 10% of time

circuit-switching

10 users

Packet switching

with 35 users, probability > 10 active at same time is less than .0004

Network core September 2, 2013 38 / 82

Packet- vs. Circuit-switching

is packet switching a “slam dunk winner?”

great for bursty dataI resource sharingI simpler, no call setup

excessive congestion possible: packet delay and lossI protocols needed for reliable data transfer, congestion control

Q: How to provide circuit-like behavior?I bandwidth guarantees needed for audio/video appsI still an unsolved problem (chapter 7, not covered)

Network core September 2, 2013 39 / 82

Internet structure: Network of networks

End systems connect to Internet via access ISPs (Internet ServiceProviders)

I Residential, company and university ISPs

Access ISPs in turn must be interconnected.I So that any two hosts can send packets to each other

Resulting network of networks is very complexI Evolution was driven by economics and national policies

Let’s take a stepwise approach to describe current Internet structure

Network core September 2, 2013 40 / 82

Notes

Notes

Notes

Notes

Internet structureQuestion

Given millions of access ISPs, how to connect them together?

Network core September 2, 2013 41 / 82

Internet structure

Option

Connect each access ISP to every other access ISP?

Network core September 2, 2013 42 / 82

Internet structureOption

Connect each access ISP to a global transit ISP? Customer and providerISPs have economic agreement.

Network core September 2, 2013 43 / 82

Internet structureBut

if one global ISP is viable business, there will be competitors...

Network core September 2, 2013 44 / 82

Notes

Notes

Notes

Notes

Internet structureBut

if one global ISP is viable business, there will be competitors... which mustbe interconnected

Network core September 2, 2013 45 / 82

Internet structureand

regional networks may arise to connect access nets to ISPS

Network core September 2, 2013 46 / 82

Internet structure

and

content provider networks (e.g., Google, Microsoft, Akamai ) may runtheir own network, to bring services, content close to end users

Network core September 2, 2013 47 / 82

Internet structure: Network of networks

at center: small # of well-connected large networksI ”tier-1” commercial ISPs (e.g., Level 3, Sprint, AT&T, NTT), national

& international coverageI content provider network (e.g, Google): private network that connects

it data centers to Internet, often bypassing tier-1, regional ISPs

Network core September 2, 2013 48 / 82

Notes

Notes

Notes

Notes

Internet structure: Tier-1 ISP (Sprint)

Network core September 2, 2013 49 / 82

Performance: Loss, Delay, Throughput

performance: loss, delay, throughput September 2, 2013 50 / 82

How do loss and delay occur?

packets queue in router buffersI packet arrival rate to link (temporarily) exceeds output link capacityI packets queue, wait for turn

performance: loss, delay, throughput September 2, 2013 51 / 82

Four sources of packet delay

nodal processing

check bit errors

determine output link

typically < msec

Queueing delay

time waiting at output link for transmission

depends on congestion level of router

Transmission delay

L: packet length (bits)

R: link bandwidth (bps)

Transmission delay = L/R

Propagation delay

d: length of physical link

s: propagation speed in medium ( 2x108 m/sec)

Propagation delay = d/s

performance: loss, delay, throughput September 2, 2013 52 / 82

Notes

Notes

Notes

Notes

Caravan analogy

cars ”propagate” at 100 km/hr

toll booth takes 12 sec to service car (bit transmission time)

car ∼ bit; caravan ∼ packet

Q: How long until caravan is lined up before 2nd toll booth?

time to “push” entire caravan through toll booth onto highway =12*10 = 120 sec

time for last car to propagate from 1st to 2nd toll both:100km/(100km/hr)= 1 hr

A: 62 minutes

performance: loss, delay, throughput September 2, 2013 53 / 82

Caravan analogy (more)

Suppose cars now “propagate” at 1000 km/hr and suppose toll boothnow takes one min to service a car

Q: Will cars arrive to 2nd booth before all cars serviced at first booth?

A: Yes! after 7 min, 1st car arrives at second booth; three cars still at1st booth.

performance: loss, delay, throughput September 2, 2013 54 / 82

Queueing delay (revisited)

R: link bandwidth (bps)

L: packet length (bits)

a: average packet arrival rate

LaR ∼ 0: avg. queueing delay smallLaR → 1: avg. queueing delay largeLaR > 1: more “work” arriving than can be serviced, average delayinfinite!

performance: loss, delay, throughput September 2, 2013 55 / 82

”Real” Internet delays and routeswhat do “real” Internet delay and loss look like?traceroute program: provides delay measurement from source torouter along end-end Internet path towards destination. For all i:

I sends three packets that will reach router i on path towards destinationI router i will return packets to senderI sender times interval between transmission and reply.

performance: loss, delay, throughput September 2, 2013 56 / 82

Notes

Notes

Notes

Notes

”Real” Internet delays and routes

$ traceroute cs.umass.edu

traceroute to cs.umass.edu (128.119.240.93), 30 hops max, 60 byte packets

1 192.168.1.1 (192.168.1.1) 4.118 ms 5.399 ms 6.217 ms

2 xe-2-0-0-1104.odnqe10.dk.ip.tdc.net (80.162.66.237) 27.879 ms 29.274 ms 29.625 ms

3 as0-0.ashbnqp1.us.ip.tdc.net (83.88.31.141) 152.961 ms 152.947 ms 152.957 ms

4 eeq-exchange.tr01-asbnva01.transitrail.net (206.126.236.45) 155.241 ms 154.874 ms 156.811 ms

5 ae-2.0.ny0.tr-cps.internet2.edu (64.57.20.197) 147.600 ms 151.800 ms 150.271 ms

6 64.57.21.210 (64.57.21.210) 157.587 ms 137.632 ms 140.931 ms

7 nox300gw1-peer--207-210-142-242.nox.org (207.210.142.242) 146.500 ms 150.512 ms 151.050 ms

8 core1-rt-xe-0-0-0.gw.umass.edu (192.80.83.101) 153.933 ms 158.008 ms 160.034 ms

9 lgrc-rt-106-8-po-10.gw.umass.edu (128.119.0.233) 167.644 ms 164.152 ms 164.443 ms

10 128.119.3.32 (128.119.3.32) 167.289 ms 169.114 ms 168.008 ms

11 loki.cs.umass.edu (128.119.240.93) 167.883 ms 169.216 ms 170.235 ms

performance: loss, delay, throughput September 2, 2013 57 / 82

Packet loss

queue (aka buffer) preceding link in buffer has finite capacity

packet arriving to full queue dropped (aka lost)

lost packet may be retransmitted by previous node, by source endsystem, or not at all

performance: loss, delay, throughput September 2, 2013 58 / 82

Throughput

throughput: rate (bits/time unit) at which bits transferred betweensender/receiver

I instantaneous: rate at given point in timeI average: rate over longer period of time

performance: loss, delay, throughput September 2, 2013 59 / 82

Throughput - more

Rs < Rc What is average end-end throughput?

Rs > Rc What is average end-end throughput?

bottleneck link

link on end-end path that constrains end-end throughput

performance: loss, delay, throughput September 2, 2013 60 / 82

Notes

Notes

Notes

Notes

Throughput: Internet scenario

per-connection end-endthroughput: min(Rc,Rs,R/10)

in practice: Rc or Rs is oftenbottleneck

performance: loss, delay, throughput September 2, 2013 61 / 82

Protocol layers, service models

Protocol layers, service models September 2, 2013 62 / 82

Protocol ”layers”

Networks are complex, with many“pieces”:

hosts

routers

links of various media

applications

protocols

hardware, software

Question:

is there any hope of organizingstructure of network? . . . . or at leastour discussion of networks?

Protocol layers, service models September 2, 2013 63 / 82

Organization of air travel

a series of steps

Protocol layers, service models September 2, 2013 64 / 82

Notes

Notes

Notes

Notes

Layering of airline functionality

layers: each layer implements a serviceI via its own internal-layer actionsI relying on services provided by layer below

Protocol layers, service models September 2, 2013 65 / 82

Why layering?

dealing with complex systems:

explicit structure allows identification, relationship of complexsystem’s pieces

I layered reference model for discussion

modularization eases maintenance, updating of systemI change of implementation of layer’s service transparent to rest of

systemI e.g., change in gate procedure doesn’t affect rest of system

layering considered harmful?

Protocol layers, service models September 2, 2013 66 / 82

Internet protocol stack

application: supporting network applicationsI FTP, SMTP, HTTP

transport: process-process data transferI TCP, UDP

network: routing of datagrams from source todestination

I IP, routing protocols

link: data transfer between neighboring networkelements Ethernet, 802.111 (WiFi), PPP

physical: bits “on the wire”

Protocol layers, service models September 2, 2013 67 / 82

ISO/OSI reference model

presentation: allow applications to interpretmeaning of data, e.g., encryption, compression,machine-specific conventions

session: synchronization, checkpointing, recoveryof data exchange

Internet stack “missing” these layers!I these services, if needed, must be implemented in

applicationI needed?

Protocol layers, service models September 2, 2013 68 / 82

Notes

Notes

Notes

Notes

Encapsulation

Protocol layers, service models September 2, 2013 69 / 82

Network security

field of network security:I how bad guys can attack computer networksI how we can defend networks against attacksI how to design architectures that are immune to attacks

Internet not originally designed with (much) security in mindI original vision: ”a group of mutually trusting users attached to a

transparent network”I Internet protocol designers playing “catch-up”I security considerations in all layers!

security September 2, 2013 70 / 82

Bad guys: put malware into hosts via Internet

malware can get in host from:I virus: self-replicating infection by receiving/executing object (e.g.,

e-mail attachment)I worm: self-replicating infection by passively receiving object that gets

itself executed

spyware malware can record keystrokes, web sites visited, upload infoto collection site

infected host can be enrolled in botnet, used for spam. DDoS attacks

security September 2, 2013 71 / 82

Bad guys: attack server, network infrastructure

Denial of Service (DoS)

Attackers make resources (server, bandwidth) unavailable to legitimatetraffic by overwhelming resource with bogus traffic

1 Select target

2 Break into hosts around thenetwork (see botnet)

3 Send packets to target fromcompromised hosts

security September 2, 2013 72 / 82

Notes

Notes

Notes

Notes

Bad guys can sniff packets

packet ”sniffing”

broadcast media (shared ethernet, wireless)

promiscuous network interface reads/records all packets (e.g.,including passwords!) passing by

security September 2, 2013 73 / 82

Bad guys can use fake addresses

IP spoofing

send packet with false source address

... lots more on security (later in the course)

security September 2, 2013 74 / 82

History

history September 2, 2013 75 / 82

1961-1972: Early packet-switching principles

1961 Kleinrock - queueing theory shows effectiveness ofpacket-switching

1964 Baran - packet-switching in military nets

1967 ARPAnet conceived by Advanced Research Projects Agency

1969 First ARPAnet node operational

1972 ARPAnet public demo

NCP (Network Control Protocol) first host-host protocolFirst e-mail programARPAnet has 15 nodes

history September 2, 2013 76 / 82

Notes

Notes

Notes

Notes

1972-1980: Internetworking, new and proprietarynets

1970 ALOHAnet satellite network in Hawaii

1974 Cerf and Kahn - architecture for interconnecting networks

1976 Ethernet at Xerox PARC

late70’s proprietary architectures: DECnet, SNA, XNA

late 70’s switching fixed length packets (ATM precursor)

1979 ARPAnet has 200 nodes

history September 2, 2013 77 / 82

1972-1980: Internetworking, new and proprietarynets

Cerf and Kahn’s internetworking principles:

Minimalism, autonomy - no internal changes required to interconnectnetworks

Best effort service model

Stateless routers

Decentralized control

Define today’s Internet architecture

history September 2, 2013 78 / 82

1980-1990: new protocols, a proliferation ofnetworks

1983 deployment of TCP/IP

1982 smtp e-mail protocol defined

1983 DNS defined for name-to-IP-address translation

1985 ftp protocol defined

1988 TCP congestion control

new national networks: Csnet, BITnet, NSFnet, Minitel

100,000 hosts connected to confederation of networks

history September 2, 2013 79 / 82

1990, 2000’s: commercialization, the Web, newapps

early 1990’s ARPAnet decommissioned

1991 NSF lifts restrictions on commercial use of NSFnet(decommissioned, 1995)

early 1990s Web

hypertext [Bush 1945, Nelson 1960’s]HTML, HTTP: Berners-Lee1994: Mosaic, later Netscapelate 1990’s: commercialization of the Web

late 1990’s – 2000’s more killer apps: instant messaging, P2P filesharingnetwork security to forefrontest. 50 million host, 100 million+ usersbackbone links running at Gbps

history September 2, 2013 80 / 82

Notes

Notes

Notes

Notes

2005-present

750 million hosts

Smartphones and tablets

Aggressive deployment of broadband access

Increasing ubiquity of high-speed wireless access (3G, 4G)

Emergence of online social networks:

Facebook: soon one billion users

Service providers (Google, Microsoft) create their own networks

Bypass Internet, providing “instantaneous” access to search, emai,etc.

E-commerce, universities, enterprises running their services in “cloud”(eg, Amazon EC2)

history September 2, 2013 81 / 82

Summary 1

Internet overview

what’s a protocol?

network edge, core, access network

packet-switching versus circuit-switching

Internet structure

performance: loss, delay, throughput

layering, service models

security

history

history September 2, 2013 82 / 82

Notes

Notes

Notes

Notes