[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EOS Row Operations (and other documents)
- To: "EOS WG (E-mail)" <eos@ops.ietf.org>
- Subject: Re: EOS Row Operations (and other documents)
- From: "Joel M. Halpern" <joel@longsys.com>
- Date: Mon, 26 Mar 2001 12:57:07 -0500
- Delivery-date: Mon, 26 Mar 2001 09:58:32 -0800
- Envelope-to: eos-data@psg.com
I listened to the discussion at the working group, and then read Lauren's
description, and I am confused. What is the behavior / need / ... that
this work item is addressing that is not addressed just by people using
creatAndGo?
Yours,
Joel M. Halpern
At 08:08 AM 3/24/01 -0800, Lauren Heintz wrote:
> - A new RowStatusLite TC (actual name yet to be determined)
> This TC will represent an evolvement from the current
> RowStatus TC. RSLite will not include a createAndWait status,
> and will require implmentations to support other extended features
> such as the SetRow PDU. I personally wonder if the row timeout
> requirement for NotInService states is still required, because I
> believe that overly complicates configuration chores (I think NIS
> should be a valid, persistent conceptual config state).