Closed boucadair closed 10 months ago
I think both modes has its own merit. Pull mode is suitable for centralized C-PS and can get better overall usage result. Push mode is suitable for distributed C-PS and does not introduce the pull latency. Please see Hybrid Solution draft and its slides for detailed discussion.
I think both modes are needed. However, in this section, I do not think the text emphasize this. It describes the processing of first packet and the following packets. so we may rephrase it as
In the example shown in Figure 2, the client sends a service access to the network though the "CATS-Forwarder 1" that is an Ingress CATS-Forwarder. Note that, a service access consists of one or more service packets. The Ingress CATS-Forwarder classifies incoming packets received from clients by the information provided by the CATS classifier (C-TC). When a matching classification entry is found for the packets, the Ingress CATS-Forwarder encapsulates and forwards them to the C-PS selected Egress CATS-Forwarder. When these packets reach the Egress CATS-Forwarder, the outer header of the possible overlay encapsulation is removed and inner packets are sent to the relevant service contact instance.
what do you think?
This has been closed by https://github.com/boucadair/CATS-framework/pull/54
Section 4.4 have the following, which may seem to be contradicting:
and
We need to discuss if we allow both Pull/Push modes or only a mode. Then, make sure we are consistent in the doc