1. 5: DataLink Layer5-1 VLANs

2. 5: DataLink Layer5-2 Introduction r Need to have different broadcast domains on the same physical network r E.g. Consider a University Campus

3. 5: DataLink Layer5-3 Port Based VLANs r Different Ports on a switch on different VLANs

4. 5: DataLink Layer5-4 VLAN Tagging

5. 5: DataLink Layer5-5 r What if want to extend this concept across a whole campus?

6. 5: DataLink Layer5-6 VLAN Tagging r Enable Ethernet frames to be tagged r VLAN capable switches keep tables of VLANs and ports that are interested in them r Ports can be marked as sending untagged frames,tagged frames or both

7. 5: DataLink Layer5-7 Virtualization of networks Virtualization of resources: a 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

8. 5: DataLink Layer5-8 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, MPSL: of technical interest in their own right

9. 5: DataLink Layer5-9 Asynchronous Transfer Mode: ATM r 1990’s/00 standard for high-speed (155Mbps to 622 Mbps and higher) Broadband Integrated Service Digital Network architecture r Goal: integrated, end-end transport of carry voice, video, data m meeting timing/QoS requirements of voice, video (versus Internet best-effort model) m “next generation” telephony: technical roots in telephone world m packet-switching (fixed length packets, called “cells”) using virtual circuits

10. 5: DataLink Layer5-10 ATM architecture r adaptation layer: only at edge of ATM network m data segmentation/reassembly m roughly analagous to Internet transport layer r ATM layer: “network” layer m cell switching, routing r physical layer

11. 5: DataLink Layer5-11 ATM: network or link layer? Vision: end-to-end transport: “ATM from desktop to desktop” m ATM is a network technology Reality: used to connect IP backbone routers m “IP over ATM” m ATM as switched link layer, connecting IP routers ATM network IP network

12. 5: DataLink Layer5-12 ATM Adaptation Layer (AAL) r ATM Adaptation Layer (AAL): “adapts” upper layers (IP or native ATM applications) to ATM layer below r AAL present only in end systems, not in switches r AAL layer segment (header/trailer fields, data) fragmented across multiple ATM cells m analogy: TCP segment in many IP packets

13. 5: DataLink Layer5-13 ATM Adaptation Layer (AAL) [more] Different versions of AAL layers, depending on ATM service class: r AAL1: for CBR (Constant Bit Rate) services, e.g. circuit emulation r AAL2: for VBR (Variable Bit Rate) services, e.g., MPEG video r AAL5: for data (eg, IP datagrams) AAL PDU ATM cell User data

14. 5: DataLink Layer5-14 ATM Layer Service: transport cells across ATM network r analogous to IP network layer r very different services than IP network layer Network Architecture Internet ATM Service Model best effort CBR VBR ABR UBR Bandwidth none constant rate guaranteed rate guaranteed minimum none Loss no yes no Order no yes Timing no yes no Congestion feedback no (inferred via loss) no congestion no congestion yes no Guarantees ?

15. 5: DataLink Layer5-15 ATM Layer: Virtual Circuits r VC transport: cells carried on VC from source to dest m call setup, teardown for each call before data can flow m each packet carries VC identifier (not destination ID) m every switch on source-dest path maintain “state” for each passing connection m link,switch resources (bandwidth, buffers) may be allocated to VC: to get circuit-like perf. r Permanent VCs (PVCs) m long lasting connections m typically: “permanent” route between to IP routers r Switched VCs (SVC): m dynamically set up on per-call basis

16. 5: DataLink Layer5-16 ATM VCs r Advantages of ATM VC approach: m QoS performance guarantee for connection mapped to VC (bandwidth, delay, delay jitter) r Drawbacks of ATM VC approach: m Inefficient support of datagram traffic m one PVC between each source/dest pair) does not scale (N*2 connections needed) m SVC introduces call setup latency, processing overhead for short lived connections

17. 5: DataLink Layer5-17 ATM Layer: ATM cell r 5-byte ATM cell header r 48-byte payload m Why?: small payload -> short cell-creation delay for digitized voice m halfway between 32 and 64 (compromise!) Cell header Cell format

18. 5: DataLink Layer5-18 ATM cell header r VCI: virtual channel ID m will change from link to link thru net r PT: Payload type (e.g. RM cell versus data cell) r CLP: Cell Loss Priority bit m CLP = 1 implies low priority cell, can be discarded if congestion r HEC: Header Error Checksum m cyclic redundancy check

19. 5: DataLink Layer5-19 ATM Physical Layer (more) Two pieces (sublayers) of physical layer: r Transmission Convergence Sublayer (TCS): adapts ATM layer above to PMD sublayer below r Physical Medium Dependent: depends on physical medium being used TCS Functions: m Header checksum generation: 8 bits CRC m Cell delineation m With “unstructured” PMD sublayer, transmission of idle cells when no data cells to send

20. 5: DataLink Layer5-20 ATM Physical Layer Physical Medium Dependent (PMD) sublayer r SONET/SDH: transmission frame structure (like a container carrying bits); m bit synchronization; m bandwidth partitions (TDM); m several speeds: OC3 = 155.52 Mbps; OC12 = 622.08 Mbps; OC48 = 2.45 Gbps, OC192 = 9.6 Gbps r TI/T3: transmission frame structure (old telephone hierarchy): 1.5 Mbps/ 45 Mbps r unstructured: just cells (busy/idle)

21. 5: DataLink Layer5-21 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

22. 5: DataLink Layer5-22 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

23. 5: DataLink Layer5-23 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

24. 5: DataLink Layer5-24 Chapter 5: Summary r principles behind data link layer services: m error detection, correction m sharing a broadcast channel: multiple access m link layer addressing r instantiation and implementation of various link layer technologies m Ethernet m switched LANS m PPP m virtualized networks as a link layer: ATM, MPLS