Multicast and IPv6 - Stanford Secure Computer Systems Group

More documents

Recommendations

Info

MTU Requirement• IPv4 requires a 576-byte link MTU• <strong>IPv6</strong> requires 1280-byte MTU• If link MTU is smaller, then it MUST supportsub-IP fragmentation <strong>and</strong> assembly to provide a1280-byte MTU• It SHOULD provide a 1500-byte MTU; nodesMUST receive 1500 byte packets
Fragmentation Revisited• High-loss links (e.g., wireless) can be a problem• 10-hop route, each link has a 10% drop rate (90%success rate)- Probability one fragment arrives is 0.9 10 ≈ 35%- Each fragment is transmitted1 + 0.9 + 0.9 2 + 0.9 3 ...0.9 9 ≈ 6.5 times along the route- 100% chance on first hop, 90% on second hop, 81% on thirdhop, etc.
Page 2 and 3: Overview• Next generation IP: IPv
Page 4: IPv6• Work started in 1994• Bas
Page 7 and 8: IPv6 HeaderVer Class FlowLength Nex
Page 9 and 10: IPv6 Addresses• Simplify DHCP and
Page 11 and 12: v4 Interoperability, continued• T
Page 13 and 14: IP Tunneling• Encapsulate an IP p
Page 15 and 16: Other Tunneling Use: VPN• Virtual
Page 17: Example Next Header Values• 0: Ho
Page 21 and 22: Link-layer reliability• High-loss
Page 23 and 24: IPv4 Status
Page 25 and 26: Flaw in the Argument• Original IP
Page 27 and 28: 6lowpan and the Internet of Things
Page 29 and 30: 6lowpan• IETF working group on IP
Page 31 and 32: 6lowpan Header Compression• draft
Page 33 and 34: 2-minute stretch
Page 35 and 36: Multicast Approach• Nodes can joi
Page 37 and 38: Network TopologyBAR1R2R3R4R5CR6R7
Page 39 and 40: Tree for B as Multicast SourceBAR1R
Page 41 and 42: IP Anycast
Page 43 and 44: Anycast at IP layer• DNS allows a
Page 45 and 46: • A /32 routing entry!The Cost•
Page 47: Overview• Next generation IP: IPv

Multicast and IPv6 - Stanford Secure Computer Systems Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?