Re: [Teas] Upcoming changes to draft-ietf-teas-ietf-network-slices

[Krzysztof Szarkowicz <[e-mail]>]

Hi,

Just wanted to add few words regarding 2nd bullet.

VPN with SLO is not only an idea, but has been implemented and in production at many operators since many years. Business Edge services (or Business VPN) type of offering is present at many service providers. It concluded isolated connectivity services between business sites, with some SLO. So, from that perspective, 5G doesn’t bring dramatic new requirements. Now, instead of business sites, we have mobile functions (RU, DU, CU, UPF, …) placed at different locations in the network, that require interconnection with some SLO.

Cheers,
Krzysztof


> On 2022 -Mar-07, at 02:22, Igor Bryskin <i_bryskin=[e-mail]> wrote:
> 
> Hi Gyan,
> 
> Thanks for the thoughtful and detailed response. Indeed, this is an important discussion.
> 
> 1. IMHO IETF network slicing does not mean something wider than 5G network slicing. On the contrary, I'd argue it is narrower than 5G network slicing. It is  just a way to say that IETF cannot take care of 5G slicing end to end, rather, it can only focus on certain segments of 5G service (e.g. core network, back hawl, etc.), but not all (e.g. RAN).
> 
> 2. The fact that things like VPN with SLOs existed as an idea for 20 years, but is taken  on realization  only now, after 5G came along (requiring the same SLOs) does not mean that we are defining something that is not limited to 5G - nothing prevents any client to take advantage of some/all  functions of 5G network slicing. This is just a lucky  byproduct.
> 
> 3. The outcome of this discussion may have consequences that are not entirely harmless. For e ample, as we see in CCAMP,  because the framework stipulates  IETF network slicing to be not only about 5G, folks are already working on things like OTN slicing, and soon will be working on microwave and all other transport layer slicing. Do we really want to go there?
> 
> The bottom line: it would be helpful if the framework  indentified clearer/narrower its  focus. 
> 
> 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 Sun, Mar 6, 2022 at 7:07 PM, Gyan Mishra
> <[e-mail]> wrote:
> _______________________________________________
> Teas mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/teas <https://www.ietf.org/mailman/listinfo/teas>
> _______________________________________________
> Teas mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/teas