[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: partial locking
Eliot,
Just to make sure that I understand the requirement here. Do you assume
that the data is writeable only by NETCONF? What if another protocol may
change the same set of data or part of it?
Dan
> -----Original Message-----
> From: owner-netconf@ops.ietf.org
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Eliot Lear
> Sent: Friday, August 31, 2007 12:43 PM
> To: Andy Bierman
> Cc: David Harrington; 'Netconf (E-mail)'
> Subject: Re: partial locking
>
>
> Should NETCONF impose a write-lock on the data then it
> shouldn't be writable to other applications, be that SNMP, or
> for that matter the CLI. An error should be returned. In
> other words, the lock interface needs to be below the
> external protocol interface. This can prove Challenging in
> some implementations, but it's still the right thing to do.
> I'm a little leery (perhaps evena little LEARy) about
> attempting to codify coherency of this form within the IETF,
> but I could be convinced. Customers, on the other hand, can
> codify anything they want in their RFPs...
>
> --
> to unsubscribe send a message to netconf-request@ops.ietf.org
> with the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/netconf/>
>
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>