[Policy][Security]Long Term Research Collaboration


Zhipeng Huang
 

Hi TOC members,

In today's Policy WG's meeting[0] we discussed the possibility of introducing formal verification into the cloud native world in conjunction with policy engine, to form a complete cloud native policy architecture. However formal verification is not a subtle work and requires significant work on theoretic side. I'm wondering is there any mechanism within CNCF that we could do long term research collaboration ?

We believe this will hugely benefit Kubernetes, Istio and many other cloud native platforms in general to have formal verification capability. Other research topics could include things like security protocol building (e.g. noise framework) which would be also quite interesting.



--
Zhipeng (Howard) Huang

Principle Engineer
OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C


Chris Aniszczyk
 

Could this work be done under the new Governance/Security SIG forming?

I'm not sure what the specific ask is here outside of a place to
collaborate / meet maybe?

On Wed, Apr 3, 2019 at 7:27 PM Zhipeng Huang <zhipengh512@...> wrote:

Hi TOC members,

In today's Policy WG's meeting[0] we discussed the possibility of introducing formal verification into the cloud native world in conjunction with policy engine, to form a complete cloud native policy architecture. However formal verification is not a subtle work and requires significant work on theoretic side. I'm wondering is there any mechanism within CNCF that we could do long term research collaboration ?

We believe this will hugely benefit Kubernetes, Istio and many other cloud native platforms in general to have formal verification capability. Other research topics could include things like security protocol building (e.g. noise framework) which would be also quite interesting.

[0] https://docs.google.com/document/d/1ihFfEfgViKlUMbY2NKxaJzBkgHh-Phk5hqKTzK-NEEs/edit?usp=sharing


--
Zhipeng (Howard) Huang

Principle Engineer
OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Zhipeng Huang
 

Like finding the right team from universities that we could collaborate with, many even funding at certain level if needed ? Basically we need a communication channel and a defined mechanism for collaboration. 

Definitely could be sponsored as part of the governance/security sig effort :) 

On Thu, Apr 4, 2019 at 8:34 AM Chris Aniszczyk <caniszczyk@...> wrote:
Could this work be done under the new Governance/Security SIG forming?

I'm not sure what the specific ask is here outside of a place to
collaborate / meet maybe?

On Wed, Apr 3, 2019 at 7:27 PM Zhipeng Huang <zhipengh512@...> wrote:
>
> Hi TOC members,
>
> In today's Policy WG's meeting[0] we discussed the possibility of introducing formal verification into the cloud native world in conjunction with policy engine, to form a complete cloud native policy architecture. However formal verification is not a subtle work and requires significant work on theoretic side. I'm wondering is there any mechanism within CNCF that we could do long term research collaboration ?
>
> We believe this will hugely benefit Kubernetes, Istio and many other cloud native platforms in general to have formal verification capability. Other research topics could include things like security protocol building (e.g. noise framework) which would be also quite interesting.
>
> [0] https://docs.google.com/document/d/1ihFfEfgViKlUMbY2NKxaJzBkgHh-Phk5hqKTzK-NEEs/edit?usp=sharing
>
>
> --
> Zhipeng (Howard) Huang
>
> Principle Engineer
> OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C
>


--
Chris Aniszczyk (@cra) | +1-512-961-6719


--
Zhipeng (Howard) Huang

Principle Engineer
OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C