Re: [I2nsf] I2NSF Re-chartering Text

[Yoav Nir]

Does Thursday, December 3rd at 14:00 UTC work for everyone?

It’s 16:00 for me, 15:00 for much of Europe, 9:00 AM EST, 6:00 AM PST, and 
unfortunately, 23:00 in Seoul.

I’ll wait 24 hours before scheduling the meeting in case there are objections.

Yoav


> On 16 Nov 2020, at 3:44, Mr. Jaehoon Paul Jeong  
> wrote:
> 
> Hi Yoav,
> I agree that we can schedule our online interim meeting on the week of the 
> 29th / first week of December.
> 
> Could you schedule such an interim meeting?
> 
> I believe that we can get more people to be engaged in the new I2NSF work 
> items
> other than the authors of the current I2NSF WG and individual drafts.
> With those people, I hope our I2NSF WG can have more energy. :)
> 
> Thanks.
> 
> Best Regards,
> Paul
> 
> On Mon, Nov 16, 2020 at 1:59 AM Yoav Nir  > wrote:
> Hi, Paul
> 
> As Roman said in a separate email message, we can’t schedule a meeting during 
> IETF week. It also requires two weeks notice, so it anyway can only be done 
> on the week of the 29th / first week of December.
> 
> That’s not a bad thing: it will give people enough time to read the charter 
> and form an opinion before coming to the meeting.
> 
> If and when we have this meeting, I think we need to get a good number (5 
> maybe?) or people who are not authors and will commit to reviewing the 
> proposed documents. I think it is very obvious that this working group has 
> lost energy, and we wouldn’t want to take on more work unless there is a 
> clear indication that there will be such energy going forward.
> 
> Yoav
> 
>> On 15 Nov 2020, at 18:26, Mr. Jaehoon Paul Jeong > > wrote:
>> 
>> Hi Linda and Yoav,
>> Here is the text for I2NSF WG Re-chartering.
>> ---
>> Charter for Working Group
>> 
>> Interface to Network Security Functions (I2NSF) provides security vendors 
>> with a standard framework and interfaces for cloud-based security services. 
>> I2NSF enables the enforcement of a high-level security policy of a user's 
>> perspective in a target network (e.g., cloud network and edge network). This 
>> security policy enforcement in I2NSF is a data-driven approach using 
>> NETCONF/YANG or RESTCONF/YANG where a security policy is constructed into an 
>> XML file based on a YANG data model.
>> 
>> The I2NSF framework consists of four components such as I2NSF User, Security 
>> Controller, Network Security Function (NSF), and Developer's Management 
>> System (DMS). I2NSF User specifies a high-level security policy for a target 
>> network (e.g., cloud network). Security Controller maintains the capability 
>> of an NSF and takes a security policy from I2NSF User for the enforcement of 
>> the corresponding security service. An NSF performs a specific security 
>> service (e.g., firewall, web filter, deep packet inspection, and DDOS-attack 
>> mitigator) according to a security policy rule. DMS registers the capability 
>> of an NSF with Security Controller.
>> 
>> The I2NSF framework has four interfaces such as Consumer-Facing Interface, 
>> NSF-Facing Interface, Registration Interface, and Monitoring Interface. 
>> Consumer-Facing Interface is used to deliver a high-level security policy 
>> from I2NSF User to Security Controller. NSF-Facing Interface is used to 
>> deliver a low-level security policy from Security Controller to an NSF. 
>> Registration Interface is used to register the capability of an NSF with 
>> Security Controller. Monitoring Interface is used to collect monitoring data 
>> from an NSF.
>> 
>> The goal of I2NSF is to define a set of software interfaces and data models 
>> of such interfaces for configuring, maintaining, and monitoring NSFs in 
>> Network Functions Virtualization (NFV) environments. For security management 
>> automation in an autonomous security system, I2NSF needs to have a feedback 
>> control loop consisting of security policy configuration in an NSF, 
>> monitoring for an NSF, data analysis for NSF monitoring data, feedback 
>> delivery, and security policy augmentation/generation. For this security 
>> management automation, the I2NSF framework requires a new component to 
>> collect NSF monitoring data and analyze them, which is called I2NSF 
>> Analyzer. Also, the I2NSF framework needs a new interface to deliver a 
>> feedback message for security policy adjustment from I2NSF Analyzer to 
>> Security Controller.
>> 
>> I2NSF is vulnerable to an inside attack and a supply chain attack since it 
>> trusts in NSFs provided by DMS, assuming that NSFs work for their security 
>> services appropriately. Also, I2NSF trusts in I2NSF User and Security 
>> Controller. The registration of an NSF's capability, the enforcement of a 
>> security policy from either I2NSF User or Security Controller, and the 
>> monitoring data from an NSF are assumed to be genuine and non-malicious. If 
>> one 

