Re: [I2nsf] Service Layer Policies - Post 0: note structure

[DIEGO LOPEZ GARCIA <[e-mail]>]

Hi,

I support this. I think it is good to be aligned with common usage of terms, unless there are very good reasons to do otherwise.

Just for the record, we are collecting some of the (already mature) results of the SECURED project policy efforts into a document we will contribute anytime soon. I hope we will be well aligned with John’s ideas.

Be goode,

On 7 Dec 2015, at 22:25 , Linda Dunbar <[e-mail]<mailto:[e-mail]>> wrote:

John,

Thank you very much for structuring the discussion. This is very helpful.


Maybe I am jumping ahead. For Post 5,  the “object” currently used in I2NSF framework is same as the  “Condition” in PCIM to describe the constraints. If no one disagree, I propose to align with PCIM, i.e. call it “Subject-Condition-Action-Function”.

Regards,
Linda

From: I2nsf [mailto:[e-mail]] On Behalf Of John Strassner
Sent: Sunday, December 06, 2015 7:00 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [I2nsf] Service Layer Policies - Post 0: note structure

The I2NSF framework draft mentions PCIM (RFC3060) and PCIMe (RFC3460) as possible candidates for guiding the policy structure that can be mapped to the Capability Layer's "Subject-Object-Action-Function" paradigm.
During IETF94, I expressed discomfort with the above paradigm. However, this is a complex subject, and is more easily understood by breaking this up into smaller discussions. Here is the order of notes that I will post:

   Post 0:  this post
   Post 1:  problems in using PCIM
   Post 2:  problems in using PCIMe
   Post 3:  differentiating between groups and roles
   Post 4:  differentiating between context, constraints, and conditions
   Post 5:  specific worries about the "Subject-Object-Action-Function" paradigm
   Post 6:  proposed replacement policy structure

Posts 1 and 2 clarify the problems in using PCIM and PCIMe, respectively, which I volunteered to do.

Posts 3 and 4 are fundamental to posts 5 and 6, as they represent software building blocks that are critical for designing and implementing Service Policies in a scalable and robust manner. These also expand on points in posts 1 and 2.

Post 5 is the heart of the manner, but can't really be tackled until the preceding posts were done. Post 6 builds on the previous posts.

regards,
John
--
regards,
John
_______________________________________________
I2nsf mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/i2nsf

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: [e-mail]<mailto:[e-mail]>
Tel:    [phone]
Mobile: [phone]
----------------------------------


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição