Re: Ever onward

[Rob Enns <rpe@juniper.net>]

Seems like this would be an issue only if the router was virtualized, but
the netconf interface to it wasn't. That's pretty unlikely, since the
mgmt interface would be virtualized along with the router itself.

That said, the global lock will be limiting even on a busy BRAS box
where there are multiple provisioning activities being done concurrently.
We recognized this in past meetings (ie. everyone agrees partial
locks are nice) but agreed to leave partial locks out of the initial
core document.

Rob

On Wed, Feb 04, 2004 at 10:50:01AM -0800, Randy Presuhn wrote:
> Hi -
> 
> Is anyone planning to allow different customers to
> use netconf to manage their respective interfaces
> on e.g. POP gear?  It seems that global locks would
> permit one customer to (inadvertantly) cause problems
> both for other customers as well as the equipment's
> owner.  Just the amount of time needed to type in
> a configuration could cause grief for other users.
> 
> Randy
> 
> 
> 
> --
> 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/>