[Teas] Re: I-D Action: draft-ietf-teas-5g-network-slice-application-06.txt

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

Hi all,

It was pending from my side to update on the way authors of draft-ietf-teas-5g-network-slice-application have addressed the comments from the 3GPP liaison concerning this document.

We went through both https://datatracker.ietf.org/liaison/2071/ (directly associated to the document) and https://datatracker.ietf.org/liaison/1957/ (which was targeted for the network slice realization document, currently RFC 9889, but that we consider as well for completeness, since it is related with the slicing work in IETF).

We extracted the points in the liaisons for a better way identifying commonalities at the time of proposing changes to address them, as follows:

/* First set of comments */:

C#1, LS-2071: “In Section 3.2 and 3.3, the FH, and MH are not 3GPP defined terminologies. For the FH described in the document, it is up to IETF TEAS to consider whether or how the methods discussed in the document for mapping between 3GPP E2E network slice and IETF network slice are used.”
C#2, LS-2071: “In Section 3.3, the definitions given for DU and CU (real-time and non-real-time components) are not consistent with 3GPP. The correct definitions for CU and DU are provided in 3GPP TS 38.401.”
C#3, LS-1957: “In light of the above, and to reflect the 5G NG-RAN architecture agreed in 3GPP, RAN3 kindly suggests IETF TEAS references in their document to TS 38.300, describing the NG-RAN architecture, and TS 38.401, describing the split NG-RAN architecture, to avoid possible misalignments”

Authors action -> All the three comments have been covered by adding the following text in Section 2.1: “The definitions of entities (e.g., DU, CU) or interfaces (e.g., F1) applicable to 3GPP slicing scenarios are provided by 3GPP specifications, such as [TS-38.401]. Similarly, the definitions of entities or interfaces (e.g., Midhaul) applicable to O-RAN slicing scenarios are provided by O-RAN specifications, such as [O-RAN-Arch]. Both 3GPP and O-RAN specifications take precedence over the definitions used in this document for 3GPP and O-RAN concepts.”

/* Second set of comments */

C#3, LS-2071: “In Section 3.4, the reference to Figure 6 seems incorrect, because the text refers to Figure 5.”

Authors action -> Typo fixed

C#4, LS-2071: “in Figure 20 and Figure 24 of section 7, the association between DU and CU-UP (i.e., the F1-U interface) is defined in 3GPP TS 38.401, TS 38.470, and TS 38.425, but not by other SDOs.”

Authors action -> Removed old text referring to O-RAN in the figure

/* Third set of comments */

C#1, LS-1957: “RAN3 would like to point out that RAN3 is not responsible for the design and specification of any aspect of IP/MPLS transport networks. However, RAN3´s Terms of Reference includes requirements concerning transport network layer´s protocols to be used for communication over 3GPP defined interfaces terminating at the NG-RAN. On these aspects, RAN3 would be happy to provide feedback, if needed.”

C#2, LS-1957: “In Appendix B.3 Radio Access Network (RAN), for the BBU/RU/Antenna components, there are no such definitions in RAN specifications. Also, for the F2 connecting between the RU and the DU in Figure 36 there is no such network interface and terminology described in 3GPP RAN specifications. And the DU in the Figure is not aligned with the DU defined in 3GPP RAN specification, in which it is a logical node also holding PHY layer in addition to RLC and MAC layers as specified in TS 38.401.”

Authors action ->  LS-1957 originally targeted the realization document (now RFC9889), and these two comments are not applicable to draft-ietf-teas-5g-network-slice-application

With this we understand that we have covered the comments received from 3GPP RAN3. This will be presented in TEAS session tomorrow.

There have not been further reactions to the draft from any other 3GPP group so far, then we understand there are no blocking points for progressing the document.

Of course, any feedback / reaction is more than welcome to improve and align the document in future versions.

Thanks in advance

Best regards

Luis

De: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]>
Enviado el: martes, 10 de marzo de 2026 5:02
Para: Vishnu Pavan Beeram <[e-mail]>
CC: [e-mail]; Charles Eckel (eckelcu) <eckelcu=[e-mail]>; [e-mail]
Asunto: [Teas] Re: I-D Action: draft-ietf-teas-5g-network-slice-application-06.txt

