MPLS-TP Throughput Estimation draft-xiao-mpls-tp-throughput-estimation-01 Xiao Min (xiao. min 2@zte. com. cn) Jin Li. Zhong (lizhong. jin@zte. com. cn) Wu Bo (wu. bo@zte. com. cn) Yang Jian (yang_jian@zte. com. cn)
What's the main differences between the solution in this draft and that in Y. 1731? For both one-way and two-way throughput estimation n Binary Search vs. Increase rate with fixed step n OAM msg exchange vs. No OAM msg exchange n Result got At initiator MEP vs. At the remote MEP For only two-way throughput estimation n Two individual results vs. One minimum result (No loopback at the remote MEP) (Loopback at the remote MEP)
Why the solution in this draft is recommended? n More efficient – In most cases, binary search will take less time than fixed step length n More precise – In most cases, binary search will return more precise result than fixed step length n More convenient – The operator may provision and obtain result at only one MEP n More reasonable – For two-way throughput estimation two individual results return
What’s updated in 01 version? Remove ACH TLVs n Align format of test data packets with data plane loopback draft n Add exception process into the procedures n Add one open issue n
Next Steps Request comments to improve this draft n Move forward to WG draft n