Re: [I2nsf] I2NSF Re-chartering Text

[Mr. Jaehoon Paul Jeong]

Hi Yoav,
I agree that we can schedule our online interim meeting on the week of the
29th / first week of December.

Could you schedule such an interim meeting?

I believe that we can get more people to be engaged in the new I2NSF work
items
other than the authors of the current I2NSF WG and individual drafts.
With those people, I hope our I2NSF WG can have more energy. :)

Thanks.

Best Regards,
Paul

On Mon, Nov 16, 2020 at 1:59 AM Yoav Nir  wrote:

> Hi, Paul
>
> As Roman said in a separate email message, we can’t schedule a meeting
> during IETF week. It also requires two weeks notice, so it anyway can only
> be done on the week of the 29th / first week of December.
>
> That’s not a bad thing: it will give people enough time to read the
> charter and form an opinion before coming to the meeting.
>
> If and when we have this meeting, I think we need to get a good number (5
> maybe?) or people who are not authors and will commit to reviewing the
> proposed documents. I think it is very obvious that this working group has
> lost energy, and we wouldn’t want to take on more work unless there is a
> clear indication that there will be such energy going forward.
>
> Yoav
>
> On 15 Nov 2020, at 18:26, Mr. Jaehoon Paul Jeong 
> wrote:
>
> Hi Linda and Yoav,
> Here is the text for I2NSF WG Re-chartering.
>
> ---
> Charter for Working Group
>
> Interface to Network Security Functions (I2NSF) provides security vendors
> with a standard framework and interfaces for cloud-based security services.
> I2NSF enables the enforcement of a high-level security policy of a user's
> perspective in a target network (e.g., cloud network and edge network).
> This security policy enforcement in I2NSF is a data-driven approach using
> NETCONF/YANG or RESTCONF/YANG where a security policy is constructed into
> an XML file based on a YANG data model.
>
> The I2NSF framework consists of four components such as I2NSF User,
> Security Controller, Network Security Function (NSF), and Developer's
> Management System (DMS). I2NSF User specifies a high-level security policy
> for a target network (e.g., cloud network). Security Controller maintains
> the capability of an NSF and takes a security policy from I2NSF User for
> the enforcement of the corresponding security service. An NSF performs a
> specific security service (e.g., firewall, web filter, deep packet
> inspection, and DDOS-attack mitigator) according to a security policy rule.
> DMS registers the capability of an NSF with Security Controller.
>
> The I2NSF framework has four interfaces such as Consumer-Facing Interface,
> NSF-Facing Interface, Registration Interface, and Monitoring Interface.
> Consumer-Facing Interface is used to deliver a high-level security policy
> from I2NSF User to Security Controller. NSF-Facing Interface is used to
> deliver a low-level security policy from Security Controller to an NSF.
> Registration Interface is used to register the capability of an NSF with
> Security Controller. Monitoring Interface is used to collect monitoring
> data from an NSF.
>
> The goal of I2NSF is to define a set of software interfaces and data
> models of such interfaces for configuring, maintaining, and monitoring NSFs
> in Network Functions Virtualization (NFV) environments. For security
> management automation in an autonomous security system, I2NSF needs to have
> a feedback control loop consisting of security policy configuration in an
> NSF, monitoring for an NSF, data analysis for NSF monitoring data, feedback
> delivery, and security policy augmentation/generation. For this security
> management automation, the I2NSF framework requires a new component to
> collect NSF monitoring data and analyze them, which is called I2NSF
> Analyzer. Also, the I2NSF framework needs a new interface to deliver a
> feedback message for security policy adjustment from I2NSF Analyzer to
> Security Controller.
>
> I2NSF is vulnerable to an inside attack and a supply chain attack since it
> trusts in NSFs provided by DMS, assuming that NSFs work for their security
> services appropriately. Also, I2NSF trusts in I2NSF User and Security
> Controller. The registration of an NSF's capability, the enforcement of a
> security policy from either I2NSF User or Security Controller, and the
> monitoring data from an NSF are assumed to be genuine and non-malicious. If
> one of such activities is malicious, the security system based on I2NSF may
> collapse. To prevent this malicious activity from happening in the I2NSF
> framework or detect the root of a security attack, all the activities in
> the I2NSF framework should be logged in either a centralized way or a
> decentralized way (e.g., blockchain). Also, the operations and activities
> of the I2NSF components (i.e., I2NSF User, Security Controller, NSF, DMS,
> and I2NSF Analyzer) need to be verified by remote attestation.
>
> 

