Re: [Ibnemo] role based intent

["Susan Hares" <[e-mail]>]

Tiaran/Terence: 

 

Very interesting concept.  It is the grouping of roles that make the intent
layer.  We look to this grouping the top of very specific acyclic graphs of
lower layer functions.  This emergence of the intent out of the essence of
being is a new thought.  Your theoretical examples are very interesting -
but can you give me an example. 

 

In another two field (organizational dynamics and general systems theory),
you are talking about groupings of functions emerging as systems.   Does
this  formal language John Strassner was suggesting something like this
idea? 

 

This is really insightful concept.  Can you give me  an example? 

 

Sue 

 

From: Ibnemo [mailto:[e-mail]] On Behalf Of Zhoutianran
Sent: Wednesday, June 03, 2015 2:30 AM
To: Dave Hood; STUART VENTERS; Natale, Bob
Cc: [e-mail]; [e-mail]
Subject: [Ibnemo] role based intent

 

Hi Dave, Stuart, Bob and all,

 

I found many problems raised in the mailing list are coursed by the layered
intent thinking. Maybe we are tainted by the ISO model:-)

 

For the layered intent, intent is a spectrum, very abstract at the top
layer, more network specific and less abstract when the layer goes down. The
problem is that the boundary of intent and non intent is vague. Or there is
no boundary between this two, since one's what may be another one's how. And
consequently, it looks like everything is intent and no clear intent
definition.

 

The role based intent will provide only one intent layer. That is always the
top layer abstraction for each role, as shown in the following figure. The
functions can be layered as the implementation of the intent layer.



With the role based intent, although the end user's intent is much
abstracted then the network administrator's intent, they are not related
each other. I.e., the end user will not use the administrator's intent. And
the admin will not provide additional services/interfaces to the end user.

 

The essential of layering is that the lower layer will provide interface to
the higher layer. In order to fit up layer requirements, the lower layer
will provide adequate interfaces/capabilities. That also means too much
information for a dedicated up layer user/app.

 

For role based intent, we can firstly indentify various roles (no need to be
complete, but those with attention), and then figure out the intent of each
role. In this way, intent can be clear defined. That will also keep the
intent of each role to a small set on what they really cares about, without
expending to support other one's intent.

 

 

Best Regards,

Terence