Re: [Teas-ns-dt] Contribution to new NS Framework draft

[Eric Gray <[e-mail]>]

Reza,

              Thanks for your response.  I will look at what you’ve added.

              I suspect there is a disconnect here, however.  An important design consideration in any relationship between entities, is to minimize unnecessary interactions.

              In terms of having material that clarifies the relationship between a transport slice and an end-to-end network slice, it is only necessary to state that each transport slice is a subset of the end-to-end network slice.  Note that I do not say a “proper subset” because I am certain that there will be applications where the transport slice is exactly the same thing as the end-to-end network slice.

              Going any further in “clarifying the relationship” is likely to introduce restrictions in the applicability of transport slices – i.e. – if we say that the relationship is some function (pick your favorite) or characteristic in common, we eliminate all applications that might otherwise benefit from the network slice abstraction, but don’t necessarily require this relationship.

              I agree that details are helpful in determining if a transport slice is doing its part in supporting an end-to-end network slice, but I suspect that this would be an implementation concern.  And I doubt it is very important in any general description of the problem we are trying to solve.

              Like I said, however, I will need to see what you have changed in your contribution.  It seems likely that I am reading more into what you’ve said than you intended.

--
Eric

From: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]>
Sent: Wednesday, February 19, 2020 11:40 AM
To: Eric Gray <[e-mail]>om>; John E Drake <[e-mail]>et>; LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>om>; Kiran Makhijani <[e-mail]>om>; Belotti, Sergio (Nokia - IT/Vimercate) <[e-mail]>om>; [e-mail]; Jari Arkko <jari.arkko=[e-mail]>rg>; Shunsuke Homma <[e-mail]>om>; Jeff Tantsura <[e-mail]>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]>
Subject: Re: [Teas-ns-dt] Contribution to new NS Framework draft
Importance: High

Hi Eric,

Good point but I explained it in my contribution why we need them. It is basically needed not for creation of the transport slice but for monitoring and assurance. It will be a tremendous help for debugging and troubleshooting of a transport slice when we know how it is mapped to e2e network slice. I have added this to my contribution I sent last week.

Cheers,

Reza

From: Eric Gray <[e-mail]<mailto:[e-mail]>>
Date: Monday, February 10, 2020 at 11:11 AM
To: Reza Rokui <[e-mail]<mailto:[e-mail]>>, John E Drake <[e-mail]<mailto:[e-mail]>>, LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>, Kiran Makhijani <[e-mail]<mailto:[e-mail]>>, Sergio Belotti <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>, Shunsuke Homma <[e-mail]<mailto:[e-mail]>>, Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Subject: RE: [Teas-ns-dt] Contribution to new NS Framework draft

Hi Reza.

Not sure why we need to know that, mostly from a perspective of orthogonality.  We (in terms of defining a Transport Slice) only need to know what the requirements are for a specific application, where the fact that the application may be a higher-layer control function for an “end-to-end” network slice does not even rise to the level of interesting information.

--
Eric

From: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]<mailto:[e-mail]>>
Sent: Monday, February 10, 2020 8:57 AM
To: Eric Gray <[e-mail]<mailto:[e-mail]>>; John E Drake <[e-mail]<mailto:[e-mail]>>; LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>; Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; Belotti, Sergio (Nokia - IT/Vimercate) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>; Shunsuke Homma <[e-mail]<mailto:[e-mail]>>; Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Teas-ns-dt] Contribution to new NS Framework draft
Importance: High

Thanks Eric and John for your comments.

In my opinion we need to have some materials to show clearly how “Transport Slice” is related to the overall e2e network slice. And also shows that “Transport Slice” is not same as “e2e network slice” and they are different.

We can revise the exiting text to make it more concise. Everyone can help with this.

Reza


From: Eric Gray <[e-mail]<mailto:[e-mail]>>
Date: Monday, February 10, 2020 at 7:51 AM
To: John E Drake <[e-mail]<mailto:[e-mail]>>, Reza Rokui <[e-mail]<mailto:[e-mail]>>, LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>, Kiran Makhijani <[e-mail]<mailto:[e-mail]>>, Sergio Belotti <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>, Shunsuke Homma <[e-mail]<mailto:[e-mail]>>, Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Subject: RE: [Teas-ns-dt] Contribution to new NS Framework draft

I agree with John, at least to the extent that we should limit discussion of “end-to-end” slice management to just that much that we need to know to understand that there will likely be a higher-level management/configuration/orchestration/controller/etc. system that needs specific support for creating/modifying/removing Transport Slices – likely at several points in an “end-to-end” network slice, whatever that might mean.

I don’t think we even need to – or should – define what an “end-to-end” network slice is, except as possible examples to provide a background for the remainder of our work, because we simply do not need to know that.

--
Eric

From: John E Drake <[e-mail]<mailto:[e-mail]>>
Sent: Friday, February 7, 2020 2:11 PM
To: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]<mailto:[e-mail]>>; Eric Gray <[e-mail]<mailto:[e-mail]>>; LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>; Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; Belotti, Sergio (Nokia - IT/Vimercate) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>; Shunsuke Homma <[e-mail]<mailto:[e-mail]>>; Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Subject: RE: [Teas-ns-dt] Contribution to new NS Framework draft
Importance: High

Hi,

There seems to be way too much emphasis on E2E slice management.

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas-ns-dt <[e-mail]<mailto:[e-mail]>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Friday, February 7, 2020 12:03 PM
To: Eric Gray <[e-mail]<mailto:[e-mail]>>; LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>; Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; Belotti, Sergio (Nokia - IT/Vimercate) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>; Shunsuke Homma <[e-mail]<mailto:[e-mail]>>; Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <[e-mail]<mailto:[e-mail]>>
Subject: [Teas-ns-dt] Contribution to new NS Framework draft


Eric, Jari and all,



As per our discussion during yesterday’s DT meeting, attached are my contribution to the new NS Framework draft. A few notes:



  *   I was not able to add these to GitHub. As a result, I wrote them in XML. Both XML and TXT versions are attached.
  *   Eric and Jari, please add them to master document in GitHub
  *   After merge, please review and send your comments/feedbacks in mailing list.
  *   There are still a few sections that I would like to contribute. I will do it later.



Thanks,

Reza