[Webtransport] Multicast for the Web (and WebTransport in particular)
"Holland, Jake" <jholland@akamai.com> Thu, 22 July 2021 17:44 UTC
Return-Path: <jholland@akamai.com>
X-Original-To: webtransport@ietfa.amsl.com
Delivered-To: webtransport@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD073A0B22 for <webtransport@ietfa.amsl.com>; Thu, 22 Jul 2021 10:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 nFQ-TewyHoJP for <webtransport@ietfa.amsl.com>; Thu, 22 Jul 2021 10:44:36 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 0F5923A0B1F for <webtransport@ietf.org>; Thu, 22 Jul 2021 10:44:35 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 16MHTsVb018400 for <webtransport@ietf.org>; Thu, 22 Jul 2021 18:44:34 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=fClfidCVxFXeVIumrXh+Fb2SqFXx5RTqntLXmyY1E7k=; b=lXFjvBHF+rhggD/cjZHd2yxL4J6wumSFm8IUpWESTW3aLJVN4LqTsLRPd3Xi4MQF0BX+ YIlv25wr712KzcpmF3zbHAMGKr9VMPjk1RNCXUtVWahrjqWRCcLv6//Ldz8z0vlCce4/ gSGaY39SUgIIH/q4j/T7ahGObMIoE+CtCpkcbSMO6agWWLevMOWhmwEG8KNltb5foOJm UqEfCOU3NCVNc8ha2juIWu7ZBD5hgZ2o0m918vxgLlEX/xRqIwubFQOjk4iUqA/Vqp4A sqk3A1VowZDnoe0B+ikPvpLbEJMfI1khHjdZiyPyIPxMGGC6+30IPbj5P9ry8QQGJoNy 3Q==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 39xtj02w2p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <webtransport@ietf.org>; Thu, 22 Jul 2021 18:44:34 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 16MHYAb7016128 for <webtransport@ietf.org>; Thu, 22 Jul 2021 13:44:33 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.112]) by prod-mail-ppoint7.akamai.com with ESMTP id 39y5eqbaqw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <webtransport@ietf.org>; Thu, 22 Jul 2021 13:44:33 -0400
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com (172.27.165.122) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.165.120) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Thu, 22 Jul 2021 12:44:32 -0500
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com ([172.27.165.122]) by ustx2ex-dag1mb4.msg.corp.akamai.com ([172.27.165.122]) with mapi id 15.00.1497.018; Thu, 22 Jul 2021 12:44:32 -0500
From: "Holland, Jake" <jholland@akamai.com>
To: "webtransport@ietf.org" <webtransport@ietf.org>
Thread-Topic: Multicast for the Web (and WebTransport in particular)
Thread-Index: AQHXfyE6Bh+sd3W2E0Osx88LWnfP4Q==
Date: Thu, 22 Jul 2021 17:44:32 +0000
Message-ID: <4B5C8DD7-8F64-4459-94E5-089CBDB04461@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.50.21061301
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/mixed; boundary="_002_4B5C8DD78F64445994E5089CBDB04461akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-07-22_12:2021-07-22, 2021-07-22 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 mlxlogscore=999 malwarescore=0 adultscore=0 bulkscore=0 suspectscore=0 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2107220116
X-Proofpoint-GUID: He0tsSHuqsG9OTpt0PANhy3gSrpKcOYq
X-Proofpoint-ORIG-GUID: He0tsSHuqsG9OTpt0PANhy3gSrpKcOYq
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-07-22_12:2021-07-22, 2021-07-22 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 adultscore=0 impostorscore=0 clxscore=1011 spamscore=0 mlxlogscore=999 malwarescore=0 phishscore=0 bulkscore=0 suspectscore=0 lowpriorityscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2107220116
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.33) smtp.mailfrom=jholland@akamai.com smtp.helo=prod-mail-ppoint7
Archived-At: <https://mailarchive.ietf.org/arch/msg/webtransport/3IMJCHkoY5dRuVLVzmsVs5a3zrw>
Subject: [Webtransport] Multicast for the Web (and WebTransport in particular)
X-BeenThere: webtransport@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: WebTransport WG <webtransport.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webtransport>, <mailto:webtransport-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webtransport/>
List-Post: <mailto:webtransport@ietf.org>
List-Help: <mailto:webtransport-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webtransport>, <mailto:webtransport-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2021 17:44:43 -0000
Hi WebTransport, I'd like to let you know about a new W3C Community group dedicated to incubating Multicast support for web traffic: https://www.w3.org/community/multicast/ https://w3c.github.io/multicast-cg/multicast-cg-charter.html For the first phase, we're working toward an integration with WebTransport, as the charter describes in more detail. I've set up a bar bof side meeting at 11am Pacific Time on Thursday July 29th to discuss further. Details are attached, the meeting link is at the bottom, and it's registered here: https://trac.ietf.org/trac/ietf/meeting/wiki/111sidemeetings (I'd ask for a slot in webtrans, but hilariously, it's at the same time as mboned, where some other parts of this work are under way.) A little more background: Akamai is wrapping up some trials and discussions with several ISPs and content owners evaluating the feasibility of standards- based multicast delivery for our popular production traffic on a 3-5 year timeline. The trials were checking whether our prototypes and specs look like they'll be feasible to deploy after productizing them, and whether the achievable traffic offload would make investment worthwhile. The moderately positive results of these trials (as well as some interest generated during a W3C Interest group presentation) led to the creation of the new community group as part of our next steps. We'll be relying on progress on some of the IETF docs to clarify and address the networking requirements for web traffic as it relates to multicast IP delivery. The first one to consider from the webtrans point of view is probably our recently-posted security considerations draft: https://datatracker.ietf.org/doc/html/draft-krose-multicast-security The aim is for this doc ultimately to perform a similar function to what RFC 8826 did for WebRTC. There are other relevant docs that taken together we think can fill the security needs we know about so far, with a little refinement: https://datatracker.ietf.org/doc/html/draft-ietf-mboned-ambi https://datatracker.ietf.org/doc/html/draft-pardue-quic-http-mcast I understand this to be outside webtransport's current charter, but we'd like to develop this work between now and IETF 112, and in November to bring a coherent and well-supported proposal for next steps either to a venue like secdispatch or to a BoF for an appropriate new group, depending on the advice we get along the way. One option that might be worth considering would be rechartering webtransport to allow for a scope that includes this work. But even if that turns out not to be the right thing, we expect that members of webtransport will have crucial expertise and opinions, and we would value your feedback and request some level of liaison as we try to move this forward. I hope to see some of you next Thursday. Best regards, Jake [1] Webex meeting for Thursday at 11am Pacific (1 hour before the first sessions of the day): https://akamai.webex.com/akamai/j.php?MTID=mbe0822775e2ba553d4669b441833ec38
- [Webtransport] Multicast for the Web (and WebTran… Holland, Jake