Discussing QUIC API mappings in TAPS
Tommy Pauly <tpauly@apple.com> Mon, 05 November 2018 00:19 UTC
Return-Path: <tpauly@apple.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291BD130DE8; Sun, 4 Nov 2018 16:19:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level:
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 STKxlEx87DnV; Sun, 4 Nov 2018 16:19:46 -0800 (PST)
Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) (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 CB335130DD2; Sun, 4 Nov 2018 16:19:46 -0800 (PST)
Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.22/8.16.0.22) with SMTP id wA501v8g043560; Sun, 4 Nov 2018 16:19:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : subject : message-id : date : cc : to; s=20180706; bh=ihHB94T+RYxYUQl2XCrgZ3S2dCq0OSXk36DaaGU3Lew=; b=Snk2BGngAq/KC47rp2XITz0TOdzPB/LDwu2joJXzXKsgS+hftjkDJzOrjnUk9crVcwDA Cq+2FlIyD/0tBg3QSOCr8hLghN2MjQ4s2KOaUGX90SsRpuxykZjcJTEbjjur3ey2JodN v3derIwxZQVt8QtEX/SEripKeU0E5laTmWRPcBNa5eiWsi6QsrtsrHoy+3WLYPmlWN35 /P0YdRVIYqFgZ4MhR55SjW4Db+uKyWOgjtdwJBpkZVz0+LaiKBW1hIrH7D38+RN3Opyb ovjr3teX+D3oToO4/La7Lbt2/CR9t+kpSjCTECkq41TMLTaOFG9m9Wui/V+DvGMYIOBf Sw==
Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2nh88mre8n-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 04 Nov 2018 16:19:46 -0800
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from ma1-mmpp-sz11.apple.com (ma1-mmpp-sz11.apple.com [17.171.128.33]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PHP00BGJ28W2R20@mr2-mtap-s03.rno.apple.com>; Sun, 04 Nov 2018 16:19:45 -0800 (PST)
Received: from process_viserion-daemon.ma1-mmpp-sz11.apple.com by ma1-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHP00N001CW0Y00@ma1-mmpp-sz11.apple.com>; Sun, 04 Nov 2018 16:19:44 -0800 (PST)
X-Va-A:
X-Va-T-CD: 4fc7fc2a6ed6f60e40832e4273217f25
X-Va-E-CD: 5696625a64fb3e3ab7bb9ce5f5e748e0
X-Va-R-CD: 913bf984ad5e215a2d7f0ecaaaef9567
X-Va-CD: 0
X-Va-ID: 7de0bf90-693b-49af-b46b-4e6408a5fb45
X-V-A:
X-V-T-CD: ad9399c1dd33874217dd92d101f0d74f
X-V-E-CD: 5696625a64fb3e3ab7bb9ce5f5e748e0
X-V-R-CD: 913bf984ad5e215a2d7f0ecaaaef9567
X-V-CD: 0
X-V-ID: b73e2937-f19d-448e-9242-ee27b555b46e
Received: from process_milters-daemon.ma1-mmpp-sz11.apple.com by ma1-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHP004001MGK300@ma1-mmpp-sz11.apple.com>; Sun, 04 Nov 2018 16:19:44 -0800 (PST)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-11-04_17:,, signatures=0
Received: from [17.234.143.171] (unknown [17.234.143.171]) by ma1-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PHP00BEB28QQW20@ma1-mmpp-sz11.apple.com>; Sun, 04 Nov 2018 16:19:44 -0800 (PST)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Subject: Discussing QUIC API mappings in TAPS
Message-id: <EAAF7487-6A3B-4901-A583-1D3609E4E91E@apple.com>
Date: Mon, 05 Nov 2018 07:19:35 +0700
Cc: TAPS WG IETF list <taps@ietf.org>
To: QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3445.100.36)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-04_17:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7VMAB8AN95ODvLUcqY-3_TTQs0s>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 00:19:48 -0000
Hello QUIC, I wanted to highlight to the working group that this week we'll be having a discussion around transport API mappings for QUIC in the Transport Services (TAPS) working group. The goal is to ensure that applications are able to smoothly migrate to QUIC from other protocols, even when not using HTTP over QUIC. If you're interested in this topic, please join us and chime in! Wednesday, November 7 1540-1710 Afternoon Session II Transport Services WG Room: Meeting 2 Thanks, Tommy
- Discussing QUIC API mappings in TAPS Tommy Pauly