<?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 CSS Command flow tcp-del-ack  in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-command-flow-tcp-del-ack/m-p/540949#M10173</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i've found a Command in the Docs, that was addes in 7.50.103 to normal Command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read a thread, where Gilles wrote about a L5 rule, which should makes a delay of 200 ms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure if i understand delayed ack right, but i think if disabled there should be no delay and if enabled there shoud one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can tell me what this feature exactly does and if it should be enabled or disabeld on L5 rules?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Sven&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 25 May 2006 14:14:20 GMT</pubDate>
    <dc:creator>Sbutzek</dc:creator>
    <dc:date>2006-05-25T14:14:20Z</dc:date>
    <item>
      <title>CSS Command flow tcp-del-ack</title>
      <link>https://community.cisco.com/t5/application-networking/css-command-flow-tcp-del-ack/m-p/540949#M10173</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i've found a Command in the Docs, that was addes in 7.50.103 to normal Command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I read a thread, where Gilles wrote about a L5 rule, which should makes a delay of 200 ms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure if i understand delayed ack right, but i think if disabled there should be no delay and if enabled there shoud one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can tell me what this feature exactly does and if it should be enabled or disabeld on L5 rules?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Sven&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2006 14:14:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-command-flow-tcp-del-ack/m-p/540949#M10173</guid>
      <dc:creator>Sbutzek</dc:creator>
      <dc:date>2006-05-25T14:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: CSS Command flow tcp-del-ack</title>
      <link>https://community.cisco.com/t5/application-networking/css-command-flow-tcp-del-ack/m-p/540950#M10174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with L5 rule, if a request spans multiple packets, the CSS waits 200msec before ACKing a packet.&lt;/P&gt;&lt;P&gt;This is to save resources and wait in case the next packet was already sent by the client.&lt;/P&gt;&lt;P&gt;However, some client needs the ACK before sending the next packet, so the command disable this delay.&lt;/P&gt;&lt;P&gt;So we will always send the ACK and no longer wait for the next packet.&lt;/P&gt;&lt;P&gt;If your CSS is already being overloaded, you should not use this command, otherwise it is pretty safe and will increase performance seen from a client perspective.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 May 2006 06:07:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-command-flow-tcp-del-ack/m-p/540950#M10174</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2006-05-26T06:07:33Z</dc:date>
    </item>
  </channel>
</rss>

