Re: [Teas] New Version Notification for draft-bestbar-teas-ns-packet-04.txt

Hi Igor,

Indeed, our narrative has been (noted earlier on the list) that the slice aggregate can be formed from slice traffic streams that have common SLOs. The NSC cherry picks such slice traffic streams (possibly from different IETF network slices)  with awareness of their SLOs and groups them into one slice aggregate that results in instantiating a network resource partition.
We could have used a longer descriptive name for slice aggregate (and maybe an acronym to go with it), but we chose to keep it short.

Regards,
Tarek

From: Igor Bryskin <i_bryskin@yahoo.com>
Date: Monday, November 8, 2021 at 1:23 PM
To: tsaad=40juniper.net@dmarc.ietf.org <tsaad=40juniper.net@dmarc.ietf.org>, Tarek Saad <tsaad=40juniper.net@dmarc.ietf.org>, Dongjie (Jimmy) <jie.dong@huawei.com>, Wubo (lana) <lana.wubo@huawei.com>, Tarek Saad <tsaad.net@gmail.com>, teas@ietf.org <teas@ietf.org>
Cc: draft-bestbar-teas-ns-packet@ietf.org <draft-bestbar-teas-ns-packet@ietf.org>
Subject: Re: [Teas] New Version Notification for draft-bestbar-teas-ns-packet-04.txt
Hi Tarek,

I think Jie has a point. If a netwok slice is configured with more than one connectivity matrices, some with different SLOs, than it would be possible that two flows of the same network slice service sharing the same sender/receiver would have to be treated differently ( i.e. belong to separate NC aggregates) even when going through the same nodes/links. A better term would be Network Slice Flow Aggregate/Group.

Cheers,
Igor
Sent from Yahoo Mail on Android<https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>

On Mon, Nov 8, 2021 at 12:13 PM, Tarek Saad
<tsaad=40juniper.net@dmarc.ietf.org> wrote:
_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas