Re: [MSEC] QUIC multicast
ATUL SHARMA <atulsharma@comcast.net> Mon, 27 June 2022 22:18 UTC
Return-Path: <atulsharma@comcast.net>
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 A36E2C15AE3C for <msec@ietfa.amsl.com>; Mon, 27 Jun 2022 15:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=comcast.net
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 vCLGw_ChBbiB for <msec@ietfa.amsl.com>; Mon, 27 Jun 2022 15:18:20 -0700 (PDT)
Received: from resdmta-a1p-077302.sys.comcast.net (resdmta-a1p-077302.sys.comcast.net [96.103.146.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 C50E4C15AE2A for <msec@ietf.org>; Mon, 27 Jun 2022 15:18:20 -0700 (PDT)
Received: from resomta-a1p-077051.sys.comcast.net ([96.103.145.229]) by resdmta-a1p-077302.sys.comcast.net with ESMTP id 5qraoxzF0HzlA5x1moTVhk; Mon, 27 Jun 2022 22:16:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1656368178; bh=dq/CCTlQnbKBgfvLUeR68FQD6KC1korLzuTTb8XX1cU=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=IcRdGGROHkHnBunqbh9Clsm9tHQJzIjY/YplZ0c2SFWkuxCoTrPjVWXze6mJ/Gesy 0YOyhAiOLgQSG+YzZnotV21lLU4J/HBoUPfSq7AsTRUEMcZwdnXbgUBBj5gifehVGc Wbk/kll7bsuzGGdJIUCMss50wgO9FspbaTVfrgnykUaXWVLTDxLsyGEfbOLkksYUYw zPTmrAH9aF9th8HW8YsvrUe+LTNCbSPhq/L0E99l89MuZXual/EtQcZbtWre5bWFUV RyfI4avqJiSe/+CEtaMHaYQXy31T7/Xls2vMV8W8q9HDQSZmvh8PspVU+0YereVdkv GLIB8erGZ+Iwg==
Received: from oxapp-asc-48o.email.comcast.net ([96.118.211.13]) by resomta-a1p-077051.sys.comcast.net with ESMTPS id 5x1QoqZiPtSGH5x1QoRv6d; Mon, 27 Jun 2022 22:15:58 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvfedrudegiedgtdelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpeffhffvkfgjfhfugggtgffrkgfoihesthejsgdtredtjeenucfhrhhomheptefvfgfnucfujfettffotecuoegrthhulhhshhgrrhhmrgestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepgfevgeduhfehueeiheehhfektdekkeeghfegleeuffeijeffudfffeffvedvudefnecuffhomhgrihhnpehivghtfhdrohhrghdpghhithhhuhgsrdgtohhmnecukfhppeeliedruddukedrvdduuddrudefpddvgedrledurdduheekrdduheejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohepohigrghpphdqrghstgdqgeekohdrvghmrghilhdrtghomhgtrghsthdrnhgvthdpihhnvghtpeeliedruddukedrvdduuddrudefpdhmrghilhhfrhhomheprghtuhhlshhhrghrmhgrsegtohhmtggrshhtrdhnvghtpdhnsggprhgtphhtthhopedvpdhrtghpthhtohepjhhhohhllhgrnhgupeegtdgrkhgrmhgrihdrtghomhesughmrghrtgdrihgvthhfrdhorhhgpdhrtghpthhtohepmhhsvggtsehivghtfhdrohhrgh
X-Xfinity-VMeta: sc=0.00;st=legit
Date: Mon, 27 Jun 2022 18:15:56 -0400
From: ATUL SHARMA <atulsharma@comcast.net>
To: "Holland, Jake" <jholland=40akamai.com@dmarc.ietf.org>, "msec@ietf.org" <msec@ietf.org>
Message-ID: <1486246645.1193677.1656368156369@connect.xfinity.com>
In-Reply-To: <367D7BA3-4883-49C3-9C9A-B0ACF82AB144@akamai.com>
References: <367D7BA3-4883-49C3-9C9A-B0ACF82AB144@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev21
X-Originating-IP: ::ffff:24.91.158.157
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/msec/lpOf2ARRbvCO6_VjAoFfLbj6G5o>
Subject: Re: [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 22:18:24 -0000
I haven't received any message from MSec in a long long time. What is the latest in this technology? Any draft, RFCs? Best, Atul > On 06/27/2022 11:48 AM Holland, Jake <jholland=40akamai.com@dmarc.ietf.org> wrote: > > > 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/ > > > _______________________________________________ > MSEC mailing list > MSEC@ietf.org > https://www.ietf.org/mailman/listinfo/msec
- Re: [MSEC] QUIC multicast ATUL SHARMA
- [MSEC] QUIC multicast Holland, Jake
- Re: [MSEC] QUIC multicast Holland, Jake
- Re: [MSEC] QUIC multicast ATUL SHARMA
- Re: [MSEC] QUIC multicast Behcet Sarikaya
- Re: [MSEC] QUIC multicast Holland, Jake
- Re: [MSEC] QUIC multicast Behcet Sarikaya
- Re: [MSEC] QUIC multicast Holland, Jake