Re: Draft minutes for IETF Network Status Reports. - please comment.
Pushpendra Mohta <pushp@cerf.net> Fri, 12 August 1994 20:20 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10293; 12 Aug 94 16:20 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10289; 12 Aug 94 16:20 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa16132; 12 Aug 94 16:20 EDT
Received: from mystic.cerf.net (mystic.cerf.net [192.153.156.11]) by merit.edu (8.6.8.1/merit-1.0) with ESMTP id PAA24254; Fri, 12 Aug 1994 15:39:59 -0400
Received: from localhost (pushp@localhost) by mystic.cerf.net (8.6.4/8.6.4) id MAA21461; Fri, 12 Aug 1994 12:37:03 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Pushpendra Mohta <pushp@cerf.net>
Message-Id: <199408121937.MAA21461@mystic.cerf.net>
Subject: Re: Draft minutes for IETF Network Status Reports. - please comment.
To: Gene Hastings <hastings@psc.edu>
Date: Fri, 12 Aug 1994 12:37:02 -0700
Cc: njm@merit.edu, nanog@merit.edu, Pushpendra Mohta <pushp@mystic.cerf.net>
In-Reply-To: <9408101140.AA06128@mailer.psc.edu> from "Gene Hastings" at Aug 10, 94 07:40:36 am
X-USMAIL: CERFnet, P.O. BOX 85608, San Diego, CA 92186-9784
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Length: 2058
> > > > ================ > > Random Bits: > > > > SWAB (SMDS Washington Area Backbone): In response to point of confusion, > > it was stated that the SWAB bilateral agreement template is just a > > sample, not a requirement > > > > CIX: The CIX router is getting a T3 SMDS connection into the PacBell > > fabric. ALTERnet and PSI are doing so too. CERFnet currently is on. > > > > Noted in passing: Each SMDS access point can be used privately, to > > support customers, to enhance backbone, etc.... This could have serious > > implications for other provider agreements. > > > > CERFnet: Pushpendra Mohta (? --not at the meeting) is reported to be happy, > > but the group understood that most CERFnet CIRs are at 4Mbps over T3 > > entrance facilities. PacBell was reportedly running two 2OOMbps (is > > this the really correct, seems rather low?) backplane capacity switches > > interconnected with single T3. Planning to increase provisioning -- > > already have a lot of demand. > > Pacbell operates two switched in the Bay Area. One in San Francisco and one in Santa Clara. The former is practically full , and the latter is brand new. All new T3 orders will end up on the Santa Clara switch. It is true that the backplane of the switch is only 200Mbps. Because the Santa Clara switch is new, the switches are interconnected by only one T3 link. However, the switches are capable of more than one T3 link and the product manager at Pacbell ( Dick Shimizu ) has assured me that enough demand would warrant a new T3 between the switches etc. Providers thinking of buying T3 level services should specify the Santa Clara switch although it should end up being used anyway. I have alerted the Product manager and he will ensure that T3 circuits are on the SC switch. A new switch is being planned for early next year, although enough demand will accelerate that deployment as well --pushpendra Pushpendra Mohta pushp@cerf.net +1 619 455 3908 Director of Engineering pushp@sdsc.bitnet +1 800 876 2373 CERFNet
- Draft minutes for IETF Network Status Reports. - … Gene Hastings
- Re: Draft minutes for IETF Network Status Reports… Susan Hares
- Re: Draft minutes for IETF Network Status Reports… Pushpendra Mohta
- Re: Draft minutes for IETF Network Status Reports… Martin Lee Schoffstall
- Re: Draft minutes for IETF Network Status Reports… Curtis Villamizar