Minutes IETF113: i2nsf
minutes-113-i2nsf-00

Interface to Network Service Functions (I2NSF) Working Group

IETF-113, Vienna

Agenda

=======

Thursday March 24, 2022
13.00 - 14.00(one hour)
Room: Park Suite 2
Chairs:
  Linda Dunbar      dunbar.ll@gmail.com
  Yoav Nir          ynir.ietf@gmail.com
AD:
  Roman Danliw      rdd@cert.org

=======

Administrivia - Chairs - 5 minutes
 - Working Group status and progress on milestones
Linda: introductes the meeting. See Note-Well.
Any questions for the agenda?

draft-ietf-i2nsf-capability-model-02 -
 we have enough ballots.  We just need to clear Discus

draft-ietf-i2nsf-nsf-facing-interface-dm-23.txt
 Enough ballots. Need to clear

raft-ietf-i2nsf-nsf-monitoring-data-model-16
Ben discusses are going to be picked up by
will be pick up by new SEC Ad.

2 WG
consumer facing
draft-ietf-i2nsf-nsf-facing-interface-dm-23
draft-ietf-i2nsf-consumer-facing-interface-dm-
registration interface

Need to be discussed because the are not consistent.

See notes below.

--- Draft discussion 25 minutes ---

I2NSF Remote Attestation Interface YANG Data Model
- Penglin Yang - 15 minutes
   draft-yang-i2nsf-remote-attestation-interface-dm-00
   - Focus: is it within the scope of RATS?
1) aligned with charter
2) Added a new paragraph regarding new

Wei Pan: ETSI ISG NFV is doing remote attestation for virtualization, should
notice the overlaps. Penglin Yang:  I will research this question. Wei Pan:
SASE - I think this might be helpful in this scenario. If it is I2NSF can be
used in this scenario, it will increase the deployment. Penglin:  I think that
SASE is about flow based. I think I2NSF is not SASE based.

Roman: Two Clarifying questions.  Given talking about the
There is Yang work in chara (?).  Why is this insufficient?
Why can you not reuse the model.

Pengling:  Runs on the VM as part of the hypervisor.
As part of the running machine, we will measure that
whether the code is secure.
Chara is how to measure a device and verify it.
This work is not appropriate for I2NSF because it
(missed ).  Chara focuses on all messages in the devices.

Roman: I'm making a modeling observation.
I thought IMA was shimmed into the Yang model.
I thought some of the NFV could be shimmed.

Penglin: I did review a great deal of information on the charter.
Diego: ETSI NFV - what proposed here is not incompatable
with ETSI NFV.  The recommendations can be used, but it
is a natural evolution from ETSI NFV.  The I2NSF architecture
with the controller and the devices (?).  There can be some
small overlaps. I do not see any [conflict (?)].

Chara as a mechanism for request/response is appropriate.
Who is going be the verifier?  Who is going to be
[] is doing something similar to what we are doing?
This kind of analysis of gap analysis is what we do.
What Penglin is aligned with this type of work.

Comparison of Consumer Facing and NSF Facing Data Models
- Focus: similarity and differences between the Consumer facing and NSF facing
DM Paul: Conclusion that the CFI and NSF facing are aligned.

Insf-registration-facing-interface-dm
- Paul Jeong Jaehoon - 10 minutes
   draft-ietf-i2nsf-registration-facing-interface-dm

  Discussion:
  Linda:  Registration is going to be aligned with changes to capability model.
  Paul: Yes it is.

--- Recharter discussion 30 minutes ---

- Proponents: Diego Lopez (Telefonica), Penglin Yang (China Mobile), Panwei
(Huawei), Paul Jeong Jaehoon, Henk Birkholz

- Focus:
1) is the proposed work already covered by RATS?
2) is there energy to continue the work?

Linda: Are there going to be containers?
(after Paul's conversation)
Diego: When we are implying a controller trust model.
I am of the belief that the use of containers and
that you can decompose the architecture.
You will have to re-think the architecture on this level.

Adapting the architecture to RATs to the automating box.
It is important that you can trust what the analyer has said.

Roman: This scope is very large.  Each of these
items could be a wG in itself.
I think the working group should consider the priorities.

Diego: The idea is not a new way of using a new
way of attestation, but an automation.
I will try to climb on the shoulder of giants.
It is important to reuse to enhance automation.

Yoav: We have the most people here to propose and talk about it.
We should discuss this on the mail list.