Re: [tcmtf] Traffic classification approach for tcmtf (Draft B)

FERNANDO PASCUAL BLANCO <fpb@tid.es> Tue, 26 February 2013 13:44 UTC

Return-Path: <fpb@tid.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 6878D21F88FB for <tcmtf@ietfa.amsl.com>; Tue, 26 Feb 2013 05:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level:
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id as6ebjqTii0X for <tcmtf@ietfa.amsl.com>; Tue, 26 Feb 2013 05:44:17 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id B916F21F880F for <tcmtf@ietf.org>; Tue, 26 Feb 2013 05:44:15 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MIT0042ZY5EV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 26 Feb 2013 14:44:05 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49]) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id DE.3C.05051.52CBC215; Tue, 26 Feb 2013 14:44:05 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MIT0043BY5HV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 26 Feb 2013 14:44:05 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS7-MAD.hi.inet ([fe80::4ccc:bab7:84dc:7c6e%15]) with mapi id 14.02.0328.009; Tue, 26 Feb 2013 14:44:04 +0100
Date: Tue, 26 Feb 2013 13:44:03 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <E004A7C54DE04F4BB87DB9F32308DA5C012CC4@MAIL4.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?utf-8?B?TWlya28gU3XFvm5qZXZpxIc=?= <Mirko.Suznjevic@fer.hr>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A268A1BA79@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_w6n4OVrd3Vq34gmE+Md17Q)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Traffic classification approach for tcmtf (Draft B)
Thread-index: Ac4QIQk7g5eAEs3XRtWNa36jlGBO6wEBk1mA
user-agent: Microsoft-MacOutlook/14.3.0.121105
X-AuditID: 0a5f4e69-b7fbe6d0000013bb-bc-512cbc25015a
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42Lhivcz1FXdoxNosHupjMWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMfPzVaaCe8kV+455NjA2JnYxcnBICJhIHD8e3cXICWSKSVy4 t56ti5GLQ0hgG6PExVN72EASQgI/GCWe9QVBJDYxSrzZNZ0dpJlFQFXi7V0pkBo2AS2J03dX sYDYwgIeEnvud4PZnAJOEosmdLBALFCQ+HPuMQtIq4hAmsTB/34gYWYBXYmZF2eCreIV8JZY 9fMnO4QtKPFj8j2wcmaBXIkD/6ohysUlmltvgk1kFJCVeDd/PiuILSLgKfF031tGiOlGEr+v xIKERQX0JO7PaGWDOEBAYsme88wQtqjEy8f/WCcwis1CsmwWwrJZSJZBhDUl1u/ShwgrSkzp fsgOYWtItM6ZC2WbSWyf+oUJWc0CRo5VjGLFSUWZ6RkluYmZOekGRnoZmXqZeaklmxgh8Ze5 g3H5TpVDjAIcjEo8vA0KOoFCrIllxZW5hxglOJiVRHiZNgGFeFMSK6tSi/Lji0pzUosPMTJx cEo1MAbPEt5wPNv+SZ3Th0sqB/f9O7NPpjfz39bDSi98pvsw2s8zV9q7PW7v/9Bw1c/yl6c9 PMC/+GrrjZi9c/59SL231+Ph3EwPu+5jzqlxxSJPLbPT/7If8DRafWJ5suCuZ0cmGS2yOShh 3M8adn/7p4dlR8VZDCdNV5PbyF8277aXvo2Ghuhf229KLMUZiYZazEXFiQB6+vJ+nQIAAA==
Cc: "mramalho@cisco.com" <mramalho@cisco.com>
Subject: Re: [tcmtf] Traffic classification approach for tcmtf (Draft B)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 26 Feb 2013 13:44:18 -0000

Hi all,

Regarding the classification approach: I think your approach is valid, nevertheless I would add the following assumption. Imagine the following scenario:

  *   Imagine you have 3 different priorities: A (with the lower multiplexing period) to C (with the higher multiplexing period)
  *   Imagine you have 2 flows: one flow A with priority A and another flow C with priority C
  *   Flow A goes into the priority A, but there is still room in that queue for more flows (flow A does not fill big packets).

Should we apply priority C to flow C? Or should we apply priority A? We have to take into account that the more flows to be multiplexed, the better the TCMTF works. In that case, mixing flows A and C in priority A helps the algorithm to work better and improve the RTT of both flows. Nevertheless, we should only apply that assumption when the highest priority is NOT full of flows, let´s say.

What do you think?

Regards,

Fernando Pascual Blanco
Telefónica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es

From: Mirko Sužnjević <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fer.hr>>
Date: jueves, 21 de febrero de 2013 11:48
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ietf.org>>
Cc: "'Michael Ramalho (mramalho) '" <mramalho@cisco.com<mailto:mramalho@cisco.com>>
Subject: [tcmtf] Traffic classification approach for tcmtf (Draft B)

Hello everybody,
I have been surveying the literature of traffic classification approaches and I need an advice for the next version of draft B. The question is regarding a "suitable" traffic classification algorithm. What should we aim at? Speed or extra accuracy?
I have been thinking about it and I propose a following solution:

1)      Each new traffic flow observed is labeled "highest" priority (shortest multiplexing period) until we classify it. The time spent in this state might get rather long for the flows with low sending rate.

2)      Once classified and then assign it to an appropriate priority (i.e., multiplexing period)?


Also I have a question regarding sampling rate. Do you think it is possible that we will have complete samples of traffic or just partial for the classification? Because on very high speed links it is very hard to obtain all of the traffic for classification.

Cheers!
Mirko Suznjevic


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx