From owner-freebsd-current  Mon Jan 22 14:12:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA20766
          for current-outgoing; Mon, 22 Jan 1996 14:12:54 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA20752
          for <current@FreeBSD.ORG>; Mon, 22 Jan 1996 14:12:50 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.3/8.7.3) with SMTP id OAA06404; Mon, 22 Jan 1996 14:11:27 -0800 (PST)
Message-Id: <199601222211.OAA06404@precipice.shockwave.com>
To: -Vince- <vince@apollo.COSC.GOV>
cc: "Garrett A. Wollman" <wollman@lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: finger problem going from 2.1R to -current 
In-reply-to: Your message of "Mon, 15 Jan 1996 13:07:41 PST."
             <Pine.BSF.3.91.960115130648.20064j-100000@apollo.COSC.GOV> 
Date: Mon, 22 Jan 1996 14:11:27 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@FreeBSD.ORG
Precedence: bulk


  From: -Vince- <vince@apollo.COSC.GOV>
  Subject: Re: finger problem going from 2.1R to -current 
  On Mon, 15 Jan 1996, Garrett A. Wollman wrote:
  
  	Cisco has RFC1323 and RFC1644 broken according to Justin...

That's not correct, according to Paul.  We handle and negotiate T/TCP
sessions just fine.  If someone believes otherwise, please send me a
tcpdump of the failure and I'll look into it.

pst@cisco.com