1. A Review of Evolving Network Technology Ethernet & IP J.J. Ekstrom March 2008

2. Who is winning? l Ethernet has won the LAN wars l Ethernet is winning the MAN wars –IProvo, Utopia… 10X bandwidth same price. l Ethernet is contending for part of the WAN… PPOE (Point to Point over Ethernet) l IP has won all best-effort wars wars… –Most ATM traffic is IP –A large portion of Sonet Traffic is IP –MPLS is taking over the core to optimize IP l IETF and Vendors making IP transport of choice for future –Voice over IP –IP Multicast Streaming

3. Why? l Simple transports l Work faster and cheaper l Put the smarts where it can work for more transports l Not as much advantage to smarter transports

4. Historical View: Ethernet Characteristics l Ethernet shared media cable l Cable access method (CSMA/CD) l Unreliable Packet Delivery l Assumes higher layers do most of the work l Simple and Relatively fast on whatever physical transport with any generation of hardware.

5. Ethernet Shared Media Cable 1 l Physics determined the maximum length of the Ethernet cable –signal strength –cable characteristics

6. Ethernet Shared Media Cable 2 l All stations (nodes) hook to, and share a single cable

7. Ethernet Shared Media Cable 3 l Each station “listens” as it transmits

8. Ethernet Shared Media Cable 4 l Each station must transmit a minimum of 64 bytes to “fill” the cable before it stops listening

9. Ethernet Shared Media Cable 5 l If a 2nd node transmits before the 1st node finishes, the two transmissions collide and they must retransmit

10. Ethernet Cable Access Method (CSMA/CD) l CSMA/CD is a media-access method used by Ethernet and 802.3 networks l CSMA/CD stands for Carrier Sense, Multiple Access / Collision Detection

11. How CSMA/CD Works - 1 l A station wishing to transmit first listens for traffic on the cable indicated by a carrier signal (CSMA/CD-Carrier Sense)

12. How CSMA/CD Works - 2 l If the carrier signal is detected, the station waits a period of time and tries again

13. How CSMA/CD Works - 3 l If NO carrier signal is detected, the station starts transmitting its packet (min. of 64 bytes) and simultaneously listening

14. How CSMA/CD Works - 4 l TWO stations can start transmitting at the same time (CSMA/CD - Multiple Access)

15. How CSMA/CD Works - 5 l If this happens, both stations hear garbage (CSMA/CD - Collision Detection)

16. How CSMA/CD Works - 6 l When collisons are detected, both stations : –cancel transmissions by sending a jam signal –wait a random amount of time before trying to transmit again

17. PROBLEM #1 l Physics doesn’t allow you to have LAN wires as long as you would like.

18. SOLUTION #1 l Repeater extended wire length, broadcast domain, and collision domain

19. PROBLEM #2 l Too many collisions. LAN wouldn’t carry enough traffic.

20. SOLUTION #2 l Bridging segments extends broadcast domain without collisions: Bigger LANs

21. PROBLEM #3 l Broadcast storms - result from multi-port bridges “flooding” all ports when packet destination is unknown and a loop exists.

22. PROBLEM #3 – when the original packet returns to a previous bridge, new packets are generated and a “storm” is generated.

23. SOLUTION #3 l 3.1 - 802.1D (spanning tree) installed on bridges. l 3.2 - Routers

24. SOLUTION #3.1 l 802.1D (Spanning Tree) added to bridges. –Spanning Tree is an algorithm that runs on bridges to eliminate loops dynamically.

25. SOLUTION #3.2 l Routers - make every segment another network or subnet by refusing to pass through any packet whose address it does not recognize.

26. SOLUTION #3.2 l NOTE: –in XNS a single broadcast domain is called a “network.” –in TCP a single broadcast domain is called a “subnet.” –network personnel often call a collision domain a “segment.”

27. PROBLEM #4 l Topology and failure characteristics - problems with bus-oriented LANs (i.e., when the wire breaks NONE of the stations can communicate).

28. SOLUTION #4 l Twisted pair LANs. –When any one wire segment fails, the whole LAN does NOT go down.

29. PROBLEM #5 l Not enough Bandwidth –only 10 MBPS available on each collision domain

30. SOLUTION #5 l Switches (multiport Bridges) - allows more segments (bandwidth) at a lower cost per port.

31. PROBLEM #6 l Controlling User Connectivity –keep groups separate –easily share resources between groups –do adds, moves, and changes without rewiring

