Hi Sri, Please find below some questions and comments. Best regards, Arashmid
1- This technique certainly eliminates the need for fixed anchor points from the data plane point of view. However, it is not clear what happens to other functions provided by the existing 3GPP fixed anchor points. It should be possible to program the nodes for these additional functions as well. I think a list of existing functions or those required by 5G in 3GPP would be a good starting point for the discussion. 2- Performance is another issue. How fast can we detect and then program MFA nodes? This is the issue that applies to all different approaches. I think performance merits a section in the draft. 3- An example with SRv6 and/or SRv6 with ID-LOC might serve the document well. Appendix? 4- Page 5, end of MFA-MNA paragraph: " Typically, the MFA-MNA function will be collocated with the UPF in the 3GPP 5G system architecture." Couldn't it be collocated with the gNB as well? Or did you purposely took gNB out to avoid touching the N3 interface? 5- When correspondent nodes are mobile themselves. e.g. UE-UE communication, isn't the MFA-CNA is just another MFA-MNA? Some clarification in the draft might come handy. 6- Page 14, figure 5: Need to change MFA-NMA-->MFA-MNA, and MFA-CAN--> MFA-CNA in the figure. 7- How does paging work? Not sure about this one, but is it possible for a UE to go to be idle (a new inactive state has also been added in the spec) in one gNB and wake in another that connects to a different first hop router? 8- Page 19 after step 10: It might be useful to talk about how and when MFA-CN removes the rule for H1::/64 from AG-2. I guess it is something along what described in 4.3. 9- Page 20, section 4.3, step 1: Might be useful to indicate how the system would know when a flow is inactive and hence the rules associated with it are no longer need.
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
