Re: [tcmtf] BoF feedback

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Tue, 06 August 2013 12:26 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 4A85821F9C2D for <tcmtf@ietfa.amsl.com>; Tue, 6 Aug 2013 05:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level:
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599]
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 i8NoclkQbp-S for <tcmtf@ietfa.amsl.com>; Tue, 6 Aug 2013 05:26:43 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id AB92921F9DA9 for <tcmtf@ietf.org>; Tue, 6 Aug 2013 05:26:43 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id eh20so649241obb.1 for <tcmtf@ietf.org>; Tue, 06 Aug 2013 05:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=djUXLF5L17ikDkY30Pbzj+PSZU8yA65Yf6w+LeJIVY8=; b=kE7wDrffyPABpHhDGHjD5ILQzpwlWt4UGzVcNuqWYPXpctFQhdk8Wclo1jKobqpAzp VQ9/SWp69aliuawR0FhUBOOi1WRiP/ST4L+BSNR7aX+qTeW/X83IqVwlulP3o3vjW0Bn FYT7grAYda1nbpHi2j1Vqc6caoZPbLgqjwercbvQHkY4ofg0LhRK94i7sZzZHfFe60N6 UekhGXOT+5feXfIJqXNEJe5eU8e7OA0MauC0l2ZqNRTdpGpQCom9pJ0OAinDAntOXos8 7lrLuXh1CYgQlzUk01cHInmae4ynvImdYhlR+8VdHt969BRW7ZbPJG5B2fAsmCmEADRD hsTA==
X-Received: by 10.182.226.199 with SMTP id ru7mr847026obc.12.1375792003256; Tue, 06 Aug 2013 05:26:43 -0700 (PDT)
Received: from [192.168.0.30] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id hm1sm875803obb.9.2013.08.06.05.26.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 05:26:42 -0700 (PDT)
Message-ID: <5200EB7E.5090105@gmail.com>
Date: Tue, 06 Aug 2013 07:26:38 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jose Saldana <jsaldana@unizar.es>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es> <51FCC957.6000100@erg.abdn.ac.uk> <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net> <51FFE8A8.6000401@gmail.com> <51FFEBCB.5020201@mti-systems.com> <520009D9.6010605@gmail.com> <002301ce927b$17b73b40$4725b1c0$@unizar.es>
In-Reply-To: <002301ce927b$17b73b40$4725b1c0$@unizar.es>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: 'Wesley Eddy' <wes@mti-systems.com>, 'Luigi Iannone' <ggx@gigix.net>, tcmtf@ietf.org, gorry@erg.abdn.ac.uk, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] BoF feedback
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, 06 Aug 2013 12:26:44 -0000

On 8/6/2013 3:00 AM, Jose Saldana wrote:
> If you look at the abstract of the "Recommendations draft"
> (http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/) , this is
> exactly what we intend to do in that document:
>
>     This document contains recommendations to be taken into account when
>     using methods which optimize bandwidth utilization through
>     compression, multiplexing, and tunneling traffic flows (TCMTF) over a
>     network path.  Different multiplexing policies and implementation
>     issues which are service and link specific are discussed.
>     Additionally, this document describes *policies which can be used for
>     detecting, classifying, and choosing the network flows suitable for
>     optimization by using TCMTF*.  Finally, recommendations of maximum
>     tolerable delays to be added by optimization techniques are reported.
>     Recommendations are presented only for network services for which
>     such bandwidth optimization techniques are applicable (i.e., services
>     with low payload to header size ratio, which will also be denoted as
>     "small-packet flows").
>
> Spencer, are you talking about the "policies which can be used for
> detecting, classifying, and choosing the network flows suitable for
> optimization by using TCMTF"?

I think so. And it's possible that a word choice is confusing me. 
"detecting" sounded pretty on-the-fly/dynamic to me (as in, you might 
detect that any random packet going past would be a packet that TCM-TF 
would process), but my understanding of recent e-mails is that 
"detecting" is much less dynamic ("I want to use TCMTF on WoW, and 
here's how you would know a packet is a WoW packet, and anything I 
didn't say how to recognize as a packet that TCM-TF should process is 
forwarded with no changes").

If my understanding based on these recent e-mails is more in line with 
what you're thinking, that answers my question.

Thanks!

Spencer

> Perhaps this was not clear enough in the BoF, but of course this is very
> important: you can only use TCM-TF for the TCM-suitable flows, and this spec
> must clearly define which flows are TCM-suitable and in what conditions.
>
> Thanks,
>
> Jose