IETF Logo Mail Archive

Re: [Taps] QUIC API for WebRTC

Tommy Pauly <tpauly@apple.com> Fri, 12 October 2018 19:53 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 4BF4B130DC8 for <taps@ietfa.amsl.com>; Fri, 12 Oct 2018 12:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 T5YAIoN7yFOs for <taps@ietfa.amsl.com>; Fri, 12 Oct 2018 12:53:03 -0700 (PDT)
Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) (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 A058B1286E3 for <taps@ietf.org>; Fri, 12 Oct 2018 12:53:03 -0700 (PDT)
Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.22/8.16.0.22) with SMTP id w9CJpeuX056465; Fri, 12 Oct 2018 12:52:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : message-id : subject : date : in-reply-to : cc : to : references; s=20180706; bh=f93lIZX1Gjd++DNc+zlBestPz082MOste959qypKqEI=; b=S4Rr4WF58F+2GKbOVPUnDLTOIGvAq2qkUtAydKUpmR2Pv5NiRJhMsO4Qs8/062Dmwv8p 8rT0PEdDvftqcL4CVl8gEqjyeRFkgneM1hKTKzyk//AZ++ydI4+EfmtbB7vI5uVfQQi9 pz3zz+LPxeDkriJi7GmDVV79Xyxsaea4sJpwUMbN3F64rLDstfFJFGn690OHiLHYIeyE PlaCPdghwJk+JVeilSl2bB+LOV64WXqu40dMnfEtRmCE6yiCyOhVR0tAzeb+ni/rtYDG Xgh+9vYJSVA5FVF9+2Tuo+qVf/WXJVxvA3NDgS/XfUG9SxR31E9FDAX1TJ3ow6xZPVvZ nQ==
Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2mxskdar5e-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 12 Oct 2018 12:52:56 -0700
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_tHHQgJbS5kZQKqBxX+LzWg)"
Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PGI000WS4K6VAE0@ma1-mtap-s01.corp.apple.com>; Fri, 12 Oct 2018 12:52:55 -0700 (PDT)
Received: from process_viserion-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PGI0040043RC500@nwk-mmpp-sz10.apple.com>; Fri, 12 Oct 2018 12:52:54 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 0325f276f41c42fd3b0ac081f7f3f808
X-Va-E-CD: 63013081a6a18f67a6b5985da63079b3
X-Va-R-CD: 093da20303732465ced0230bd12ee60d
X-Va-CD: 0
X-Va-ID: ef8da63b-1d64-4899-9b29-d176514532ea
X-V-A:
X-V-T-CD: 9ea90e61654dad0c8920388428deae70
X-V-E-CD: 63013081a6a18f67a6b5985da63079b3
X-V-R-CD: 093da20303732465ced0230bd12ee60d
X-V-CD: 0
X-V-ID: c6ffebe2-d2bd-4c57-9ac7-7d07ccf3a40e
Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PGI008004GCL600@nwk-mmpp-sz10.apple.com>; Fri, 12 Oct 2018 12:52:54 -0700 (PDT)
Authentication-results: corp.apple.com; spf=softfail smtp.mailfrom=tpauly@apple.com; dmarc=none header.from=apple.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-12_13:,, signatures=0
X-Proofpoint-Scanner-Instance: nwk-grpmailp-qapp15.corp.apple.com-10000_instance1
Received: from [17.234.88.48] (unknown [17.234.88.48]) by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PGI00I2C4K5NS60@nwk-mmpp-sz10.apple.com>; Fri, 12 Oct 2018 12:52:53 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Message-id: <A8FB9ECB-A342-4A84-B250-FC86D28D789E@apple.com>
Date: Fri, 12 Oct 2018 12:52:42 -0700
In-reply-to: <DFCA1DAF-C774-44E8-AE8E-ACBC58266705@gmail.com>
Cc: Michael Welzl <michawe@ifi.uio.no>, youenn fablet <yfablet@apple.com>, Colin Perkins <csp@csperkins.org>, taps@ietf.org
To: Aaron Falk <aaron.falk@gmail.com>
References: <71E6690F-44E7-4E5C-AC84-F8BDDB12F852@ifi.uio.no> <FF152FCC-0EB3-4A20-8079-F17BFB3BE824@apple.com> <DFCA1DAF-C774-44E8-AE8E-ACBC58266705@gmail.com>
X-Mailer: Apple Mail (2.3445.100.36)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-12_13:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/YtxQjiHrZR6N_fu4IMjZcHQ0Hm8>
Subject: Re: [Taps] QUIC API for WebRTC
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: Fri, 12 Oct 2018 19:53:06 -0000

I think it would be useful to have agenda time in TAPS to discuss both:

- Transport API mappings for QUIC
- TAPS API mappings for WebRTC

Having input on the requirements and background for WebRTC + QUIC would be great.

Thanks,
Tommy

> On Oct 12, 2018, at 12:48 PM, Aaron Falk <aaron.falk@gmail.com> wrote:
> 
> On 11 Oct 2018, at 17:14, Tommy Pauly wrote:
> 
> I think this also brings up a point that it may be good to have a discussion in Bangkok with the group about getting a bit more in detail to how TAPS can best serve WebRTC use cases, and make that aspect of the API really concrete.
> 
> Are you thinking an offline discussion or would you like to spend some agenda time on the topic? I could invite the authors to present.
> 
> --aaron
>

v2.23.0 | Report a Bug | By Email