Subject: [I2nsf] If you want to remotely present to the I2NSF session during IETF 99, please let us know (was FW: Call for Agenda items for IETF99 Prague

From: Linda Dunbar <[email-masked]>
Date: Thu, 29 Jun 2017 22:23:30 +0000

Again, there will be Meetecho available for people to present remotely for IETF 99 Prague.

However, we have to register the presenters ahead of time. So if you want to present something but can't physically come to Prague, please let us know.

Regards,

Adrian & Linda

From: Linda Dunbar
Sent: Wednesday, June 28, 2017 11:10 AM
To: [email-masked]
Subject: 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.

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