Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!NNSC.NSF.NET!craig From: craig@NNSC.NSF.NET (Craig Partridge) Newsgroups: comp.protocols.tcp-ip Subject: re: TCP Fletcher Checksum Option Message-ID: <8911301513.AA28635@ucbvax.Berkeley.EDU> Date: 30 Nov 89 13:25:45 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 25 Johnny: If you are seriously interested in seeing such an option become available, it is pretty easy to get the process started to standardize it. Given this is a very simple thing to specify (it is a one page RFC describing the option format) I suggest you write up the one page RFC for a TCP checksum-type option sent in the SYN (I'd suggest allowing other checksums besides Fletcher's to be specified). Make sure that when a host that doesn't recognize the option silently ignores it, the TCP connection will continue to use the TCP checksum. Then send that draft to me and I'll arrange a meeting at the next Internet Engineering Task Force meeting (in February) to review it. If it's approved at that meeting, there's a good chance we can roll it out as an "if you are going to do this, do it this way" option sometime in mid-1990. Craig Partridge IETF Area Director, Host-Based and User Services PS: IETF meetings are open to anyone who wants to attend. The next IETF meeting is in Tallahassee Florida in February. To keep track of what's up in IETF, I suggest you join the IETF list (ietf-request@isi.edu). Brought to you by Super Global Mega Corp .com