[Teas] Mail regarding draft-ietf-idr-flowspec-network-slice-ts

[[e-mail]]

Hi Authors,

The proposal in the draft is not actually about slice steering, but NRP steering. An NRP can be shared between multiple connectivity constructs of the same or distinct slices. Likewise, there is no assumption that all CCs of a slice will be mapped to the same NRP. Also, when the same NRP is used for more than one slice, distinct forwarding paths (and thus distinct actions) may be selected for each slice that shares the NRP. The NRP-ID alone is not sufficient to disambiguate slice traffic. Whether an NRP maps to one and only one slice is deployment-specific.

I think the current text in the draft is misleading. I suggest you revise the draft to better articulate the intent and capture the differences between the concept of slice vs. nrp. Thanks.

BTW, how the global bit is used?

Thanks.

Cheers,
Med

_________________________________________________________________________________________________________________________

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.