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

["Dongjie (Jimmy)" <[e-mail]>]

Hi Med,

Thanks for your review and comments on this document. You may misunderstand the mechanisms described in this draft a little, so let me try to clarify.


The purpose of the proposed mechanism is to use BGP Flowspec to distribute the rules for matching some fields of the network slice service packets at the network ingress nodes, then the matched packets could be steered into the corresponding NRP.  Thus it is about steering network slice services into NRPs, and optionally specific TE paths of the NRPs. It does not infer any limitation about whether multiple network slices services are mapped to the same or different NRPs. As you said that is all based on deployment policy.



As mentioned in the draft, the existing Flowspec components can be reused for the matching of network slice services at the edge of an NRP, so the matching is not just based on the NRP ID. Actually the NRP ID component is only introduced for some specific cases (e.g. the domain edge nodes of multi-domain NRPs) for packet matching. We will clarify that in next revision.


Best regards,
Jie

From: [e-mail] <[e-mail]>
Sent: Tuesday, April 18, 2023 1:47 PM
To: [e-mail]
Cc: TEAS WG ([e-mail]) <[e-mail]>
Subject: Mail regarding draft-ietf-idr-flowspec-network-slice-ts

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.