Re: [Teas] Applicability of IETF network slices in the 3GPP context

[LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>]

Hi Pavan, Greg, all,

Just to clarify to Greg, there has not been yet any additional meeting than the one you attended, so nothing missed yet fortunately.

Apologies for not having yet provided notes and coordinates for next meetings (we continued with preparations and arrangements for forthcoming meetings last week). I take profit of this mail for doing that.

Regarding the notes, these are the raw notes we collected, together with the material that was shared (attached):

8< --
Notes:
Luis Contreras introduced the purpose of the meeting according to chairs advice of merging three drafts touching the topic of 5G slices (based on 3GPP specs) and how to map to IETF Network Slices. The documents are https://datatracker.ietf.org/doc/draft-rokui-5g-ietf-network-slice/, https://datatracker.ietf.org/doc/draft-geng-teas-network-slice-mapping , https://datatracker.ietf.org/doc/draft-contreras-teas-3gpp-ietf-slice-mapping/
Xuesong Geng went through an initial exercise of merging parts of the existing documents as agreed among the main editors of the previous documents. The structure of the new documents expands the previous documents by adding section on terminology alignment between 3GPP and IETF, gap analysis on realization of 3GPP slices, as well as example of usage of IETF Network Slice NBI for requesting 5G slices
Hannu Flinck commented on the fact that figure 1 in chapter 3 of the merging exercise is not correct at all, being more precise the fig 2 in chapter 5 of the merging exercise. Authors will review and fix accordingly.
Luay Jalil commented on the fact of considering as well F1 interface as de defined by 3GPP as part of the network segment to be sliced (F1 implies to consider dissagregated scenarios in the radio part, i.e. RU / DU / CU).
Ivan Bykov commented that EP_transport in Release 16 considers in fact F1.
Hannu Flinck commented on the idea of considering simply the gNB for the purpose of the draft.
Luis Contreras commented that it is necessary to consider F1 to understand if some differences appear by that fact, and if so, to consider also F1 in the document.
Greg Mirsky commented about the work on slicing being performed in BBF. Greg suggest a liaison with BBF.
End of Notes
8< --

After the meeting we have been discussing on where to host the merged document, asking the chairs about using TEAS github for that, which has been agreed. So very next step will be to put there the merging exercise here attached.

We plan also to have weekly calls from now till IETF 114 with the objective of preparing a document that could be presented and discussed there. Main editors have agreed to meet on Thursdays 14:00 CET. By now we plan to use TEAMS session, which we can forward to interested individuals or to overall TEAS mailing list (@chairs, please, could you advice how to proceed?) By now I will forward the invite to Greg, waiting for further instructions on how to proceed.

Tomorrow we will have our first call, and for sure, we can record it (@chairs, please, could you advice where to store the recordings?)

Hope everything is clarified now

Best regards

Luis (on behalf of merged document editors)


De: Vishnu Pavan Beeram <[e-mail]>
Enviado el: miércoles, 22 de junio de 2022 15:56
Para: Greg Mirsky <[e-mail]>
CC: Rokui, Reza <[e-mail]>; Gengxuesong (Geng Xuesong) <[e-mail]>; LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>; TEAS WG <[e-mail]>; Ivan Bykov <[e-mail]>; TEAS WG Chairs <[e-mail]>
Asunto: Re: [Teas] Applicability of IETF network slices in the 3GPP context

Greg, Hi!

The meeting that was held was an open informal meeting driven by the authors of three related individual drafts (not by the chairs). It wasn’t recorded. The only instruction from the chairs to the authors of these documents is to find ways to collaborate and produce a single document that can be reviewed by the WG.

Note to the authors (who are driving these sessions):
Given the interest in the topic, please record subsequent meetings and share the notes/minutes on the list.

Regards,
-Pavan and Lou

On Wed, Jun 22, 2022 at 7:04 AM Greg Mirsky <[e-mail]<mailto:[e-mail]>> wrote:
Hi Pavan and Lou,
I missed the meeting (West Coast penalty).v I have several questions:

  *   if the meeting was recorded, where I can find it?
  *   if there were any presentation materials. where I can find/download them?
  *   had anyone proposed having periodic open meetings?
Regards,
Greg

On Thu, Jun 2, 2022 at 7:40 AM Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>> wrote:
The meeting has been scheduled as requested (June 10th 8am US Eastern Time). The webex invite has been sent out to the list.

