IETF Logo Mail Archive

[Taps] On Profiles for TAPS Preconnections

Tommy Pauly <tpauly@apple.com> Mon, 22 July 2019 19:09 UTC

Return-Path: <tpauly@apple.com>
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 41AE3120125 for <taps@ietfa.amsl.com>; Mon, 22 Jul 2019 12:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 Kyk7eAnS5_tu for <taps@ietfa.amsl.com>; Mon, 22 Jul 2019 12:09:34 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) (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 25ECE12011B for <taps@ietf.org>; Mon, 22 Jul 2019 12:09:34 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x6MJ74Rf010780 for <taps@ietf.org>; Mon, 22 Jul 2019 12:09:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : content-type : content-transfer-encoding : mime-version : subject : message-id : date : to; s=20180706; bh=sDOKiBdAi3/7uCl00xecL6BV3Cz29XOF/QiM9xxcS+4=; b=YyEdN8k0rjE6WcaeT1GXWuIczDT8aupKTTYM2tHDtU4G1MXwfZ6SlGmEIkTZZI0M3yCd BeIfMkY+TuwbmtMYpsveO6iT9hLKUy9WM0wawketoFO2NpqHIGVr0f84siA4ZF4Eqgd3 Kx5Tx46fAnmJ6GlUubRepLG7/optFFj2+iQNGLdwPZIAslF7b5SzhIzC7sZ+iaTQyhE0 n+miUJ/Fvn2OJPrEvA2bMRprL65+V+tZG/s8PElA1zauSAQ8jgwCHfiXluaPy6/80bJd BzWXog7BqEmybbmk99oz3OnZxI+7uzyACNWHQiOlFErF3S7SE0AD7JbrtsdMkKSnB8sZ mA==
Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2tv1m5v9dj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <taps@ietf.org>; Mon, 22 Jul 2019 12:09:32 -0700
Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0PV20043G57OPT80@ma1-mtap-s02.corp.apple.com> for taps@ietf.org; Mon, 22 Jul 2019 12:09:25 -0700 (PDT)
Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0PV200A005703J00@nwk-mmpp-sz13.apple.com> for taps@ietf.org; Mon, 22 Jul 2019 12:09:24 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 5808c5f95406ec7719a15f5c3784581a
X-Va-E-CD: 7767081b3a220600287c21a9b1a4ebdf
X-Va-R-CD: c1589dcd68ee813140d015a7610f5889
X-Va-CD: 0
X-Va-ID: 707d5062-af02-4e49-a548-d3f3acbf4c99
X-V-A:
X-V-T-CD: 5808c5f95406ec7719a15f5c3784581a
X-V-E-CD: 7767081b3a220600287c21a9b1a4ebdf
X-V-R-CD: c1589dcd68ee813140d015a7610f5889
X-V-CD: 0
X-V-ID: 752b9fe8-7869-47e2-b06d-b6d022b2d262
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-22_14:,, signatures=0
Received: from [17.235.20.105] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0PV200C9957LZF50@nwk-mmpp-sz13.apple.com> for taps@ietf.org; Mon, 22 Jul 2019 12:09:24 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Message-id: <370C3CC6-363D-4036-ABCC-7B02F6BD04F6@apple.com>
Date: Mon, 22 Jul 2019 15:09:17 -0400
To: taps WG <taps@ietf.org>
X-Mailer: Apple Mail (2.3445.104.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-22_14:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/_xIe4Hw7XtJG1dY-XCL45e1Jldw>
Subject: [Taps] On Profiles for TAPS Preconnections
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <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, 22 Jul 2019 19:09:36 -0000

An issue we discussed today in the TAPS meeting was whether or not we should add a concept of "profiles" to the Transport Services APIs. An example of a profile is a "reliable, secure, in-order stream"; or "unreliable datagrams". Another way to think of these profiles are as convenient ways to initialize common parameters.

One option is described in this PR: https://github.com/ietf-tapswg/api-drafts/pull/328

To help discern the working group's position, I'll try to distill the high-level options here:

1. Add Profiles as a top-level API document concept that modifies how transport properties and/or preconnections are created. (This is PR #328.)
2. Mention in the API document that specific API implementations may expose conveniences and profiles (presumably as a way to initialize preconnections), but do not modify the API or specify an abstract symbol for profiles.
3. Do not mention profiles at all in the API document, but mention something in the implementation document.

Let's use this thread to discuss how to converge!

Thanks,
Tommy

v2.23.0 | Report a Bug | By Email