From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Today I learned something new about File Transfer Protocol.
Date: Sat, 7 Jul 2018 23:17:43 -0600 [thread overview]
Message-ID: <4d26a222-b3d8-eb17-3d61-4d2c1d69fefb@spamtrap.tnetconsulting.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]
Today I learned that File Transfer Protocol supports transferring data
between two remote systems without passing the data through a
controlling host.
The end of § 2.3, The FTP Model, of RFC 959, File Transfer Protocol,
states the following:
"""
In another situation a user might wish to transfer files between two
hosts, neither of which is a local host. The user sets up control
connections to the two servers and then arranges for a data connection
between them. In this manner, control information is passed to the
user-PI but data is transferred between the server data transfer
processes. Following is a model of this server-server interaction.
Control ------------ Control
---------->| User-FTP |<-----------
| | User-PI | |
| | "C" | |
V ------------ V
-------------- --------------
| Server-FTP | Data Connection | Server-FTP |
| "A" |<---------------------->| "B" |
-------------- Port (A) Port (B) --------------
"""
I also learned that FTP uses (a subset of) the Telnet protocol for it's
control connection. Yet another reason to dislike it. (I strongly
prefer 8-bit clean connections and dislike things that need special
handling.)
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20180707/ec76f8f9/attachment.bin>
next reply other threads:[~2018-07-08 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 5:17 gtaylor [this message]
2018-07-08 20:28 ` perry
2018-07-09 3:30 ` gtaylor
2018-07-09 3:36 ` imp
2018-07-09 4:02 ` gtaylor
2018-07-09 11:27 ` perry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d26a222-b3d8-eb17-3d61-4d2c1d69fefb@spamtrap.tnetconsulting.net \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).