[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thoughts on NetConf Requirements

To: abierman@cisco.com
Subject: Re: Thoughts on NetConf Requirements
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Thu, 5 Jun 2003 10:36:12 +0200
Cc: randy@psg.com, dperkins@dsperkins.com, kevinm@andrew.cmu.edu, netconf@ops.ietf.org
In-reply-to: <4.3.2.7.2.20030604142148.023ca900@mira-sjc5-c.cisco.com>(message from Andy Bierman on Wed, 04 Jun 2003 14:33:48 -0700)
References: <274753314.1054652094@portatool.dhcp.nanog28.merit.net><5.2.0.9.2.20030603140800.037e66e0@127.0.0.1> <4.3.2.7.2.20030604142148.023ca900@mira-sjc5-c.cisco.com>

>>>>> Andy Bierman writes:

Andy> So what's so complex about reads? The authorization model?  IMO,
Andy> the authorization model amounts to a set of tuples: { user,
Andy> operations-allowed, element-subtree }. 

Make that typle { user, operations-allowed, filter } and I am much
more happy. ;-)

Andy> I hope we all can agree that the essence of good engineering is
Andy> how simple you can make the solution, not how complex it can be.

Yes. The only problem is how to measure simplicity. ;-)

/js

--
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/>

References:
- Thoughts on NetConf Requirements
  - From: Kevin C Miller <kevinm@andrew.cmu.edu>
- Re: Thoughts on NetConf Requirements
  - From: "David T. Perkins" <dperkins@dsperkins.com>
- Re: Thoughts on NetConf Requirements
  - From: Andy Bierman <abierman@cisco.com>

Prev by Date: Re: Thoughts on NetConf Requirements
Next by Date: Re: Thoughts on NetConf Requirements
Previous by thread: Re: Thoughts on NetConf Requirements
Next by thread: Re: Thoughts on NetConf Requirements
Index(es):
- Date
- Thread