<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ACK Filter one direction on MLX in Data Center (MLX &amp; CER/CES)</title>
    <link>https://community.extremenetworks.com/t5/data-center-mlx-cer-ces/ack-filter-one-direction-on-mlx/m-p/52295#M4</link>
    <description>IHAC who provides Internet service to customers.  He has asymmetrical bandwidth that he provides via a broadband access product (600Mbit/sec down and 20Mbit/sec up).  He wants to keep his download speeds high for his customers so he want to only prioritize his customer's ACK packets back for their TCP applications.  I am sure someone other provider of ours ran into this same problem already. Do we have a sample ACL that can accomplish this?&lt;BR /&gt;</description>
    <pubDate>Fri, 13 Apr 2018 18:08:00 GMT</pubDate>
    <dc:creator>John_Brancato</dc:creator>
    <dc:date>2018-04-13T18:08:00Z</dc:date>
    <item>
      <title>ACK Filter one direction on MLX</title>
      <link>https://community.extremenetworks.com/t5/data-center-mlx-cer-ces/ack-filter-one-direction-on-mlx/m-p/52295#M4</link>
      <description>IHAC who provides Internet service to customers.  He has asymmetrical bandwidth that he provides via a broadband access product (600Mbit/sec down and 20Mbit/sec up).  He wants to keep his download speeds high for his customers so he want to only prioritize his customer's ACK packets back for their TCP applications.  I am sure someone other provider of ours ran into this same problem already. Do we have a sample ACL that can accomplish this?&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Apr 2018 18:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-mlx-cer-ces/ack-filter-one-direction-on-mlx/m-p/52295#M4</guid>
      <dc:creator>John_Brancato</dc:creator>
      <dc:date>2018-04-13T18:08:00Z</dc:date>
    </item>
  </channel>
</rss>

