[Teas] 答复: Fwd: WG Last Call: draft-ietf-teas-native-ip-scenarios-05

Hi, Qin:

Thanks for your review.

Please see the responses below inline for your comments.

Best Regards.

Aijun Wang

Network R&D and Operation Support Department

China Telecom Corporation Limited Beijing Research Institute,Beijing, China.

发件人: Qin Wu [mailto:bill.wu@huawei.com] 
发送时间: 2019年6月25日 14:40
收件人: lberger@labn.bet
抄送: teas@ietf.org
主题: Re: [Teas] Fwd: WG Last Call: draft-ietf-teas-native-ip-scenarios-05

I have read this draft and have a few comments:

1.       Section 1 paragraph2 

“   MPLS-TE technology is one solution for finely planned network but it

   will put heavy burden on the routers when we use it to meet the

   dynamic QoS assurance requirements within real time traffic network.”

Do we have real time traffic network, how about s/ QoS assurance requirements within real time traffic network/ QoS assurance requirements for real time traffic

【Aijun Wang】: Yes, we have.  The scenarios described in this document are all raised on our Native IP network. Customer wants the operator to provide some solutions to these requirements. The traffic is changing dynamically in real time, but it has some regular pattern within a day, a week or a month.  The solution to these requirements is described in  https://datatracker.ietf.org/doc/draft-ietf-teas-pce-native-ip/ (Solution Draft), which depends mainly on the global view and optimal path calculation capabilities of SDN/PCE components.

2.       Section 1, paragraph 4

“DetNet[RFC8578] describes use cases for diverse industries that have

   in common a need for "deterministic flows",”

s/ that have in common a need/that have a common need

【Aijun Wang】: OK, will update in next version.

3.       Section 2.1

“

The communication between the private and public cloud will span the WAN

network.  The bandwidth requirements between them are variable and

the background traffic between these two sites changes from time to

time. “

To make these two sentence coherent and consist with the figure in this section, suggested change
The communication between the private and public cloud sites will span the WAN

network.  The bandwidth requirements between them are variable and

the background traffic between these two sites changes from time to

time.

【Aijun Wang】： OK, will update in next version.

4.  Section 2.3

Can you clarify what traffic engineering technology is used in this case? If there is no traffic engineering technology used,

Suggest to change the title into traffic load balance support

【Aijun Wang】: It is one special situation within TE domain and is different from the traditional load balance scenario. As described in the text, the main challenge here is that the asymmetric flow characteristic of the links. One can only eliminate such phenomena via the movement of some traffic from the default path to the calculated optimal path.

-Qin

From: Lou Berger <lberger@labn.net>
Date: June 14, 2019 at 00:51:17 GMT+8
To: TEAS WG <teas@ietf.org>
Subject: [Teas] WG Last Call: draft-ietf-teas-native-ip-scenarios-05

All,

This starts a two-week working group last call for
draft-ietf-teas-native-ip-scenarios-05

The working group last call ends on June 27.
Please send your comments to the working group mailing list.

Positive comments, e.g., "I've reviewed this document
and believe it is ready for publication", are welcome!
This is useful and important, even from authors.

Thank you,
Lou (TEAS Co-Chair & doc Shepherd)

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas