[Taps] Fwd: New Version Notification for draft-gjessing-taps-minset-04.txt

Michael Welzl <michawe@ifi.uio.no> Mon, 13 March 2017 16:06 UTC

Return-Path: <michawe@ifi.uio.no>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F00129428 for <taps@ietfa.amsl.com>; Mon, 13 Mar 2017 09:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2YuJctAsGJhu for <taps@ietfa.amsl.com>; Mon, 13 Mar 2017 09:06:20 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D55A129405 for <taps@ietf.org>; Mon, 13 Mar 2017 09:06:20 -0700 (PDT)
Received: from mail-mx03.uio.no ([129.240.10.15]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1cnSUE-0006rN-RQ for taps@ietf.org; Mon, 13 Mar 2017 17:06:18 +0100
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx03.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1cnSUD-000086-3c for taps@ietf.org; Mon, 13 Mar 2017 17:06:18 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Mar 2017 17:06:16 +0100
References: <148942050575.17043.6419886474129053646.idtracker@ietfa.amsl.com>
To: taps WG <taps@ietf.org>
Message-Id: <BCAD8550-769D-4794-9C5C-01D565A2C676@ifi.uio.no>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx03.uio.no: 129.240.68.135 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.68.135; envelope-from=michawe@ifi.uio.no; helo=boomerang.ifi.uio.no;
X-UiO-Ratelimit-Test: rcpts/h 1 msgs/h 1 sum rcpts/h 4 sum msgs/h 3 total rcpts 52629 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=-0.044, RP_MATCHES_RCVD=-0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 9628D46657F19F2B36B1D68694249908C82984B8
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 12574 max/h 21 blacklist 0 greylist 0 ratelimit 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/uSLJbm0n78-_pJ2kF60muuPdlOo>
Subject: [Taps] Fwd: New Version Notification for draft-gjessing-taps-minset-04.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 13 Mar 2017 16:06:23 -0000

Dear TAPS WG,

This update addresses the feedback that we got at the last meeting: people said that this minset isn't much of a minset. ... that's because we had only worked on the first step: categorizing transport features such that the list can then be reduced.

Now, in this update:
- we've brought the list in line with the latest version of the -usage draft (the list is a lot longer now, and includes what we think are *all* transport features of TCP, MPTCP, SCTP, UDP(-Lite) ... except for TCP Authentication. We'll fix this one in the next version.
- we then shortened the list brutally  :)   by only allowing "functional" and "optimizing" transport features, and also removing transport features for which it doesn't seem possible to fall back to TCP
- we then wrote text discussing the strange list that we got ... some weird things there need consideration when designing a TAPS system
- and then we made a first stab at constructing a "minimum set", derived from the above.

I hope folks will find this interesting despite its length - it captures several things that I've had in mind for a while, and partially talked about to people, but never really wrote up anywhere. A lot of love has gone into this document  ;-)

Cheers,
Michael



> Begin forwarded message:
> 
> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-gjessing-taps-minset-04.txt
> Date: 13 Mar 2017 16:55:05 CET
> To: Michael Welzl <michawe@ifi.uio.no>, Stein Gjessing <steing@ifi.uio.no>
> Resent-From: <michawe@ifi.uio.no>
> 
> 
> A new version of I-D, draft-gjessing-taps-minset-04.txt
> has been successfully submitted by Michael Welzl and posted to the
> IETF repository.
> 
> Name:		draft-gjessing-taps-minset
> Revision:	04
> Title:		A Minimal Set of Transport Services for TAPS Systems
> Document date:	2017-03-13
> Group:		Individual Submission
> Pages:		38
> URL:            https://www.ietf.org/internet-drafts/draft-gjessing-taps-minset-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/
> Htmlized:       https://tools.ietf.org/html/draft-gjessing-taps-minset-04
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-gjessing-taps-minset-04
> 
> Abstract:
>   This draft recommends a minimal set of IETF Transport Services
>   offered by end systems supporting TAPS, and gives guidance on
>   choosing among the available mechanisms and protocols.  It is based
>   on the set of transport features given in the TAPS document
>   draft-ietf-taps-transports-usage-03.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>