Lecture 3: Systems Engineering III

1. Lecture 3: Systems Engineering III EEN 112: Introduction to Electrical and Computer Engineering Professor Eric Rozier, 2/6/2013

2. COMBINING GATORS, GRADES, AND BOOLEAN ALGEBRA/LOGIC

3. How can we formalize how we solve these problems? • Same rules as last time… • In Room I, if a grade is in the room, the sign will be true. If a gator is in the room, the sign will be false. • In Room II, the situation is the opposite.

4. The Grade and the GatorQ1 Room I Room II Both rooms contain grades. Both rooms contain grades.

5. The Grade and the GatorQ1 Room I Room II A

6. ASSESSMENT

7. Pop Quiz Today • Important notes • I will have this graded by Friday Morning • This quiz is correctable, up to full credit. • If you get an answer wrong, when I hand it back you can correct it and submit it for regrading. • Use this to help test how well prepared you are for the exam’s section on boolean algebra and logic gates.

8. NETWORKING

9. How do machines talk to each other? • TCP/IP – one of the main methods. • TCP – Transmission Control Protocol • IP – Internet Protocol • Also called the DoD model due to ARPANET

10. ARPANET • ARPANET – Advanced Research Projects Agency Network • Funded by ARPA and later DARPA • Connected research Universities and laboratories in the US

11. ARPANET • The world’s first “packet switching” network • Groups all transmitted data, regardless of content, type, or structure, into suitably sized blocks called “packets”. • Packets are then routed through the network • Circuit switching was the previous technology (like how corded phones used to work) • A limited number of dedicated point to point connections.

12. ARPANET • Packet Switching • Based on designs by Baran, Davies, and Roberts of Lincoln Laboratory • More robust than circuit switching

13. ARPANET • Packet Switching • Optimize utilization, link capacity • Minimize response times • Increase robustness

14. ARPANET 1971

15. ARPANET 1980

16. Internet Today • http://www.internet-map.net/

17. Anatomy of Internet Traffic Internet protocol suite Uses encapsulation to provide abstraction of protocols and services. Data is sent down the layers by an application. Layers near the top are logically closer to the application Layers near the bottom are logically closer to data transmission.

18. Anatomy of Internet Traffic

19. Anatomy of Internet Traffic • Application layer • Process to process • Same layer applications might use to talk on the same “host”. • Transport layer • Host to host • The way two applications on different hosts but the same router might use.

20. Anatomy of Internet Traffic • Internet layer • Used to exchange data across network boundaries • Host addressing and identification using IP addresses • Packet routing – how to get from source to destination

21. Anatomy of Internet Traffic

22. Anatomy of Internet Traffic • Link layer • Defines networking methods within the scope of a local area network on which hosts communicate without intervening routers, describes local topology. • MAC, VPNs, networking tunnels, etc

23. Internet Protocol • IP address • Numerical label assigned to each device participating in a network • Identifies – a name is what we are looking for • Addresses – Indication of where what we are looking for is

24. Internet Protocol

25. Internet Protocol • Each of the four numbers is a set of 8 bits, or an octet • Originally the were supposed to indicated network number (highest order octet), and host identifier with the rest

26. IP Address Problem • How many IP addresses are possible with 32 bits? • About 4.294 billion addresses • First exhaustion of a pool happened on Jan, 31, 2011. • Next pool exhaustion happened on April 15, 2011. • Only a few years until total exhaustion.

27. IPv6 • 32-bit examples are IPv4 • IPv6 has 128 bits, or 16 octets • How many more? • 3.403 * 10^38

28. How do I get from a name to an address? • First we contact a name server • Our router or gateway will have the information needed to contact a domain name server • They contain DNS records, such as: • A records - address records • NS records – name servers • MX records – mail exchange • etc

29. Domain Name Servers • Domain names are divided up into zones • TLDs – top level domains • .com, .net, .org, .edu, .us, .uk, etc • Divide up their space into second level domains • Hierarchical

30. Domain Name Servers • en.wikipedia.org • First we get a referral to .org’s TLD name server • TLD server for .org then tells us who to contact about wikipedia.org • This server will then tell us how to contact en.wikipedia.org • In this case we are first told to chat with text.wikipedia.org which then gives us text.esams.wikipedia.org

31. Domain Name Servers • Final resolution is a CNAME record, or canonical name, which will lead to an A record, or address

32. How this ends up working • Imagine addressing a person in our class • TLD might be UM • Next level might be Stanford • Next level might be 105 • Finally, student X • X.105.stanford.um • Address could be your position in the desks, and latitude and longitude.

33. Important note • People aren’t telling us the route, just who to talk to in order to get the address • Robust! We can lose nodes in the route • Usually have many people to talk to in order to get an address

34. WRAP UP

35. Upcoming Items of Interest • No lab next week • Midterm I on Wednesday 2/13 • Boolean Algebra • Logic Gates • Networking