Re: [I2nsf] Request for Online Meeting for I2NSF WG Rechartering

[Mr. Jaehoon Paul Jeong]

Hi Roman,
Thanks for your kind guidance.

I think it will be better to have an online interim meeting after two weeks
for the discussion of the I2NSF re-chartering.

I also think there are several organizations to have the new work items.
They will speak up their voice in the matter of the re-chartering soon.

Thanks.

Best Regards,
Paul

On Mon, Nov 16, 2020 at 1:44 AM Roman Danyliw  wrote:

> Hi!
>
>
>
> It seems like a great idea to gather the WG group to discuss the issue.  A
> gentle reminder -- it isn’t possible to convene an interim meeting during
> the virtual IETF 109 week.  Likewise, such a meeting ideally needs two
> weeks notice to allow the participants digest the planned topics of
> discussion.  Of course, nothing stops individuals from informally
> gathering, but this is not an official meeting.
>
>
>
> When we do get to discussing re-charter I’m going to be looking if there
> is energy and broad support for this proposed new work.  Ideally, there
> were would be excitement and willingness to implement from beyond the
> current set of authors on the inflight documents.
>
>
>
> Regards,
>
> Roman
>
>
>
>
>
> *From:* I2nsf  *On Behalf Of * Mr. Jaehoon Paul
> Jeong
> *Sent:* Wednesday, November 11, 2020 10:46 PM
> *To:* Linda Dunbar 
> *Cc:* Roman Danyliw ; DIEGO LOPEZ GARCIA <
> diego.r.lo...@telefonica.com>; i2nsf@ietf.org; Yoav Nir <
> ynir.i...@gmail.com>; JungSoo Park ; Mr. Jaehoon Paul
> Jeong ; Xialiang (Frank) <
> frank.xiali...@huawei.com>; Yunchul Choi ; Younghan Kim
> ; Patrick Lingga ;
> skku-iotlab-members ; Qin Wu <
> bill...@huawei.com>; Susan Hares ; Hyunsik Yang <
> yan...@dcn.ssu.ac.kr>
> *Subject:* Re: [I2nsf] Request for Online Meeting for I2NSF WG
> Rechartering
>
>
>
> Linda,
>
> Yes, I am requesting an informal session to discuss the text for
> re-chartering.
>
> Could you set up an informal session date/time for I2NSF WG re-chartering
> next week?
>
>
>
> If you want, I can set up a WebEx meeting.
>
>
>
> In any case, could you decide the meeting date and time?
>
>
>
> I will provide you and the I2NSF WG with the text for re-chartering this
> weekend.
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
>
>
>
>
> On Thu, Nov 12, 2020 at 11:25 AM Linda Dunbar 
> wrote:
>
> Paul,
>
>
>
> Thank you very much for writing the 3 additional drafts for I2NSF. I
> already read through them.
>
> Waiting review your drafted re-chartering text. Make sure to identify
> clearly the detailed work items.
>
>
>
> Are you  requesting an informal session to discuss the text for
> re-chartering?
>
> It would be good to give people some time to review.
>
>
>
> Thank you.
>
>
>
> Linda
>
>
>
>
>
>
>
>
>
> *From:* Mr. Jaehoon Paul Jeong 
> *Sent:* Tuesday, November 10, 2020 12:54 AM
> *To:* Linda Dunbar ; Yoav Nir <
> ynir.i...@gmail.com>
> *Cc:* Roman Danyliw ; i2nsf@ietf.org; DIEGO LOPEZ GARCIA <
> diego.r.lo...@telefonica.com>; Susan Hares ; Xialiang
> (Frank) ; Qin Wu ;
> Younghan Kim ; JungSoo Park ; Yunchul
> Choi ; Patrick Lingga ;
> Hyunsik Yang ; skku-iotlab-members <
> skku-iotlab-memb...@googlegroups.com>; Mr. Jaehoon Paul Jeong <
> jaehoon.p...@gmail.com>
> *Subject:* Request for Online Meeting for I2NSF WG Rechartering
>
>
>
> Hi Linda and Yoav,
>
> I would like to suggest an online meeting for I2NSF WG Rechartering
>
> during the IETF-109 week (from November 16 to November 20).
>
>
>
> Diego Lopez and I expressed new work items for our I2NSF WG before.
>
>
>
> I am preparing the text for the I2NSF WG Recharter and will share it with
> our I2NSF WG this week.
>
>
>
> The new work items to be discussed  in this online meeting are as follows:
>
> - An Extension of I2NSF Framework for Security Management Automation in
> Cloud-Based Security Services
>
> https://tools.ietf.org/html/draft-jeong-i2nsf-security-management-automation-00
> 
>
> - Remote Attestation Procedures for Network Security Functions (NSFs)
> through the I2NSF Security Controller
>   https://tools.ietf.org/html/draft-pastor-i2nsf-nsf-remote-attestation-07
> 
>
> - An I2NSF Interface in NFV Container Environment (i.e., Cloud Native
> Environment)
>   

