Liaison statement
LS Reply on "A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
| State | Posted |
|---|---|
| Submitted Date | 2024-09-05 |
| From Group | 3GPP-TSGSA-SA2 |
| From Contact | Charles Eckel |
| To Group | teas |
| To Contacts | Vishnu Beeram <vbeeram@juniper.net> Lou Berger <lberger@labn.net> Oscar de Dios <oscar.gonzalezdedios@telefonica.com> |
| Cc | Oscar de Dios <oscar.gonzalezdedios@telefonica.com> Gunter Van de Velde <gunter.van_de_velde@nokia.com> Traffic Engineering Architecture and Signaling Discussion List <teas@ietf.org> Jim Guichard <james.n.guichard@futurewei.com> John Scudder <jgs@juniper.net> Vishnu Beeram <vbeeram@juniper.net> |
| Response Contact | Peter.Schmitt@huawei.com Susanna Kooistra <3GPPLiaison@etsi.org> |
| Purpose | In response |
| Attachments | S2-2408691 upload was 7889 LSOut LS Reply on A Realization of Network Slices for 5G Networks Using Current IP MPLS Technologies_Jinguo (002) |
| Liaisons referred by this one |
LS on a Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies
|
| Body |
1. Overall Description:
Thanks IETF for the LS on "A Realization of Network Slices for 5G Networks
Using Current IP/MPLS Technologies". SA2 would like to provide feedback related
to system architecture.
1.For the description of 5G architecture in Appendix B.1 and B.2, it is
suggested to only have reference to TS 23.501 in IETF specifications instead of
repeating the description to have an up-to-date architecture and functionality
of 5GS. Currently the description is not precise. 2.Regarding clause 4, SA2 has
not discussed any mechanism to associate the end point of GTP-U tunnel with the
S-NSSAI because there is no need to introduce such mechanism for 5GS to
differentiate the tunnels of different slices. 3.Regarding clause 5, SA2 would
like to clarify 5G QoS model is an independent feature from network slicing.
Binding with S-NSSAI is not aligned with the current 5G QoS model.
2. Actions:
To IETF Traffic Engineering Architecture and Signaling Working Group
(teas)group. ACTION: SA2 asks IETF Traffic Engineering Architecture and
Signaling Working Group (teas) group to take the above information into account.
3. Date of Next TSG SA WG2 Meetings:
TSG-SA2 Meeting #165 15th Oct – 18th Oct, 2024
Hyderabad, IN TSG-SA2 Meeting #166 17th Nov – 22nd Nov, 2024
Orlando, US
|