Closed sergiobelotti closed 1 year ago
@tsaad-dev can you comment on this? My understanding is the model allows this, but as Sergio points out, it is indeed a bidirectional P2P connection between Hub SDPs
@sergiobelotti Could you check whether the updated section 5 has addressed this issue? The A.5.2 has been removed since this seems redundant with A.5.1 and is also error-prone [A.5.
@sergiobelotti Could you check whether the updated section 5 has addressed this issue? The A.5.2 has been removed since this seems redundant with A.5.1 and is also error-prone [A.5. @lana-wu OK, thanks. You can close the issue for me.
The section A.5 of the draft is addressing the case of A2A and how you can differentiate the traffic flow management in the SDPs . In particular A.5.2 is showing the usage of multiple overlapping (in terms of SDPs) A2A constructs, with 2 A2A connectivity constructs with different slo-sle policy applied to the same set of SDPs. I think the usage of multiple A2A CC, is error-prone and a combination of P2P connectivity construct and one final A2A CC it would be the better way to go.