AVISO/WARNING: Este mail se ha originado fuera de la organización y no se pudo verificar al remitente / This mail was originated outside the organization and the sender could not be verified

Thanks a lot Pavan!

De: Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>
Enviado el: lunes, 9 de marzo de 2026 14:39
Para: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>
CC: [e-mail]<mailto:[e-mail]>; Charles Eckel (eckelcu) <eckelcu=[e-mail]<mailto:eckelcu=[e-mail]>>; [e-mail]<mailto:[e-mail]>
Asunto: Re: [Teas] Re: I-D Action: draft-ietf-teas-5g-network-slice-application-06.txt

AVISO/WARNING: Este correo electrónico se originó desde fuera de la organización. No haga clic en enlaces ni abra archivos adjuntos a menos que reconozca al remitente y sepa que el contenido es seguro / This email has been originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Luis,

This draft will be on the agenda for next week's TEAS WG session. The updated agenda will be posted mid-week.

Regards,
-Pavan

On Mon, Mar 9, 2026 at 6:06 AM LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>> wrote:
Dear Charles, Adrian, all,

The new versión intends to address both liasons, correct.

The way in which the comments are addressed will be reported in TEAS session (I was late asking a slot, so not sure if it will be in final agenda, otherwise we will include the status update slide on chairs deck). But of course, maybe is even better if we populate this to the mailing list, so I take the action of doing so in the next days.

Thanks

Luis

De: Adrian Farrel <[e-mail]<mailto:[e-mail]>>
Enviado el: lunes, 9 de marzo de 2026 12:57
Para: 'Charles Eckel (eckelcu)' <eckelcu=[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Asunto: [Teas] Re: I-D Action: draft-ietf-teas-5g-network-slice-application-06.txt

AVISO/WARNING: Este correo electrónico se originó desde fuera de la organización. No haga clic en enlaces ni abra archivos adjuntos a menos que reconozca al remitente y sepa que el contenido es seguro / This email has been originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Charles,

I think you’ll find that this revision is just a keep-alive – some of us have been whining about WG I-Ds that are allowed to expire :-)

But’ you’re right: the liaisons provide important comments that the WG needs to fold into the draft.

Cheers,
Adrian

From: Charles Eckel (eckelcu) <eckelcu=[e-mail]<mailto:eckelcu=[e-mail]>>
Sent: 09 March 2026 11:35
To: [e-mail]<mailto:[e-mail]>
Subject: [Teas] Re: I-D Action: draft-ietf-teas-5g-network-slice-application-06.txt

Hi Authors,

Thanks for posting this update to the draft.

Is it intended to have addresses the feedback provided by 3GPP?
https://datatracker.ietf.org/liaison/2071/
https://datatracker.ietf.org/liaison/2096/

Thanks,
Charles

On Mar 3, 2026, at 8:15 AM, [e-mail]<mailto:[e-mail]> wrote:

Internet-Draft draft-ietf-teas-5g-network-slice-application-06.txt is now
available. It is a work item of the Traffic Engineering Architecture and
Signaling (TEAS) WG of the IETF.

  Title:   IETF Network Slice Application in 3GPP 5G End-to-End Network Slice
  Authors: Xuesong Geng
           Luis M. Contreras
           Reza Rokui
           Jie Dong
           Ivan Bykov
  Name:    draft-ietf-teas-5g-network-slice-application-06.txt
  Pages:   68
  Dates:   2026-03-02

Abstract:

  Network Slicing is one of the core features of 5G defined in 3GPP,
  which provides different network service as independent logical
  networks.  To provide 5G network slices services, an end-to-end
  network slice has to span three network segments: Radio Access
  Network (RAN), Mobile Core Network (CN) and Transport Network (TN).
  This document describes the application of the IETF network slice
  framework in providing 5G end-to-end network slices, including
  network slice mapping in the management, control and data planes.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-5g-network-slice-application/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-teas-5g-network-slice-application-06

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-teas-5g-network-slice-application-06

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Teas mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>


________________________________

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]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>

________________________________

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