Re: Fwd: Re: [PMOL] Fwd: I-D Action: draft-sun-tsvwg-flowbased-pm-00.txt

Hi Morton and Andreas, 

Thanks for your comments. I have read the RFCs and give comments as follow.
We called the method we proposed FPM.

1. The differences between TWAMP and FPM:
(1) Technically, although FPM is an active measurement protocol, there exist much difference between
TWAMP and FPM. First, TWAMP and FPM both support the on-the-spot measurement, it means that they can
perform measurement online 
when traffic of applications is running. But TWAMP is probe based, in TWAMP, extra probe measurement
packets are injected to simulate real traffic, to carry out measurements and sample the performance of
the network. The frequency 
of injected packets has great impact on the accuracy of measurements. For example, if TWAMP wants to
measure an application that transmits packets frequently, it should also injected probe measurement
packets (TWAMP-test packets) frequently, then it may make negative impact on the real traffic of
applications, otherwise it can't reflect the actual service performance if the TWAMP-test packets are
sparsely inserted.
FPM is based on the running traffic of applications, it collects the statistics of real traffic flow. FPM
needs additional OAM packets participate in measurement. The OAM packets are used to carry statistics of
the path/flow/application, they can be small and the inserted frequency can be lower.

(2) In addition, in some cases, it needs to monitor the various time-varying performance indexes of the IP
network, the performance measurement should be based on real traffic  and reflect the real performance of
the network. 
IP Performance Monitoring based on flow/applications is needed in many cases. For example, in mobile
operator's backhaul network, there must be performance monitoring mechanism to check the traffic
status in the network, and the applications/traffic are divided into multiple bearers with proper
mobile QoS parameters (e.g. QCI). If the mobile network would manage bearers as QoS and applications,
then the performance of backhaul is more like to be based on applications or QoS. With the status
information, some strategies can be implemented, for example, eNB can implement online congestion