Probability, Preview, and Principles
|
|
- Alison Simpson
- 5 years ago
- Views:
Transcription
1 Probability, Preview, and Principles EE122 Fall 2011 Scott Shenker Materials with thanks to Jennifer Rexford, Ion Stoica, Vern Paxson and other colleagues at Princeton and UC Berkeley 1
2 Announcements Sections this week! Shaddi Hasan We have new account forms Get them after class, one per person, no exceptions Project will be released on Wednesday So we can get to Reliable Transport beforehand Problem 3.iii Consider case where F and Q increase, but H and P stay constant. Waiting list: No way to move more students in Could try doing a 194 2
3 Outline Primer on probability (6 slides) Simple, but all you need. Discussion of Homework #1 Layering Design Principles for the Internet Layering E2E Principle Fate Sharing 3
4 Probability Primer Get out a sheet of paper or otherwise be able to jot down your answers This is not a test, this is so you can tell if you understand the material
5 Independent Events Independent: occurrence of one event does not affect the likelihood of the other event Example of two independent events: Flow 1 sends 5 packets in a particular frame Flow 2 sends 2 packets in a particular frame Assume that: Event A happens with probability p A Event B happens with probability p B What is probability both event A and B happen? Write it down! Answer: Probability = p A p B 5
6 Consider Dice Probability that rolling a single die yields a 1? 1/6 th Probability rolling two dice yields 1 1? 1/36 th Probability rolling two dice yields a 1 and a 2? Write it down! 6
7 Be Careful Counting Events First die is 1 and second die is 2: 1/36 th One die is 1 and one die is 2: 1/18 th That s because you could have 1 2 or 2 1 7
8 Mutually Exclusive Events First roll of die is 1:1/6 th First roll of die is 2:1/6 th First roll of die is 3:1/6 th First roll of die is 4:1/6 th First roll of die is 5:1/6 th First roll of die is 6:1/6 th This set of events is complete (or exhaustive) in that one of them must be true Total of probabilities = 1 8
9 Exclusive vs Independent Events First roll of die is 1, second roll of die is 3 Independent First roll of die is 1, first roll of die is 2 Exclusive 9
10 Computing Averages Assume that x is some property of an event and that events A, B, C are mutually exclusive and complete (i.e., one of them happens) E.g., x = number of packets sent in a particular frame Assume that: Event A has x=5 Event B has x=2 Event C has x=10 What is the average value of x? (denoted by <x>) Write it down! Average <x> = 5p A + 2p B + 10p C 10
11 THIS IS ALL YOU NEED TO KNOW! The problems are easier than you think but think clearly before computing the answer 11
12 Discussion of HW#1
13 #2: Statistical Multiplexing Time is divided into frames, frames into slots Each flow is assigned one slot per frame The flows have identical proabilistic behavior: With equal probability, send zero, one, or two packets Exclusive events! Compute the fraction of packets that are dropped when n flows share their slots, for n=1, 2, 3, 4 Does fraction dropped decrease as n grows? 13
14 Consider Two Flows (n=2) Flow A sends 1 packet Probability 1/3 rd Flow B sends no packets Probability 1/3 rd Are these independent or exclusive events? Independent! So probability that both happen is: Probability = 1/3 x 1/3 = 1/9 Average number packets/frame generated by A? (1/3 x 0) + (1/3 x 1) + (1/3 x 2) = 1 14
15 n=2 Cases: Each with Prob 1/9 th Flow A Flow B In which cases are packets dropped? 15
16 N=2 Cases: Have two slots to share Flow A Flow B Average number of drops: 1/9 th x (1+1+2) Average number of packets generated: 2 Fraction of drops: 2/9 th s 16
17 Cases n=3 and n=4 n=3 you can easily enumerate n=4 have patience, but if you understand how to group equivalent events (and count permutations properly) then it is easy. And even easier to focus only on cases where shared and individual differ Reason to do 3 and 4 is to convince you that there is a trend as n increases.. If this problem bores you, compute the asymptotic behavior as a function of n. it to me, don t hand it in with homework. 17
18 #4: PS/CS Retransmission After Failure Fact: if transmission fails with probability p, number of retransmissions until success is given by: 18
19 Derivation Success on first transmission: (1-p) Success on second transmission: p(1-p) Success on third transmission: p 2 (1-p). Average number of retransmissions: 0(1-p) + 1*p(1-p) + 2*p 2 (1-p) +.. = 19
20 Failure Model Assume that probability that the link goes down sometime during a time period t is given by: 20
21 Using these facts Only delay is transmission time Ignore latency, queueing Use this time to determine failure rate Using the formula f(t) for the right value of t Use that to determine retransmissions Using f(t)/(1-f(t)) Packet-switched has to send Q packets So do the above calculation for packets, not file. 21
22 #3: Delays under PS and CS Compare the time it takes to transfer a file of size F under circuit-switching and packet-switching. Network: n links in a row, bandwidth B, latency L. Circuit-switching: Reservation packet (stored-andforwarded), confirmation packet, file transmission. Packet-switching: File broken into packets (with headers). Packets stored-and-forwarded at nodes. Express delays in terms of: n,b, L, F, etc. Understand limiting behaviors 22
23 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 time 23
24 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment propagation delay between Host 1 and Switch1 time 24
25 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment Transmission delay propagation delay between Host 1 and Switch1 time 25
26 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment Transmission delay propagation delay between Host 1 and Switch1 time 26
27 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment Transmission delay propagation delay between Host 1 and Switch1 propagation delay between Host 1 and Host 2 time 27
28 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment Transmission delay propagation delay between Host 1 and Switch1 propagation delay between Host 1 and Host 2 Transfer Information time 28
29 Timing in Circuit Switching Host 1 Host 2 Switch 1 Switch 2 Circuit Establishment Transmission delay propagation delay between Host 1 and Switch1 propagation delay between Host 1 and Host 2 Transfer Circuit Teardown Information time 29
30 Timing of Datagram Packet Switching Host 1 Host 2 Node 1 Node 2 Packet 1 propagation delay between Host 1 and Node 1 30
31 Timing of Datagram Packet Switching Host 1 Host 2 Node 1 Node 2 transmission time of Packet 1 at Host 1 Packet 1 propagation delay between Host 1 and Node 1 31
32 Timing of Datagram Packet Switching Host 1 Host 2 Node 1 Node 2 transmission time of Packet 1 at Host 1 Packet 1 Packet 1 We ignore processing delay in the homework! Packet 1 32
33 Timing of Datagram Packet Switching Host 1 Host 2 Node 1 Node 2 transmission time of Packet 1 at Host 1 Packet 1 Packet 2 Packet 3 propagation delay between Host 1 and Node 1 Packet 1 Packet 2 Packet 3 We ignore processing delay in the homework! Packet 1 Packet 2 Packet 3 33
34 Layering
35 Modularity in Computer Science Modularity based on abstraction is the way things get done --Barbara Liskov 35
36 Benefits of Modularity Implementations hidden behind clean interfaces Interfaces are incarnations of abstractions Changes are limited in scope Allows for continuing evolution and innovation Easier to reason about 36
37 Methodology Break job down into smaller tasks And understand how they interact Define abstractions for these tasks Then implement them.. 37
38 Tasks in Networking What does it take to send packets across country? Simplistic decomposition: Task 1: send along a single wire Task 2: string these together to go across country What makes Task 2 nontrivial? Routing! More detailed decomposition in next slide. 38
39 Tasks in Networking (bottom up) Electrons on wire Bits on wire Packets on wire Deliver packets across local network Local addresses Deliver packets across country Global addresses Ensure that packets get there Do something with the data 39
40 How do we organize these tasks? Put them into layers Layering is a particularly strict form of modularity Interactions limited to interfaces above and below To motivate layers, we go back to the beginning 40
41 You now have 3 minutes to answer Who invented layering? 41
42 Wrong Answers ISO ARPANET Walt Disney 42
43 Answer: Henry Ford Before: Each person worked on the whole car After: Each person only handled one particular task Handed off car to next person in line Only needed to understand the state of the car as it arrived, and only needed to produce the appropriate output Could remain ignorant of everything else! 43
44 Advantages of Assembly Line Specialization allows people to get faster i.e., local improvements in implementation If you want to change something in the car, only one person needed to know. i.e., changes of limited scope 44
45 More Layering in the Real World CEO A writes letter to CEO B Folds letter and hands it to administrative aide Aide: Dear Steve, Puts letter in envelope with CEO B s name Takes to FedEx We give up. Let s merge. FedEx Office Puts letter in larger envelope Puts name --Bill and street address on FedEx envelope Puts package on FedEx delivery truck FedEx delivers to other company 45
46 The Path of the Letter Peers on each side understand the same things No one else does Lowest level has most packaging CEO Semantic Letter Content CEO Aide Envelope Identity Aide FedEx Fedex Location Envelope (FE) FedEx 46
47 The Path Through FedEx Higher Stack at Ends Partial Stack Truck During Transit FE Sorting Office Airport Crate Highest Level of Transit Stack is Routing Crate FE Sorting Office Airport New Crate FE Crate Deepest Packaging at the Lowest Level of Transport Truck Sorting Office Airport 47
48 How Does This Apply to Networking? Let s return to task decomposition. 48
49 Tasks in Networking Electrons on wire Bits on wire Packets on wire Deliver packets across local network Local addresses Deliver packets across country Global addresses Ensure that packets get there Do something with the data 49
50 Resulting Layers Electrons on wire (contained in next layer) Bits on wire (Physical) Packets on wire (contained in next layer) Deliver packets across local network (Link) Local addresses Deliver packets across country (Internetwork) Global addresses Ensure that packets get there (Transport) Do something with the data (Application) 50
51 Who Does What? Five layers Lower three layers implemented everywhere Top two layers implemented only at hosts What is top layer of router doing? Application Transport Network Datalink Physical Host A Network Datalink Physical Router Application Transport Network Datalink Physical Host B 51
52 Logical Communication Layers interacts with peer s corresponding layer Application Transport Network Datalink Physical Host A Network Datalink Physical Router Application Transport Network Datalink Physical Host B 52
53 Physical Communication Communication goes down to physical network Then from network peer to peer Then up to relevant layer Application Transport Network Datalink Physical Host A Network Datalink Physical Router Application Transport Network Datalink Physical Host B 53
54 The Path Through FedEx In both cases, the highest layer inthe transit nodes is doing routing! Company Company Sorting Office Sorting Office Sorting Office Airport Airport Airport 54
55 IP Suite: End Hosts vs. Routers host HTTP HTTP message host HTTP TCP TCP segment TCP router router IP IP packet IP IP packet IP IP packet IP Ethernet interface Ethernet interface SONET interface SONET interface Ethernet interface Ethernet interface 55
56 Layer Encapsulation User A User B Appl: Get index.html Trans: Connection ID Net: Source/Dest Link: Src/Dest Common case: 20 bytes TCP header + 20 bytes IP header + 14 bytes Ethernet header = 54 bytes overhead 56
57 Five Minute Break.
58 Quote for the day.. The Internet is the first thing that humanity has built that humanity doesn't understand, the largest experiment in anarchy that we have ever had. ~Eric Schmidt 58
59 Characterizing the Layers (OSI) Service: what a layer does Service interface: how to access the service Interface for layer above Protocol: how peers communicate Protocol interface: set of rules and formats that govern the communication between network elements Determines how the peers achieve the service Does not govern implementation on a single machine, but how the layer is implemented between machines Examples: layer can have many implementations This allows innovation! 59
60 Physical Layer (1) Service: move bits between two systems connected by a single physical link Interface: specifies how to send and receive bits E.g., require quantities and timing Protocols: coding scheme used to represent bits, voltage levels, duration of a bit Examples: Optical, wireless, etc. 60
61 (Data) Link Layer (2) Service: Enable hosts to exchange messages Using abstract (but local) addresses Not just direct physical connections Interface: send messages (frames) to other end hosts; receive messages addressed to end host Protocols: Routing Media Access Control (MAC) Examples: Ethernet, , Frame Relay, ATM 61
62 (Inter) Network Layer (3) Service: Deliver packets to specified destination Using abstract global addresses Inter-network = across multiple layer-2 networks E.g., from Ethernet to to Frame Relay to ATM Interface: send packets to specified internetwork destinations; receive packets destined for end host Protocols: construct routing tables Examples: IP Why no other examples? 62
63 Transport Layer (4) Service: Communication between processes Demultiplexing of communication between hosts Perhaps: reliable transport, rate adaptation Interface: send message to specific process at given destination local process receives messages sent to it Protocol: reliability, flow control, packetization of large messages, framing Examples: TCP and UDP SCTP, T/TCP, DCCP, 63
64 Application Layer (7 - not 5!) Service: any service provided to the end user Interface: depends on the application Protocol: depends on the application Examples: Skype, SMTP ( ), HTTP (Web), Halo, BitTorrent 64
65 The Internet Hourglass SMTP HTTP DNS NTP Applications TCP UDP Transport IP Waist Ethernet SONET Data Link Physical Copper Fiber Radio The Hourglass Model There is just one network-layer protocol, IP. The narrow waist facilitates interoperability. 65
66 Avoids NxM Implementation Problem Application Skype SSH NFS HTTP Transmission Media Coaxial cable Fiber optic Radio 66
67 Implications of Hourglass Allows arbitrary L2 networks to interoperate Any networks that support IP can exchange packets Allows applications to function on all networks Applications that can run on IP can use any network Supports innovations above and below IP Innovations can be independent, done in parallel But changing IP itself, i.e., IPv6, very hard Many claim that a narrow waist is a necessary aspect of any Internet architecture I am not among them. 67
68 Internet Design Principles
69 Back to Modularity Modularity in programming: Set of abstractions Modularity in networking: Distributed nature of system requires deciding where abstractions are implemented 69
70 Three Basic Architectural Decisions How to break system into modules Where modules are implemented Where state is stored 70
71 Breaking into Modules That is described by layering 71
72 Placing Network Functionality Hugely influential paper: End-to-End Arguments in System Design by Saltzer, Reed, and Clark ( 84) End-to-end principle Basic observation: some types of network functionality can only be correctly implemented end-to-end Because of this, end hosts: Can satisfy the requirement without network s help Must do so, since can t rely on network s help Thus, don t need to implement them in network 72
73 Example: Reliable File Transfer Host A Appl. OS OK Host B Appl. OS Solution 1: make each step reliable, and string them together to make reliable end-to-end process Solution 2: allow steps to be unreliable, but do endto-end check and try again if necessary 73
74 Discussion Solution 1 cannot be made perfectly reliable What happens if a network element misbehaves? Receiver has to do the check anyway! Solution 2 can also fail, but only if the end system itself fails (i.e., doesn t follow its own protocol) Solution 2 only relies on what it can control The endpoint behavior Solution 1 requires endpoints trust other elements That s not what reliable means! 74
75 Robust (From Clark s Paper) As long as the network is not partitioned, two endpoints should be able to communicate Failures (excepting network partition) should not interfere with endpoint semantics 75
76 Question? Should you ever implement reliability in network? Perhaps, if needed for reasonable efficiency Don t aim for perfect reliability, but ok to reduce error rate If individual links fail 10% of the time, and are traversing 10 links, then E2E error rate is 65% Implementing one retransmission on links Link error rate reduced to 1%, E2E error rate is 9.5% 76
77 Back to the End-to-End Principle Implementing such functionality in the network: Doesn t reduce host implementation complexity Does increase network complexity Probably imposes delay and overhead on all applications, even if they don t need functionality However, implementing in network can enhance performance in some cases E.g., very lossy link 77
78 Conservative Interpretation of E2E Don t implement a function at the lower levels of the system unless it can be completely implemented at this level Unless you can relieve the burden from hosts, don t bother 78
79 Radical Interpretation of E2E Don t implement anything in the network that can be implemented correctly by the hosts E.g., multicast Make network layer absolutely minimal E2E principle trumps performance issues Increases flexibility, since lower layers stay simple 79
80 Important life lessons (partial) Flexibility often more important than performance Architect for flexibility, engineer for performance 80
81 Moderate Interpretation Think twice before implementing functionality in the network If hosts can implement functionality correctly, implement it in a lower layer only as a performance enhancement But do so only if it does not impose burden on applications that do not require that functionality 81
82 What Does E2E Principle Ignore? There are other stakeholders besides users ISP might care about the good operation of their network Various commercial entities Money-chain might require insertion into the network The need for middlebox functionality Some functions that, for management reasons, are more easily done in the network. 82
83 Three Basic Architectural Decisions How to break system into modules Where modules are implemented Where state is stored 83
84 Fate-Sharing Note that E2E principles relied on fate-sharing Invariants break only when endpoints themselves break Minimize dependence on other network elements This should dictate placement of storage 84
85 General Principle: Fate-Sharing When storing state in a distributed system, colocate it with entities that rely on that state Only way failure can cause loss of the critical state is if the entity that cares about it also fails... in which case it doesn t matter Often argues for keeping network state at end hosts rather than inside routers In keeping with End-to-End principle E.g., packet-switching rather than circuit-switching E.g., NFS file handles, HTTP cookies 85
86 Another Quote A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable ---Leslie Lamport 86
87 Decisions and Their Principles How to break system into modules Dictated by Layering Where modules are implemented Dictated by End-to-End Principle Where state is stored Dictated by Fate-Sharing 87
88 Question If reliability is implemented by the ends, how is it done? That s the subject of the next lecture! 88
Internet Design: Goals and Principles
Internet Design: Goals and Principles EE122 Fall 2012 Scott Shenker http://inst.eecs.berkeley.edu/~ee122/ Materials with thanks to Jennifer Rexford, Ion Stoica, Vern Paxson and other colleagues at Princeton
More informationPage 1. Goals for Today" What Is A Protocol?" CS162 Operating Systems and Systems Programming Lecture 10. Protocols, Layering and e2e Argument"
Goals for Today" CS162 Operating Systems and Systems Programming Lecture 10 Protocols, Layering and e2e Argument" What is a protocol?! Layering! End-to-end arguments!! October 3, 2011! Anthony D. Joseph
More informationCS 268: Internet Architecture & E2E Arguments. Today s Agenda. Scott Shenker and Ion Stoica (Fall, 2010) Design goals.
CS 268: Internet Architecture & E2E Arguments Scott Shenker and Ion Stoica (Fall, 2010) 1 Today s Agenda Design goals Layering (review) End-to-end arguments (review) 2 1 Internet Design Goals Goals 0 Connect
More informationInternet Design Principles
Internet Design Principles EE 122: Intro to Communication Networks Fall 2006 (MW 4-5:30 in Donner 155) Vern Paxson TAs: Dilip Antony Joseph and Sukun Kim http://inst.eecs.berkeley.edu/~ee122/ Materials
More informationCS4700/CS5700 Fundaments of Computer Networks
CS4700/CS5700 Fundaments of Computer Networks Lecture 5: Internet architecture Slides used with permissions from Edward W. Knightly, T. S. Eugene Ng, Ion Stoica, Hui Zhang Alan Mislove amislove at ccs.neu.edu
More informationNetwork Architecture. EE 122, Fall 2013 Sylvia Ratnasamy
Network Architecture EE 122, Fall 2013 Sylvia Ratnasamy http://inst.eecs.berkeley.edu/~ee122/ Administrivia l Enrollment l l Discussion sections are *not* the bottleneck to enrollment State of the waitlist
More informationCS 268: Lecture 4 (Internet Architecture & E2E Arguments)
CS 268: Lecture 4 (Internet Architecture & E2E Arguments) Today s Agenda Course Theme Course overview History of the Internet Design goals Layering (review) Focus on the Internet Other topics covered,
More informationQuestion. Reliable Transport: The Prequel. Don t parse my words too carefully. Don t be intimidated. Decisions and Their Principles.
Question How many people have not yet participated? Reliable Transport: The Prequel EE122 Fall 2012 Scott Shenker http://inst.eecs.berkeley.edu/~ee122/ Materials with thanks to Jennifer Rexford, Ion Stoica,
More informationLecture 2: Internet Architecture
CS 3700 Networks and Distributed Systems Lecture 2: Internet Architecture Revised 1/6/14 Organizing Network Functionality 2 Organizing Network Functionality 2 Networks are built from many components! Networking
More informationGoal of Today s Lecture. EE 122: Designing IP. The Internet Hourglass. Our Story So Far (Context) Our Story So Far (Context), Con t
Goal of Today s Lecture EE 122: Designing IP Ion Stoica TAs: Junda Liu, DK Moon, David Zats http://inst.eecs.berkeley.edu/~ee122/ (Materials with thanks to Vern Paxson, Jennifer Rexford, and colleagues
More informationCS3600 SYSTEMS AND NETWORKS
CS3600 SYSTEMS AND NETWORKS NORTHEASTERN UNIVERSITY Lecture 17: Internet architecture Prof. Alan Mislove (amislove@ccs.neu.edu) Slides used with permissions from Edward W. Knightly, T. S. Eugene Ng, Ion
More informationCS4700/5700: Network fundamentals
Cristina Nita-Rotaru CS4700/5700: Network fundamentals. 1: Organizing network functionality } Networks are built from many components } Networking technologies } Ethernet, Wifi, Bluetooth, Fiber Optic,
More informationPage 1. Goals for Today" Discussion" Example: Reliable File Transfer" CS162 Operating Systems and Systems Programming Lecture 11
Goals for Today" CS162 Operating Systems and Systems Programming Lecture 11 Reliability, Transport Protocols" Finish e2e argument & fate sharing Transport: TCP/UDP Reliability Flow control October 5, 2011
More informationCSE 123A Computer Networks
CSE 123A Computer Networks Winter 2005 Lecture 3: Protocols & Layering Alex Snoeren (standing in for Stefan Savage) Yesterday How to send data from point A to point B? January 13, 2005 CSE 123A -- Lecture
More information416 Distributed Systems. Networks review; Day 1 of 2 Jan 5 + 8, 2018
416 Distributed Systems Networks review; Day 1 of 2 Jan 5 + 8, 2018 1 Distributed Systems vs. Networks Low level (c/go) Run forever Support others Adversarial environment Distributed & concurrent Resources
More informationNetworking Acronym Smorgasbord: , DVMRP, CBT, WFQ
Networking Acronym Smorgasbord: 802.11, DVMRP, CBT, WFQ EE122 Fall 2011 Scott Shenker http://inst.eecs.berkeley.edu/~ee122/ Materials with thanks to Jennifer Rexford, Ion Stoica, Vern Paxson and other
More informationCS 3640: Introduction to Networks and Their Applications
CS 3640: Introduction to Networks and Their Applications Fall 2018, Lecture 2: More layering and the end-to-end principle. Instructor: Rishab Nithyanand Teaching Assistant: Md. Kowsar Hossain 1 Today in
More informationAnnouncements. Designing IP. Our Story So Far (Context) Goals of Today s Lecture. Our Story So Far (Context), Con t. The Internet Hourglass
Announcements Designing IP EE 122: Intro to Communication Networks Fall 200 (MW -:30 in Donner 1) Homework #2 out Wednesday rather than today And due Oct 11 instead of Oct We will likely shift the remaining
More informationAnnouncements Computer Networking. What is the Objective of the Internet? Today s Lecture
Announcements 15-441 15-441 Computer ing 15-641 Lecture 2 Protocol Stacks Peter Steenkiste Fall 2016 www.cs.cmu.edu/~prs/15-441-f16 Sign up for piazza: https://piazza.com/cmu/fall2016/15441641 P1 will
More informationTDTS21 Advanced Networking
TDTS21 Advanced Networking Lecture 2: Hosts, the Internet architecture, and the E2E arguments Based on slides from D. Choffnes, P. Gill, and J. Rexford Revised Spring 2015 by N. Carlsson End hosts The
More informationPage 1. Goals for Today" Placing Network Functionality" Basic Observation" CS162 Operating Systems and Systems Programming Lecture 15
Goals for Today" CS162 Operating Systems and Systems Programming Lecture 15 Finish e2e argument & fate sharing! Transport: TCP/UDP! Reliability! Flow control! Reliability, Transport Protocols" March 16,
More informationECE 650 Systems Programming & Engineering. Spring 2018
ECE 650 Systems Programming & Engineering Spring 2018 Networking Introduction Tyler Bletsch Duke University Slides are adapted from Brian Rogers (Duke) Computer Networking A background of important areas
More informationCSCI Computer Networks
CSCI-1680 - Computer Networks Chen Avin (avin) Based partly on lecture notes by David Mazières, Phil Levis, John Jannotti, Peterson & Davie, Rodrigo Fonseca Administrivia Sign and hand in Collaboration
More informationLecture 2. Computer Networks Models. Network Models 1-1
Lecture 2 Computer Networks Models Network Models 1-1 Agenda Introduction to the Internet Reference Models for Computer Networks The OSI Model The TCP/IP Model Network Models 1-2 Announcements Bonus -
More informationData and Computer Communications. Chapter 2 Protocol Architecture, TCP/IP, and Internet-Based Applications
Data and Computer Communications Chapter 2 Protocol Architecture, TCP/IP, and Internet-Based s 1 Need For Protocol Architecture data exchange can involve complex procedures better if task broken into subtasks
More informationb) Diverse forms of physical connection - all sorts of wired connections, wireless connections, fiber optics, etc.
Objectives CPS221 Lecture: Layered Network Architecture last revised 6/22/10 1. To discuss the OSI layered architecture model 2. To discuss the specific implementation of this model in TCP/IP Materials:
More informationIP Packet Switching. Goals of Todayʼs Lecture. Simple Network: Nodes and a Link. Connectivity Links and nodes Circuit switching Packet switching
IP Packet Switching CS 375: Computer Networks Dr. Thomas C. Bressoud Goals of Todayʼs Lecture Connectivity Links and nodes Circuit switching Packet switching IP service model Best-effort packet delivery
More informationCPS221 Lecture: Layered Network Architecture
CPS221 Lecture: Layered Network Architecture Objectives last revised 9/8/14 1. To discuss the OSI layered architecture model 2. To discuss the specific implementation of this model in TCP/IP Materials:
More informationPage 1. Review: The Problem" Software System Modularity" Solution: Intermediate Layers"
Review: The Problem" CS162 Operating Systems and Systems Programming Lecture 16 Layering" Transmission" Media" Skype " SSH" NFS" Coaxial " cable" Fiber" optic" HTTP" Packet" Radio" March 31, 2014 Anthony
More informationInternet Design Principles and Architecture
Internet Design Principles and Architecture Venkat Padmanabhan Microsoft Research 2 April 2001 Venkat Padmanabhan 1 Lecture Outline A brief history of the Internet How is the Internet different from the
More informationLecture 2: Layering & End-to-End
Lecture 2: Layering & End-to-End CSE 222A: Computer Communication Networks Alex C. Snoeren Thanks: Mike Freedman & Amin Vahdat Lecture 2 Overview Layering Application interface Transport services Discussion
More informationLecture 3: Modulation & Layering"
Lecture 3: Modulation & Layering" CSE 123: Computer Networks Alex C. Snoeren HW 1 out Today, due 10/09! Lecture 3 Overview" Encoding schemes Shannon s Law and Nyquist Limit Clock recovery Manchester, NRZ,
More informationNetwork Architecture COS 461: Computer Networks
Network Architecture COS 461: Computer Networks Nick Feamster Spring 2015 Lectures: MW 10-10:50 am in CS 104 Acknowledgments: Lecture slides are from Computer networks course thought by Nick Feamster at
More informationECE 158A: Data Networks I. Fall 2015 Massimo Franceschetti
ECE 158A: Data Networks I Fall 2015 Massimo Franceschetti What is a Network? A system of links that interconnect nodes in order to exchange information A B We will focus on the INTERNET Where nodes are
More informationComponent Function Example
Network Components Component Names Component Function Example Application, or app, user Uses the network Skype, itunes, Amazon Host, or end-system, edge device, node, source, sink Router, or switch, node,
More informationPeer entities. Protocol Layering. Protocols. Example
Peer entities Protocol Layering An Engineering Approach to Computer Networking Customer A and B are peers Postal worker A and B are peers Protocols A protocol is a set of rules and formats that govern
More informationComputer Networks. Fall 2012 (M 6:15-9:00 in Jbarry 201B) Mirela Damian.
Computer Networks Fall 2012 (M 6:15-9:00 in Jbarry 201B) Mirela Damian http://www.csc.villanova.edu/~mdamian/csc8400.html/ Slides by Rexford @ Princeton & Slides accompanying the Internet Lab Manual, slightly
More informationConnectionless and Connection-Oriented Protocols OSI Layer 4 Common feature: Multiplexing Using. The Transmission Control Protocol (TCP)
Lecture (07) OSI layer 4 protocols TCP/UDP protocols By: Dr. Ahmed ElShafee ١ Dr. Ahmed ElShafee, ACU Fall2014, Computer Networks II Introduction Most data-link protocols notice errors then discard frames
More informationTransport and TCP. EE122 Fall 2011 Scott Shenker
Transport and TCP EE122 Fall 2011 Scott Shenker http://inst.eecs.berkeley.edu/~ee122/ Materials with thanks to Jennifer Rexford, Ion Stoica, Vern Paxson and other colleagues at Princeton and UC Berkeley
More informationGoals for Today s Class. EE 122: Networks & Protocols. What Global (non-digital) Communication Network Do You Use Every Day?
Goals for Today s Class EE 122: & Protocols Ion Stoica TAs: Junda Liu, DK Moon, David Zats http://inst.eecs.berkeley.edu/~ee122/fa09 (Materials with thanks to Vern Paxson, Jennifer Rexford, and colleagues
More informationIntroduction to computer networking
edge core Introduction to computer networking Comp Sci 3600 Security Outline edge core 1 2 edge 3 core 4 5 6 The edge core Outline edge core 1 2 edge 3 core 4 5 6 edge core Billions of connected computing
More informationLecture 3 Protocol Stacks and Layering
Lecture 3 Protocol Stacks and ing Hui Zhang School of Computer Science Carnegie Mellon University 15-441 Networking, Fall 2007 http://www.cs.cmu.edu/~srini/15-441/f07/ 1 What is a Communication Network?
More informationLecture 2: Links and Signaling
Lecture 2: Links and Signaling CSE 123: Computer Networks Alex C. Snoeren DISCUSSION @7pm Tomorrow Our Problem Communications is complicated Modulation and encoding bits Splitting sequences of bits into
More informationCS 43: Computer Networks The Link Layer. Kevin Webb Swarthmore College November 28, 2017
CS 43: Computer Networks The Link Layer Kevin Webb Swarthmore College November 28, 2017 TCP/IP Protocol Stack host host HTTP Application Layer HTTP TCP Transport Layer TCP router router IP IP Network Layer
More informationPage 1. Goals for Today" Why is Networking Important?" Example: Whatʼs in a Search Query?"
Goals for Today" CS162 Operating Systems and Systems Programming Lecture 16 Layering" April 1, 2013 Anthony D. Joseph http://inst.eecs.berkeley.edu/~cs162 Networking Concepts and Functionalities Properties
More informationParts of a Network. app. router. link. host. Computer Networks 2
Network Components Parts of a Network app host router link Computer Networks 2 Parts of a Network app host router link Computer Networks 3 Component Names Component Function Example Application, or app,
More informationHomework Assignment #1 Due 9/19 at 5:00pm EE122 Fall 2011
Homework Assignment #1 Due 9/19 at 5:00pm EE122 Fall 2011 Please submit your solutions using BSpace (https://bspace.berkeley.edu/). Log in to BSpace with your CalNet ID, click on the EL ENG 122 Fa11 tab,
More informationCSC 4900 Computer Networks: End-to-End Design
CSC 4900 Computer Networks: End-to-End Design Professor Henry Carter Fall 2017 Villanova University Department of Computing Sciences Review In the last two lectures, we discussed the fundamentals of networking
More information416 Distributed Systems. Networks review; Day 2 of 2 Fate sharing, e2e principle And start of RPC Jan 10, 2018
416 Distributed Systems Networks review; Day 2 of 2 Fate sharing, e2e principle And start of RPC Jan 10, 2018 1 Last Time Modularity, Layering, and Decomposition Example: UDP layered on top of IP to provide
More informationCS 43: Computer Networks The Network Layer. Kevin Webb Swarthmore College November 2, 2017
CS 43: Computer Networks The Network Layer Kevin Webb Swarthmore College November 2, 2017 TCP/IP Protocol Stack host host HTTP Application Layer HTTP TCP Transport Layer TCP router router IP IP Network
More informationWeb Mechanisms. Draft: 2/23/13 6:54 PM 2013 Christopher Vickery
Web Mechanisms Draft: 2/23/13 6:54 PM 2013 Christopher Vickery Introduction While it is perfectly possible to create web sites that work without knowing any of their underlying mechanisms, web developers
More informationAnnouncements. IP Forwarding & Transport Protocols. Goals of Today s Lecture. Are 32-bit Addresses Enough? Summary of IP Addressing.
IP Forwarding & Transport Protocols EE 122: Intro to Communication Networks Fall 2007 (WF 4-5:30 in Cory 277) Vern Paxson TAs: Lisa Fowler, Daniel Killebrew & Jorge Ortiz http://inst.eecs.berkeley.edu/~ee122/
More informationCS519: Computer Networks. Lecture 1 (part 2): Jan 28, 2004 Intro to Computer Networking
: Computer Networks Lecture 1 (part 2): Jan 28, 2004 Intro to Computer Networking Remember this picture? How did the switch know to forward some packets to B and some to D? From the address in the packet
More informationprecise rules that govern communication between two parties TCP/IP: the basic Internet protocols IP: Internet protocol (bottom level)
Protocols precise rules that govern communication between two parties TCP/IP: the basic Internet protocols IP: Internet protocol (bottom level) all packets shipped from network to network as IP packets
More informationDesign Principles : Fundamentals of Computer Networks Bill Nace
Design Principles 14-740: Fundamentals of Computer Networks Bill Nace Material from Computer Networking: A Top Down Approach, 6 th edition. J.F. Kurose and K.W. Ross Administrivia No Paper Review for today
More informationLecture (11) OSI layer 4 protocols TCP/UDP protocols
Lecture (11) OSI layer 4 protocols TCP/UDP protocols Dr. Ahmed M. ElShafee ١ Agenda Introduction Typical Features of OSI Layer 4 Connectionless and Connection Oriented Protocols OSI Layer 4 Common feature:
More informationCSC2209 Computer Networks
CSC2209 Computer Networks Network Architecture Stefan Saroiu Computer Science University of Toronto Outline Overview Protocols and layering Brief Internet tour E2E paper Internet design philosophy Protocols
More informationOperating Systems. 16. Networking. Paul Krzyzanowski. Rutgers University. Spring /6/ Paul Krzyzanowski
Operating Systems 16. Networking Paul Krzyzanowski Rutgers University Spring 2015 1 Local Area Network (LAN) LAN = communications network Small area (building, set of buildings) Same, sometimes shared,
More informationSwitching Networks (Fall 2010) EE 586 Communication and. August 27, Lecture 2. (modified by Cheung for EE586; based on K&R original) 1-1
EE 586 Communication and Switching Networks (Fall 2010) Lecture 2 August 27, 2010 (modified by Cheung for EE586; based on K&R original) 1-1 Announcements Read Chapter 1 First homework is due 9/3 In Blackboard
More informationPatrick Stuedi, Qin Yin, Timothy Roscoe Spring Semester 2015
Oriana Riva, Department of Computer Science ETH Zürich Advanced Computer Networks 263-3501-00 Principles Patrick Stuedi, Qin Yin, Timothy Roscoe Spring Semester 2015 Last time Course introduction Principles
More informationNetworking and Internetworking 1
Networking and Internetworking 1 Today l Networks and distributed systems l Internet architecture xkcd Networking issues for distributed systems Early networks were designed to meet relatively simple requirements
More informationNetwork Architecture
Unit 7 Network Architecture Acknowledgments: These slides were originally developed by Prof. Jean Walrand for EE122. The past and current EE122 instructors including Kevin Fall, Abhay Parekh, Shyam Parekh,
More informationMessage, Segment, Packet, and Frame Link-layer services Encoding, framing, error detection, transmission control Error correction and flow control
Links EE 122: Intro to Communication Networks Fall 2007 (WF 4-5:30 in Cory 277) Vern Paxson TAs: Lisa Fowler, Daniel Killebrew & Jorge Ortiz http://inst.eecs.berkeley.edu/~ee122/ Announcements Homework
More informationECE 4400:427/527 - Computer Networks Spring 2017
ECE 4400:427/527 - Computer Networks Spring 2017 Dr. Nghi Tran Department of Electrical & Computer Engineering Lecture 3: Network Architectures Dr. Nghi Tran (ECE-University of Akron) ECE 4400:427/527
More informationCS 640: Introduction to Computer Networks. Today s Lecture. Page 1
CS 640: Introduction to Computer Networks Aditya Akella Lecture 2 Layering, Protocol Stacks, and Standards 1 Today s Lecture Layers and Protocols A bit about s 2 Network Communication: Lots of Functions
More informationPart VI. Appendixes. Appendix A OSI Model and Internet Protocols Appendix B About the CD
Part VI Appendixes Appendix A OSI Model and Internet Protocols Appendix B About the CD OSI Model and Internet Protocols APPENDIX A In this appendix, you will Learn about the OSI model Review the network
More informationArchitectural Principles
Architectural Principles Brighten Godfrey cs598pbg August 31 2010 slides 2010 by Brighten Godfrey unless otherwise noted Today Clark: TCP / IP design philosophy Architectural principles Goals of the architecture
More informationClass Overview. CSE 123b Communications Software. Some hints. Some hints (2) Administrativa. Course material. Winter 2002
CSE 123b Communications Software Winter 2002 Lecture1: I ntroducti on & Re vi e w Stefan Savage Class Overview Course Material Class lectures, textbook readings, and handouts Course Assignments Homework
More informationCS 678 Spring 2013 Network Architecture and Principles
CS 678 Spring 2013 Network Architecture and Principles The Design Philosophy of the DARPA Internet Protocols, Dave Clarke, 1988 Ihsan Ayyub Qazi Computer Science Department LUMS SBASSE Slides use info
More informationHomework 1. Question 1 - Layering. CSCI 1680 Computer Networks Fonseca
CSCI 1680 Computer Networks Fonseca Homework 1 Due: 27 September 2012, 4pm Question 1 - Layering a. Why are networked systems layered? What are the advantages of layering? Are there any disadvantages?
More informationLayering in Networked computing. OSI Model TCP/IP Model Protocols at each layer
Layering in Networked computing OSI Model TCP/IP Model Protocols at each layer Learning outcomes Understand the need of layering in Networked computing Understand the OSI model and the tcp/ip model Understand
More informationCommunications Software. CSE 123b. CSE 123b. Spring Lecture 1: Introduction & Review. Stefan Savage.
CSE 123b CSE 123b Communications Software Spring 2003 Lecture 1: Introduction & Review Stefan Savage Stefan Savage savage@cs.ucsd.edu Class Overview Course Material Class lectures, textbook readings, and
More informationCE693: Adv. Computer Networking
CE693: Adv. Computer Networking L-2 Design Considerations Fall 1391 Acknowledgments: Lecture slides are from the graduate level Computer Networks course thought by Srinivasan Seshan at CMU. When slides
More informationNetwork Architecture. TOC Architecture
Network Architecture Introduction Layering Example Internet Layers First Look Layering Step by Step Downside of Layering Interconnecting Networks The Internet TOC Architecture Introduction Issues: Inter-operability
More informationComputer Communication & Networks / Data Communication & Computer Networks Week # 03
Computer Communication & Networks / Data Communication & Computer Networks Week # 03 M.Nadeem Akhtar CS & IT Department The University of Lahore Email: nadeem.akhtar@cs.uol.edu.pk URL-https://sites.google.com/site/nadeemuolcsccn/home
More informationChapter 2 Communicating Over the Network
Chapter 2 Communicating Over the Network Elements of Communication Communicating the Messages Continuous stream of bits 00101010100101010101010101010101010 I have to wait Single communications (e.g. video,
More informationDesign Considerations : Computer Networking. Outline
Design Considerations 15-744: Computer Networking L-2 Design Considerations How to determine split of functionality Across protocol layers Across network nodes Assigned Reading [SRC84] End-to-end Arguments
More informationInternet Architecture. CPS 214 (Nick Feamster) January 14, 2008
Internet Architecture CPS 214 (Nick Feamster) January 14, 2008 Today s Reading Design Philosophy of the DARPA Internet Protocols. Dave Clark, 1988. Conceptual Lessons Design principles/priorities were
More informationOperating Systems CS 571
Computer Networks: Overview Operating Systems CS 571 Network types Range Bandwidth (Mbps) Latency (ms) LAN 1-2 kms 10-1000 1-10 WAN worldwide 0.010-600 100-500 MAN 2-50 kms 1-150 10 Wireless LAN 0.15-1.5
More informationCMSC 322 Computer Networks Applications and End-To- End
CMSC 322 Computer Networks Applications and End-To- End Professor Doug Szajda CMSC 332: Computer Networks Announcements Project 2 has been posted and is due Monday, February 8 (No extension!) Homework
More informationModule 2 Overview of Computer Networks
Module 2 Overview of Computer Networks Networks and Communication Give me names of all employees Who earn more than $00,000 ISP intranet backbone satellite link desktop computer: server: network link:
More informationModule 2 Overview of. Computer Networks
Module Overview of Networks and Communication Give me names of all employees Who earn more than $00,000 ISP intranet backbone satellite link desktop computer: server: network link: CS454/654 - Issues How
More informationCS164 Final Exam Winter 2013
CS164 Final Exam Winter 2013 Name: Last 4 digits of Student ID: Problem 1. State whether each of the following statements is true or false. (Two points for each correct answer, 1 point for each incorrect
More informationIntroduction to Information Science and Technology 2017 Networking I. Sören Schwertfeger 师泽仁
I Sören Schwertfeger 师泽仁 Outline Internet History of the Internet Internet Structure Internet Protocols Network layer details 1. Physical Layer 2. Data Link Layer 3. Network Layer Internet: Huge network
More informationWeek 2 / Paper 1. The Design Philosophy of the DARPA Internet Protocols
Week 2 / Paper 1 The Design Philosophy of the DARPA Internet Protocols David D. Clark ACM CCR, Vol. 18, No. 4, August 1988 Main point Many papers describe how the Internet Protocols work But why do they
More informationCSC 4900 Computer Networks: Network Layer
CSC 4900 Computer Networks: Network Layer Professor Henry Carter Fall 2017 Villanova University Department of Computing Sciences Review What is AIMD? When do we use it? What is the steady state profile
More informationCOS 140: Foundations of Computer Science
COS 140: Foundations of C Networks Fall 2017 Copyright c 2002 2017 UMaine School of Computing and Information S 1 / 21 Homework, announcements New chapter (23) online No homework assigned today, sorry!
More informationL1: Introduction. Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806
L1: Introduction Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806 8/15/2016 CSCI 445 Fall 2016 1 Acknowledgements Some pictures used in this presentation
More informationNetworking Background
Networking Background CMSC 414 October 30, 2017 General Overview We are going to take a quick look at What a network protocol is The abstract design of the network The 7-Layer network stack Protocols We
More informationAssignment #1. Csci4211 Spring Due on Feb. 13th, Notes: There are five questions in this assignment. Each question has 10 points.
Assignment #1 Csci4211 Spring 2017 Due on Feb. 13th, 2017 Notes: There are five questions in this assignment. Each question has 10 points. 1. (10 pt.) Describe the special properties of the following transmission
More informationChapter -4 OSI Reference Model
Chapter -4 OSI Reference Model Objectives Concept of Reference Model. OSI Reference Model Concept. Layers of OSI Reference Model. 4.1 Introduction Layered Architecture, Peer-to- Peer Processes, Interfaces
More informationNetwork and Security: Introduction
Network and Security: Introduction Seungwon Shin KAIST Some slides are from Dr. Srinivasan Seshan Some slides are from Dr. Nick Mckeown Network Overview Computer Network Definition A computer network or
More informationCommunicating over the Network
Communicating over the Network Network Fundamentals Chapter 2 Version 4.0 1 Network Structure The elements of communication 3 common elements of communication Message source people/electronic devices need
More informationECE 158A: Lecture 7. Fall 2015
ECE 158A: Lecture 7 Fall 2015 Outline We have discussed IP shortest path routing Now we have a closer look at the IP addressing mechanism We are still at the networking layer, we will examine: IP Headers
More informationDesign Considerations : Computer Networking. Outline. Challenge 1: Address Formats. Challenge. How to determine split of functionality
Design Considerations 15-744: Computer Networking L-2 Design Considerations How to determine split of functionality Across protocol layers Across network nodes Assigned Reading [SRC84] End-to-end Arguments
More informationCE 443: Computer Networks
CE 443: Computer Networks Acknowledgments: Lecture slides are from Computer networks course thought by Jennifer Rexford at Princeton University. When slides are obtained from other sources, a a reference
More informationChapter 1. Computer Networks and the Internet
Chapter 1 Computer Networks and the Internet Internet traffic What s the Internet? (hardware) PC server wireless laptop cellular handheld wired links millions of connected computing devices: hosts = end
More informationNetworking Applications
Networking Dr. Ayman A. Abdel-Hamid College of Computing and Information Technology Arab Academy for Science & Technology and Maritime Transport 1 Outline Internet Layers Internet Data Packet transmission
More informationL6: OSI Reference Model
EECS 3213 Fall 2014 L6: OSI Reference Model Sebastian Magierowski York University 1 Outline The OSI Reference Model An organized way of thinking about network design (from low-level to high-level considerations)
More informationCS 43: Computer Networks. 08:Network Services and Distributed Systems 19 September
CS 43: Computer Networks 08:Network Services and Distributed Systems 19 September Reading Quiz Lecture 8 -Slide 2 Last class Inter-process communication using message passing How send and recv buffers
More information