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

Hi,

I also agree with the importance of this work. We are planning to provide
"transport network" to mobile carriers, and I expect the future
requirements for "transport network" would be clarified from this work.

BTW, although its scope is not only 3GPP network slice, the following
document may be help to understand the architecture of 3GPP user plane and
its requirements including network slicing.

https://www.ietf.org/archive/id/draft-ietf-dmm-5g-uplane-analysis-04.txt

Regards,

Shunsuke

2022年5月31日(火) 1:29 LUIS MIGUEL CONTRERAS MURILLO <
luismiguel.contrerasmurillo@telefonica.com>:

> 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 <
> luismiguel.contrerasmurillo@telefonica.com>
> *Enviado el:* lunes, 30 de mayo de 2022 15:55
> *Para:* Rokui, Reza <rrokui=40ciena.com@dmarc.ietf.org>; Gengxuesong
> (Geng Xuesong) <gengxuesong=40huawei.com@dmarc.ietf.org>; Vishnu Pavan
> Beeram <vishnupavan@gmail.com>; TEAS WG <teas@ietf.org>
> *CC:* TEAS WG Chairs <teas-chairs@ietf.org>; Rokui, Reza <rrokui@ciena.com
> >
> *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 <teas-bounces@ietf.org> *En nombre de *Rokui, Reza
> *Enviado el:* lunes, 30 de mayo de 2022 14:59
> *Para:* Gengxuesong (Geng Xuesong) <
> gengxuesong=40huawei.com@dmarc.ietf.org>; Vishnu Pavan Beeram <
> vishnupavan@gmail.com>; TEAS WG <teas@ietf.org>
> *CC:* TEAS WG Chairs <teas-chairs@ietf.org>; Rokui, Reza <rrokui@ciena.com
> >
> *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 <teas-bounces@ietf.org> on behalf of Gengxuesong (Geng
> Xuesong) <gengxuesong=40huawei.com@dmarc.ietf.org>
> *Date: *Thursday, May 26, 2022 at 3:49 AM
> *To: *Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>
> *Cc: *TEAS WG Chairs <teas-chairs@ietf.org>
> *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:teas-bounces@ietf.org <teas-bounces@ietf.org>] *On
> Behalf Of *Vishnu Pavan Beeram
> *Sent:* Wednesday, May 25, 2022 8:58 PM
> *To:* TEAS WG <teas@ietf.org>
> *Cc:* TEAS WG Chairs <teas-chairs@ietf.org>
> *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
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>