Date: Tue, 30 Sep 1997 15:33:16 -0700
From: Russ Hobby <rdhobby@ucdavis.edu>
To: Elise Marie Meyer <emm@physics.ucsb.edu>, cenic-tpg@ucdavis.edu
Subject: Re: CalREN-2 Query

Elise, Kevin,

I think that the I2 Campus Networking Workshop that we held here
on the 15-16 came to a lot of the the same conclusions that you
did.  The protocols that are being developed in the IETF provide
some of the pieces but there are still a lot of holes in
providing the overall I2 fuctionality, in particular, QoS and
multicast.  Even those pieces that are coming out of the IETF
have quite aways to go but I2 (and CalREN-2) can help push them
along by trying them out learning what works.  In general the
workshop came up with more problems than answers, but it is still
good to have the problems enumerated.

I think the general consensus at the workshop was that for the
first step, the traditional approach of bandwidth overkill is the
only way to support QoS on campus.  The next easiest thing to do
is implement a few priority queues (minimum of 2 ;-) to provide
differentiated service.  Access control into to the higher
priority will be critical if it is to fuction any better than the
lower queues.  Access mechanisms to the queues could be by user
(high priority on available to I2 apps developers for example),
or by application if there is a way to identify it.  RSVP may be
able to provide a mechanism for entry into access control but I
would guess that will take a bit before we get there.

Anyone else have a crystal ball that is less cloudy?

Russ