Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!VITAM6.UUCP!baker From: baker@VITAM6.UUCP (Fred Baker) Newsgroups: comp.protocols.tcp-ip Subject: TCP Fletcher Checksum Option Message-ID: <8911300048.AA01598@uunet.uu.net> Date: 30 Nov 89 00:45:15 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 12 That's actually an interesting idea. BUT, why not simply reuse the TCP checksum field? If the use of the new checksum has been negotiated, then the standard checksum is useless except as a component of the Fletcher Checksum, and any implementation which negotiates to use Fletch will by definition understand the change. I disagree, however, that TCP will only use this on folks known to support it. I think it will always ask and sometimes get a positive response. Otherwise, you need some kind of extra-architectural configuration table. Fred Baker baker@vitalink.com Brought to you by Super Global Mega Corp .com