Hi Pete, Thanks a lot for your comments. We will address these.
Thanks, Ramki From: [email protected] [mailto:[email protected]] On Behalf Of pete Sent: Tuesday, September 03, 2013 10:35 AM To: Melinda Shore Cc: [email protected]; [email protected] Subject: Re: [OPSAWG] WG last call for "Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks" I support this document, as these mechanisms are needed in SP and Research and Education Networks (RENs). I have a few minor comments: 1- 4.2. Overview of the mechanism ... Step 2) The egress component links are periodically scanned for link utilization. If the egress component link utilization exceeds a pre-programmed threshold, an operator alert is generated. The large flows mapped to the congested egress component link are exported to a central management entity I believe you mean to say that the information about the large flows is exported, rather than the large flows themselves being exported. 2 - Providing large flow information to a central management entity provides the capability to further optimize flow distribution at with multi-node visibility. The last part of that sentence needs clarification. Thanks. pete On Sat, Aug 24, 2013 at 1:07 PM, Melinda Shore <[email protected]<mailto:[email protected]>> wrote: This is to announce the start of working group last call on: Mechanisms for Optimal LAG/ECMP Component Link Utilization in Networks http://datatracker.ietf.org/doc/draft-ietf-opsawg-large-flow-load-balancing/ It is intended for publication as an informational RFC. Please give it a careful read and provide any feedback to this mailing list by September 9, 2013 Thanks, opsawg chairs _______________________________________________ OPSAWG mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
