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

[Shunsuke Homma <[e-mail]>]

Hi authors,

I have some questions on mapping(stitching?) of 3GPP and IETF network
slices as below, and I'll be happy if they are resolved in this work.

-  Is any special identifier, which is IETF-nodes aware (e.g., SID in an
IPv6 extension header, MPLS label, NSH, etc.), is needed for classification
on IETF NS PE? As you know, packets on N3 and N9 interfaces are
encapsulated  with GTP-U, and traffic assigned to different network slices
may have the same src/dst IP addresses. If we use some special identifier,
a standardized scheme for that would be needed, especially for
multi-administrative domains environment. Or, 3GPP 5G system is required to
deploy an interface or a UPF instance for each network slice?

- Are there any differences between procedures of mapping/stitching
3GPP-IETF network slices at RAN, 5G-Core, and DN (i.e., N3, N6, and N9
interfaces) ? (For example, information exchanged between IETF NSC and 5G
OpS, or classification scheme.) 5G has MEC scenarios and guaranteed
communication quality may be required in DN. On N6 packets are passed as
user-plane PDU, and network slices run on DN may be required to support
ethernet and unstructured forms, in addition to IPv4/v6 (ref TS23 501).
Also, 5G allows multiple access, and we may need to consider cases where
IETF network slices deployed on a fixed network (this is not TN within RAN)
connected to a 5G-core.

Regards,

Shunsuke




2022年6月3日(金) 12:01 Gengxuesong (Geng Xuesong) <gengxuesong=
[e-mail]>:

> Thanks Pavan and Lou. The webex invite is received.
>
>
>
> *From:* Vishnu Pavan Beeram [mailto:[e-mail]]
> *Sent:* Thursday, June 2, 2022 10:40 PM
> *To:* Rokui, Reza <[e-mail]>
> *Cc:* Gengxuesong (Geng Xuesong) <[e-mail]>; LUIS MIGUEL
> CONTRERAS MURILLO <[e-mail]>; TEAS WG <
> [e-mail]>; Ivan Bykov <[e-mail]>; TEAS WG Chairs <
> [e-mail]>
> *Subject:* Re: [Teas] Applicability of IETF network slices in the 3GPP
> context
>
>
>
> 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]> 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]>
> *Date: *Tuesday, May 31, 2022 at 11:05 AM
> *To: *LUIS MIGUEL CONTRERAS MURILLO <
> [e-mail]>, Rokui, Reza <[e-mail]>,
> Vishnu Pavan Beeram <[e-mail]>, TEAS WG <[e-mail]>,
> Ivan Bykov <[e-mail]>
> *Cc: *TEAS WG Chairs <[e-mail]>, Rokui, Reza <[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]]
> *Sent:* Tuesday, May 31, 2022 12:30 AM
> *To:* LUIS MIGUEL CONTRERAS MURILLO <
> [e-mail]>; Rokui, Reza <[e-mail]>;
> Gengxuesong (Geng Xuesong) <[e-mail]>; Vishnu Pavan Beeram <
> [e-mail]>; TEAS WG <[e-mail]>; Ivan Bykov <
> [e-mail]>
> *Cc:* TEAS WG Chairs <[e-mail]>; Rokui, Reza <[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]>
> *Enviado el:* lunes, 30 de mayo de 2022 15:55
> *Para:* Rokui, Reza <rrokui=[e-mail]>; Gengxuesong
> (Geng Xuesong) <gengxuesong=[e-mail]>; Vishnu Pavan
> Beeram <[e-mail]>; TEAS WG <[e-mail]>
> *CC:* TEAS WG Chairs <[e-mail]>; Rokui, Reza <[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]> *En nombre de *Rokui, Reza
> *Enviado el:* lunes, 30 de mayo de 2022 14:59
> *Para:* Gengxuesong (Geng Xuesong) <
> gengxuesong=[e-mail]>; Vishnu Pavan Beeram <
> [e-mail]>; TEAS WG <[e-mail]>
> *CC:* TEAS WG Chairs <[e-mail]>; Rokui, Reza <[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]> on behalf of Gengxuesong (Geng
> Xuesong) <gengxuesong=[e-mail]>
> *Date: *Thursday, May 26, 2022 at 3:49 AM
> *To: *Vishnu Pavan Beeram <[e-mail]>, TEAS WG <[e-mail]>
> *Cc: *TEAS WG Chairs <[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] <[e-mail]>] *On
> Behalf Of *Vishnu Pavan Beeram
> *Sent:* Wednesday, May 25, 2022 8:58 PM
> *To:* TEAS WG <[e-mail]>
> *Cc:* TEAS WG Chairs <[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]
> https://www.ietf.org/mailman/listinfo/teas
>