Presentation is loading. Please wait.

Presentation is loading. Please wait.

5: DataLink Layer5-1 Virtualization of networks Virtualization of resources: powerful abstraction in systems engineering: r computing examples: virtual.

Published byVictor Cook Modified over 8 years ago

Similar presentations

Presentation on theme: "5: DataLink Layer5-1 Virtualization of networks Virtualization of resources: powerful abstraction in systems engineering: r computing examples: virtual."— Presentation transcript:

1 5: DataLink Layer5-1 Virtualization of networks Virtualization of resources: powerful abstraction in systems engineering: r computing examples: virtual memory, virtual devices m Virtual machines: e.g., java m IBM VM os from 1960’s/70’s r layering of abstractions: don’t sweat the details of the lower layer, only deal with lower layers abstractly

2 5: DataLink Layer5-2 The Internet: virtualizing networks 1974: multiple unconnected nets m ARPAnet m data-over-cable networks m packet satellite network (Aloha) m packet radio network … differing in: m addressing conventions m packet formats m error recovery m routing ARPAnet satellite net "A Protocol for Packet Network Intercommunication", V. Cerf, R. Kahn, IEEE Transactions on Communications, May, 1974, pp. 637-648.

3 5: DataLink Layer5-3 The Internet: virtualizing networks ARPAnet satellite net gateway Internetwork layer (IP): r addressing: internetwork appears as single, uniform entity, despite underlying local network heterogeneity r network of networks Gateway: r “embed internetwork packets in local packet format or extract them” r route (at internetwork level) to next gateway

4 5: DataLink Layer5-4 Cerf & Kahn’s Internetwork Architecture What is virtualized? r two layers of addressing: internetwork and local network r new layer (IP) makes everything homogeneous at internetwork layer r underlying local network technology m cable m satellite m 56K telephone modem m today: ATM, MPLS … “invisible” at internetwork layer. Looks like a link layer technology to IP!

5 5: DataLink Layer5-5 ATM and MPLS r ATM, MPLS separate networks in their own right m different service models, addressing, routing from Internet r viewed by Internet as logical link connecting IP routers m just like dialup link is really part of separate network (telephone network) r ATM, MPLS: of technical interest in their own right

6 5: DataLink Layer5-6 Multiprotocol label switching (MPLS) r initial goal: speed up IP forwarding by using fixed length label (instead of IP address) to do forwarding m borrowing ideas from Virtual Circuit (VC) approach m but IP datagram still keeps IP address! PPP or Ethernet header IP header remainder of link-layer frame MPLS header label Exp S TTL 20 3 1 5

7 5: DataLink Layer5-7 MPLS capable routers r a.k.a. label-switched router r forwards packets to outgoing interface based only on label value (don’t inspect IP address) m MPLS forwarding table distinct from IP forwarding tables r signaling protocol needed to set up forwarding m RSVP-TE m forwarding possible along paths that IP alone would not allow (e.g., source-specific routing) !! m use MPLS for traffic engineering r must co-exist with IP-only routers

8 5: DataLink Layer5-8 R1 R2 D R3 R4 R5 0 1 0 0 A R6 in out out label label dest interface 6 - A 0 in out out label label dest interface 10 6 A 1 12 9 D 0 in out out label label dest interface 10 A 0 12 D 0 1 in out out label label dest interface 8 6 A 0 0 8 A 1 MPLS forwarding tables

9 5: DataLink Layer5-9 Synthesis: a day in the life of a web request r journey down protocol stack complete! m application, transport, network, link r putting-it-all-together: synthesis! m goal: identify, review, understand protocols (at all layers) involved in seemingly simple scenario: requesting www page m scenario: student attaches laptop to campus network, requests/receives www.google.com

10 5: DataLink Layer5-10 A day in the life: scenario Comcast network 68.80.0.0/13 Google’s network 64.233.160.0/19 64.233.169.105 web server DNS server school network 68.80.2.0/24 browser web page

