Last, but not least,
I'll explain how you can deploy any variant of FTP
using IPv6 as the layer 3 transport.
Some FTP variants require new messages to deal with such a change,
while others handle it seamlessly.
Let's dive in.
For completeness, I'll review all of the FTP variants shown in this course,
rather than just a subset.
Both FTP active and passive modes require new messages to support IPv6,
and we will start with that.
We will spend most of our time here.
Because FTPS and SFTP are encrypted,
we won't directly see the differences in Wireshark,
but I'll be sure to explain them.
TFTP is a simple protocol,
so it's no trouble to explore the entire packet
captures for uploads and downloads.
We'll do that next.
It would be very repetitive if I detailed how to secure each IPv6 option,
given the similarities to IPv4,
but it's important for me to summarize the key details.
You might be thinking, FTP is just an application.
It shouldn't matter whether it rides over IPv4 or IPv6.
You're right, it shouldn't, but it does.
The original FTP RFC 959 specifically mentions that the port
command carries exactly 6 comma-separated bytes,
4 bytes for the network address and 2 bytes for the TCP port.
IPv6 did not exist in 1985.
IPv6 FTP operates differently.
Suppose we are starting a new FTP file transfer from our FTP client
to our FTP server using the IPv6 addresses shown.
The client asks the server what features it supports.
The server replies with a large list, but I want to highlight the extended port and extended passive messages.