Re: [I2nsf] I2NSF Re-chartering Text

[Yoav Nir]

Hi, Paul

As Roman said in a separate email message, we can’t schedule a meeting during 
IETF week. It also requires two weeks notice, so it anyway can only be done on 
the week of the 29th / first week of December.

That’s not a bad thing: it will give people enough time to read the charter and 
form an opinion before coming to the meeting.

If and when we have this meeting, I think we need to get a good number (5 
maybe?) or people who are not authors and will commit to reviewing the proposed 
documents. I think it is very obvious that this working group has lost energy, 
and we wouldn’t want to take on more work unless there is a clear indication 
that there will be such energy going forward.

Yoav

> On 15 Nov 2020, at 18:26, Mr. Jaehoon Paul Jeong  
> wrote:
> 
> Hi Linda and Yoav,
> Here is the text for I2NSF WG Re-chartering.
> ---
> Charter for Working Group
> 
> Interface to Network Security Functions (I2NSF) provides security vendors 
> with a standard framework and interfaces for cloud-based security services. 
> I2NSF enables the enforcement of a high-level security policy of a user's 
> perspective in a target network (e.g., cloud network and edge network). This 
> security policy enforcement in I2NSF is a data-driven approach using 
> NETCONF/YANG or RESTCONF/YANG where a security policy is constructed into an 
> XML file based on a YANG data model.
> 
> The I2NSF framework consists of four components such as I2NSF User, Security 
> Controller, Network Security Function (NSF), and Developer's Management 
> System (DMS). I2NSF User specifies a high-level security policy for a target 
> network (e.g., cloud network). Security Controller maintains the capability 
> of an NSF and takes a security policy from I2NSF User for the enforcement of 
> the corresponding security service. An NSF performs a specific security 
> service (e.g., firewall, web filter, deep packet inspection, and DDOS-attack 
> mitigator) according to a security policy rule. DMS registers the capability 
> of an NSF with Security Controller.
> 
> The I2NSF framework has four interfaces such as Consumer-Facing Interface, 
> NSF-Facing Interface, Registration Interface, and Monitoring Interface. 
> Consumer-Facing Interface is used to deliver a high-level security policy 
> from I2NSF User to Security Controller. NSF-Facing Interface is used to 
> deliver a low-level security policy from Security Controller to an NSF. 
> Registration Interface is used to register the capability of an NSF with 
> Security Controller. Monitoring Interface is used to collect monitoring data 
> from an NSF.
> 
> The goal of I2NSF is to define a set of software interfaces and data models 
> of such interfaces for configuring, maintaining, and monitoring NSFs in 
> Network Functions Virtualization (NFV) environments. For security management 
> automation in an autonomous security system, I2NSF needs to have a feedback 
> control loop consisting of security policy configuration in an NSF, 
> monitoring for an NSF, data analysis for NSF monitoring data, feedback 
> delivery, and security policy augmentation/generation. For this security 
> management automation, the I2NSF framework requires a new component to 
> collect NSF monitoring data and analyze them, which is called I2NSF Analyzer. 
> Also, the I2NSF framework needs a new interface to deliver a feedback message 
> for security policy adjustment from I2NSF Analyzer to Security Controller.
> 
> I2NSF is vulnerable to an inside attack and a supply chain attack since it 
> trusts in NSFs provided by DMS, assuming that NSFs work for their security 
> services appropriately. Also, I2NSF trusts in I2NSF User and Security 
> Controller. The registration of an NSF's capability, the enforcement of a 
> security policy from either I2NSF User or Security Controller, and the 
> monitoring data from an NSF are assumed to be genuine and non-malicious. If 
> one of such activities is malicious, the security system based on I2NSF may 
> collapse. To prevent this malicious activity from happening in the I2NSF 
> framework or detect the root of a security attack, all the activities in the 
> I2NSF framework should be logged in either a centralized way or a 
> decentralized way (e.g., blockchain). Also, the operations and activities of 
> the I2NSF components (i.e., I2NSF User, Security Controller, NSF, DMS, and 
> I2NSF Analyzer) need to be verified by remote attestation.
> 
> Furthermore, an NSF can be instantiated as either a Virtual Network Function 
> (VNF) in an NFV-based cloud or a container in a native cloud. The current 
> YANG data models for the I2NSF interfaces are designed on the basis of VNF, 
> so they need to be redesigned for the case where I2NSF components are 
> instantiated by containers.
> 
> The I2NSF working group's deliverables include:
> 
> o A single document for an extension of I2NSF 

