From owner-freebsd-isp Thu Feb 13 07:10:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA16415 for isp-outgoing; Thu, 13 Feb 1997 07:10:08 -0800 (PST) Received: from anacreon.sol.net (anacreon.sol.net [206.55.64.116]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA16392 for ; Thu, 13 Feb 1997 07:10:01 -0800 (PST) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by anacreon.sol.net (8.6.12/8.6.12) with ESMTP id JAA10750; Thu, 13 Feb 1997 09:09:30 -0600 Received: from localhost by solaria.sol.net (8.5/8.5) id JAA06403; Thu, 13 Feb 1997 09:09:25 -0600 From: Joe Greco Message-Id: <199702131509.JAA06403@solaria.sol.net> Subject: Re: Net connection guidelines To: batie@agora.rdrop.com (Alan Batie) Date: Thu, 13 Feb 97 9:09:19 CST Cc: isp@freebsd.org In-Reply-To: from "Alan Batie" at Feb 13, 97 08:59:40 am X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Recently, I saw a nice little summary of bandwidth guidelines, e.g. if > you're reselling T1's, you need one upstream T1 for every 4 downstream > T1's, plus something similar for end users (x 28.8's -> 56K, y 28.8's -> T1) > Of course, now that I've been asked about such metrics, I've lost the > reference. Any ideas? Thanks... It's all dependent on your utilization patterns. If your customers are not really _using_ the T1 too much, you can overcommit fifty to one (I know some organizations that approached that number). If you have folks like me living on a downstream T1, you'll be lucky to get two to one. Four to one is probably a reasonable "worst case" guess, you should be able to go as high as ten to one, as long as the organizations that you are connecting are not whapping the daylights out of their links. Any more detailed advice requires some analysis of your existing network traffic (or, if you don't have any yet, you need to set it up and _see_). When pricing your services, remember this: Many ISP's are looking to cover the cost of their existing (single) T1 when they price their services. That is almost invariably a mistake, in my opinion. You should assume that it will take you two T1's (to different providers) to get reliable single-T1 bandwidth. That may change somewhat when you grow, but historically it's been easier to lower prices a bit down the road than to raise them. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847