Re: [Taps] plans for draft-welzl-taps-transports?

Michael Welzl <> Thu, 07 January 2016 10:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 287F01A88B9 for <>; Thu, 7 Jan 2016 02:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0rnDcKwQ7sBa for <>; Thu, 7 Jan 2016 02:55:15 -0800 (PST)
Received: from ( [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9E3901A88B8 for <>; Thu, 7 Jan 2016 02:55:15 -0800 (PST)
Received: from ([]) by with esmtp (Exim 4.80.1) (envelope-from <>) id 1aH8Dp-00060b-B0; Thu, 07 Jan 2016 11:55:13 +0100
Received: from ([]) by with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <>) id 1aH8Do-0005hS-Rl; Thu, 07 Jan 2016 11:55:13 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Michael Welzl <>
In-Reply-To: <>
Date: Thu, 7 Jan 2016 11:55:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Aaron Falk <>
X-Mailer: Apple Mail (2.2104)
X-UiO-Ratelimit-Test: rcpts/h 4 msgs/h 1 sum rcpts/h 6 sum msgs/h 2 total rcpts 36849 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.048, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: AF4492BF7906015D86E070FEA3AC802883D18CE6
X-UiO-SPAM-Test: remote_host: spam_score: -59 maxlevel 80 minaction 1 bait 0 mail/h: 1 total 8836 max/h 17 blacklist 0 greylist 1 ratelimit 0
Archived-At: <>
Cc: Michael Tuexen <>, "<> Khademi" <>, "" <>
Subject: Re: [Taps] plans for draft-welzl-taps-transports?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Jan 2016 10:55:18 -0000

Aaron, all,

In fact we've been working on an update, which I should be able to post VERY soon - sorry for keeping you in the dark while this takes a little longer than expected!
More below:

> On 06 Jan 2016, at 23:13, Aaron Falk <> wrote:
> Hi Michael, et al-
> Now that we've settled the first doc, what is the plan for completing your proposed approach (which I'll refer to as doc 1b)?  As a strawman, let me suggest that you extend the 1b draft to include the additional protocols to be included and the authors of the analogous sections from doc 1 perform the 3 pass analysis, perhaps with some assistance from you and your co-authors.  I'm open to alternative proposals but would like to figure out where we are going while the year is still fresh and uncluttered. :)

I agree about involving the folks from doc 1 if they're willing - but I don't think we need to be strict about this mapping: whoever volunteers should be welcome, I think. That's because the workload is probably much higher for most protocols, and overall it's quite a different task, so let's see...

The update that I'll post soon is almost ready now, it contains:

> >>> - addressing the many comments by Gorry
> >>> - addressing the comments by Karen on the TAPS list
> >>> - fixing the language chaos, to make use of one terminology that's in line with the other TAPS document
> >>> - an appendix explaining how to contribute
> >>> - many other fixes

For the version following this, we have Gorry up for UDP and Christoph Paasch has already volunteered for MPTCP.

> An initial step is to submit the draft as a wg doc.  Since just substituting "ietf' for "welzl" will cause the draftstring to collide with doc 1, I suggest something like draft-ietf-taps-3pass.

I like how Stein put it in his presentation in Yokohama: draft-ietf-taps-transports explains what transport service features exist, whereas draft-welzl-taps-transports explains how to use them.
Hence I suggest: draft-ietf-taps-transport-usage

... and this will already be the updated version, coming VERY soon (maybe even today or tomorrow). Ok?