RE: IPS Draft Charter update

["VanArsdale, Lynne" <Lynne_VanArsdale@bmc.com>]

Storage involves issues related to data in place.  For instance, the data
stored needs to have longevity (reliability in place) and different kinds of
security.  Also, sharing has different meanings for data in place and data
on the move.  The words may be the same.  The application is, in part,
different.

lynne_vanarsdale@bmc.com
2101 City West Blvd
Houston, Texas  77042
( 713 ) 918 - 3167 (voice)
( 713 ) 918 - 1750 (FAX)
( 800 ) 791 - 4526 (pager)


-----Original Message-----
From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
Sent: Thursday, July 20, 2000 5:12 PM
To: Mark A. Carlson
Cc: Black_David@emc.com; ips@ece.cmu.edu; Lynne VanArsdale
Subject: Re: IPS Draft Charter update


"Mark A. Carlson" wrote:
...
> As far as this working group is concerned, the standards might take the
form of
> signaled service level objectives (requesting a certain performance goal,
for example)
> to the storage device or perhaps a protocol for negotiation of the service
level.
> Service level metrics, such as performance, availability and perhaps even
cost
> might be exposed through a storage MIB.

This seems very strange to me - why would any of this be specific to
storage? These sound like quite generic QOS issues. They are also very
tough ones, that the IETF has not yet got a handle on.

See draft-iab-qos-01.txt for more on what is missing in this area.

   Brian