From owner-freebsd-isp Thu Feb 25 6:55: 6 1999 Delivered-To: freebsd-isp@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3783A14CF3 for ; Thu, 25 Feb 1999 06:54:58 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port46.netsvr1.cst.vastnet.net [207.252.73.46]) by etinc.com (8.8.8/8.6.9) with SMTP id JAA14731; Thu, 25 Feb 1999 09:55:53 -0500 (EST) Message-Id: <199902251455.JAA14731@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 25 Feb 1999 10:03:32 -0500 To: "Louis A. Mamakos" From: Dennis Subject: Re: cdrom.com bandwidth limits Cc: isp@freebsd.org In-Reply-To: <199902251434.JAA48676@whizzo.transsys.com> References: <199902231921.OAA03755@y.dyson.net> <36D3A26A.922CE5A9@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:34 AM 2/25/99 -0500, you wrote: >> "John S. Dyson" wrote: >> > >> > It is not likely to get that much due to protocol overheads, but I >> > have seen >160KBytes/sec on a good T1. Don't T1's do bit stealing >> > for signalling (I forget?) >> >> Unless you are on a "clear channel." If you are, the throughput is >> 24 x 64 Kbits/sec, if not, 24 x 64 Kbits/sec - 8 Kbits/sec. The bit >> stealing totals 8 Kbits/sec for the entire channel, regardless of how >> "big" the channel is. > >Some CSU/DSU's can be pretty stupid when framing the synchronous data coming >in for >transmission on the T1 span. The problem they face is that there is a >specific one's density requirement when pushing bits over the wire; if you >have too many zero bits in a row, then the T1 span will blow it's clocking. > >So, some really stupid CSU/DSU's will format the data where they "force" every >8th bit to a one. This is how you end up with 1344 kb/s of bandwidth. > >The other more common way to do this is to observe that most modern uses of >T1 spans for data transmission use HDLC bit-synchronous framing these days. >If the DSU inverts the data coming in, then the HDCL framing will ensure >adequate one's density on the T1 span. In this instance, you get to use >all 1536 kb/s of capacity (64kb/s*24 channels) of the T1 span. > >The 1544 kb/s number you see including the T1 frame overhead, and isn't >normally >available if you expect to push your bits though a transmission system with >other multiplexing equipment (M31 muxes, digital cross connect systems, etc.) > >louie > They are not "stupid"..it depends on the encoding in place. With ESF you get the extra bandwidth, which is what most lines use. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message