Hi Jeffrey, all, Thanks for putting together an interesting draft on mobile user plane evolution and related IP network related aspects. There are some important aspects that IETF/dmm could consider for xG without directly impacting 3GPP architecture/standards. This is partly described in comments under (3) below but would obviously need much more discussion in the group.
Questions/comments for consideration: 1. Motivation for tightly integrating AN/UP functions in section 1.1 is not fully clear The point seems to be that with further virtualization and disaggregation, the functions could be combined. Sure, but the advantage of "combining" them is not clearly mentioned. - for simplification (as for multicast, mobility, etc), perhaps the draft can outline best practices to cut out unnecessary options, integrated management of AN + UP. - for performance, pseudo-wire as in 1.2 or some other dedicated high speed N3 connection should suffice (along with other recommendations in 3). 2. Concerns when combining AN, UP: While the draft points out advantages of combining, there are some risks as well. For example: a) QoS - the basic QoS aspects that are conveyed via N4 to UPF (filters, rules, etc) and other policies via NG-AP to RAN (and GTP-U /N3 in between) need to be considered in depth. Further, there are studies in 3GPP Rel 18 that are extending the QoS model, what's handled on N4, policies to UPF or RAN and extensions to GTP-U. Just saying that its all at ANUP does not address the issues (and furthermore, this would be 3GPP work). b) network sharing - in cases where, e.g., provider A operates AN and providers B, C operates UPs, tight integration into ANUP can be inflexible. (Reverse is also an issue, i.e., providers X, Y operate ANs and provider Z operates UP) 3. Other aspects Consistent with the trend/direction to "softwarize" the different network components, i.e., AN and UP in this case, IETF may be able to complement 3GPP standards. For example, scenarios where AN, UP functions deployed in an infrastructure domain /data center and how security aspects, routing, QoS, mobility or management of these group of functions are handled optimally. (Note that in the above case, AN and UP are perhaps "loosely" integrated as opposed to the "tight" integration in ANUP) BR, John
_______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm