IETF Logo Mail Archive

[MSEC] QUIC multicast

"Holland, Jake" <jholland@akamai.com> Mon, 27 June 2022 15:48 UTC

Return-Path: <jholland@akamai.com>
X-Original-To: msec@ietfa.amsl.com
Delivered-To: msec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B345BC14F747 for <msec@ietfa.amsl.com>; Mon, 27 Jun 2022 08:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.851
X-Spam-Level:
X-Spam-Status: No, score=-2.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.745, 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_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMuFH3ypqK6M for <msec@ietfa.amsl.com>; Mon, 27 Jun 2022 08:48:44 -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 E718AC14F73A for <msec@ietf.org>; Mon, 27 Jun 2022 08:48:44 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.17.1.5/8.17.1.5) with ESMTP id 25REf9sm009713 for <msec@ietf.org>; Mon, 27 Jun 2022 16:48:44 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=WA/DUfCmLYzFTnyMCD+1p1nHHuu8F/xyzUHFFgk8vlI=; b=H1OOMVTfH8qjamPh5opBzhGYu8P/fWuBHOq2Adc0QmeX5PMX1xHByFEUqNRFE5S/YTTn pi2Ldzy7MkZgZEMe6NTy57mnZcfAViSFzcuK/U/O9kbQVglaX2JBTu0XvOlQ/By5hTT4 zBjJRNlVQ/NBQScNJh5NvDuqAD74ToRT85bUQpCooYeWrHGyigXOeDV6uoXGsK39/EHU +tbXI0QWPimbkFgPeMnyRVKwy1HkJxiCm1+ek9IZC8MNPcw6T26hIwQJi0TuhfQG30tT Cf4+WkoOu7CLfF4LDYlb25mLJBREfEaZZmAGBDrAwUJbAHMv5BT0RB9JFcp6W2eNl6bC Kw==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050093.ppops.net-00190b01. (PPS) with ESMTPS id 3gwsmu4271-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <msec@ietf.org>; Mon, 27 Jun 2022 16:48:44 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.17.1.5/8.17.1.5) with ESMTP id 25REqn02013235 for <msec@ietf.org>; Mon, 27 Jun 2022 11:48:42 -0400
Received: from email.msg.corp.akamai.com ([172.27.91.26]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 3gx4wsde5f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <msec@ietf.org>; Mon, 27 Jun 2022 11:48:42 -0400
Received: from usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) by usma1ex-dag4mb8.msg.corp.akamai.com (172.27.91.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.986.26; Mon, 27 Jun 2022 11:48:42 -0400
Received: from usma1ex-dag3mb5.msg.corp.akamai.com (172.27.123.55) by usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) with Microsoft SMTP Server (TLS) id 15.0.1497.36; Mon, 27 Jun 2022 11:48:42 -0400
Received: from usma1ex-dag3mb5.msg.corp.akamai.com ([172.27.123.55]) by usma1ex-dag3mb5.msg.corp.akamai.com ([172.27.123.55]) with mapi id 15.00.1497.036; Mon, 27 Jun 2022 11:48:42 -0400
From: "Holland, Jake" <jholland@akamai.com>
To: "msec@ietf.org" <msec@ietf.org>
Thread-Topic: QUIC multicast
Thread-Index: AQHYij1gcuY29HGYmk+y8BxGzr0uNA==
Date: Mon, 27 Jun 2022 15:48:41 +0000
Message-ID: <367D7BA3-4883-49C3-9C9A-B0ACF82AB144@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.61.22050700
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B1ECE929BEAC6A40BEF2854432EC7A6F@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-06-27_06,2022-06-24_01,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=697 malwarescore=0 mlxscore=0 phishscore=0 bulkscore=0 adultscore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2204290000 definitions=main-2206270067
X-Proofpoint-GUID: fcNusLg7hS0Mw0KgwysDffL5p9VkUr5C
X-Proofpoint-ORIG-GUID: fcNusLg7hS0Mw0KgwysDffL5p9VkUr5C
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-06-27_06,2022-06-24_01,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 mlxscore=0 clxscore=1011 bulkscore=0 lowpriorityscore=0 mlxlogscore=619 adultscore=0 impostorscore=0 priorityscore=1501 malwarescore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2204290000 definitions=main-2206270067
Archived-At: <https://mailarchive.ietf.org/arch/msg/msec/hpv0dkBM67JYC-58XHYnZp9uEEE>
Subject: [MSEC] QUIC multicast
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/msec>, <mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/msec/>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>, <mailto:msec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2022 15:48:48 -0000

Hi msec,

One of the actionable pieces of feedback[1] from the secdispatch
presentation of draft-krose-multicast-security at IETF 112 was
that we needed a concrete protocol proposal in order to evaluate
the security considerations, so we went ahead and made a
concrete proposal for multicast QUIC:
https://datatracker.ietf.org/doc/draft-jholland-quic-multicast/
https://github.com/GrumpyOldTroll/draft-jholland-quic-multicast

We think this proposal meets the security goals given in
draft-krose-multicast-security (plus the one that Ekr raised that
we haven't added text for about web content needing to be associated
with a url), but if you can see any sense in which this draft falls
short or is unclear on how those security properties are achieved,
we'd love to get that feedback (and suggestions on fixing it if you
have any).

I haven't sent this to quic yet, but will do so before long
unless anyone in msec can point out a critical flaw.  I'm planning
to ask for a short slot in quic to present at 114.  My main question
will be about what wg members would want to see addressed before
we ask for adoption (not planning to ask for adoption this time yet),
plus soliciting general feedback.

-Jake

PS: several members of the W3C Multicast Community Group have
been working on an implementation and we'll have a table at the
hackathon, so if you'd like to be involved with that, please let
me know.

[1] notes from the secdispatch feedback:
https://mailarchive.ietf.org/arch/msg/msec/FYx5GsAtAyI3pypPIlJ_s3vtiwc/

v2.23.0 | Report a Bug | By Email