RE: [tcpm] AW: RFC2581bis ooo acking WAS: New I-D posted :draft-moncaster-tcpm-rcv-cheat-00

"Anantha Ramaiah \(ananth\)" <ananth@cisco.com> Sun, 25 February 2007 18:04 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLNk0-0001Ll-3Q; Sun, 25 Feb 2007 13:04:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLNjy-0001Lg-MN for tcpm@ietf.org; Sun, 25 Feb 2007 13:04:54 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLNjv-0004aP-Nu for tcpm@ietf.org; Sun, 25 Feb 2007 13:04:54 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 25 Feb 2007 10:04:51 -0800
X-IronPort-AV: i="4.14,216,1170662400"; d="scan'208"; a="466961627:sNHT47861768"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l1PI4pN1014436; Sun, 25 Feb 2007 10:04:51 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l1PI4fUw023144; Sun, 25 Feb 2007 10:04:45 -0800 (PST)
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 25 Feb 2007 10:04:40 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [tcpm] AW: RFC2581bis ooo acking WAS: New I-D posted :draft-moncaster-tcpm-rcv-cheat-00
Date: Sun, 25 Feb 2007 10:04:39 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC5802ED6AC4@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <1172408468.45e1889489b08@web-mail2.uibk.ac.at>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] AW: RFC2581bis ooo acking WAS: New I-D posted :draft-moncaster-tcpm-rcv-cheat-00
Thread-Index: AcdY3Xp0vzFmNpcPS0WyFOClm/8PWQAJAdQw
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: Michael Welzl <Michael.Welzl@uibk.ac.at>, tcpm@ietf.org
X-OriginalArrivalTime: 25 Feb 2007 18:04:40.0857 (UTC) FILETIME=[6B9EF090:01C75907]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2097; t=1172426691; x=1173290691; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ananth@cisco.com; z=From:=20=22Anantha=20Ramaiah=20\(ananth\)=22=20<ananth@cisco.com> |Subject:=20RE=3A=20[tcpm]=20AW=3A=20RFC2581bis=20ooo=20acking=20WAS=3A=2 0New=20I-D=20posted=20=3Adraft-moncaster-tcpm-rcv-cheat-00 |Sender:=20; bh=crur7iAen5P228lBnHoVoQR7gHORX682YGI+04f/WyM=; b=br/LN6mYgKG8StElnXLbX7wEh/xQvzPV4jTXCvL0vjIZ5d6NgjLZK4WQSbqo9OQNRVvpesOo NuBP6KeHmGoYsplfOj92wjx8y0pGMHiaYshn6fRfMiYfPPoNK86b6q6r;
Authentication-Results: sj-dkim-3; header.From=ananth@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc:
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

Actually my thinking is a bit different here. If there is choice to
pick, and I was given that choice, I would go with MUST ;-) A few
comments inline ( I may be repeating myself here)..... 

<snip>

> 
> Zitat von Ethan Blanton <eblanton@cs.ohiou.edu>:
> 
> > [The "something" below being delaying a dup ACK for a 
> segment received  
> > out-of-order using delayed ACKs.]
> >
> > Michael Welzl spake unto us the following wisdom:
> > > Does it make sense to allow a receiver to do something 
> which has no 
> > > obvious benefit, but clearly leads to undesirable behavior?
> >
> > Yes, if it does not break the protocol.  The receiver may 
> have other 
> > concerns than absolute rapidity of throughput; for example, power 
> > savings, bandwidth conservation, local processing time, etc. etc.
> > This, in my mind, simply falls into the realm of dictating 
> > implementation details.  The point is that a receiver delaying that 
> > out-of-order ACK will still perform correctly with respect 
> to protocol 
> > semantics, it may just take a little bit longer.

- The question I would ask is: "Is fast retransmission considered a
MUST? Yes, according to RFC 2581. If so I would think the surrounding
mechanisms, esp the ones which has direct influence, which facilitate
the fast-retransmision, can also be considered for a MUST candidate,
like in this case the generation of Duplicate ACK's. 

- The above example on "power savings, b/w conservation etc.," can be
applied to, in theory, to any packet, not just the duplicate ACK's. I
may sound argumentative here, but my experience ( not theoretical,
coming from working on internet devices/stacks which use TCP) treats the
dupacks as a MUST. Also to my knowledge, I haven't heard of stacks which
don't send or delay ( the latter may be ok, like you point out above)
these duplicate ACKs and would be interested to know if any one of the
widely used stacks permit this either naturally or by means of knob. But
this is my opinion, OMMV.

Thanks,
-Anantha

<snip>

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm