Liaison statement
Reply LS on “IETF Network Slice Application in 3GPP 5G End-to-End Network Slice”

1       Overall description

RAN3 thanks IETF TEAS for the LS on "IETF Network Slice Application in 3GPP 5G
End-to-End Network Slice".

For the informational document, RAN3 would like to highlight that the points
mentioned in the previous LS in R3-244785 (e.g., referring to the 3GPP
specifications on 5G NG-RAN architecture) should also be considered. RAN3 would
like to provide the following observations:

- 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.

- 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.

- In Section 3.4, the reference to Figure 6 seems incorrect, because the text
refers to Figure 5.

- 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.

2       Actions
To IETF TEAS:
ACTION:         RAN3 respectfully asks to take above information into account.

3       Dates of next RAN3 meetings
Updated meeting schedule can be found at:
https://portal.3gpp.org/?tbid=373&SubTB=381#/ RAN3#130        2025-11-17 -
2025-11-21         Dallas, US