Subject: [I2nsf] Call for Agenda items for IETF99 Prague

From: Linda Dunbar <[email-masked]>
Date: Wed, 28 Jun 2017 16:09:35 +0000

I2NSF WG is scheduled to meet on Tuesday 13:30 - 15:30 of the IETF week at Prague.

If you'd like to present drafts at the meeting, kindly send the following
 - name of the draft
 - time requested
 - presenter's name

In addition to the presentations, we are thinking of reserving at least 30 minutes of time discussing the relationship among multiple Information Model and Data model drafts in Client Facing and NSF Facing interfaces.
The goal is to make sure those drafts are consistent and complement each other, specifically:

Information model:

NSF Facing:

draft-xibassnez-i2nsf-capability-01

draft-xia-i2nsf-security-policy-object-00 (Is it intended for NSF facing? Or for client facing ?)

draft-hyun-i2nsf-registration-interface-im-01 (even though it is intended for Registration Interface, should it be aligned with the NSF facing Information model? )

Client facing:

draft-kumar-i2nsf-client-facing-interface-im-02

draft-xia-i2nsf-security-policy-object-00 (Is it intended for NSF facing? Or for client facing?)

Data Model:
NSF Facing:

draft-hares-i2nsf-capability-data-model-01

draft-kim-i2nsf-nsf-facing-interface-data-model

Question: Is it consistent to draft-xibassnez-i2nsf-capability ?

Client Facing:

draft-jeong-i2nsf-consumer-facing-interface-dm-0

draft-hyun-i2nsf-registration-interface-dm-00

How should we categorize those draft?
-      https://datatracker.ietf.org/doc/html/draft-pastor-i2nsf-nsf-remote-attestation
-      https<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>/<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>
-      https://datatracker.ietf.org/doc/draft-zhang-i2nsf-info-model-monitoring/
-      https<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>/<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>

Thanks,
Adrian & Linda

---

From: "Xialiang (Frank)" <[email-masked]>
Date: Fri, 30 Jun 2017 08:52:13 +0000

Hi Linda,
We’d like to present the following update drafts (will submit before the deadline~~):
draft-xibassnez-i2nsf-capability-02   20 min     John Strassner
draft-zhang-i2nsf-info-model-monitoring-04   20 min             Henk Birkholz
draft-xia-i2nsf-security-policy-object-01       15 min          Qiushi Lin or me

Thanks!

B.R.
Frank

发件人: I2nsf [mailto:[email-masked]] 代表 Linda Dunbar
发送时间: 2017年6月29日 0:10
收件人: [email-masked]
主题: [I2nsf] Call for Agenda items for IETF99 Prague

I2NSF WG is scheduled to meet on Tuesday 13:30 – 15:30 of the IETF week at Prague.

Information model:

NSF Facing:

Client facing:

Data Model:
NSF Facing:

Client Facing:

How should we categorize those draft?
–      https://datatracker.ietf.org/doc/html/draft-pastor-i2nsf-nsf-remote-attestation
–      https<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>/<https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>
–      https://datatracker.ietf.org/doc/draft-zhang-i2nsf-info-model-monitoring/
–      https<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>/<https://datatracker.ietf.org/doc/draft-hyun-i2nsf-nsf-triggered-steering/>

Thanks,
Adrian & Linda