Please note that this is an open informal session driven by the authors/contributors of the relevant drafts. The objective is to produce a single document on the topic that the TEAS WG can look to adopt.

Regards,
-Pavan and Lou

On Tue, May 31, 2022 at 9:42 PM Rokui, Reza <[e-mail]<mailto:[e-mail]>> wrote:
Hello TEAS chairs,

To give more time to all co-authors, would it be possible to create a Webex meeting for Friday June 10 @ 8:00 EST

Thanks,
Reza

From: Gengxuesong (Geng Xuesong) <[e-mail]<mailto:[e-mail]>>
Date: Tuesday, May 31, 2022 at 11:05 AM
To: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>, Rokui, Reza <[e-mail]<mailto:[e-mail]>>, Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>, TEAS WG <[e-mail]<mailto:[e-mail]>>, Ivan Bykov <[e-mail]<mailto:[e-mail]>>
Cc: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>, Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Subject: [**EXTERNAL**] RE: [Teas] Applicability of IETF network slices in the 3GPP context
Hi authors and WG,

It is great to hear that people agree this topic is important and willing to work together.

  1.  Call meeting proposal
Agree with Reza that a call meeting will be very helpful.
-       Friday June 3 @ 8:00 EST
-       Friday June 10 @ 8:00 EST
These 2 time slots both work for me and the 1st one is preferred. Could chairs kindly help to book a webex meeting if the authors think the time is suitable?

  1.  Document merge proposal
There are 3 documents in TEAS about this topic with slightly different side focus:

  *   draft-geng-teas-network-slice-mapping provides a procedure of mapping 5G end-to-end network defined in 5GPP slice to transport network slice defined in IETF, which gives guidance about how to use IETF network slice in 5G scenario in management plane, control plane and data plane respectively.
  *   draft-contreras-teas-3gpp-ietf-slice-mapping discusses mapping of 3GPP slice and IETF network slice endpoint and other related parameters, which mainly focuses about how to provide connection between 3GPP connection by IETF Network Slice with NSC
  *   draft-rokui-5g-ietf-network-slice discusses the relationship between 5G E2E network slicing and IETF network slice for 5G use-case, which also gives 5G IETF Network Slice NBI Information Model

Here is an initial proposal about the structure for combining these 3 documents:

  *   5G End-to-End Network Slice Introduction  . . . . . . . . .   background information summarized from 3 documents
  *   Network Slice Mapping Structure . . . . . . . . . . . . . . .   draft-geng-teas-network-slice-mapping/draft-rokui-5g-ietf-network-slice
  *   Network Slice Mapping Parameters  . . . . . . . . . . . . . . . draft-contreras-teas-3gpp-ietf-slice-mapping/ draft-geng-teas-network-slice-mapping
  *   Network Slice Mapping Procedure . . . . . . . . . . . . . . .   draft-geng-teas-network-slice-mapping

•   Network Slice Mapping in Management Plane . . . . . . . .   draft-contreras-teas-3gpp-ietf-slice-mapping

•   Network Slice Mapping in Control Plane  . . . . . . . . .  draft-geng-teas-network-slice-mapping

•   Network Slice Mapping in Data Plane . . . . . . . . . . .  draft-geng-teas-network-slice-mapping

  *   5G IETF Network Slice NBI  . . . . . . . . . . . . . . . .  draft-rokui-5g-ietf-network-slice

Best
Xuesong


From: LUIS MIGUEL CONTRERAS MURILLO [mailto:[e-mail]<mailto:[e-mail]>]
Sent: Tuesday, May 31, 2022 12:30 AM
To: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>; Rokui, Reza <[e-mail]<mailto:[e-mail]>>; Gengxuesong (Geng Xuesong) <[e-mail]<mailto:[e-mail]>>; Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>; TEAS WG <[e-mail]<mailto:[e-mail]>>; Ivan Bykov <[e-mail]<mailto:[e-mail]>>
Cc: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>; Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Subject: RE: [Teas] Applicability of IETF network slices in the 3GPP context

Adding my co-author Ivan to this thread for commenting on the proposed slots for the tentative discussion.

Best regards

Luis

De: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>
Enviado el: lunes, 30 de mayo de 2022 15:55
Para: Rokui, Reza <rrokui=[e-mail]<mailto:rrokui=[e-mail]>>; Gengxuesong (Geng Xuesong) <gengxuesong=[e-mail]<mailto:gengxuesong=[e-mail]>>; Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>; TEAS WG <[e-mail]<mailto:[e-mail]>>
CC: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>; Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Asunto: RE: [Teas] Applicability of IETF network slices in the 3GPP context