11 5: DataLink Layer5-11 A day in the life… connecting to the Internet r connecting laptop needs to get its own IP address, addr of first-hop router, addr of DNS server: use DHCP router (runs DHCP) DHCP UDP IP Eth Phy DHCP UDP IP Eth Phy DHCP r DHCP request encapsulated in UDP, encapsulated in IP, encapsulated in 802.1 Ethernet r Ethernet frame broadcast (dest: FFFFFFFFFFFF ) on LAN, received at router running DHCP server r Ethernet demux’ed to IP demux’ed, UDP demux’ed to DHCP

12 5: DataLink Layer5-12 A day in the life… connecting to the Internet r DHCP server formulates DHCP ACK containing client’s IP address, IP address of first-hop router for client, name & IP address of DNS server router (runs DHCP) DHCP UDP IP Eth Phy DHCP UDP IP Eth Phy DHCP r encapsulation at DHCP server, frame forwarded (switch learning) through LAN, demultiplexing at client Client now has IP address, knows name & addr of DNS server, IP address of its first-hop router r DHCP client receives DHCP ACK reply

13 5: DataLink Layer5-13 A day in the life… ARP (before DNS, before HTTP) r before sending HTTP request, need IP address of www.google.com: DNS DNS UDP IP Eth Phy DNS r DNS query created, encapsulated in UDP, encapsulated in IP, encasulated in Eth. In order to send frame to router, need MAC address of router interface: ARP r ARP query broadcast, received by router, which replies with ARP reply giving MAC address of router interface r client now knows MAC address of first hop router, so can now send frame containing DNS query ARP query Eth Phy ARP ARP reply

14 5: DataLink Layer5-14 A day in the life… using DNS DNS UDP IP Eth Phy DNS r IP datagram containing DNS query forwarded via LAN switch from client to 1 st hop router r IP datagram forwarded from campus network into comcast network, routed (tables created by RIP, OSPF, IS-IS and/or BGP routing protocols) to DNS server r demux’ed to DNS server r DNS server replies to client with IP address of www.google.com Comcast network 68.80.0.0/13 DNS server DNS UDP IP Eth Phy DNS

15 5: DataLink Layer5-15 A day in the life… TCP connection carrying HTTP HTTP TCP IP Eth Phy HTTP r to send HTTP request, client first opens TCP socket to web server r TCP SYN segment (step 1 in 3-way handshake) inter- domain routed to web server r TCP connection established! 64.233.169.105 web server SYN TCP IP Eth Phy SYN SYNACK r web server responds with TCP SYNACK (step 2 in 3- way handshake)

16 5: DataLink Layer5-16 A day in the life… HTTP request/reply HTTP TCP IP Eth Phy HTTP r HTTP request sent into TCP socket r IP datagram containing HTTP request routed to www.google.com r IP datgram containing HTTP reply routed back to client 64.233.169.105 web server HTTP TCP IP Eth Phy r web server responds with HTTP reply (containing web page) HTTP r web page finally (!!!) displayed

Download ppt "5: DataLink Layer5-1 Virtualization of networks Virtualization of resources: powerful abstraction in systems engineering: r computing examples: virtual."

Similar presentations

3-1 Design Principles Goals: r identify, study common architectural components, protocol mechanisms r what approaches do we find in network architectures?

3-1 Design Principles Goals: r identify, study common architectural components, protocol mechanisms r what approaches do we find in network architectures?
Everything.

