Re: [tcmtf] A terminological question: "small-packet flows"
"Jose Saldana" <jsaldana@unizar.es> Thu, 13 June 2013 08:47 UTC
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 2802B21F9A73 for <tcmtf@ietfa.amsl.com>;
Thu, 13 Jun 2013 01:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level:
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.168,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEK9hBFXPqr9 for
<tcmtf@ietfa.amsl.com>; Thu, 13 Jun 2013 01:47:08 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by
ietfa.amsl.com (Postfix) with ESMTP id D62FA21F8AF7 for <tcmtf@ietf.org>;
Thu, 13 Jun 2013 01:47:07 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by
ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5D8l2u7012182;
Thu, 13 Jun 2013 10:47:02 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es> <5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk> <010201ce6788$bb0ba9c0$3122fd40$@unizar.es>
<0ffb9f6fbd94eec2170b9506b2bfcfd6.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <0ffb9f6fbd94eec2170b9506b2bfcfd6.squirrel@www.erg.abdn.ac.uk>
Date: Thu, 13 Jun 2013 10:47:07 +0200
Organization: Universidad de Zaragoza
Message-ID: <006601ce6812$9676ef40$c364cdc0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbWNGeasK9gJiAVLdN29QxUaAJagIWQdJ+ATYyFbQCkMQN/pnqiWfA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, =?iso-8859-1?Q?'=22'Mirko_Su=BEnjevi=E6=22'=22=22'?=
<mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion
list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>,
<mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>,
<mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 08:47:21 -0000
Gorry, Thanks for the suggestion. I have included it in the end of Paragraph 8 of the charter draft v6: 8. As a counterpart of the bandwidth saving, TCMTF may add some delay and jitter. This is not a problem for the services which are not sensitive to delay. However, regarding delay-sensitive services, the Working Group will also develop a document (TCMTF - recommendations) with useful recommendations in order to decide which packet flows can or can not be multiplexed and how. The document will present a list of available traffic classification methods which can be used for identification of the service or application to which a particular flow belongs, as well as recommendations of the maximum delay and jitter to be added depending of the identified service or application. The eventual impact of multiplexing on protocol dynamics (e.g., when multiplexing TCP flows) will also have to be addressed. I think we should study this in the TCMTF - recommendations document. Do you agree? Thanks, Jose > -----Mensaje original----- > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de > gorry@erg.abdn.ac.uk > Enviado el: miércoles, 12 de junio de 2013 18:33 > Para: jsaldana@unizar.es > CC: gorry@erg.abdn.ac.uk; tcmtf@ietf.org; "'Mirko Su¾njeviæ"'"" > Asunto: Re: [tcmtf] A terminological question: "small-packet flows" > > See below, > > Gorry > > > Gorry, > > > > Thanks for the suggestion. > > > > Some ACK flows generate a lot of pps: > > > > - A file download may easily generate 100 ACKs per second from a > > computer to the file server. > > - TCP-based games also generate ACKs (maybe 10 pps) > > > > Which delays would impair an ACK flow, according to RFC 3449? The idea > > I have in mind is using multiplexing periods between 50 and 100 ms. > > > RFC 3449 gives BCP guidance on how to manage compression of the TCP ACK > stream and things to do and things to avoid. > > For example, you may well be aware that bunching ACKs by sending them all > in one burst **IS** likely something that would need to be examined in > detail, since this impacts the flow dynamics and can therefore modify the > congestion behaviour across the network. > > I'm just suggesting that your charter should be clear about about the set of > topics the group is currently addressing (e.g. TCP changes) so that people > understand whether they support or have issues with the proposed scope of > the work. > > > There is another problem, related to TCP Friendly Rate Control (TFRC, > > RFC > > 5348): if you add too much delay, the throughput can be reduced. This > > idea was suggested by Michael some weeks ago: > > http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html > > > That's also true - but I am not sure Michael was actually talking about looking > at TFRC, more as I saw it, he was talking about the sort of TCP rate you > should expect based on the throughput equation (i.e. as a function of loss > and RTT). > > > Thanks! > > > > Jose > > > >> -----Mensaje original----- > >> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk] Enviado el: > >> miércoles, 12 de junio de 2013 17:55 > >> Para: jsaldana@unizar.es > >> CC: tcmtf@ietf.org; "Mirko Su¾njeviæ" > >> Asunto: Re: [tcmtf] A terminological question: "small-packet flows" > >> > >> If you're talking about TCP ACKs RFC 3449 could be relevant. > >> > >> Gorry > >> > >> > Hi all. > >> > > >> > > >> > > >> > Mirko and I are working on an improved version of the "TCMTF - > >> > recommendations" document. Since TCMTF is not only suitable for > >> > real-time services, but also for non real-time ones (M2M, flows of > >> > ACKs, instant messaging), one possibility is using the term > > "small-packet > >> flows". > >> > > >> > > >> > > >> > The advantages are clear: > >> > > >> > > >> > > >> > - It is more generic. > >> > > >> > - It includes the characteristics of TCMTF-able packets: > >> > > >> > - low payload-to-header ratio > >> > > >> > - long-term flows > >> > > >> > > >> > > >> > This term is also being used in some technical documents: > >> > www.huawei.com/ilink/en/download/HW_193034. > >> > > >> > > >> > > >> > What do you think? Any other proposals? > >> > > >> > > >> > > >> > Jose > >> > > >> > > >> > > >> > _______________________________________________ > >> > tcmtf mailing list > >> > tcmtf@ietf.org > >> > https://www.ietf.org/mailman/listinfo/tcmtf > >> > > > > > > > _______________________________________________ > > tcmtf mailing list > > tcmtf@ietf.org > > https://www.ietf.org/mailman/listinfo/tcmtf > > > > > _______________________________________________ > tcmtf mailing list > tcmtf@ietf.org > https://www.ietf.org/mailman/listinfo/tcmtf
- [tcmtf] A terminological question: "small-packet … Jose Saldana
- Re: [tcmtf] A terminological question: "small-pac… Dan Wing
- Re: [tcmtf] A terminological question: "small-pac… gorry
- Re: [tcmtf] A terminological question: "small-pac… Jose Saldana
- Re: [tcmtf] A terminological question: "small-pac… Jose Saldana
- Re: [tcmtf] A terminological question: "small-pac… gorry
- Re: [tcmtf] A terminological question: "small-pac… Jose Saldana