32. SOLUTION #6 l VLANs of various forms create isolated broadcast domains (networks) l Connection between Virtual LAN networks requires a router. l People do security in their routers and firewalls at network boundaries anyway

33. Problem #7 l During roughly the same 20-25 year period Token-Ring LANs, FDDI, ATM, and several other LAN and WAN technologies have been undergoing similar evolutionary tracks as ethernet. l It was not clear that there would be a clear winner. l How do you hook them together and protect your technology investments? l Users don’t care how their bits get pushed around, only that things work.

34. Solution #7 l Internetworking…The real reason IP has won the protocol wars. –Works well on P2P links –Works well on LANs –Makes very few demands of participant networks –“Rough consensus and working code” l Motto of the IETF l The way to get useful things quickly in a world of confusion…what works best wins.

35. Internetworking Outline Best Effort Service Model Global Addressing Scheme

36. IP Internet l Concatenation of Networks l Protocol Stack R2 R1 H4 H5 H3 H2 H1 Network 2 (Ethernet) Network 1 (Ethernet) H6 Network 3 (FDDI) Network 4 (point-to-point) H7R3H8 R1 ETH FDDI IP ETH TCP R2 FDDI PPP IP R3 PPP ETH IP H1 IP ETH TCP H8

37. Service Model l Connectionless (datagram-based) l Best-effort delivery (unreliable service) –packets are lost –packets are delivered out of order –duplicate copies of a packet are delivered –packets can be delayed for a long time –(Sound like Ethernet?) l Datagram format VersionHLen TOSLength IdentFlagsOffset TTLProtocolChecksum SourceAddr DestinationAddr Options (variable) Pad (variable) 048161931 Data

38. Fragmentation and Reassembly l Each network has some MTU l Strategy –fragment when necessary (MTU < Datagram) –try to avoid fragmentation at source host –re-fragmentation is possible –fragments are self-contained datagrams –use CS-PDU (not cells) for ATM –delay reassembly until destination host –do not recover from lost fragments

39. Example Ident = xOffset = 0 Start of header 0 Rest of header 1400 data bytes Ident = xOffset = 0 Start of header 1 Rest of header 512 data bytes Ident = xOffset = 512 Start of header 1 Rest of header 512 data bytes Ident = xOffset = 1024 Start of header 0 Rest of header 376 data bytes

40. Global Addresses l Properties –globally unique –hierarchical: network + host l Dot Notation –10.3.2.4 –128.96.33.81 –192.12.69.77 NetworkHost 724 0 A: NetworkHost 1416 10 B: NetworkHost 218 110 C:

41. Datagram Forwarding l Strategy –every datagram contains destination’s address –if directly connected to destination network, then forward to host –if not directly connected to destination network, then forward to some router –forwarding table maps network number into next hop –each host has a default router –each router maintains a forwarding table l Example (R2) Network Number Next Hop 1 R3 2 R1 3 interface 1 4 interface 0

42. Address Translation l Map IP addresses into physical addresses –destination host –next hop router l Techniques –encode physical address in host part of IP address –table-based l ARP –table of IP to physical address bindings –broadcast request if IP address not in table –target machine responds with its physical address –table entries are discarded if not refreshed

43. ARP Details l Request Format –HardwareType: type of physical network (e.g., Ethernet) –ProtocolType: type of higher layer protocol (e.g., IP) –HLEN & PLEN: length of physical and protocol addresses –Operation: request or response –Source/Target-Physical/Protocol addresses l Notes –table entries timeout in about 10 minutes –update table with source when you are the target –update table if already have an entry –do not refresh table entries upon reference

44. ARP Packet Format TargetHardwareAddr (bytes 2–5) TargetProtocolAddr (bytes 0–3) SourceProtocolAddr (bytes 2–3) Hardware type = 1ProtocolType = 0x0800 SourceHardwareAddr (bytes 4–5) TargetHardwareAddr (bytes 0–1) SourceProtocolAddr (bytes 0–1) HLen = 48PLen = 32Operation SourceHardwareAddr (bytes 0–3) 081631

45. Internet Control Message Protocol (ICMP) l Echo (ping) l Redirect (from router to source host) l Destination unreachable (protocol, port, or host) l TTL exceeded (so datagrams don’t cycle forever) l Checksum failed l Reassembly failed l Cannot fragment

46. Summary