Please take out the homework - viewing sheet fro the movie

Slides:



Advertisements
Similar presentations
The Internet.
Advertisements

Jaringan Komputer Dasar Network Layer dan IP (1) Aurelio Rahmadian.
Introduction to TCP/IP TCP / IP –including 2 protocols Protocol : = a set of rules that govern the communication between different devices Protocol : =
IS333, Ch. 26: TCP Victor Norman Calvin College 1.
Chapter 3 CCNA Discovery Encapsulation - Explanations and Clarifications CCNA Discovery Encapsulation - Explanations and Clarifications.
Protocols. Basics Defining Interactions VERTICAL Application Presentation Session Transport Network Data Link Physical Please do this for me OK It’s.
CS335 Networking & Network Administration Tuesday, May 11, 2010.
Vocabulary URL = uniform resource locator: web address protocol –set of rules that networked computers follow in order to share data and coordinate communications.
The internet and the WWW
Syllabus outcomes Describes and applies problem-solving processes when creating solutions Designs, produces and evaluates appropriate solutions.
Computer Networks.  The OSI model is a framework containing seven layers that defines the protocols and devices used at each stage of the process when.
IP Tutorial 1. 2 An IP address is a unique number used to identify your computer on the internet. Every system has it’s own unique IP address. IP addresses.
More on TCP Acknowledgements Sequence Number Field Initial Sequence Number Acknowledgement Number Field.
Network Protocols and Standards (Part 2). The OSI Model In 1984, the International Organization for Standardization (ISO) defined a standard, or set of.
UNIT 2 LESSON 5 CS PRINCIPLES. OBJECTIVES Students will be able to: Explain why protocols are necessary to overcome the underlying unreliability of the.
UNIT 2 LESSON 4 CS PRINCIPLES. OBJECTIVES Students will be able to: Describe the redundancy of routing between two points on the Internet. Send messages.
Firewalls A brief introduction to firewalls. What does a Firewall do? Firewalls are essential tools in managing and controlling network traffic Firewalls.
Networks, Part 2 March 7, Networks End to End Layer  Build upon unreliable Network Layer  As needed, compensate for latency, ordering, data.
AP CSP: Sending Binary Messages
Chapter 9 Introduction To Data-Link Layer 9.# 1
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
Routers and Redundancy
Safer Internet Day.
Day 8- The Need for Addressing
AP CSP: The Need for Addressing
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
AP CSP: Sending Binary Messages with the Internet Simulator
How is all that data traffic controlled on the Internet?
THE NEED FOR DNS DOMAIN NAME SYSTEM
HTTP and Abstraction on the Internet
Code.org Lessons 11 & 12 Lesson 11- Packets and Making a Reliable Internet Lesson 12- The Need for DNS.
ROUTERS AND REDUNDANCY
Day 10- The Need for Addressing
Routers and Redundancy
THE NEED FOR ADDRESSING
Packets & Routing Lower OSI layers (1-3) concerned with packets and the network Packets carry data independently through the network, and into other networks…
Lesson 2-9 AP Computer Science Principles
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
Packets and Making a Reliable Internet
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
Vocabulary Prototype: A preliminary sketch of an idea or model for something new. It’s the original drawing from which something real might be built or.
Introducing To Networking
Lesson 2-9 AP Computer Science Principles
Byungchul Park ICMP & ICMPv DPNM Lab. Byungchul Park
AP CSP: Making a reliable Internet & DNS
Unit 1.4 Wired and Wireless Networks Lesson 2
Unit Network Topologies, protocols and layers Lesson 3
Computer Networks Lesson 3.
Packet Sniffing.
Sarah Diesburg Operating Systems COP 4610
Dr. John P. Abraham Professor UTPA
Digital Citizenship and You.
Modelling the internet
Dr. John P. Abraham Professor UTRGV, EDINBURG, TX
Modelling the internet
Dr. John P. Abraham Professor UTPA
CS4470 Computer Networking Protocols
Dr. John P. Abraham Professor UTPA
Computer communications
Dr. John P. Abraham Professor UTPA
Here are some good questions to start out the presentation:
Andy Wang Operating Systems COP 4610 / CGS 5765
Net 323 D: Networks Protocols
Code.org Lessons 11 & 12 Lesson 11- Packets and Making a Reliable Internet Lesson 12- The Need for DNS.
CSE 313 Data Communication
How Our Customers Communicate With Us
Computer Networks Lesson 3.
Code.org Lessons 11 & 12 Lesson 11- Packets and Making a Reliable Internet Lesson 12- The Need for DNS.
Example 9 (Continued) 1. The first mask (/26) is applied to the destination address. The result is , which does not match the corresponding network.
Presentation transcript:

