Re: [tcmtf] BoF feedback

Joe Touch <touch@isi.edu> Fri, 02 August 2013 18:00 UTC

Return-Path: <touch@isi.edu>
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 AD73D11E8101 for <tcmtf@ietfa.amsl.com>; Fri, 2 Aug 2013 11:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.987
X-Spam-Level:
X-Spam-Status: No, score=-105.987 tagged_above=-999 required=5 tests=[AWL=0.612, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 XPFuH3eojJMb for <tcmtf@ietfa.amsl.com>; Fri, 2 Aug 2013 11:00:39 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAE111E80E8 for <tcmtf@ietf.org>; Fri, 2 Aug 2013 11:00:39 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r72I0DjA021101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 11:00:13 -0700 (PDT)
Message-ID: <51FBF3AD.4020301@isi.edu>
Date: Fri, 02 Aug 2013 11:00:13 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
In-Reply-To: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
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: Fri, 02 Aug 2013 18:00:44 -0000

FWIW, I'd like to see how/whether this can be cast as an extension to SEAL.

It'd be useful not to have to reinvent the many wheel-like parts of this 
that could leverage existing tunneling capabilities.

Joe

On 8/2/2013 3:34 AM, Luigi Iannone wrote:
> Hi,
>
> I was thinking a little bit about the turn the BoF took yesterday, going a bit off topic IMHO.
>
> At a certain point people were going to the mic to explain yet another scenario where TCMTF would not work or is not useful.
>
> It is obvious to me that such scenarios exist, but  the goal of TCMTF is not to provide something that will be applied to all packets under a certain size.
>
> It is also obvious to me that scenarios where TCMTF is beneficial exist as well. Goal of TCMTF should be to provide the right mechanism for those scenarios.
>
> A key point to discuss in TCMTF is how we identify and select the flow we want to be multiplexed on a single compressed tunnel.
>
> All of this to say that we should not focus or scenarios where TCMTF doesn't help but rather to answer the following question:
>
> Are there scenarios and use cases where TCMTF provides benefits?
>
> The answer IMHO is YES so some work should be done.
>
> Just let me add that,  before thinking how to encapsulate we should answer: How do we select the flows we want to encamp?
>
> So that we are sure that we do not touch traffic that will suffer because of TCMTF.
>
> Just my thoughts after the BoF.
>
> ciao
>
> Luigi
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>