Re: [OT] CNN bragging about "FTP technology"

On 2005-08-31, Andrew Arensburger <arensb.no-bloody-spam@xxxxxxx> wrote:
> Longfellow <not@xxxxxxxxxxxx> wrote:
>> On 2005-08-30, Andrew Arensburger <arensb.no-bloody-spam@xxxxxxx> wrote:
>> > Longfellow <not@xxxxxxxxxxxx> wrote:
>> >> Gopher was the next step from Archie, IIRC. Or was there something
>> >> between?
>> >
>> > No, Gopher was sort of a primitive version of HTTP+HTML. It
>> > would present you with a directory tree, the leaves of which were
>> > documents that you could read. But there were no hyperlinks.
>> > Archie, on the other hand, was an indexing system; sort of an
>> > early version of Google. You'd give it a keyword or a filename, and it
>> > would tell you were that file could be found.
>
>> Ah yes. Archie was out of U of M, as I recall.
>
> Which U of M? Maine? Minnesota? Mississippi?

Michigan!! ;)

>> >> For the curious, there is in the TCPs a set of specifications for
>> > ^^^^
>> > Do you mean RFCs?
>
>> Well, yes. And in fact I erred. The specs for addresses aren't TCP,
>> they're IP.
>
> Addresses of the form 10.12.96.123 are IP. But IIRC you were
> talking about URLs. Those are neither TCP nor IP, but at a higher
> level.

Yep, you're correct. That's what domain name servers are for, right?

> [...]
>> TCP is the packet protocols, or did my brains fall out without my
>> noticing? AGAIN!?? LOL!!
>
> IP is the Internet Protocol, which specifies, at a
> comparatively low level, how to transmit data from one host to
> another.
> TCP sits above that, and adds things like making sure that
> data packets are put together in the right order at the receiving end;
> ensuring that if a packet makes it to the receiver, then the sender
> knows about it, and, conversely, if something goes wrong, the sender
> knows about it.
> HTTP, the main protocol used in the world-wide web, is an
> application protocol that sits on top of TCP. So is NNTP, without
> which Usenet wouldn't exist.

Well stated. IIRC, TCP packets get resent, UDP packets don't, or
something like that. I take it that you are a computer/IT professional?
I'm talking from memory over a decade old now.

Lessee... There are seven standard model layers of networking. From
bottom to top, we have machine, data, network, transport, session,
presentation and application. The machine, or physical layer, comprises
the hardware and cabling. The data layer defines the signal format and
transmission protocols. The network layer has to do with addresses,
data management (packets, etc), and data translation. The transport
layer monitors the transmission of data for reliability, error-checking,
etc. The session layer establishes and monitors connections. The
presentation layer deals with such things as data compression schemes.
And the application layer provides the port protocols like HTTP, SMPT,
POP3, NNTP, etc.

IIRC, IP is about the data and network layers, and TCP is about
transport and session layers, or something like that.

And at that point, memory fails, if I even got that correct. In any
case, we're way OT now, and I yield to the far more accurate knowledge
of those in the field.

Thanks for the error checking ;)

Longfellow

.

Relevant Pages

  • RE: Timeout strategy: terminal vs Telnet drivers
    ... >>> layer may or may not send them as individual packets. ... > The context was Telnet which IS an application wrt TCP ...
    (comp.os.vms)
  • Re: NDIS miniport Driver - packet re-ordering
    ... receiver issue? ... You might fail on WDK NDIS testing if your packets are not ordering. ... I've reviewed the TCP / IP Layer concepts in wikipedia.org. ...
    (microsoft.public.development.device.drivers)
  • Re: Need a script to understand names posts
    ... the physical layer of the ISO model, augmented by providing all of the logic ... a network model that does more than just detect the fact that packets ... and brings them back onto the network as if they had never been lost. ... the packets previously lost will never ever be lost again, ...
    (microsoft.public.scripting.wsh)
  • Re: network programming
    ... how an IP header is formed and in what OSI layer they fit. ... Sockets abstract part of the transport layer. ... packets so if you need them you may have to use FFI to access the OS ...
    (comp.lang.lisp)
  • Re: [DLM] Add support for tcp communications [38/70]
    ... [DLM] Add support for tcp communications ... The following patch adds a TCP based communications layer ...
    (Linux-Kernel)