IETF Logo Mail Archive

Re: [Taps] New Version Notification for draft-welzl-taps-transports-00.txt

Brian Trammell <ietf@trammell.ch> Wed, 07 October 2015 09:18 UTC

Return-Path: <ietf@trammell.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832EB1A906E for <taps@ietfa.amsl.com>; Wed, 7 Oct 2015 02:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErhDUdRghSVu for <taps@ietfa.amsl.com>; Wed, 7 Oct 2015 02:18:21 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 63E861B2C90 for <taps@ietf.org>; Wed, 7 Oct 2015 02:18:21 -0700 (PDT)
Received: from [IPv6:2001:67c:10ec:2a49:8000::b9] (unknown [IPv6:2001:67c:10ec:2a49:8000::b9]) by trammell.ch (Postfix) with ESMTPSA id C891A1A02FB; Wed, 7 Oct 2015 11:17:49 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_99883EEB-F8B3-4C4F-B6A7-3EE6D4EEFE6E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.2
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <4656A4F1-8A56-424C-95A7-506D5FEE3FC3@ifi.uio.no>
Date: Wed, 07 Oct 2015 11:17:49 +0200
Message-Id: <3D3C1025-32D9-4E60-B31D-35D15CC3D163@trammell.ch>
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no> <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com> <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk> <435C039A-5B01-450B-9223-883194F0B94D@mjmontpetit.com> <BCE21679-705E-4B51-B946-95D80A7EAE1A@ifi.uio.no> <CAD62q9VXwMw3-rU9YaWvyU=1EV6giEm6C8k4Vb+iwTs_oevFWg@mail.gmail.com> <4656A4F1-8A56-424C-95A7-506D5FEE3FC3@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/ECF1J3XJ57AZXIwNUTZ_vQTQHBU>
Cc: Aaron Falk <aaron.falk@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Marie-Jose Montpetit <marie@mjmontpetit.com>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2015 09:18:23 -0000

> On 07 Oct 2015, at 09:17, Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> Hi,
> 
> 
>> On 05 Oct 2015, at 20:42, Aaron Falk <aaron.falk@gmail.com> wrote:
>> 
>> Have others read this draft yet?   It is clearly aimed at addressing charter deliverable #1.  Do other folks have an opinion on how well it helps the group achieve the goals in our charter?  Should we use this document in some way? I'm looking for more input from the working group on how we should proceed.
>> 
>> My opinion: I am very mindful (& appreciative) of the significant effort by Mirja and Brian and the other contributors on draft-ietf-taps-transports.
> 
> +1
> 
> 
>>   The discussion around this doc has been very useful for clarifying (to me) how difficult it can be to pull useful common abstractions out of the 30+ years of transport technologies.  Having been down this path for over a year, I appreciate the fairly narrow approach draft-welzl-taps-transports and think it may be the best chance for TAPS to succeed.
>> 
>> Please share your views.
> 
> You say you appreciate the "fairly narrow" approach of draft-welzl-taps-transports. This makes me wonder - maybe draft-welzl-taps-transports should only cover a subset of the transports in draft-ietf-taps-transports, based on what we can see in draft-ietf-taps-transports?

Definitely. I think the "narrow" approach can work here -- the scope is already narrowed by only considering unicast services, which simplifies things quite a bit. The question is how and whether to narrow further. TCP (and MPTCP), UDP (and UTP-lite), and SCTP clearly make the cut, as they are widely deployed and/or there is active work on top of them for which we expect wide deployment. Others I'm less sure of.

Cheers,

Brian

> (e.g. the eventual text on RTP in draft-ietf-taps-transports will probably not be a short list of features, which may indicate that RTP should not be included in draft-welzl-taps-transports).
> 
> Cheers,
> Michael
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

v2.29.0 | Report a Bug | By Email | System Status