Update identification and length

yakov@watson.ibm.com Mon, 04 May 1992 12:26 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa01189; 4 May 92 8:26 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa17406; 4 May 92 8:31 EDT
Received: from PARK-STREET.BBN.COM by NRI.Reston.VA.US id aa17402; 4 May 92 8:31 EDT
Received: from park-street by PARK-STREET.bbn.COM id aa16125; 4 May 92 8:14 EDT
Received: from BBN.COM by PARK-STREET.BBN.COM id aa16121; 4 May 92 8:12 EDT
Received: from watson.ibm.com by BBN.COM id aa18415; 4 May 92 8:12 EDT
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R2) with BSMTP id 0229; Mon, 04 May 92 08:12:19 EDT
Date: Mon, 4 May 92 08:12:17 EDT
From: yakov@watson.ibm.com
To: woody@sparta.com, idpr-wg@bbn.com
Subject: Update identification and length
Message-ID: <9205040831.aa17402@NRI.Reston.VA.US>

Ref:  Your note of Sat, 2 May 92 12:26:32 -0400

>Rather than reinventing the wheel, we may have to think
>about TCP....

That certainly sounds like an excellent idea. I wonder
why TCP wasn't used by IDPR from the beginning ?

Yakov.