[Taps] Progress on taps-trasports

Brian Trammell <ietf@trammell.ch> Fri, 11 September 2015 15:40 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 9E3241B3D61 for <taps@ietfa.amsl.com>; Fri, 11 Sep 2015 08:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4zSxtmL-HMRv for <taps@ietfa.amsl.com>; Fri, 11 Sep 2015 08:40:41 -0700 (PDT)
Received: from trammell.ch (trammell.ch []) by ietfa.amsl.com (Postfix) with ESMTP id AAD3C1B39AB for <taps@ietf.org>; Fri, 11 Sep 2015 08:40:41 -0700 (PDT)
Received: from nb-10604.ethz.ch (nb-10604.ethz.ch []) by trammell.ch (Postfix) with ESMTPSA id CA03E1A05F0 for <taps@ietf.org>; Fri, 11 Sep 2015 17:40:09 +0200 (CEST)
From: Brian Trammell <ietf@trammell.ch>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E10344D-9E46-48C4-B443-AD4EE90D3466@trammell.ch>
Date: Fri, 11 Sep 2015 17:40:07 +0200
To: taps WG <taps@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/mWoYe96F0k1ItG5j9wPcLWOwDvg>
Subject: [Taps] Progress on taps-trasports
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: Fri, 11 Sep 2015 15:40:43 -0000

Greetings, all,

We've integrated the FLUTE/ALC text into the working copy of the document (github.com/britram/taps-transports) as well as moving over to a slightly more streamlined Makefile (though, due to smart quote replacement issues I'm still debugging -- don't ask -- the toolchain to build the RFC from the markdown is not working at the moment).

We've discussed the decisions taken in the Prague meeting about how to handle features vs. components in each transport protocol section. Our (somewhat complicated) attempt on -06 to really describe TCP in terms of what we believe the components are didn't work out so well, and we'll go back to the previous, simpler, more thoroughly decomposed list from the previous version.

It strikes us that part of the issue is that what we've listed for each protocol in the 3.x.3 sections aren't really components (in the sense of sets intertwined of behaviors that are inherent to the protocol as designed), but rather features (whether or not these features should be exposed in the eventual TAPS framework). The *distinction* between a component and a feature, though useful for thinking about how to decompose protocols, is (as Michael indicated in Prague) perhaps a bit academic when the point of the exercise in the first place is to ensure we have a reasonably complete list of features that TAPS can/should support.

So we propose the following resolution to the components-versus-features confusion on a per-protocol basis:

(1) Keep each list in the 3.x.3 sections more or less as-is.
(2) Retitle the sections 3.x.3 "Features Provided" and make editorial changes as necessary for agreement.

Please yell if you think this is a terrible idea; otherwise we'll spin a -07 shortly. After this, we still need to handle the following items

	• Karen & Michael will add some text on SCTP

This is actually Mirja's action; she'll review the SCTP section and coordinate with Karen & Michael shortly. Arms untwisted 'til then :) and apologies -- I thought we were synced up here.

	• Varun will add some text on RTP

We're also missing text on WebSockets. Since we have nothing for either at this point, we'll strike these sections

	• Gorry will write something on applications learning about network conditions (ICMP)

This is still pending.

We'll integrate these into an -08, and then I think we're ready for WGLC.

Thanks, cheers,

Brian and Mirja