Re: [I2nsf] Request for Online Meeting for I2NSF WG Rechartering

[Roman Danyliw]

Hi!

It seems like a great idea to gather the WG group to discuss the issue.  A 
gentle reminder -- it isn’t possible to convene an interim meeting during the 
virtual IETF 109 week.  Likewise, such a meeting ideally needs two weeks notice 
to allow the participants digest the planned topics of discussion.  Of course, 
nothing stops individuals from informally gathering, but this is not an 
official meeting.

When we do get to discussing re-charter I’m going to be looking if there is 
energy and broad support for this proposed new work.  Ideally, there were would 
be excitement and willingness to implement from beyond the current set of 
authors on the inflight documents.

Regards,
Roman


From: I2nsf  On Behalf Of Mr. Jaehoon Paul Jeong
Sent: Wednesday, November 11, 2020 10:46 PM
To: Linda Dunbar 
Cc: Roman Danyliw ; DIEGO LOPEZ GARCIA 
; i2nsf@ietf.org; Yoav Nir ; 
JungSoo Park ; Mr. Jaehoon Paul Jeong 
; Xialiang (Frank) ; Yunchul 
Choi ; Younghan Kim ; Patrick Lingga 
; skku-iotlab-members 
; Qin Wu ; Susan 
Hares ; Hyunsik Yang 
Subject: Re: [I2nsf] Request for Online Meeting for I2NSF WG Rechartering

