IETF Logo Mail Archive

[rtcweb] Discussing WebRTC API mappings in TAPS

Tommy Pauly <tpauly@apple.com> Mon, 05 November 2018 00:19 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 159EE130DD2; Sun, 4 Nov 2018 16:19:49 -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 C50MjzapoU73; Sun, 4 Nov 2018 16:19:47 -0800 (PST)
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 B0CCF130E01; Sun, 4 Nov 2018 16:19:47 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.22/8.16.0.22) with SMTP id wA501xCd024738; 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=gkL4CMVPiZWKRiHnhTR/c4jXteFPT04uGfGofkSHqPA=; b=wl7rExabYmj8aYwK9D2hmUuvcAbIChEkWjQAu83L+bvaK1tupdPxQafy3USmRMevPccU eo3Ha6wa7OVfPqz7yaT3FRZXWR0H+HVMBdKSQOImioLW+iTdKAZzk5CTLPigqZlqGCcd iq8CB5sUcpp+J4HKm6ZRleqWbMgorcWlvKQs48xGvgwXp1RauMRJ3Ar0ZtCAJgNNDd03 14AB7uHKwVowa5T+HVgb0k4pJLK4IrrAb4P3xCVqyWHqeq0a7sjXC7MJc2O/S7yAEfep M0Skj0HJ1ERkBn/b6Qo2qM7Ti17nrLlgZKx6+DoxjI+iofaCKSUZgeiOcEx7DoeQiaAL HA==
Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2nhab730nh-1 (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 ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PHP00GUL28YPR30@ma1-mtap-s01.corp.apple.com>; Sun, 04 Nov 2018 16:19:46 -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:46 -0800 (PST)
X-Va-A:
X-Va-T-CD: 8f06955753c9914ccee2ead7b013056e
X-Va-E-CD: 3aff4d1e31abfdf3d4431ab8fb3cfe87
X-Va-R-CD: b7ef2668a01b66eb24691e801e63c290
X-Va-CD: 0
X-Va-ID: 64d0c7fc-3806-4743-ba75-8d66e52c8010
X-V-A:
X-V-T-CD: 8f06955753c9914ccee2ead7b013056e
X-V-E-CD: 3aff4d1e31abfdf3d4431ab8fb3cfe87
X-V-R-CD: b7ef2668a01b66eb24691e801e63c290
X-V-CD: 0
X-V-ID: a541b8fd-c7d7-49a5-8785-919b25dc6ef4
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:46 -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:46 -0800 (PST)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Message-id: <9FB4DA1B-B45C-41A0-85FF-A7E09199F380@apple.com>
Date: Mon, 05 Nov 2018 07:19:36 +0700
Cc: TAPS WG IETF list <taps@ietf.org>
To: rtcweb@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/rtcweb/dbuMM38CzK8rhjrfh_M9wVhO8sc>
Subject: [rtcweb] Discussing WebRTC API mappings in TAPS
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 00:19:49 -0000

Hello rtcweb,

Based on recent proposals for WebRTC APIs to run over QUIC, the Transport Services (TAPS) working group will be spending some time this week looking at the usefulness and applicability of our flexible transport APIs for use in WebRTC. One of the main goals is providing an API surface that will work well across protocols and require minimal application effort to adopt, as well as being able to dynamically use newer protocols. We'd like to get input and feedback on how well such a model can serve the WebRTC use case.

Please join us in our discussion if you're interested!

Wednesday, November 7
1540-1710  Afternoon Session II
Transport Services WG
Room: Meeting 2

Thanks,
Tommy

v2.23.0 | Report a Bug | By Email