Re: [Teas] A draft on the framework for end-to-end IETF network slicing

Hi Joel/all,

Indeed, not all usecases necessitate distinguishing packets belonging to different slices/aggregates on a transit router. For example, packets of different slice/aggregates can share the same queue(s) on specific resource/link. Slicing of BW resources can still happen in control plane (e.g. assigning max guaranteed bandwidth per slice/aggregate, and/or allowing sharing of available bandwidth amongst slice aggregates, etc.). We have described this in draft-bestbar-teas-ns-packet<https://datatracker.ietf.org/doc/html/draft-bestbar-teas-ns-packet> as the “control plane” slicing mode (3GPP may also refer to this as “soft slicing”).

In other cases, assigning dedicated queues per slice aggregate is desirable to achieve certain level of isolation between different slice aggregate traffic (I reference “isolation” requirement from section 4.1.2.1<https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-network-slices-02#section-4.1.2.1>. of draft-ietf-teas-ietf-network-slices). In such cases, packets of different slice aggregates will need to distinguishable. We have described two methods in MPLS to distinguish such packets (either by carrying a slice-ID in the packet, or by allocating a different label per prefix for different slice/aggregates – in draft-bestbar-spring-scalable<https://datatracker.ietf.org/doc/html/draft-bestbar-spring-scalable-ns>)

Regards,

Tarek

On 5/13/21, 12:48 AM, "Teas" <teas-bounces@ietf.org> wrote:

It is not at all clear that any identifiers are needed inside the
various networks, and specifically it is not clear that an internal
identifier for the end-to-end network slice is needed at the level of
the IETF network slice as is being defined by teas.  Since path
selection, QoS parameter handling, and resource allocation needs to be
handled in aggregate, it seems likely that no such identifier is needed.

Yours,
Joel

On 5/12/2021 10:53 PM, Dongjie (Jimmy) wrote:
> Hi WG,
>
> Recently we published a draft on the framework for end-to-end IETF
> network slicing:
> https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-slicing
> <https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-slicing>
>
> This document describes the scenarios of end-to-end network slicing, and
> the framework of network slice mapping between different network
> segments and network domains. Multiple network slice related identifiers
> are defined to covers different network scopes.
>
> The network slice related identifiers of different network scopes can be
> instantiated with MPLS or IPv6 data plane, which are further described
> in the following drafts:
>
> https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slicing/
> <https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slicing/>
>
> https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-slicing
> <https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-slicing>
>
> https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing
> <https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing>
>
> Your review and comments are welcome. (Comments on the specific data
> plane draft can go to the corresponding WG mail list).
>
> Best regards,
>
> Jie
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas