Re: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

[[e-mail]]

Hi all,

Fully agree with John.

The text proposed by Krzysztof looks good to me.

Queuing aspects mentioned by Joel fall under “a collection of resources” in the proposed text. More generally, queuing management falls under differentiated forwarding while topology customization is an aspect of differentiated routing that can be tweaked to put into effect an NRP. Other differentiated behaviors can be a result of traffic management considerations (admission control, ratio of reserved-provisioned/allowed traffic, etc.).

Cheers,
Med

De : John E Drake <[e-mail]>
Envoyé : jeudi 19 mai 2022 14:50
À : Dongjie (Jimmy) <[e-mail]>; Krzysztof Szarkowicz <[e-mail]>; adrian <[e-mail]>; BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Cc : teas <[e-mail]>
Objet : RE: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

Hi,

Comment inline.

Yours Irrespectively,

John



Juniper Business Use Only
From: Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, May 18, 2022 9:52 PM
To: Krzysztof Szarkowicz <[e-mail]<mailto:[e-mail]>>; John E Drake <[e-mail]<mailto:[e-mail]>>; adrian <[e-mail]<mailto:[e-mail]>>; mohamed.boucadair <[e-mail]<mailto:[e-mail]>>
Cc: teas <[e-mail]<mailto:[e-mail]>>
Subject: RE: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

[External Email. Be cautious of content]

Hi Krzysztof and all,

Most of this text looks good to me except the last sentence. "A single NRP with the resources of the entire underlay network" is the same as a network without network resource partition. I think we agreed that an NRP refers to a subset of the underlay network resources (e.g. a subset of the buffer/queueing/scheduling resources), thus it is different from the whole underlay network.

[JD]  A subset can consist of the entire set

That said, an NRP may have the same topology as the underlay network.

IMO we need to keep in mind that resource and topology are two separate attributes of an NRP.

Best regards,
Jie
发件人：Krzysztof Szarkowicz <[e-mail]<mailto:[e-mail]>>
收件人：Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>;John E Drake <[e-mail]<mailto:[e-mail]>>;adrian <[e-mail]<mailto:[e-mail]>>;mohamed.boucadair <[e-mail]<mailto:[e-mail]>>
抄 送：teas <[e-mail]<mailto:[e-mail]>>
时 间：2022-05-19 03:16:57
主 题：Re: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

Hi,

So, do we have agreement for following change:


          An NRP is simply a collection of resources identified in the underlay network. The amount and granularity of resources allocated in different portions of an NRP can be flexible. Depends on the operator’s policy and the service requirements, some NRP realizations may build the NRPs with dedicated topologies, while some other realizations may allow shared topology for multiple NRPs, one possible case is that the entire underlay network topology is used by all the NRPs. Some realization might as well use single NRP only with the resources of the entire underlay network topology.

Best regards,
Krzysztof

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.