Re: [tcmtf] BoF feedback

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Mon, 05 August 2013 20:24 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 E44AD21F8423 for <tcmtf@ietfa.amsl.com>; Mon, 5 Aug 2013 13:24:42 -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 5VyIZaa+E6iT for <tcmtf@ietfa.amsl.com>; Mon, 5 Aug 2013 13:24:42 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC4B21F9371 for <tcmtf@ietf.org>; Mon, 5 Aug 2013 13:24:42 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id dn14so6662287obc.12 for <tcmtf@ietf.org>; Mon, 05 Aug 2013 13:24:41 -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=U28DlULkX4ogCpgs4Q8Ibywz1QheJp+pJcwZyR1e7zA=; b=kNH1BxcUUQMSLE7H2HfJBeGi4/9Sh71NbjGaICM8NKs6jjTXffIWBOR0rOBtUaiBOk AUUgYKP4mwLagRB4My4Rn+LNm3sU59egQAUK9vzQSxWj6NnNgoSSucYmheIrz5J0vcFH 8MvMNyUTolNk8k3emW2WDh54SXqgAluy6LWvw5d9AHkLC1w2yXDtymKMJhmLryVJ2eDU CG7aYJbYyEr3LVNw2fS4CP09cypeZPAvQJ6W0gbTr9ZDFTaRYUH5wpmBBdPcC1lPBXpE d0CCcdzWMUPGvSl1jareAKQRkUN9n92JudpiqP34ARRZG3w2vXxHxJyWAZ2PljycglW5 Gr0w==
X-Received: by 10.42.224.136 with SMTP id io8mr1838633icb.54.1375734281682; Mon, 05 Aug 2013 13:24:41 -0700 (PDT)
Received: from [192.168.0.23] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id q4sm404850igp.6.2013.08.05.13.24.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 13:24:40 -0700 (PDT)
Message-ID: <520009D9.6010605@gmail.com>
Date: Mon, 05 Aug 2013 15:23:53 -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: Wesley Eddy <wes@mti-systems.com>
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>
In-Reply-To: <51FFEBCB.5020201@mti-systems.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Luigi Iannone <ggx@gigix.net>, gorry@erg.abdn.ac.uk, Spencer Dawkins <spencerdawkins.ietf@gmail.com>, 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: Mon, 05 Aug 2013 20:24:43 -0000

On 8/5/2013 1:15 PM, Wesley Eddy wrote:
> On 8/5/2013 2:02 PM, Spencer Dawkins wrote:
>> So, Martin and I were talking this morning, and a question came up that
>> you folks might want to ponder, if you haven't already done so ...
>>
>> Re: UDP/IP flows, the theory here would be to say that UDP/IP flows are
>> more like RTP flows than TCP flows, so the concerns about TCP in TCM-TF
>> don't apply, but the nice people in RTCWeb are defining their data
>> channel over SCTP/DTLS/UDP, and my guess would be that their data
>> channel would behave exactly like TCP for bulk transfers.
>>
>> Have people already considered that?
>>
>
> I think the answer is that instead of searching for particular
> protocol layerings that could be harmed, the rules for invoking
> TCMTF on a flow would be such that it only operates on things
> that it is configured to (e.g. UDP to a game server IP and port),
> and that it would "fail off" and not do anything for types of
> flows that it isn't sure how to optimize, time release for, or
> otherwise not break.

Right. That might not have been clear, but that matches what I was 
thinking - opt-in.

So I think my next question if if people expect the spec to give 
guidance about how to decide what gets configured "in".

Thanks,

Spencer