Re: tcp connection
At 12:50 AM 6/19/00 +0200, Russell Coker wrote: >It is called TCP - Transmission Control Protocol. RFC793. I'm starting to conclude that it's just called a "tcp connection". But I'm still reading through the RFC... It was written in 1983 and for whatever reason it seems to use the term socket and port interchangeably. Seems like they had different meanings than they do now. I guess it's just coincidence that the common high level protocols all use the same NVT settings. Otherwise, telneting to a web server would fail. Maybe its the NVT settings that are the highest common thread here, does that standard have a name I wonder. >If you have doc-rfc package installed: >file:/usr/doc/doc-rfc/rfc793.txt.gz Don't got that, but I found faqs.org. >Anyone who calls the protocol "Transport Control Protocol" is stupid and >should be ignored. Instruct such people to read the documents and learn. I've never heard anybody call it that. >PS There's no need to read 2500 RFC. A zgrep of the indexes will usually >allow you to find what you want rapidly. I was being facetious. :) +---+ |-=I T ' S P R I N C I P L E T H A T C O U N T S=- | |=- -=ALAN KEYES FOR PRESIDENT=- -=| | Balanced Budgets Personal Freedoms Morality Lower Tax | |=-- http://www.Keyes2000.com. --=| ++
Re: tcp connection
At 12:50 AM 6/19/00 +0200, Russell Coker wrote: >It is called TCP - Transmission Control Protocol. RFC793. I'm starting to conclude that it's just called a "tcp connection". But I'm still reading through the RFC... It was written in 1983 and for whatever reason it seems to use the term socket and port interchangeably. Seems like they had different meanings than they do now. I guess it's just coincidence that the common high level protocols all use the same NVT settings. Otherwise, telneting to a web server would fail. Maybe its the NVT settings that are the highest common thread here, does that standard have a name I wonder. >If you have doc-rfc package installed: >file:/usr/doc/doc-rfc/rfc793.txt.gz Don't got that, but I found faqs.org. >Anyone who calls the protocol "Transport Control Protocol" is stupid and >should be ignored. Instruct such people to read the documents and learn. I've never heard anybody call it that. >PS There's no need to read 2500 RFC. A zgrep of the indexes will usually >allow you to find what you want rapidly. I was being facetious. :) +---+ |-=I T ' S P R I N C I P L E T H A T C O U N T S=- | |=- -=ALAN KEYES FOR PRESIDENT=- -=| | Balanced Budgets Personal Freedoms Morality Lower Tax | |=-- http://www.Keyes2000.com. --=| ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tcp connection
On Sun, 18 Jun 2000, Chris Wagner wrote: >What I meant by that was what "octets mean and do" in terms of establishing >and maintaining the connection. Like, what octets are exchanged that tell >each machine, "yes the connection is established". That protocol has a name. It is called TCP - Transmission Control Protocol. RFC793. If you have doc-rfc package installed: file:/usr/doc/doc-rfc/rfc793.txt.gz Anyone who calls the protocol "Transport Control Protocol" is stupid and should be ignored. Instruct such people to read the documents and learn. Russell Coker PS There's no need to read 2500 RFC. A zgrep of the indexes will usually allow you to find what you want rapidly.
Re: tcp connection
On Sun, 18 Jun 2000, Chris Wagner wrote: >What I meant by that was what "octets mean and do" in terms of establishing >and maintaining the connection. Like, what octets are exchanged that tell >each machine, "yes the connection is established". That protocol has a name. It is called TCP - Transmission Control Protocol. RFC793. If you have doc-rfc package installed: file:/usr/doc/doc-rfc/rfc793.txt.gz Anyone who calls the protocol "Transport Control Protocol" is stupid and should be ignored. Instruct such people to read the documents and learn. Russell Coker PS There's no need to read 2500 RFC. A zgrep of the indexes will usually allow you to find what you want rapidly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
