Re: [tcmtf] Support to create the working group for TCM-TF

Wesley Eddy <wes@mti-systems.com> Sat, 03 August 2013 02:05 UTC

Return-Path: <wes@mti-systems.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 5D34311E813F for <tcmtf@ietfa.amsl.com>; Fri, 2 Aug 2013 19:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 mnwFkoEuV8FF for <tcmtf@ietfa.amsl.com>; Fri, 2 Aug 2013 19:05:22 -0700 (PDT)
Received: from atl4mhob07.myregisteredsite.com (atl4mhob07.myregisteredsite.com [209.17.115.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1F95921E80B8 for <tcmtf@ietf.org>; Fri, 2 Aug 2013 19:05:17 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r7325Bf9025395 for <tcmtf@ietf.org>; Fri, 2 Aug 2013 22:05:11 -0400
Received: (qmail 7058 invoked by uid 0); 3 Aug 2013 02:05:11 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.122?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 3 Aug 2013 02:05:11 -0000
Message-ID: <51FC653A.8050206@mti-systems.com>
Date: Fri, 02 Aug 2013 22:04:42 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu>
In-Reply-To: <51FBF33D.8000401@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
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: Sat, 03 Aug 2013 02:05:28 -0000

On 8/2/2013 1:58 PM, Joe Touch wrote:
> Hi, all,
> 
> FWIW, I don't understand why this is being requested of the TRANSPORT area.
> 
> Tunnels such as this ought to be the purview of INTAREA. I admit I
> remain confused as to why so many tunneling protocols are in ROUTING,
> but regardless neither is TRANSPORT.
> 


Hi Joe; here are a few reasons I can think of for justifying
transport as the area:

- the intent was not to invent new tunnel protocols, but to use
  existing ones as part of a stack
- all of the possible downsides that people brought up during
  the meeting are impacts to the transport protocol; so there is
  a tight coupling between transport configuration and what the
  recommendation for performing TCMTF on a flow should be
- many of the design considerations are directly related to things
  transport has dealt with in the past like delayed ACKs, ACK
  compression, buffer sizing, etc.
- PILC and PEP documentation were done in the transport area
- RoHC was done in the transport area
- PMTUD was in transport area (since you noted that this is a
  an additional concern)

In my opinion, if this is done, it should be in transport.

-- 
Wes Eddy
MTI Systems