computer organizational architecture lecture 14 william starliin
Download as PPT, PDF0 likes63 views
This document discusses the network layer and key concepts such as virtual circuits, datagrams, forwarding, and routing. It describes the differences between virtual circuit and datagram networks, and how routers work by examining packet headers to forward datagrams using routing algorithms and forwarding tables. The goals of the network layer are to transport segments between hosts using network layer protocols in hosts and routers.
computer organizational architecture lecture 14 william starliin
- 1. Chapter 4 Network Layer slides are modified from J. Kurose & K. Ross CPE 400 / 600 Computer Communication Networks Lecture 14
- 2. Network Layer 2 Chapter 4: Network Layer Chapter goals: understand principles behind network layer services: network layer service models forwarding versus routing how a router works routing (path selection) dealing with scale advanced topics: IPv6, mobility instantiation, implementation in the Internet
- 3. Network Layer 3 Chapter 4: Network Layer 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 addressing, ICMP, IPv6 4.5 Routing algorithms Link state, Distance Vector, Hierarchical routing 4.6 Routing in the Internet RIP, OSPF, BGP 4.7 Broadcast and multicast routing
- 4. Network Layer 4 Network layer transport segment from sending to receiving host network layer protocols in every host, router on sending side encapsulates segments into datagrams on rcving side, delivers segments to transport layer router examines header fields in all IP datagrams passing through it application transport network data link physical application transport network data link physical network data link physical network data link physical network data link physical network data link physical network data link physical network data link physical network data link physical network data link physical network data link physical network data link physicalnetwork data link physical
- 5. Network Layer 5 Two Key Network-Layer Functions forwarding: move packets from router’s input to appropriate router output routing: determine route taken by packets from source to dest. routing algorithms analogy: routing: process of planning trip from source to dest forwarding: process of getting through single interchange
- 6. Network Layer 6 1 23 0111 value in arriving packet’s header routing algorithm local forwarding table header value output link 0100 0101 0111 1001 3 2 2 1 Interplay between routing and forwarding
- 7. Network Layer 7 Connection setup 3rd important function in some network architectures: ATM, frame relay, X.25 before datagrams flow, two end hosts and intervening routers establish virtual connection routers get involved network vs transport layer connection service: network: between two hosts (may also involve intervening routers in case of VCs) transport: between two processes
- 8. Network Layer 8 Network service model Q: What service model for “channel” transporting datagrams from sender to receiver? Example services for individual datagrams: guaranteed delivery guaranteed delivery with less than 40 msec delay Example services for a flow of datagrams: in-order datagram delivery guaranteed minimum bandwidth to flow restrictions on changes in inter-packet spacing
- 9. Network Layer 9 Network layer service models: Network Architecture Internet ATM ATM ATM ATM Service Model best effort CBR VBR ABR UBR Bandwidth none constant rate guaranteed rate guaranteed minimum none Loss no yes yes no no Order no yes yes yes yes Timing no yes yes no no Congestion feedback no (inferred via loss) no congestion no congestion yes no Guarantees ?
- 10. Network Layer 10 Lecture 14: Outline 4. 1 Introduction 4.2 Virtual circuit and datagram networks 4.3 What’s inside a router
- 11. Network Layer 11 Network layer connection and connection-less service datagram network provides network-layer connectionless service VC network provides network-layer connection service analogous to the transport-layer services, but: service: host-to-host no choice: network provides one or the other implementation: in network core
- 12. Network Layer 12 Virtual circuits call setup, teardown for each call before data can flow each packet carries VC identifier not destination host address every router on source-dest path maintains “state” for each passing connection link, router resources (bandwidth, buffers) may be allocated to VC dedicated resources = predictable service “source-to-dest path behaves much like telephone circuit” performance-wise network actions along source-to-dest path
- 13. Network Layer 13 VC implementation a VC consists of: 1. path from source to destination 2. VC numbers, one number for each link along path 3. entries in forwarding tables in routers along path packet belonging to VC carries VC number (rather than dest address) VC number can be changed on each link. New VC number comes from forwarding table
- 14. Network Layer 14 Forwarding table 12 22 32 1 2 3 VC number interface number Incoming interface Incoming VC # Outgoing interface Outgoing VC # 1 12 3 22 2 63 1 18 3 7 2 17 1 97 3 87 … … … … Forwarding table in northwest router: Routers maintain connection state information!
- 15. Network Layer 15 Virtual circuits: signaling protocols used to setup, maintain teardown VC used in ATM, frame-relay, X.25 not used in today’s Internet application transport network data link physical application transport network data link physical 1. Initiate call 2. incoming call 3. Accept call4. Call connected 5. Data flow begins 6. Receive data
- 16. Network Layer 16 Datagram networks no call setup at network layer routers: no state about end-to-end connections no network-level concept of “connection” packets forwarded using destination host address packets between same source-dest pair may take different paths application transport network data link physical application transport network data link physical 1. Send data 2. Receive data
- 17. Network Layer 17 Forwarding table Destination Address Range Link Interface 11001000 00010111 00010000 00000000 through 0 11001000 00010111 00010111 11111111 11001000 00010111 00011000 00000000 through 1 11001000 00010111 00011000 11111111 11001000 00010111 00011001 00000000 through 2 11001000 00010111 00011111 11111111 otherwise 34 billion possible entries
- 18. Network Layer 18 Longest prefix matching Prefix Match Link Interface 11001000 00010111 00010 0 11001000 00010111 00011000 1 11001000 00010111 00011 2 otherwise 3 DA: 11001000 00010111 00011000 10101010 Examples DA: 11001000 00010111 00010110 10100001 Which interface? Which interface?
- 19. Network Layer 19 Datagram or VC network: why? Internet (datagram) data exchange among computers “elastic” service, no strict timing req. “smart” end systems (computers) can adapt, perform control, error recovery simple inside network, complexity at “edge” many link types different characteristics uniform service difficult ATM (VC) evolved from telephony human conversation: strict timing, reliability requirements need for guaranteed service “dumb” end systems telephones complexity inside network
- 20. Network Layer 20 Lecture 14: Outline 4. 1 Introduction 4.2 Virtual circuit and datagram networks 4.3 What’s inside a router
- 21. Network Layer 21 Router Architecture Overview Two key router functions: run routing algorithms/protocol (RIP, OSPF, BGP) forwarding datagrams from incoming to outgoing link
- 22. Network Layer 22 Input Port Functions Decentralized switching: given datagram dest., lookup output port using forwarding table in input port memory goal: complete input port processing at ‘line speed’ queuing: if datagrams arrive faster than forwarding rate into switch fabric Physical layer: bit-level reception Data link layer: e.g., Ethernet
- 23. Network Layer 23 Three types of switching fabrics
- 24. Network Layer 24 Lecture 14: Summary Network layer Datagrams Forwarding Routing Connection Setup Service models Virtual circuits Connection service Signaling protocols Datagram networks Connectionless service Longest prefix match Router Architectures