Linda,
Yes, I am requesting an informal session to discuss the text for re-chartering.
Could you set up an informal session date/time for I2NSF WG re-chartering next 
week?

If you want, I can set up a WebEx meeting.

In any case, could you decide the meeting date and time?

I will provide you and the I2NSF WG with the text for re-chartering this 
weekend.

Thanks.

Best Regards,
Paul


On Thu, Nov 12, 2020 at 11:25 AM Linda Dunbar 
mailto:linda.dun...@futurewei.com>> wrote:
Paul,

Thank you very much for writing the 3 additional drafts for I2NSF. I already 
read through them.
Waiting review your drafted re-chartering text. Make sure to identify clearly 
the detailed work items.

Are you  requesting an informal session to discuss the text for re-chartering?
It would be good to give people some time to review.

Thank you.

Linda




From: Mr. Jaehoon Paul Jeong 
mailto:jaehoon.p...@gmail.com>>
Sent: Tuesday, November 10, 2020 12:54 AM
To: Linda Dunbar 
mailto:linda.dun...@futurewei.com>>; Yoav Nir 
mailto:ynir.i...@gmail.com>>
Cc: Roman Danyliw mailto:r...@cert.org>>; 
i2nsf@ietf.org; DIEGO LOPEZ GARCIA 
mailto:diego.r.lo...@telefonica.com>>; Susan 
Hares mailto:sha...@ndzh.com>>; Xialiang (Frank) 
mailto:frank.xiali...@huawei.com>>; Qin Wu 
mailto:bill...@huawei.com>>; Younghan Kim 
mailto:young...@ssu.ac.kr>>; JungSoo Park 
mailto:p...@etri.re.kr>>; Yunchul Choi 
mailto:cy...@etri.re.kr>>; Patrick Lingga 
mailto:patricklink...@gmail.com>>; Hyunsik Yang 
mailto:yan...@dcn.ssu.ac.kr>>; skku-iotlab-members 
mailto:skku-iotlab-memb...@googlegroups.com>>;
 Mr. Jaehoon Paul Jeong mailto:jaehoon.p...@gmail.com>>
Subject: Request for Online Meeting for I2NSF WG Rechartering

Hi Linda and Yoav,
I would like to suggest an online meeting for I2NSF WG Rechartering
during the IETF-109 week (from November 16 to November 20).

Diego Lopez and I expressed new work items for our I2NSF WG before.

I am preparing the text for the I2NSF WG Recharter and will share it with our 
I2NSF WG this week.

The new work items to be discussed  in this online meeting are as follows:
- An Extension of I2NSF Framework for Security Management Automation in 
Cloud-Based Security Services
  
https://tools.ietf.org/html/draft-jeong-i2nsf-security-management-automation-00

- Remote Attestation Procedures for Network Security Functions (NSFs) through 
the I2NSF Security Controller
  
https://tools.ietf.org/html/draft-pastor-i2nsf-nsf-remote-attestation-07

- An I2NSF Interface in NFV Container Environment (i.e., Cloud Native 
Environment)
  

[I2nsf] I2NSF Re-chartering Text

[Mr. Jaehoon Paul Jeong]

Hi Linda and Yoav,
Here is the text for I2NSF WG Re-chartering.
---
Charter for Working Group

