From owner-freebsd-isp  Tue Sep 10 08:30:57 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA22546
          for isp-outgoing; Tue, 10 Sep 1996 08:30:57 -0700 (PDT)
Received: from patty.loop.net (patty.loop.net [204.179.169.20])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22539
          for <freebsd-isp@freebsd.org>; Tue, 10 Sep 1996 08:30:46 -0700 (PDT)
Received: from mlcoh.loop.com (mlcoh.loop.com [204.179.169.6]) by patty.loop.net (8.6.12/8.6.12) with SMTP id IAA01068 for <freebsd-isp@freebsd.org>; Tue, 10 Sep 1996 08:30:22 -0700
Message-Id: <199609101530.IAA01068@patty.loop.net>
Comments: Authenticated sender is <greg@pop.loop.com>
From: "Greg Wiley" <greg@loop.com>
Organization: The Loop
To: FreeBSD ISP List <freebsd-isp@freebsd.org>
Date: Tue, 10 Sep 1996 08:31:27 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: T1 offc. resell config
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42)
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

If you fractionalize your T-span, you'll need a routing port or 
switched virtual circuit port for each fraction you sell.  Why not,
instead, create an ethernet backbone resource for the building and
charge tenants to hang on to that?  You'll be capitalizing on the
bursty nature of Inet traffic and so maintaining higher throughput
for individual transactions.

If you want differentiate usage levels, you could set up some kind
of IP accounting but it might not be worth it.

  -greg