Re: [tcpm] review of draft-zimmermann-tcpm-reordering-detection
"Zimmermann, Alexander" <Alexander.Zimmermann@netapp.com> Fri, 06 February 2015 17:46 UTC
Return-Path: <Alexander.Zimmermann@netapp.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1351D1A700C for <tcpm@ietfa.amsl.com>; Fri, 6 Feb 2015 09:46:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DAfBBMsFvsK for <tcpm@ietfa.amsl.com>; Fri, 6 Feb 2015 09:46:06 -0800 (PST)
Received: from mx142.netapp.com (mx142.netapp.com [216.240.21.19]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C5F01A1E0F for <tcpm@ietf.org>; Fri, 6 Feb 2015 09:46:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,530,1418112000"; d="asc'?scan'208";a="20937212"
Received: from hioexcmbx06-prd.hq.netapp.com ([10.122.105.39]) by mx142-out.netapp.com with ESMTP; 06 Feb 2015 09:41:05 -0800
Received: from HIOEXCMBX06-PRD.hq.netapp.com (10.122.105.39) by hioexcmbx06-prd.hq.netapp.com (10.122.105.39) with Microsoft SMTP Server (TLS) id 15.0.995.29; Fri, 6 Feb 2015 09:41:05 -0800
Received: from HIOEXCMBX06-PRD.hq.netapp.com ([::1]) by hioexcmbx06-prd.hq.netapp.com ([fe80::5ceb:17f1:1ecd:c4c9%21]) with mapi id 15.00.0995.031; Fri, 6 Feb 2015 09:41:05 -0800
From: "Zimmermann, Alexander" <Alexander.Zimmermann@netapp.com>
To: Wesley Eddy <wes@mti-systems.com>
Thread-Topic: [tcpm] review of draft-zimmermann-tcpm-reordering-detection
Thread-Index: AQHQQXzFva7VDhVhZUSRjwVCoGgnfpzka0qA
Date: Fri, 06 Feb 2015 17:41:04 +0000
Message-ID: <1E453322-868C-4569-8635-231440E04417@netapp.com>
References: <54D3C911.6020205@mti-systems.com>
In-Reply-To: <54D3C911.6020205@mti-systems.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.2070.6)
x-originating-ip: [10.120.60.36]
Content-Type: multipart/signed; boundary="Apple-Mail=_B1B676FC-F386-407D-B79A-A51398AC67C6"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/46ZhWXfAgH6L8WmmtaxZck4PvYw>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] review of draft-zimmermann-tcpm-reordering-detection
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 17:46:12 -0000
Hi Wes, thanks a lot for looking into the draft! Comments below. > Am 05.02.2015 um 20:48 schrieb Wesley Eddy <wes@mti-systems.com>: > > I reviewed the reordering detection algorithm document: > https://tools.ietf.org/html/draft-zimmermann-tcpm-reordering-detection-02 > > The document is very well written. The specification in the draft seems > quite clear and like it would be easy to implement directly from the > document. > > The purpose of section 4.7 ("Placeholder for Response Algorithm") isn't > clear to me, especially in relation to the separate reaction draft > (draft-zimmermann-tcpm-reordering-reaction). The purpose of section 4.7 is to have a hook for a further reordering reaction algorithm. RFC 4015 has something similar. However, Eifel reaction is maybe a bit more explicit and clear at this point (see step (DET) in RFC 4015) > > One thing that was unclear to me, and seems useful, is a discussion of > the potential sources of error. In other words, what events would > cause the computed metrics to be wrong and how significantly wrong? > There are a number of different events and potential corner cases that > are already addressed in the algorithm, and it wasn't clear to me > "what's left" or if it's supposed to just work perfectly in all cases. > (I’m sure it's not!) Very good point! I agree. We will add some text in the next version. > > Obvious things that occurred to me were: > - different compositions of loss and reordering "features" in the > forward path: > - lossiness followed by reordering > - reordering followed by lossiness > - reordering followed by reordering somewhere else (and do we even > care about this, since it's the state of the packets at the > receiver that matters, and not how many times the order has been > shuffled) > - loss and reordering in the ACK path + packet duplication > > The sensitivity to these things, I think, matters in understanding the > utility of the computed metrics, and their feedback into a response > function. I agree. Have a nice WE Alex > > > -- > Wes Eddy > MTI Systems > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Wesley Eddy
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Yoshifumi Nishida
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Zimmermann, Alexander
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Zimmermann, Alexander
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Zimmermann, Alexander
- Re: [tcpm] review of draft-zimmermann-tcpm-reorde… Carsten Wolff
- [tcpm] review of draft-zimmermann-tcpm-reordering… Wesley Eddy