To:
ietf-provreg@cafax.se
From:
"Bason, Chris" <cbason@verisign.com>
Date:
Thu, 22 Mar 2001 13:53:39 -0500
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Design teams
> -----Original Message----- > From: Dave Crocker [mailto:dcrocker@brandenburg.com] > Sent: Wednesday, March 21, 2001 8:58 PM > To: Brian W. Spolarich > Cc: Jordyn A. Buchanan; Bill Manning; George Michaelson; > Peter Chow; Zhu > Yu; ietf-provreg@cafax.se > Subject: RE: Design teams > > > At 07:49 PM 3/21/2001, Brian W. Spolarich wrote: > > A particular implementation might open several connections to a > >given peer and use those in a similar manner to pooled database > >connections. > > Thank you for providing the glinching reason to use beep: > multiplexing > data streams over a single connection. (Multiple TCP > connections cause > problems.) > The use of multiplexing also introduces a problem in that when a TCP connection is dropped (for whatever reason) you lose ALL ongoing transactions through X number of data streams. X being the number of channels opened within the multiplexed TCP connection. > d/ > > > ---------- > Dave Crocker <mailto:dcrocker@brandenburg.com> > Brandenburg InternetWorking <http://www.brandenburg.com> > tel: +1.408.246.8253; fax: +1.408.273.6464 >