Please take out the homework - viewing sheet fro the movie

Lesson 11: Packets and Making a Reliable Internet Unit One Lesson 11

Your friend sent you a message on the Internet, but you never received it. Based on what you already know about routers and the physical Internet, list what reasons might explain this fact. Wires are cut Interference on a radio channel Router malfunctions or cannot keep up with traffic being directed to it

activity simulates issues of packets traveling on the internet with a paper-passing activity: Make a simple drawing, or write a handwritten message on a piece of paper. “You have just made a message that you are going to send to someone else on the other side of the room.  However, we’re going to imagine that it’s too big to send all at once.  So tear it into a few pieces (4 is fine)” Look across the room to find a partner - they can point at or make eye contact with someone.  (Students in the middle should find partners who aren’t at the middle table) Once each student has a partner, tell your partner your IP address. Students should write their partner’s IP address on each piece of paper that makes up their drawing, clearly indicating that it is going to that address.  For example “To: 4.2”. Lets play!

Rules: Goal: You are going to try to send your drawing to your partner across the room, and also to receive and re-construct your partner’s drawing. No moving - You may not move from your current position. Only one piece at a time - You may hand one (and only one) piece of paper at a time to any person who is within arm’s reach. You can’t pass a handful of paper to anyone. Forward messages to destination - If you receive a piece of paper that is not for you, you should hand it to someone who can get it closer to its intended destination. Collect all your pieces and reconstruct the drawing - You are looking for pieces of paper with your address on it, and once you have them all to reconstruct the drawing your partner sent you. Start and stop on my command - When I say “GO” everyone start passing pieces of paper.  And stop when I call “STOP”

The good the bad and the ugly? What worked? What didn’t? How could you write this protocol better?

Video: The Internet: Packets, Routing, and Reliability https://www.youtube.com/watch?v=AYdF7b3nMto&feature=you tu.be Video: The Internet: Packets, Routing, and Reliability

Develop a Protocol that will allow you to overcome the unreliability of the network so that a message can be sent and both sender and receiver can be confident the full message was received. What to Look For In student solutions, you should primarily be looking for: Some way to confirm receipt of a packet / message Some way to define the ordering of packets

Then you would send back a message like: A Simple Solution Sender: The simplest solution is to develop something akin to TCP, in which you use part of the message to indicate the the packet number and how many there are total. For example: Message 1: 1/4 Hi Message 2: 2/4 Th Message 3: 3/4 er Meesage 4: 4/4 e! Receiver: should know how many messages there are and can request a re-send of any that are missing. For example if you received messages 1, 2 and 4. You could send a message back, something like one of these: req: 3 or need 3 or send 3 The way the real TCP works is this: every once in a while TCP sends back a “cumulative acknowledgement” of how many in-order packets it has received. For example, in an 8-packet message if you received packets: 1 2 _ 4 5 6 _ 8 Then you would send back a message like: ack 2 or maybe ack 3 This would indicate to the sender that next packet you need is packet 3. The sender would send 3, and once you got it, your next message would be: ack 6 or ack 7 Because you received packets 4, 5 and 6 already.

The challenges we encountered in today’s activity very closely mirror those that exist on the actual Internet. The response was the development of a protocol called the Transmission Control Protocol, or more simply, TCP. TCP divides larger messages into smaller packets which have ordering information added to their header. When a packet arrives at a destination computer, an acknowledgement is sent to the sender, letting them know they don’t need to resend that packet. Once all the packets have arrived, the ordering information in the headers of the packets allows them to be reordered to create the original message.

Code.org – answer the questions