IETF Logo Mail Archive

Re: ISPACs

Tony Li <tli@jnx.com> Mon, 09 December 1996 01:14 UTC

Received: from cnri by ietf.org id aa29788; 8 Dec 96 20:14 EST
Received: from nico.aarnet.edu.au by CNRI.Reston.VA.US id aa17223; 8 Dec 96 20:14 EST
Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id LAA22949 for <cidrd@iepg.org>; Mon, 9 Dec 1996 11:20:21 +1100
Received: from chimp.jnx.com (chimp.jnx.com [208.197.169.246]) by red.jnx.com (8.8.3/8.8.3) with ESMTP id QAA18538; Sun, 8 Dec 1996 16:20:18 -0800 (PST)
Received: (from tli@localhost) by chimp.jnx.com (8.7.6/8.7.3) id QAA28014; Sun, 8 Dec 1996 16:19:59 -0800 (PST)
Date: Sun, 08 Dec 1996 16:19:59 -0800
Message-Id: <199612090019.QAA28014@chimp.jnx.com>
From: Tony Li <tli@jnx.com>
To: presnick@research.att.com
CC: justin@erols.com, cidrd@iepg.org
In-reply-to: <2.2.32.19961208144116.008ce638@raptor.research.att.com> (message from Paul Resnick on Sun, 08 Dec 1996 09:41:16 -0500)
Subject: Re: ISPACs

   Tony's answer suggests that an ISPAC is an upstream interconnect provider
   collectively owned by the downstream ISPs. If I'm interpreting correctly,
   then the proposal is a purely business innovation, and not a technical one
   at all. I have no problem with that, but I want to make sure I'm
   understanding correctly.

Largely yes.  It has some quasi-technical effects, such as address
allocation to the ISPAC as an organizational entity.

Tony

v2.23.0 | Report a Bug | By Email