Everything.
5: DataLink Layer5-1 Chapter 5 Link Layer and LANs A note on the use of these ppt slides: Were making these slides freely available to all (faculty, students,

5: DataLink Layer5-1 Chapter 5 Link Layer and LANs A note on the use of these ppt slides: Were making these slides freely available to all (faculty, students,
11-1 Last time □ Distance vector link cost changes ♦ Count-to-infinity, poisoned reverse □ Hierarchical routing ♦ Autonomous Systems ♦ Inter-AS, Intra-AS.

11-1 Last time □ Distance vector link cost changes ♦ Count-to-infinity, poisoned reverse □ Hierarchical routing ♦ Autonomous Systems ♦ Inter-AS, Intra-AS.
Chapter 5 Link Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 A note on the use of these.

Chapter 5 Link Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 A note on the use of these.
A Complete End-to-End View. Laptop Wifi AP BERKELEY DHCP Server/ Gateway Router DNS Server (9.9.9.9) www.google.com AT&T GOOGLE.

A Complete End-to-End View. Laptop Wifi AP BERKELEY DHCP Server/ Gateway Router DNS Server ( ) AT&T GOOGLE.
Review of Important Networking Concepts

Review of Important Networking Concepts
Network Layer 4-1 4.1 introduction 4.2 virtual circuit and datagram networks 4.3 what’s inside a router 4.4 IP: Internet Protocol  datagram format  IPv4.

Network Layer introduction 4.2 virtual circuit and datagram networks 4.3 what’s inside a router 4.4 IP: Internet Protocol  datagram format  IPv4.
1 School of Computing Science Simon Fraser University CMPT 771/471: Internet Architecture and Protocols Link Layer Instructor: Dr. Mohamed Hefeeda.

1 School of Computing Science Simon Fraser University CMPT 771/471: Internet Architecture and Protocols Link Layer Instructor: Dr. Mohamed Hefeeda.
5: DataLink Layer5-1 Cerf & Kahn’s Internetwork Architecture What is virtualized? r two layers of addressing: internetwork and local network r new layer.

5: DataLink Layer5-1 Cerf & Kahn’s Internetwork Architecture What is virtualized? r two layers of addressing: internetwork and local network r new layer.
Link Layer & Physical Layer CPE 400 / 600 Computer Communication Networks Lecture 24.

Link Layer & Physical Layer CPE 400 / 600 Computer Communication Networks Lecture 24.
1 ATM and MPLS ECS 152A. 2 Virtualization of networks Virtualization of resources: a powerful abstraction in systems engineering: r computing examples:

1 ATM and MPLS ECS 152A. 2 Virtualization of networks Virtualization of resources: a powerful abstraction in systems engineering: r computing examples:
5: DataLink Layer5-1 Chapter 5b Link Layer and LANs (for reference only) Computer Networking: A Top Down Approach 5 th edition. Jim Kurose, Keith Ross.

5: DataLink Layer5-1 Chapter 5b Link Layer and LANs (for reference only) Computer Networking: A Top Down Approach 5 th edition. Jim Kurose, Keith Ross.
Everything. MACIP End-host IP: 10.1.2.3 MAC: 11:11:11:11:11 gateway IP: 10.1.2.1 MAC: 22:22:22:22:22 Google server IP: 201.1.2.3 MACIP MACInterfaceMACInterface.

Everything. MACIP End-host IP: MAC: 11:11:11:11:11 gateway IP: MAC: 22:22:22:22:22 Google server IP: MACIP MACInterfaceMACInterface.
PPP, ATM, MPLS EECS 489 Computer Networks Z. Morley Mao Monday March 12, 2007 Acknowledgement: Some slides.

PPP, ATM, MPLS EECS 489 Computer Networks Z. Morley Mao Monday March 12, 2007 Acknowledgement: Some slides.
CS 5565 Network Architecture and Protocols Godmar Back Lecture 25.

CS 5565 Network Architecture and Protocols Godmar Back Lecture 25.
Lecture 8 Modeling & Simulation of Communication Networks.

Lecture 8 Modeling & Simulation of Communication Networks.
Chapter 5 Link Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Link Layer5-1 5.6 data center.

Chapter 5 Link Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012 Link Layer data center.
Chapter 5 Link Layer and LANs

Chapter 5 Link Layer and LANs
CP476 Internet ComputingCh.1 # 1 Lecture 2. A Brief Introduction to the Internet The objective is to understand The history of Internet What the Internet.

CP476 Internet ComputingCh.1 # 1 Lecture 2. A Brief Introduction to the Internet The objective is to understand The history of Internet What the Internet.

Similar presentations

Ads by Google