ittc © james p.g. sterbenz introduction to communication ...jpgs/courses/intronets/... · 30...
TRANSCRIPT
© James P.G. SterbenzITTC
30 October 2018 © 2004–2018 James P.G. Sterbenzrev. 18
Introduction to Communication NetworksThe University of Kansas EECS 563
Link Layer and LANs
James P.G. Sterbenz
Department of Electrical Engineering & Computer Science
Information Technology & Telecommunications Research Center
The University of Kansas
http://www.ittc.ku.edu/~jpgs/courses/intronets
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-2
Link Layer and LANsOutline
LL.1 Link layer functions and services
LL.2 Framing and delineation
LL.3 LAN types and topologies
LL.4 Multiplexing and switching
LL.5 Per-hop error and flow control
LL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
LL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-3
Link LayerHybrid Layer/Plane Cube
physical
MAC
link
network
transport
session
application
L1
L7
L5
L4
L3
L2
L1.5
data plane control plane
p
l
a
n
e
management
socialL8
virtual linkL2.5
Layer 2:
hop-by-hop
data transfer
in data and control planes
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-4
Link LayerLink Definition
• Link is the interconnection between nodes– intermediate systems (switches or routers)
– end systems (or hosts)
networkCPU
M app
end system
CPU
M app
end system
intermediate
system
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-5
Link LayerLink Protocol
• Link protocol
– is responsible for per hop transfer of data frame
– assume dedicated links for now: no MAC lecture MW
network
application
session
transport
network
link
end system
network
link
intermediate
system
network
link
intermediate
systemnetwork
link
intermediate
system
application
session
transport
network
link
end system
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-6
Link LayerService and Interfaces
• Link layer is HBH analog of E2E transport layer– transport layer (L4) transfers packets E2E
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-7
Link LayerService and Interfaces
• Link layer is HBH analog of E2E transport layer– transport layer (L4) transfers packets E2E
• Link layer (L2) service to network layer (L3)– transfer frame HBH (hop-by-hop)
• sender: encapsulate packet into frame and transmit
• receiver: receive frame and decapsulate into packet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-8
Link LayerService and Interfaces
• Link layer is HBH analog of E2E transport layer– transport layer (L4) transfers packets E2E
• Link layer (L2) service to network layer (L3)– transfer frame HBH (hop-by-hop)
• sender: encapsulate packet into frame and transmit
• receiver: receive frame and decapsulate into packet
– error checking / optional correction or retransmission• recall end-to-end arguments:
E2E reliability with HBH error control only for performance
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-9
Link LayerService and Interfaces
• Link layer is HBH analog of E2E transport layer– transport layer (L4) transfers packets E2E
• Link layer (L2) service to network layer (L3)– transfer frame HBH (hop-by-hop)
• sender: encapsulate packet into frame and transmit
• receiver: receive frame and decapsulate into packet
– error checking / optional correction or retransmission• recall end-to-end arguments:
E2E reliability with HBH error control only for performance
– flow control possible but not generally needed at link layer• parameter negotiation typical (e.g. data rate)
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-10
Link LayerService and Interfaces
• Link layer is HBH analog of E2E transport layer– transport layer (L4) transfers packets E2E
• Link layer (L2) service to network layer (L3)– transfer frame HBH (hop-by-hop)
• sender: encapsulate packet into frame and transmit
• receiver: receive frame and decapsulate into packet
– error checking / optional correction or retransmission• recall end-to-end arguments:
E2E reliability with HBH error control only for performance
– flow control possible but not generally needed at link layer• parameter negotiation typical (e.g. data rate)
• Link layer multiplexing and switching
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-11
Link LayerService and Interfaces
• Link layer frame encapsulates network layer packet– packet (NPDU – network layer protocol data unit)
– frame (LPDU link layer protocol data unit)
• frame = header + packet + (trailer)
network layer
MAC/phy layer
link layer
network layer
MAC/phy layer
link layer
NPDU
NPDU TH
NPDU
NPDU TH
…10111001010…
frame
packet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-12
Link LayerFunctional Placement
• Link layer functionality per line interface
– end system: network interface (NIC)
– switch/router: line card
switch
forwarding
line card
framespackets
line card
line card
line card
end system
network interface
mem CPU
routing
frames
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-13
Link Layer and LANsLL.2 Framing and Delineation
LL.1 Link layer functions and services
LL.2 Framing and delineation
LL.3 LAN types and topologies
LL.4 Multiplexing and switching
LL.5 Per-hop error and flow control
LL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
LL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-14
Link FramingStructure and Fields
• Link protocols need to delimit link layer frame
why?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-15
Link FramingStructure and Fields
• Link protocols need to delimit link layer frame
– physical layer is coded bit stream
– receiver needs to delimit frames
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-16
Link FramingStructure and Fields
• Delimits link layer frame
– physical layer is coded bit stream
– receiver needs to delimit frames
• Header: where the frame goes
– beginning of frame
– multiplexing information for multiplexed links
– addressing information for multiple access links
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-17
Link FramingStructure and Fields
• Delimits link layer frame
– physical layer is coded bit stream
– receiver needs to delimit frames
• Header: where the frame goes
– beginning of frame
– multiplexing information for multiplexed links
– addressing information for multiple access links
• Trailer: what to do with the frame once arrived
– integrity check (typically strong CRC)
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-18
Link FramingReceiver Delineation
• Key problem: how to detect start of frameideas?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-19
Link FramingReceiver Delineation
• Key problem: how to detect start of frame– in the presence of errors
ideas?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-20
Link FramingReceiver Delineation Techniques
• Synchronous clocks
• Counting
• Flags with – byte stuffing
– bit stuffing
• Preamble pattern
• Special physical layer code
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-21
Link FramingReceiver Delineation: Flags with Stuffing
• Flags
– special sequence of bits
• Stuffing– add escape (byte or 0-bit) for data transparency
• Data stream transformation
– bits or bytes inserted
– data rate non-deterministically altered
– sufficient link-capacity headroom must be provided
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-22
Link FramingPreamble Pattern
• Preamble pattern
– special pattern in header (like a flag)
How to handle data transparency?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-23
Link FramingPreamble Pattern
• Preamble pattern
– special pattern in header (like a flag)
• Significantly longer than flag
– lowers probability of bit error impacting
payload
header
preamble
trailer
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-24
Link FramingPreamble Pattern
• Preamble pattern
– special pattern in header (like a flag)
• Significantly longer than flag
– lowers probability of bit error impacting
• Length field in header
– allows preamble in payload
length
payload
header
preamble
trailer
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-25
Link FramingPreamble Pattern
• Preamble pattern
– special pattern in header (like a flag)
• Significantly longer than flag
– lowers probability of bit error impacting
• Length field in header
– allows preamble bits in payload
• Error check in trailer
– protects against errors
– e.g. FCS (frame check sequence)
length
payload
header
preamble
FCS
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-26
Link FramingPreamble Pattern
• Preamble pattern
– special pattern in header (like a flag)
• Significantly longer than flag
– lowers probability of bit error impacting
• Length field in header
– allows preamble bits in payload
• Error check in trailer
– protects against errors
– e.g. FCS (frame check sequence)
• Example: Ethernet 10101010…
MAC
header
30B 14B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-27
Link Layer and LANsLAN Types and Topologies
LL.1 Link layer functions and servicesLL.2 Framing and delineationLL.3 LAN types and topologiesLL.4 Multiplexing and switchingLL.5 Per-hop error and flow controlLL.6 Link layer componentsLL.7 VLANs, L2 tunnels, and ARPLL.8 Residential broadbandLL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-28
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-29
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
• multiplexed (layer 2) more later
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-30
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
• multiplexed (layer 2) more later
• Shared medium (multiple access)
– multiple transmitters per medium
implication?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-31
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
• multiplexed (layer 2) more later
• Shared medium (multiple access)
– multiple transmitters per medium
– results in contention for medium
problem?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-32
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
• multiplexed (layer 2) more later
• Shared medium (multiple access)
– multiple transmitters per medium
– results in contention for medium
• medium access control (MAC) neededlecture MW
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-33
Link Types and TopologiesPoint-to-Point vs. Shared Medium
• Point-to-point links
– one transmitter per medium
• dedicated
• multiplexed (layer 2) more later
• Shared medium (multiple access)
– multiple transmitters per medium
– results in contention for medium
• medium access control (MAC) neededlecture MW
– examples
• wireless networks
• original Ethernet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-34
Link TopologiesPoint-to-Point Links
• Point-to-point links between switches
– space division mesh2
2 2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-35
Link TopologiesPoint-to-Point Links
• Point-to-point links between switches
– space division mesh
Network scalability?2
2 2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-36
Link TopologiesPoint-to-Point Links
• Point-to-point links between switches
– space division mesh
• Scalable:
– add links and expand switches
2
2 2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-37
Link TopologiesPoint-to-Point Links
• Point-to-point links between switches
– space division mesh
• Scalable:
– add links and expand switches
– add switches
2
2 2
2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-38
Link TechnologiesPoint-to-Point Dedicated Links
• Point-to-point dedicated links
– sequence of framed packets along a link
H T payload H T payload H T payload
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-39
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
advantages and problems?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-40
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• host is frequently called a station
station
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-41
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
Network scalability?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-42
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-43
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
– contention for shared medium
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-44
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
– contention for shared medium
• possible to prevent collisions
• need MAC lecture MW
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-45
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
– contention for shared medium
• possible to prevent collisions
• need MAC lecture MW
• Resilience
– how?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-46
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
– contention for shared medium
• possible to prevent collisions
• need MAC lecture MW
• Resilience
– dual ring can survive cut
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-47
Link TopologiesShared Medium LAN/MAN: Ring
• Ring topology
– topology constraints
– interstation distance an issue
• Limited scalability
– all stations share capacity of ring
– contention for shared medium
• possible to prevent collisions
• need MAC lecture MW
• Resilience
– dual ring can survive cut
• Example: token ring
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-48
LAN ProtocolsIEEE 802
• IEEE 802 LAN/MAN standards [IEEE 802.1]
www.ieee802.org
• Definition of LAN/MAN protocols for L1–L2
– does not align perfectly with conventional layers
• L2 defined by LLC (logical link control) and MAC header
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-49
LAN ProtocolsIEEE 802
• IEEE 802 LAN/MAN standards [IEEE 802.1]
www.ieee802.org
• Definition of LAN/MAN protocols for L1–L2
– 802.2 : logical link control
– 802.n : MAC and physical media dependent
LLC sublayer
logical link control
MAC sublayer
medium access control
MI sublayer
media independent
PMD sublayer
physical media dependent
physical
layer
link
layer
MAC
layer
802.2
802.n
PMD1 PMD2 PMDk
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-50
Internet ProtocolsImportant IEEE 802 Protocols
• Many other 802.n protocols– some important, but obsolete, e.g. 802.5– some never important, e.g. 802.6 DQDB, 802.20 MBWA– some lost to competing standards, e.g. 802.14, 802.16– the jury is still out on others, e.g. 802.17, 802.22
Common name Standard Scope Technology
architecture IEEE 802.1 LAN.MAN media independent
LLC IEEE 802.2 LAN/MAN media independent
Ethernet IEEE 802.3 LAN/MAN wire, fiber
Token ring IEEE 802.5 LAN wire
WLAN IEEE 802.11 LAN RF, (IR)
WPAN IEEE 802.15 PAN RF
WMAN IEEE 802.16 MAN RF
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-51
Shared Medium LinksEthernet
• Early LAN technology (1973)
– DIX: Digital, Intel, Xerox
• IPv4 over DIX [RFC 0894]
– IEEE 802.3 using 802.2 LLC
• IPv4 over 802.3 [RFC 1042]
– note: DIX and 802.3 similar
• but not identical
MAC
header
30B 14B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-52
Shared Medium LinksEthernet
• Early LAN technology (1973)
– DIX: Digital, Intel, Xerox
– IEEE 802.3 using 802.2 LLC
• Initially shared coaxial medium
– CSMA/CD MAC lecture MW
– performs well in light load < 50%
– performs poorly in heavy load > 80%
MAC
header
30B 14B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-53
Shared Medium LinksEthernet
• Early LAN technology (1973)
– DIX: Digital, Intel, Xerox
– IEEE 802.3 using 802.2 LLC
• Initially shared coaxial medium
– CSMA/CD MAC lecture MW
– performs well in light load < 50%
– performs poorly in heavy load > 80%
• Dominant 1980s LAN
– token ring only significant competitor
– evolved 10 to 100 Mb/s to …
MAC
header
30B 14B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-54
Shared Medium LinksEthernet
• Early LAN technology (1973)
– DIX: Digital, Intel, Xerox
– IEEE 802.3 EECS 780
• Shared wire medium
– CSMA/CD MAC
– performs well in light load < 50%
– performs poorly in heavy load > 80%
• Dominant 1980s LAN
– token ring only significant competitor
– evolved 10 to 100 Mb/s to … trailer
4B
MAC
header
14B
length / type
destination
address
source
address
FCS
frame body
38 – 1492 B
10101010 1010101010101010 10101010
10101010 1010101110101010 10101010
preamble
+SFD
LLC
SNAP
pad
LLC/MAC
subheader
8B
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-55
Shared Medium LinksEthernet
• Scaling to high data rates
– 10 Mb/s 100 Mb/s 1 Gb/s 10 Gb/s 40/100 Gb/s
– 802.3u 802.3ab 802.3an 802.3ba Cu
– 802.3z 802.3ae 802.3ba fib.
• fiber standards and deployment first for 1 and 10 Gb/s
• consistent with aggregation for enterprise and metro use
• MAC and link framing enhancements
– slot time increase, frame extension, and bursting for 1 Gb/s
– elimination of CSMA/CD for 10 Gb/s: full duplex only
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-56
Dedicated LinksEthernet
• …Evolving toward 1Tb/s
• IEEE 802.3bs-2017
– decision was made to initially target 400 Gb/s
• interim 4 step before 10 level likely to persist
– 200 Gb/s was added
– 1 Tb/s will be considered later
• probably ~2020
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-57
Ring LinksSONET Rings
• SONET links in ring configuration
– dual rings provide fault tolerance
– APS: automatic protection switching
• restoration after fiber cut (aka backhoe fade)
more on SONET later
✄
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-58
Link-Layer Multiplexing & SwitchingOverview
• Link-layer multiplexing
– multiplexing multiple lower rate links higher rate link
– demultiplexing to lower rate links higher rate link
• Link-layer switching (L2 switching)
– switching in space or time at the link layer
– transparent to layer 3
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-59
Link-Layer MultiplexingOverview
• Link-layer multiplexing
• PSTN evolution
– synchronous multiplexing for traffic aggregation
• Broadband Internet access
– PONs (passive optical networks)
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-60
Link-Layer MultiplexingScenarios
• PSTN and PON multiplexing
– multiplexing for traffic aggregation
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-61
Link-Layer MultiplexingScenarios
• PSTN and PON multiplexing
– multiplexing for traffic aggregation
• PSTN access to SONET rings
– ADM: add-drop multiplexor
– insert into ring
– extract from ring
A
D
M
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-62
Link-Layer MultiplexingMultiplexing Schemes
• TDM: time division multiplexing
– synchronous (e.g. PDH, SDH/SONET)
– asynchronous or statistical (e.g. ATM)
• FDM: frequency division multiplexing (typically RF)
– WDM: wavelength division multiplexing (light)
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-63
Link-Layer MultiplexingMultiplexing vs. Multiple Access
• Multiplexing vs. multiple access
• Link multiplexing
– single transmitter
– dedicated point-to-point link
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-64
Link-Layer MultiplexingMultiplexing vs. Multiple Access
• Multiplexing vs. multiple access
• Link multiplexing
– single transmitter
– dedicated point-to-point link
• Multiple access
– multiple transmitters
– shared medium
– essentially physical layer multiplexing
– MAC algorithm needed to arbitrate
lecture MW
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-65
Link-Layer MultiplexingHigher Layer Multiplexing
• Higher layers multiplex into lower layersL7⇇⇒L4 multiple applications use E2E transport flow (port)
L4⇇⇒L3 multiple transport flows use network paths (prot id)
L3⇇⇒L2 multiple network path use links
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-66
Link-Layer MultiplexingLink Layer Multiplexing
• Higher layers multiplex into lower layersL7⇇⇒L4 multiple applications use end-to-end transport flow
L4⇇⇒L3 multiple transport flows use network paths
L3⇇⇒L2 multiple network path use links
• Link layer multiplexing: L2⇇⇒L2
– some link layers also provide native multiplexing
• mux/demux without network layer switching
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-67
Link-Layer MultiplexingLink Layer Multiplexing
• Higher layers multiplex into lower layersL7⇇⇒L4 multiple applications use end-to-end transport flow
L4⇇⇒L3 multiple transport flows use network paths
L3⇇⇒L2 multiple network path use links
• Link layer multiplexing: L2⇇⇒L2
– some link layers also provide native multiplexing
• mux/demux without network layer switching
• Recall historical precedence
– PSTN has minimal layer 3 switching
– time division multiplexing from premises–CO–long-distance
– digital hierarchy: T-carrier and SONET/SDH
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-68
Link-Layer MultiplexingLink Layer Simple Multiplexing
• Link layer multiplexing
• Layer 2 combine/split
– of lower rate signals
• Examples
– SONET/T-carrier
• OC-m ⇇⇒ OC-n , m < n
• T3 ⇇⇒ OC-3
– PONs (passive optical nets)
• residential broadbandmore later
STS-n
STS-n
OC-n
OC-n
OC-m
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-69
Link-Layer SwitchingPSTN SONET Rings
• PSTN synchronous multiplexing
– multiplexing for traffic aggregation
• PSTN SONET switching
– XC: inter-ring cross-connect
– ADM: add-drop multiplexors
XCA
D
M
A
D
M
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-70
Link-Layer SwitchingInternet LANs
• Internet LAN switching
– shared-medium segments
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-71
Link-Layer SwitchingInternet LANs
• Internet LAN switching
– shared-medium segments replaced by Ethernet switches
• more on this evolution later
– no awareness, involvement, or management of IP
L2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-72
Link-Layer SwitchingEvolution
• Link layer switching
– native layer 2 protocol and device switching
• Evolved with PSTN and Internet
– migration from shared medium to switched LAN
• e.g. Ethernet
– add switching functionality to multiplexing structure
• e.g. SONET cross-connects
Advantages?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-73
Link-Layer SwitchingAdvantages
• Potential advantages
– simpler, cheaper switches than L3 (IP switch/router)
• less important with fast IP lookup hardware
– no need to manage IP in small networks
• less important with DHCP and router auto-configuration
– faster restoration on link failure
• IP routing convergence much slower than L2 restoration
Disadvantages?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-74
Link-Layer SwitchingDisadvantages
• Potential advantages
– simpler, cheaper switches than L3 (IP switch/router)
– no need to manage IP in small networks
– faster restoration on link failure
• Disadvantages
– duplication of L3 functions in L2
– where should functionality really go?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-75
TDM Transport NetworksOverview
• Transport networks– link layer (L2) infrastructure in the PSTN context
– not to be confused with end-to-end (L4) transport
• used in Internet protocol terminology
• Transport network evolution
– PDH: digital hierarchy, generally over wires (e.g. T-carriers)
– SDH/SONET: digital hierarchy over optical fiber
– OTN: optical transport network with WDM switches
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-76
TDM Transport NetworksITU Hierarchy
PDH: pleisiochronous digital hierarchy
SDH: synchronous digital hierarchy
ATM/B-ISDN Ethernet
OTN: optical transport network
PNNI GMPLS
ASON
GFP CBRkSDH/SONET
ATM ETH
GFPCBRk AAL
proprietary DWDM
OTN
CBR
IP
ASON
PNNI
GMPLS
control planes
PDH
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-77
TDM Transport NetworksITU Hierarchy
• Data and management planes
– OTN: optical transport network WDM links
– SDH: synchronous digital hierarchy (SONET) links
– Ethernet: long-haul point-to-point Ethernet links
– ATM/B-ISDN: asynchronous transfer mode / broadband ISDN
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-78
TDM Transport NetworksPSTN Digital Hierarchy
• PSTN digital hierarchy
– digital multiplexing structure to replace analog circuits
– hierarchy of increasing rates for aggregation in network core
– multiplexors and demultiplexors independent of switching
• Plesiochronous
– from the greek: πλησίος = nearly + χρόνος = time
– digital signals are nearly synchronous
– bit slips tolerated with bit-stuffing in frame structure
– signals are bit streams
– framing not visible to next-higher level
– no relative synchronisation among signals below given level
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-79
PSTN Digital HierarchyUS Multiplexing Structure
• Digital signals (DS) on T-carriers (others for DS-4)
– DS0: digital voice channel or 56 kb/s leased data line
– DS1: 24 DS0 or 1.5 Mb/s T-1 data service
– DS2: 4 DS1
– DS3: 7 DS2 or 45 Mb/s T-3 data service
– DS4: 3 DS3 (historical – now replaced by SONET)
DS4
DS3 DS3
DS2 DS2
DS1
DS0
DS0
T1
T3
T1
T3
24:1
4:1
3:1 1:3
1:4
1:24
7:1 1:7
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-80
US Multiplexing StructureFrame Structure
• Framing
– bit patterns distributed throughout frames
• Alarms
– indicate loss of signal or framing to other end of link
– used by networking monitoring and management
• Error detection
– parity or CRC
• Signalling and data channels
– robbed from DS0 or distributed throughout frame
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-81
TDM Transport NetworksSONET/SDH Overview
• SONET: synchronous optical network
– evolution of T-carrier digital hierarchy in the Bell System
– extension of TDM multiplexing structure
– higher data rates over fiber optic cable
• OC: optical carrier
– electronic multiplexing and cross-connects
• O/E: optical to electrical conversion at inputs
• E/O: electrical to optical conversion at outputs
• SDH: synchronous digital hierarchy
– ITU standard similar to SONET
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-82
Link Layer and LANsPer Hop Error and Flow Control
LL.1 Link layer functions and services
LL.2 Framing and delineation
LL.3 LAN types and topologies
LL.4 Multiplexing and switching
LL.5 Per-hop error and flow control
LL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
LL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-83
Link Layer Error ControlIntroduction
• Per-hop error control for frame transfers
Why?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-84
Link Layer Error ControlIntroduction
• Per-hop error control for frame transfers
• Recall end-to-end arguments:
– if error checking and correction needed E2E …… it must be done end-to-end by transport (or application)
• HBH link error control
– improve overall performance for apps requiring reliability
• in addition to E2E error control
– improve performance over lossy links for loss-tolerant apps
• Alternatives
– e.g. ARQ for wireless links
– e.g. FEC for satellite and fiber optic links
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-85
Link Layer Error ControlDetection vs. Correction
• Error detection
– generally useful at link layer to detect errors
– corrupted frames typically dropped
why?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-86
Link Layer Error ControlDetection vs. Correction
• Error detection
– generally useful at link layer to detect errors
– corrupted frames typically dropped
• useless data not sent through network consuming resources
• transport layer detects (or signalled) and corrects as necessary
– it needs to do this anyway
– link layer checks frequently stronger than E2E
• link frame CRC much stronger than TCP checksum
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-87
Link Layer Error ControlDetection vs. Correction
• Error detection
– generally useful at link layer to detect errors
– corrupted frames typically dropped
• useless data not sent through network consuming resources
• transport layer detects (or signalled) and corrects as necessary
– it needs to do this anyway
– link layer checks frequently stronger than E2E
• link frame CRC much stronger than TCP checksum
• Error correction
– used when hop-by-hop correction needed
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-88
Link Layer Error ControlDetection Techniques
• Byte, word, or block
– parity
– 2-dimensional parity
– Hamming codes
• Frame
– checksum
– CRC
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-89
Block Error DetectionParity
What is simplest error detection method?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-90
Block Error DetectionParity
• Parity : detect single errors
– no ability to correct errors
– only an odd number of bit errors detected
• only useful if bit error probability very low
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-91
Block Error DetectionParity
• Parity: detect single errors
– no ability to correct errors
– only an odd number of bit errors detected
• only useful if bit error probability very low
• Parity bit covers n bit block
• Even parity: even number of 1s (including parity)– example: 0111 0001 1010 1011 ?
• Odd parity odd number of 1s (including parity)– example: 0111 0001 1010 1011 ?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-92
Block Error DetectionParity
• Parity: detect single errors
– no ability to correct errors
– only an odd number of bit errors detected
• only useful if bit error probability very low
• Parity bit covers n bit block
• Even parity: even number of 1s (including parity)
– example: 0111 0001 1010 1011 1
• Odd parity odd number of 1s (including parity)
– example: 0111 0001 1010 1011 0
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-93
Block Error DetectionParity
• Parity: detect single errors
– no ability to correct errors
– only an odd number of bit errors detected
• only useful if bit error probability very low
• Parity bit covers n bit block
• Even parity: even number of 1s (including parity)
– example: 0111 0001 1010 1011 1
• Odd parity odd number of 1s (including parity)
– example: 0111 0001 1010 1011 0
Extension to detect which bit in error?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-94
Block Error Detection & CorrectionHamming Codes
• Hamming codes: correct single bit errors
– detects which bit flipped and can therefore correct
– k parity bits per block cover different sets of n data bits
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-95
Block Error Detection & CorrectionHamming Codes
• Hamming codes: correct single bit errors
– detects which bit flipped and can therefore correct
– k parity bits per block cover different sets of n data bits
• Example 4 data bits covered by 3 parity bits
– parity bits p2 p1 p0 interleaved with data bits d3 d2 d1 d0
1011010 d3 d2 d1 p2 d0 p1 p0
1-1-0-1 d3 d1 d0 covered by p0
10--00- d3 d2 d0 covered by p1
1011--- d3 d2 d1 covered by p2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-96
Block Error Detection & CorrectionHamming Codes
• Hamming codes: correct single bit errors
– detects which bit flipped and can therefore correct
– k parity bits per block cover different sets of n data bits
• Example 4 data bits covered by 3 parity bits
– parity bits p2 p1 p0 interleaved with data bits d3 d2 d1 d0
1011010 d3 d2 d1 p2 d0 p1 p0 1111010
1-1-0-1 d3 d1 d0 covered by p0 1-1-0-1
10--00- d3 d2 d0 covered by p1 11--00- p1 detects error
1011--- d3 d2 d1 covered by p2 1111--- p2 detects error
• SECDED: single error correct double error detect
– additional parity bit permits detection of second error
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-97
Frame Error DetectionChecksum
• Detect errors in PDU
• Binary addition of bytes/words
– sender: compute checksum and insert in header/trailer
– receiver: compute checksum and compare to header/trailer
Advantages?
Disadvantages?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-98
Frame Error DetectionChecksum
• Detect errors in PDU
• Binary addition of bytes/words
– sender: compute checksum and insert in header/trailer
– receiver: compute checksum and compare to header/trailer
• Advantage:
– simple to compute
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-99
Frame Error DetectionChecksum
• Detect errors in PDU
• Binary addition of bytes/words
– sender: compute checksum and insert in header/trailer
– receiver: compute checksum and compare to header/trailer
• Advantage:
– simple to compute
• Disadvantage:
– weak detection of errors
– some bit-flip combinations may remain undetected
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-100
Frame Error DetectionCRC
• Cyclic redundancy check
– stronger error detection for PDU
CRC
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-101
Frame Error DetectionCRC
• Cyclic redundancy check
– stronger error detection for PDU
• View data bits, D, as a binary number
– choose r + 1 bit pattern (generator), G
• Goal: choose r CRC bits R such that
– <D,R> exactly divisible by G (modulo 2)
– receiver knows G, divides <D,R> by Gif non-zero remainder: error detected
– can detect all burst errors less than r + 1 bits
D R
d r
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-102
Frame Error Detection & CorrectionFEC
• Forward error correction
– each PDU has error correcting header
– combination of header/payload allows significant correction
DFEC
dh
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-103
Frame Error Detection & CorrectionFEC
• Forward error correction
– each PDU has error correcting header
– combination of header/payload allows significant correction
• Open-loop error control
– errors corrected at the receiver without retransmissions
how does this help?
DFEC
dh
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-104
Frame Error Detection & CorrectionFEC
• Forward error correction
– each PDU has error correcting header
– combination of header/payload allows significant correction
• Open-loop error control
– errors corrected at the receiver without retransmissions
– reduces need over long delay links for:
• retransmissions
• sender buffers
– statistical reliability good enough for some applications
– e.g. G.975 (255,239) Reed Solomon code in SDH/SONET
DFEC
dh
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-105
Frame Error Detection & CorrectionFEC
• Forward error correction
– each PDU has error correcting header
– combination of header/payload allows significant correction
• Open-loop error control
– errors corrected at the receiver without retransmissions
– reduces need for retransmissions over long delay links
– statistical reliability good enough for some applications
– e.g. G.975 (255,239) Reed Solomon code in SDH/SONET
• Note: FEC can also be done end-to-end
– but TCP doesn’t support it
DFEC
dh
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-106
Per Hop Error and Flow ControlLL.5.2 Error Control
LL.1 Link layer functions and services
LL.2 Framing and delineation
LL.3 LAN types and topologies
LL.4 Multiplexing and switching
LL.5 Per-hop error and flow controlLL.5.1 Error detection and correction
LL.5.2 Error control
LL.5.3 Flow control
LL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-107
Error ControlOverview
• Error control mechanisms
– detect lost or corrupted frames
– retransmit as needed
– generally only for very lossy links
• satellite, wireless, optical with long inter-regen spans
why?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-108
Error ControlOverview
• Error control mechanisms
– detect lost or corrupted frames
– retransmit as needed
– generally only for very lossy links
• satellite, wireless, optical with long inter-regen spans
• recall end-to-end arguments
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-109
Error ControlOverview
• Error control mechanisms
– detect lost or corrupted frames
– retransmit as needed
– generally only for very lossy links
• satellite, wireless, optical with long inter-regen spans
• recall end-to-end arguments
• Same as E2E mechanisms Lecture TL
– unrestricted simplex (baseline no error control)
– stop-and-wait: sufficient for short links such as WLANs
– go-back-n
– selective repeat
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-110
Link Layer and LANsLink Layer Components
LL.1 Link layer functions and services
LL.2 Framing and delineation
LL.3 LAN types and topologies
LL.4 Multiplexing and switching
LL.5 Per-hop error and flow control
LL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
LL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-111
Link Layer ComponentsTypes
• Amplifiers and regenerators
• Multiplexors and cross-connects
• Optical wavelength converters
• Hubs and bridges
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-112
Link Layer ComponentsLAN Components
How to extend the reach of LAN segment?original shared medium bus or ring
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-113
Link Layer ComponentsBridges
• Bridges connect LAN segments– extend reach beyond limits
– important for early LANS
• e.g. Ethernet extension
• Promiscuous
– repeat (pass) all frames
network scalability?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-114
Link Layer ComponentsBridges
• Bridges connect LAN segments– extend reach beyond limits
– important for early LANS
• e.g. Ethernet extension
• Promiscuous
– repeat (pass) all frames
– all interconnected segments share intra-segment frames
alternative?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-115
Link Layer ComponentsBridges
• Bridges connect LAN segments
– extend reach beyond limits
– important for early LANS
• e.g. Ethernet extension
• Learning bridge
– learns local segment addresses
• snooped on source MAC address in frame header
– only repeat frames destined for other segments
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-116
Link Layer ComponentsHubs
• Early LANs dictated wiring topology
– linear segments for Ethernet
– loops for token ring
Problems?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-117
Link Layer ComponentsHubs
• Early LANs dictated wiring topology
– linear segments for Ethernet
– rings for token ring
• Office topology frequently didn’t match LAN topology
– Ethernet bridges frequently needed to bridge hallways
• End user could take down network
– by disconnecting network interface
• token ring
• some Ethernet links (e.g. 10Base2)
– sys/netadmins would have to run from office to office
Response?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-118
Link Layer ComponentsHubs
• Alternative
– use a star wiring plan
– host/station links all go to a hub in a wiring closet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-119
Link Layer ComponentsHubs
• Alternative
– use a star wiring plan
– host/station links all go to a hub in a wiring closet
• More flexible wiring plan
• Central location for debugging
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-120
Link Layer ComponentsHubs
• Alternative
– use a star wiring plan
– host/station links all go to a hub in a wiring closet
• More flexible wiring plan
• Central location for debugging
Network scalability?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-121
Link Layer ComponentsHubs
• Alternative
– use a star wiring plan
– host/station links all go to a hub in a wiring closet
• More flexible wiring plan
• Central location for debugging
• Hub is still shared medium bottleneck
alternative?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-122
Link Layer ComponentsLAN Switches
• Alternative
– replace hub with a space division switch
L2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-123
Link Layer ComponentsLAN Switches
• Alternative
– replace hub with a space division switch
• LAN switch
– switches on layer 2 (MAC address) header
– full bandwidth of each link available
• assuming non-blocking switch fabric
L2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-124
Link Layer ComponentsLAN Switches
• Alternative
– replace hub with a space division switch
• LAN switch
– switches on layer 2 (MAC address) header
– full bandwidth of each link available
• assuming non-blocking switch fabric
– not a substitute for L3 (IP) switch (router)
why?
L2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-125
Link Layer ComponentsLAN Switches
• Alternative
– replace hub with a space division switch
• LAN switch
– switches on layer 2 (MAC address) header
– full bandwidth of each link available
– not a substitute for L3 (IP) switch (router)
– no IP routing and forwarding capability
– fwd table must contain every randomly assigned L2 address
L2
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-126
Link Layer and LANsVLANs, L2 Tunnels, and ARP
LL.1 Link layer functions and servicesLL.2 Framing and delineationLL.3 LAN types and topologiesLL.4 Multiplexing and switchingLL.5 Per-hop error and flow controlLL.6 Link layer components
LL.7 VLANs, L2 tunnels, and ARP
LL.8 Residential broadband
LL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-127
VLANs, L2 Tunnels, and ARPMotivation
• LANs operate as part of Global Internet
– using IP
• Several technologies needed or useful for this
– VLANs: Virtual LANs
– L2 tunnels: link emulation over IP
– ARP: IP address resolution protocol
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-128
Virtual LANsMotivation
• LANs provide useful infrastructure at network edge
– cheap and simple interconnection for workgroup
– “plug-and-play” interfaces
– no need to understand or configure IP routing
• Workgroup may not match physical topology
– multiple workgroups share LAN infrastructure
– workgroups scattered across wide area Internet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-129
Virtual LANsVLAN Topology Alternatives
• Workgroup may not match physical topology
– virtual LANs (VLANs)
• Multiple workgroups share LAN infrastructure
– VLANs segregate physical LANs
– traffic isolation
• separate L2 broadcast domain
• security: prevent L2 frames to be visible across VLANs
• Workgroup scattered across wide-area Internet
– layer 2 tunnels extend LAN with L2 tunnel in IP datagram
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-130
Virtual LANsL2 Switch Configuration
How to configure VLANs in a L2 switch?
0 L2
1
2
3
4
5
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-131
Virtual LANsL2 Switch Configuration
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
How to interconnectVLANs?
0 L2
1
2
3
4
5
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-132
Virtual LANsL2 Switch Configuration
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN interconnection
– must be done with IP router0 L2
1
2
3
4
5
6
7
IP
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-133
Virtual LANsL2 Switch Configuration
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN interconnection
– must be done with IP router
– some VLAN switcheshave built-in router for this
0 L2
1
2
3
4
5
IP
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-134
Virtual LANsScaling to Multiple Switches
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
How to extend tomultiple switches?
0 L2
1
2
3
4
5
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-135
Virtual LANsScaling to Multiple Switches
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN extension
– link/VLAN between switches
problem?
0 L2
1
2
3
4
5
6
7
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-136
Virtual LANsScaling to Multiple Switches
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN extension
– link/VLAN between switches
• not scalable
0 L2
1
2
3
4
5
6
7
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-137
Virtual LANsScaling to Multiple Switches
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN extension
– link/VLAN between switches
– VLAN trunking
how to segregate frames?
0 L2
1
2
3
4
5
7
6
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-138
Virtual LANsScaling to Multiple Switches
• VLANs defined by assigning VLAN id to switch port
– end systems must plug into correct physical port subset
– logical division into multiple switches
• VLAN extension
– link/VLAN between switches
– VLAN trunking
• tagging to segregate frames
0 L2
1
2
3
4
5
7
6
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-139
Virtual LANs802.1Q Tagging
• VLAN tagging
– additional field with VLAN id
where must it go?
MAC
header
22B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-140
Virtual LANs802.1Q Tagging
• VLAN tagging: IEEE 802.1Q
– additional field with VLAN id
– VLAN tag must go after preamble
• inserted into header after addresses
MAC
header
26B
trailer
4B
LLC/SNAP
subheader
8B
payload
length/type
payload
destination address
source address
LLC
SNAP
10101010 10101010
FCS
10101010 10101010
10101010 1010101110101010 10101010
preamble + SFD
VLAN tag
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-141
Layer 2 TunnelsMotivation
• Layer 2 tunnels
– permit LAN extension across longer-than-LAN networks
– permits VLAN interconnection across IP Internet
0 L2
1
2
3
4
5
7
IP6
0L2
1
2
3
4
5
6
7IP
IP
IP
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-142
Layer 2 TunnelsL2TP Encapsulation
• L2TP: layer 2 tunneling protocol
– L2TPv3: current version [RFC 3931]
• L2 frame encapsulated in
– L2TP data message in
– UDP datagram flow in
– IP datagram through Internet in
– L2 frames on each link
L2TP header
UDP header
IP header
L2 frame header
L2 frame header
L2 frame payload
L2 frame trailer
L2 frame trailer
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-143
IP Address ResolutionARP Motivation
• Addresses used for forwarding
– IP addresses for Internet layer 3 IP switching (routing)
• What about layer 2 addressing?
– in shared medium MAC address specifies destination station
– legacy Ethernet and thus switched Ethernet
– 802.11 lecture MW
• Problem: incoming IP packet has only address
how to determine station address to put in MAC header?
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-144
IP Address ResolutionARP Motivation
• Addresses used for forwarding
– IP addresses for Internet layer 3 IP switching (routing)
• What about layer 2 addressing?
– in shared medium MAC address specifies destination station
– legacy Ethernet and thus switched Ethernet
– 802.11 lecture MW
• Problem: incoming IP packet has only address
– need an address resolution protocol (ARP)
– translates IP address L2 LAN (MAC) address
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-145
IP Address ResolutionARP Overview
• ARP (address resolution protocol) [RFC 0826]
– translates IP address L2 LAN (MAC) address
– router broadcasts REQUEST; node responds with REPLY
• IP router at LAN edge has ARP table– IP MAC mappings for some nodes
• ARP designed as multiprotocol
– any network protocol over any LAN/MAC protocol
– type and address length fields define L2 and L3 protocol
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-146
Link Layer and LANsResidential Broadband
LL.1 Link layer functions and servicesLL.2 Framing and delineationLL.3 LAN types and topologiesLL.4 Multiplexing and switchingLL.5 Per-hop error and flow controlLL.6 Link layer componentsLL.7 VLANs, L2 tunnels, and ARPLL.8 Residential broadbandLL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-147
Link TechnologiesResidential Broadband Overview
• RBB (residential broadband)
– umbrella term for residential Internet access technologies
• significantly higher data rates than 56kb/s dialup modem
– typically a combination of link and physical layers
– frequently called last mile or first mile
• Standards
– proprietary technologies
– ad hoc standards from industry fora
– standards (ITU, ANSI, IEEE)
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-148
Link TechnologiesResidential Broadband Deployment Strategies
• Reusing legacy infrastructure
– PSTN: DSL – digital subscriber line
– CATV: HFC – hybrid fiber coax
– power grid: broadband over power line
• Deployment of new infrastructure
– fiber
• to the neighbourhood: FTTN
• to the home: FTTH
– wireless
• 802.16 lecture MW
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-149
Residential BroadbandDigital Subscriber Line Overview
• DSL (digital subscriber line) also xDSL
– based on PSTN local loop infrastructure
• Local loop reuse
– entire local loop: central office to home
Technology Medium Infrastructure Deployment
DSL twisted pair reuse widespread
HFC shared coax reuse widespread
FTTX PON fiber new emerging
BPL copper reuse future
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-150
Residential BroadbandDigital Subscriber Line Overview
• DSL (digital subscriber line) also xDSL
– based on PSTN local loop infrastructure
• Local loop reuse
– entire local loop: central office to home
– may be hybrid
• fiber to neighbourhood node (e.g. FTTN, VDSL)
• twisted pair to and in home
• POTS sharing alternatives
– transparent multiplexing with POTS for residential use
– dedicated pair originally for business use
• DSL forum dslforum.org
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-151
ADSLOriginal Motivation
• ADSL (asymmetric DSL) [ANSI T1.413] / [ITU G.992.1 ]
– developed by Bellcore late 1980s to deliver video to home
• video market didn’t develop and not enough streams supported
• but demand for always-on higher-rate Internet access did
– assumed asymmetric data access
• Web access and video download
• not peer-to-peer file sharing
• exploits asymmetry to reduce interference in DSLAM
– frequency multiplexed with POTS
• uses DMT coding to provide
• requires splitter in home to segregate data from POTS
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-152
ADSLModulation and Spectrum
• POTS telephony
– UTP (unshielded twisted pair) local loop
– analog baseband signal to 12 kHz
– significantly more bandwidth available with clever coding
• ADSL uses frequencies above 12 kHz
– upstream: 25.875 – 138 kHz
– downstream: 138 – 1104 kHz
12kHz 26kHz 138kHz
voice downstream data upstream data
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-153
ADSL LiteCentral Office and Residence Architecture
• DSL multiplexed with POTS between home and CO– subscriber side does not need splitter– DSL modems can be plugged into any RJ-11 phone jack
PC
NID5
central office
Internet
PSTN
DSLAM
DSLAM: DSL access mux
NID: network interface device
DSL: hub or switch with DSL modem
split
split
DSL
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-154
Digital Subscriber LinesAdvantages and Disadvantages
• Advantages of ADSL
– reuse of existing local loops in their entirety
• shared with POTS without need for additional pair
– dedicated point-to-point links
• bandwidth not shared with other users
• better latency characteristics
• Disadvantages of ADSL
– lower rates than FTTN architectures (VDSL and HFC)
– rate dependent length, gauge, wire and termination quality
– blocked by load coils (POTS line extenders)
– ADSL lite limited by number and spacing of bridge taps
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-155
Residential BroadbandHybrid Fiber Coax Overview
• HFC (hybrid fiber coax)
– based on CATV distribution infrastructure
– fiber to neighbourhood node
– coax to and within home
Technology Medium Infrastructure Deployment
DSL twisted pair reuse widespread
HFC shared coax reuse widespread
FTTX PON fiber new emerging
BPL copper reuse future
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-156
HFCNetwork Architecture
• Head end is CATV equivalent to PTSN central office
– fiber links from head end to fiber node in neighbourhoods
• optical electrical conversion
– coax distribution lines serve multiple houses (10 – 2000)
• amplifiers may be used to extend coax runs
• subscriber drops tap into distribution cable
OE
head end
OE
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-157
HFCHead End and Residence Architecture
• Data multiplexed with analog and digital TV channels
– IP telephony delivered over data stream
PC
head end
Internet
PSTN
CMTS: cable modem termination system
DOCSIS: hub or switch with DOCSIS modem
LIS: local insertion video server (weather, ads)
TRAC: telco return access concentrator
TV
TVIP
DOCSIS
OETRAC
CMTS
local
local
studio
LISVOD
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-158
HFCModulation and Spectrum
• Data spectrum: FDM – frequency division multiplexed
• Upstream: 5 – 42 MHz (below old broadcast channel 2)
– QPSK QAM-16 QAM-64 QAM-256
• Downstream: 91 – 857 MHz– spectrum divided with analog and digital television
• analog channels no longer transported
– QAM-64 or -256 downlink shared among users• per user bandwidth depends on network engineering and load
5 42
u
p
54 88 108 857 MHz
FM
digital CATV channels
216 MHz
downstream DOCSIS data
VHF analog analog CATV channels
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-159
HFCDOCSIS Overview
• Data over cable interface specification (DOCSIS)
– Originally begun as IEEE 802.14
– CableLabs to ITU-T J.XX2 standards
• DOCSIS 2.0 and 3.0 www.cablemodem.com/specifications/
• DOCSIS versions
– 1.0 [J.112]: downstream over HFC, upstream using POTS
– 1.1 [J.112]: downstream and upstream using HFC
– 2.0 [J.122]: higher upstream rate of 30.72 Mb/s
– 3.0 [J.222]: upstream & downstream rates > 100 Mb/s
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-160
HFCDOCSIS Protocol Stack
• DOCSIS standards
– operations interfaces
– security
– MAC (+link)
• link framing
• TDM downstream
• TDMA upstream
– physical layer
• RF on coax
• QPSK/QAMPHY
convergence
MAC
security
DIX/802.3 MAC
802.2 LLC
IP + ARP
UDP
DHCP TFTP SNMPsecurity
mgt
Ethernet
LLC+MAC
MAC
filter
PHY
cable modem mgt.
RF on coax.
cat-n to
CPE
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-161
HFCDOCSIS Frame Formats
• Convergence sublayer header– downstream: MPEG header type=data
– upstream: PMD preamble
• MAC header– FC: frame control – type of header [1B]
– MAC_PARM: MAC parameters [1B]
– LEN: length of EDR+payload [2B]
– EHDR: extended header [0–240B]
– HCS: header check sequence [2B]
• Payload
– Ethernet frame encapsulating user dataEthernet CRC
FC
LEN
HCS
EHDR
MPEG (downstream)
PMD (upstream)
MAC_PARM
Ethernet header
IP packet
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-162
HFCAdvantages and Disadvantages
• Advantages of HFC
– reuse of existing CATV plant
• but required upgrades for upstream channels
• Disadvantages of HFC
– shared medium infrastructure
– usable data rate and latency per user highly dependent on…
• number of homes in fiber node area
• take rate (number of subscribers in fiber node area)
• traffic demand
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-163
Link Layer and LANsData Centre Networks
LL.1 Link layer functions and servicesLL.2 Framing and delineationLL.3 LAN types and topologiesLL.4 Multiplexing and switchingLL.5 Per-hop error and flow controlLL.6 Link layer componentsLL.7 VLANs, L2 tunnels, and ARPLL.8 Residential broadbandLL.9 Data Centre Networks
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-164
Data Centre NetworksOverview
• Large application service providers (ASPs)
– cloud service providers (e.g. Amazon, IBM, MS, Google)
– social networking providers (e.g. Facebook, YouTube)
– large retailers (e.g. Walmart)
– financial, insurance, healthcare providers
• Require massive computing and storage capabilities
• Consolidated in data centres
– physically secure facilities
– access to significant power with massive generator backup
• significant environmental impact
– racks of server blades interconnected by switched network
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-165
Data Centre NetworksFat Tree Topology
hosts
core
aggregation
TOR
L2
L2
IP
EL2
EL2
EL2
EL2
EL2
EL2
EL2
EL2
L2 L2 L2
L2
border
router
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-166
Link LayerKey Acronyms1
HBH hop-by-hop
NIC network interface {chip | card}
CRC cyclic redundancy check
LAN local-area network
MAN metropolitan-area network
TDM time-division multiplexing
SONET synchronous optical network
OTN optical transport network
FEC forward error correction
VLAN virtual LAN
ARP address resolution protocol
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-167
Link LayerKey Acronyms2
(A)DSL asymmetric digital-subscriber line
HFC hybrid fibre coax
DOCSIS data over cable interface specification
© James P.G. SterbenzITTC
30 October 2018 KU EECS 563 – Intro Comm Nets – Links & LANs ICN-LL-168
Communication NetworksAcknowledgements
Some material in these foils comes from the textbook supplementary materials:
• Kurose & Ross,Computer Networking:
A Top-Down Approach Featuring the Internet
• Sterbenz & Touch,High-Speed Networking:
A Systematic Approach to
High-Bandwidth Low-Latency Communication
http://hsn-book.sterbenz.org