Re: [Teas-ns-dt] Notes from Feb 24th call & deadline

[Kiran Makhijani <[e-mail]>]

Hello Sergio,
It is my bad! I assumed through conversations in meetings it was clear not to change the definition.

  *   The current definition has a wide consensus from the group. I am afraid we might undo what we agreed upon 5-6 months ago.
  *   We also had discussions on why we would not use the term virtual network (to not to exclude physical/dedicated network, resources – abstract was the best term). I highlight my concerns in your proposed definition, please see below (essentially, it is too verbose- we tried to keep it to the point).



“A transport network slice is a virtual network with a particular

   network topology and a set of shared or dedicated network resources,



[KM] We capture this essence in SLOs. See discussion on SLO section

   which are used to provide the network slice consumer with the

   required connectivity, appropriate isolation and



[KM] We use “topology connecting…”, therefore, no point repeating this.

   specific Service Level Agreement (SLA) or Service Level Objective (SLO).”

^^^^

[KM] in IETF 106, we decided to distinguish between SLA and SLO. SLO are more accurate. If we use both SLA and SLO – the definition is vague.

How about we make it sound like below?

"A transport slice is an abstract network topology connecting a
   number of endpoints and a set of shared or dedicated network resources, with expected objectives specified through a set
   of service level objectives (SLO)".

If you would like to propose some text outside the definition which you think could help, please suggest.
HTH,
Kiran

From: "Belotti, Sergio (Nokia - IT/Vimercate)" <[e-mail]>
Date: Tuesday, February 25, 2020 at 12:19 AM
To: Jari Arkko <jari.arkko=[e-mail]>rg>, "[e-mail]" <[e-mail]>rg>, "Rokui, Reza (Nokia - CA/Ottawa)" <[e-mail]>
Cc: Kiran Makhijani <[e-mail]>
Subject: RE: Notes from Feb 24th call & deadline

Hi Jari, Reza as co-author of definition draft, all,
I read again draft definition and in the new version is still missing the proposed new definition of transport slice as for my pull request sent 25 days ago.
Is there any objection to the adoption of my proposed text? If not, I suggest editor to provide a new version including the text contained in
https://github.com/teas-wg/teas-ns-dt/pull/4<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteas-wg%2Fteas-ns-dt%2Fpull%2F4&data=02%7C01%7Ckiranm%40futurewei.com%7C0bad100fc6cb45847dda08d7b9cb7e58%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637182155959468964&sdata=2hC8HaNlywBaFkuA7KntBK4llSwP2FEkZLfq4qFBmdE%3D&reserved=0>amp;reserved=0>.

Thanks
Sergio

Sergio Belotti
Senior System Engineer and Standardization Architect
IP/Optical Networks, Optics BU
Nokia
M: [phone]
Via Energy Park, 20871 Vimercate (MB) , Italy
[e-mail]<mailto:[e-mail]>



From: Teas-ns-dt <[e-mail]> On Behalf Of Jari Arkko
Sent: Tuesday, February 25, 2020 8:26 AM
To: [e-mail]
Subject: [Teas-ns-dt] Notes from Feb 24th call & deadline

The notes are now available here: https://github.com/teas-wg/teas-ns-dt/blob/master/notes/notes-2020-02-20.md<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteas-wg%2Fteas-ns-dt%2Fblob%2Fmaster%2Fnotes%2Fnotes-2020-02-20.md&data=02%7C01%7Ckiranm%40futurewei.com%7C0bad100fc6cb45847dda08d7b9cb7e58%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637182155959468964&sdata=LH54VedrNDrA%2F3M1K9swHnhrWSX7cYjFrGNiC2VJ7Ro%3D&reserved=0> Let me know if there are any changes needed.

I would also like to underline the importance of working on the two documents and their issues now on the mailing list. It feels like we are now making rapid progress. However, we only have 13 days left. It is important that we check the discussion daily so that we have enough email roundtrips to finish the issues we’re discussing. And contributions on both documents are also needed. You can suggest changes by sending mail to the list.

The drafts in their current form are at

  https://github.com/teas-wg/teas-ns-dt/blob/master/definitions/draft-rokui-teas-transport-slice-definition-00.txt<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteas-wg%2Fteas-ns-dt%2Fblob%2Fmaster%2Fdefinitions%2Fdraft-rokui-teas-transport-slice-definition-00.txt&data=02%7C01%7Ckiranm%40futurewei.com%7C0bad100fc6cb45847dda08d7b9cb7e58%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637182155959478919&sdata=0xwFzDv3Pyw0eX421EolRMU3E9Cf8Y%2BlCqtFowdNLFs%3D&reserved=0>
  https://github.com/teas-wg/teas-ns-dt/blob/master/framework/draft-ejj-teas-ns-framework-00.txt<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteas-wg%2Fteas-ns-dt%2Fblob%2Fmaster%2Fframework%2Fdraft-ejj-teas-ns-framework-00.txt&data=02%7C01%7Ckiranm%40futurewei.com%7C0bad100fc6cb45847dda08d7b9cb7e58%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637182155959478919&sdata=5cDKu8PtHbJI5buiNObDeH0CAyO61YWcp9cmRYnq9mI%3D&reserved=0>

But there are also a number of big contributions discussed, see the notes for pointers.

Jari