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

[[e-mail]]

Hi Krzysztof, all,

Looks good to me. Thanks.

Cheers,
Med

De : Krzysztof Szarkowicz <[e-mail]>
Envoyé : mardi 12 avril 2022 16:08
À : [e-mail]; John E Drake <[e-mail]>; BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Cc : [e-mail]
Objet : Re: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

John, Adrian, Med

In that case, I would propose following text update. The reason is, from the current text, I cannot extract the the examples provided by Med and Adrian could be and well considered as an NSP realization.

===== Current Text ============
An NRP is simply a collection of resources identified in the underlay network.  Thus, the NRP is a scoped view of a topology and may be considered as a topology in its own right.  The process of determining the NRP may be made easier if the underlay network topology is first filtered into a Filter Topology in order to be aware of the subset of network resources that are suitable for specific NRPs, but this is optional.
====== End of current text ==========


===== New Text ============
It is out of scope for this document to describe the details, how an NSP can be realized. However, at a high-level, an NRP is simply a collection of resources identified in the underlay network. Some (none exhaustive) examples of an NSP realization are:

a) collection of paths optimized based on certain criteria. For example low latency paths for NSP-A, and high capacity paths for NSP-B.

b) admission control - possibly with large number of QoS classes - at the transport access, coupled with limited set of transport core QoS classes (PDBs), and N:M mapping between access and core classes.

c) combination of above

d) more complex realization schemes, with combinations of advanced QoS at both the access and transport core, possibly coupled with Filter Topology and different path optimizations methods.
====== End of new text ==========

Best regards,
Krzysztof Szarkowicz

On 2022 -Apr-01, at 14:43, John E Drake <[e-mail]<mailto:[e-mail]>> wrote:

Krzysztof,

The usual answer to such a request is to ask you to provide text.

Yours Irrespectively,

John


_________________________________________________________________________________________________________________________

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.