Re: [I2nsf] Magnus Westerlund's Discuss on draft-ietf-i2nsf-capability-data-model-12: (with DISCUSS)

2020-09-28 Thread Roman Danyliw
Hi Martin! This document has been (completely) removed from the upcoming telechat agenda, and the document is back in the WG. It will come back only after another the updates are done, another WG LC, IETC LC, Directorate review, etc. Roman From: I2nsf On Behalf Of Martin Duke Sent: Monday, S

Re: [I2nsf] Magnus Westerlund's Discuss on draft-ietf-i2nsf-capability-data-model-12: (with DISCUSS)

2020-09-28 Thread Martin Duke
So do I understand correctly that this is going to defer from next telechat, and I should review it at a later time? On Mon, Sep 28, 2020 at 8:18 AM Roman Danyliw wrote: > Hi Magnus! > > > -Original Message- > > From: I2nsf On Behalf Of Magnus Westerlund > > Sent: Monday, September 28,

Re: [I2nsf] Is there any objection of sunset the I2NSF Capabilities Information Model Draft and merge the relevant information to the I2NSF Capability Data model draft?

2020-09-28 Thread Mr. Jaehoon Paul Jeong
Hi Linda, I agree at merging the NSF Capabilities Information Model Draft into the NSF Capability Data Model Draft. I will be able to work on the merging with the help of Susan and other coauthors. Thanks. Best Regards, Paul 2020년 9월 29일 (화) 오전 1:00, Linda Dunbar 님이 작성: > I2NSF WG, > > > > As

[I2nsf] Is there any objection of sunset the I2NSF Capabilities Information Model Draft and merge the relevant information to the I2NSF Capability Data model draft?

2020-09-28 Thread Linda Dunbar
I2NSF WG, As Diego has expressed that the original I2NSF capability information model was based on a policy expression calculus suitable for manipulating high-level policy expressions. The capability data model has been evolving in a quite reasonable and pragmatic way, including running code a

Re: [I2nsf] Magnus Westerlund's Discuss on draft-ietf-i2nsf-capability-data-model-12: (with DISCUSS)

2020-09-28 Thread Roman Danyliw
Hi Magnus! > -Original Message- > From: I2nsf On Behalf Of Magnus Westerlund > Sent: Monday, September 28, 2020 10:35 AM > To: i...@ietf.org; sha...@ndzh.com > Cc: i2nsf@ietf.org; draft-ietf-i2nsf-capability-data-mo...@ietf.org; > dunbar...@gmail.com; i2nsf-cha...@ietf.org > Subject: Re:

Re: [I2nsf] Magnus Westerlund's Discuss on draft-ietf-i2nsf-capability-data-model-12: (with DISCUSS)

2020-09-28 Thread Magnus Westerlund
Hi, On Fri, 2020-09-25 at 11:08 -0400, Susan Hares wrote: > Magnus: > > Do you have specific transport people that you have assigned to work on this > review? No, I missed that Roman had deferred this document and tried to look at it and was personally unable to review it due to lack of conte

Re: [I2nsf] [Last-Call] [yang-doctors] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08

2020-09-28 Thread tom petch
On 28/09/2020 10:01, Rafa Marin-Lopez wrote: Hi Rob, Tom: Renaming the modules sounds reasonable. With regard to have a different prefix, it is also ok. Perhaps the easiest way is to solve this is the following: instead of using -sdn- we could include -i2nsf- so we would have: ietf-i2nsf-comm

Re: [I2nsf] [Last-Call] [yang-doctors] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08

2020-09-28 Thread Rafa Marin-Lopez
Hi Rob, Tom: Renaming the modules sounds reasonable. With regard to have a different prefix, it is also ok. Perhaps the easiest way is to solve this is the following: instead of using -sdn- we could include -i2nsf- so we would have: ietf-i2nsf-common, ietf-i2nsf-ike, and ietf-i2nsf-ikeless. Thi