Interface to Network Security Functions (I2NSF) provides security vendors
with a standard framework and interfaces for cloud-based security services.
I2NSF enables the enforcement of a high-level security policy of a user's
perspective in a target network (e.g., cloud network and edge network).
This security policy enforcement in I2NSF is a data-driven approach using
NETCONF/YANG or RESTCONF/YANG where a security policy is constructed into
an XML file based on a YANG data model.

The I2NSF framework consists of four components such as I2NSF User,
Security Controller, Network Security Function (NSF), and Developer's
Management System (DMS). I2NSF User specifies a high-level security policy
for a target network (e.g., cloud network). Security Controller maintains
the capability of an NSF and takes a security policy from I2NSF User for
the enforcement of the corresponding security service. An NSF performs a
specific security service (e.g., firewall, web filter, deep packet
inspection, and DDOS-attack mitigator) according to a security policy rule.
DMS registers the capability of an NSF with Security Controller.

The I2NSF framework has four interfaces such as Consumer-Facing Interface,
NSF-Facing Interface, Registration Interface, and Monitoring Interface.
Consumer-Facing Interface is used to deliver a high-level security policy
from I2NSF User to Security Controller. NSF-Facing Interface is used to
deliver a low-level security policy from Security Controller to an NSF.
Registration Interface is used to register the capability of an NSF with
Security Controller. Monitoring Interface is used to collect monitoring
data from an NSF.

The goal of I2NSF is to define a set of software interfaces and data models
of such interfaces for configuring, maintaining, and monitoring NSFs in
Network Functions Virtualization (NFV) environments. For security
management automation in an autonomous security system, I2NSF needs to have
a feedback control loop consisting of security policy configuration in an
NSF, monitoring for an NSF, data analysis for NSF monitoring data, feedback
delivery, and security policy augmentation/generation. For this security
management automation, the I2NSF framework requires a new component to
collect NSF monitoring data and analyze them, which is called I2NSF
Analyzer. Also, the I2NSF framework needs a new interface to deliver a
feedback message for security policy adjustment from I2NSF Analyzer to
Security Controller.

I2NSF is vulnerable to an inside attack and a supply chain attack since it
trusts in NSFs provided by DMS, assuming that NSFs work for their security
services appropriately. Also, I2NSF trusts in I2NSF User and Security
Controller. The registration of an NSF's capability, the enforcement of a
security policy from either I2NSF User or Security Controller, and the
monitoring data from an NSF are assumed to be genuine and non-malicious. If
one of such activities is malicious, the security system based on I2NSF may
collapse. To prevent this malicious activity from happening in the I2NSF
framework or detect the root of a security attack, all the activities in
the I2NSF framework should be logged in either a centralized way or a
decentralized way (e.g., blockchain). Also, the operations and activities
of the I2NSF components (i.e., I2NSF User, Security Controller, NSF, DMS,
and I2NSF Analyzer) need to be verified by remote attestation.

Furthermore, an NSF can be instantiated as either a Virtual Network
Function (VNF) in an NFV-based cloud or a container in a native cloud. The
current YANG data models for the I2NSF interfaces are designed on the basis
of VNF, so they need to be redesigned for the case where I2NSF components
are instantiated by containers.

The I2NSF working group's deliverables include:

o A single document for an extension of I2NSF framework for security
management automation. This document will initially be produced for
reference as a living list to track and record discussions: the working
group may decide to not publish this document as an RFC.
o A YANG data model document for I2NSF Application Interface to deliver
feedback from I2NSF Analyzer to Security Controller.
o A single document for applicability and use cases in I2NSF-based security
management automation.
o A single document for security policy translator to support the mapping
between a high-level YANG module and a low-level YANG module: the working
group may decide to not publish this document as an RFC.
o A single document for remote attestation for I2NSF components.
o A single document for I2NSF in Cloud Native NFV Architecture.
---

Linda,
Could you schedule our online meeting to discuss this