890:126c::1:10 49440 3.2695 2001:14b8:138:0:f4a2:39ea:d220:37ac 2001:1890:126c::1:1e GET / 3.4768 2001:1890:126c::1 2001:14b8:138:0:f4a2:39ea:d220:37ac http > 3.4812 2001:1890:126c::1:1e 2001:14b8:138:0:f4a2:39ea:d220:37ac 19 3.4845 2001:1890:126c::1:1e 2001:14b8:138:0:f4a2:39ea:d220:37ad [TCP 5 Frame 18 (1414 bytes on wire, 1414 bytes captured) Ethernet II, Src: 00:23:69:5b:6d:f9 (00:23:69:5b:6d:f9), Dst: c4:17:fe:47:35:f5 (c4:17:fe:47: Internet Protocol Version 6 Version: 6 Traffic class: 0x00 Flowlabel: 0x00000 Payload length: 1360 Next header: TCP (0x06) Hop limit: 40 Source address: 2001:1890:126c::1:1e Destination address: 2001:14b8:138:0:f4a2:39ea:d220:37ac Transmission Control Protocol, Src Port: http (80), Dst Port: 49440 (49440), Seq: 1, Ack: 243 Source port: http (80) Destination port: 49440 (49440) Sequence number: 1 (relative sequence number) [Next sequence number: 1341 (relative sequence number)] Acknowledgement number: 243 (relative ack number) Header length: 20 bytes Flags: 0x10 (ACK) window size: 6432 checksum: 0x5e38 [correct] TCP segment data (1340 bytes) Figure 3.35 Example: highlighting TCP packet sizes and MTU. the DHCPv6 and DNS. To really help readers jump into the 3GPP specific features in the next chapter, we also introduced different models of links that can transport IPv6. The chapter ended with detailed real-life IPv6 packet captures and explanations of each message shown. The packet captures and their analysis should help to get up to speed with IPv6 traffic debugging and analysis - at least the packet traces will not look all that scary after studying these examples. This chapter has provided general descriptions of IPv6 and will prove to be helpful when reading how IPv6 is used and applied on 3GPP accesses. References 1. Jankiewicz, E., Loughney, J., and Narten, T. IPv6 Node Requirements. RFC 6434, Internet Engineering Task Force, December 2011. 2. Singh, H., Beebee, W., Donley, C., Stark, B., and Troan, O. Basic Requirements for IPv6 Customer Edge Routers. RFC 6204, Internet Engin