Agree here, as well.

I think we have complementary parts which are worthy to put together. On one hand there are generic architectural aspects that can show how 3GPP systems will act as upper systems of IETF NSC. There are also aspects on how 3GPP expects (as today) to requests slices at TN (in 3GPP terminology), which could show limitations (or undefined terms) on some of the required capabilities at the connectivity slices. And finally there are potential realizations today that could be documented.

The task is huge, anyway, so we need to analyze what can be delivered for IETF114, maybe an structure of the merged content, hopefully something else. In any case, definitely worthy to work on it.

Both dates as proposed by Reza are fine for me. I expect to do some preliminary work on proposition of parts to consider from the 3 drafts before the potential meeting, so we can advance with the work offline.

Thanks,

Best regards

Luis

De: Teas <[e-mail]<mailto:[e-mail]>> En nombre de Rokui, Reza
Enviado el: lunes, 30 de mayo de 2022 14:59
Para: Gengxuesong (Geng Xuesong) <gengxuesong=[e-mail]<mailto:gengxuesong=[e-mail]>>; Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>; TEAS WG <[e-mail]<mailto:[e-mail]>>
CC: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>; Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Asunto: Re: [Teas] Applicability of IETF network slices in the 3GPP context

Thanks Lou and Pavan,
Agreed with your suggestion.

To all authors of the three drafts mentioned below,
It would be a good idea to have a meeting between us to decide about the next step. What is the best way to have this meeting? Does either of the following slots work for you?

  *   Friday June 3 @ 8:00 EST
  *   Friday June 10 @ 8:00 EST
Cheers,
Reza

From: Teas <[e-mail]<mailto:[e-mail]>> on behalf of Gengxuesong (Geng Xuesong) <gengxuesong=[e-mail]<mailto:gengxuesong=[e-mail]>>
Date: Thursday, May 26, 2022 at 3:49 AM
To: Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>, TEAS WG <[e-mail]<mailto:[e-mail]>>
Cc: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>
Subject: [**EXTERNAL**] Re: [Teas] Applicability of IETF network slices in the 3GPP context
Hi Pavan and Lou,

Thanks for the suggestion. We will coordinate with the authors of other drafts.

Best
Xuesong

From: Teas [mailto:[e-mail]] On Behalf Of Vishnu Pavan Beeram
Sent: Wednesday, May 25, 2022 8:58 PM
To: TEAS WG <[e-mail]<mailto:[e-mail]>>
Cc: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>
Subject: [Teas] Applicability of IETF network slices in the 3GPP context

WG,
We (the chairs) acknowledge that it is important for the WG to work on a document that discusses the applicability of IETF network slices in the 3GPP context.

We have had 3 documents presented in past TEAS sessions that can form the basis of such a document:
https://datatracker.ietf.org/doc/draft-contreras-teas-3gpp-ietf-slice-mapping/
[datatracker.ietf.org]<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-contreras-teas-3gpp-ietf-slice-mapping/__;!!OSsGDw!MeCTM2ODJOQpcbP4VaxqGk4gua_Vi78oH8VsMeH8f7isG1X-DXxf1BRe0aWG0Ml7kcu9MAl_svtR5BwU3qWU5oOhIwk$>
https://datatracker.ietf.org/doc/draft-geng-teas-network-slice-mapping [datatracker.ietf.org]<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-geng-teas-network-slice-mapping/__;!!OSsGDw!MeCTM2ODJOQpcbP4VaxqGk4gua_Vi78oH8VsMeH8f7isG1X-DXxf1BRe0aWG0Ml7kcu9MAl_svtR5BwU3qWUreVkEHI$>
https://datatracker.ietf.org/doc/draft-rokui-5g-ietf-network-slice/
[datatracker.ietf.org]<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-rokui-5g-ietf-network-slice/__;!!OSsGDw!MeCTM2ODJOQpcbP4VaxqGk4gua_Vi78oH8VsMeH8f7isG1X-DXxf1BRe0aWG0Ml7kcu9MAl_svtR5BwU3qWULIAwjco$>

We encourage the authors of these documents to find ways to collaborate and produce a single document (ideally before IETF114) that the WG can look to adopt.

Regards,
-Pavan and Lou

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Teas mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/teas

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição