Re: [MSEC] Multicast Security Considerations

ATUL SHARMA <atulsharma@comcast.net> Sat, 13 November 2021 18:26 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 988193A04BB for <msec@ietfa.amsl.com>; Sat, 13 Nov 2021 10:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olzmeU3SY-vT for <msec@ietfa.amsl.com>; Sat, 13 Nov 2021 10:26:27 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 7A2B93A048D for <msec@ietf.org>; Sat, 13 Nov 2021 10:26:27 -0800 (PST)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id lxhMmKSoKdtzzlxjMmHm8m; Sat, 13 Nov 2021 18:26:24 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1636827984; bh=DxNOu0HFNoPnOXU9RXq/VzmURV8KsSp8lPeXi996PxU=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=XSTKGGOxK+6AS+taBYbIHRExfsZki++4Cnz9/ps+rxwnZIXk35OFIXunTZKeCHKIL mFVkhqgfqbm4lbUHvJYK3lrojZ8vnGAEuYnJrJ+tji+8/eZHXBVjDlMVafgFGIJkKO kT0vWxHXbiJeU0CkJnkqlnRB5lAcEsLb5b9Sw0QgyYGjQDW9KEZiGQezqGJFs+wqqW f7LNIelrKrvHsimLLHKrryE8l736FBTy0Ei/2Ujm6Yp2VO0yFunY+lLDDam7vXr0s5 N9pv8Ib/o4fJn7pyBinM4SXVwiPtvZjppx1NG3zZ79/Gn5FG2/DqxiEwgnPNQNM2po VJCOxWyuZcKYw==
Received: from oxapp-asc-53o.email.comcast.net ([96.118.210.117]) by resomta-ch2-03v.sys.comcast.net with ESMTPS id lxjLmz5A9nLBRlxjLmLG3q; Sat, 13 Nov 2021 18:26:24 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvuddrvdehgdduudefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpeffhffvkfgjfhfugggtgffrkgfoihesthejsgdtredtjeenucfhrhhomheptefvfgfnucfujfettffotecuoegrthhulhhshhgrrhhmrgestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepffejveeiveegtdehjeevkedtleduvdfhgeejvddvjefhleeufeevhfeuveffveevnecuffhomhgrihhnpehivghtfhdrohhrghdphihouhhtuhgsvgdrtghomhenucfkphepleeirdduudekrddvuddtrdduudejpddviedtudemudekfhemiedttdemfhdttdemrgegsggvmeelfedvmeejvgehsgemsggtiegvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohepohigrghpphdqrghstgdqheefohdrvghmrghilhdrtghomhgtrghsthdrnhgvthdpihhnvghtpeeliedruddukedrvddutddruddujedpmhgrihhlfhhrohhmpegrthhulhhshhgrrhhmrgestghomhgtrghsthdrnhgvthdprhgtphhtthhopehjhhholhhlrghnugepgedtrghkrghmrghirdgtohhmsegumhgrrhgtrdhivghtfhdrohhrghdprhgtphhtthhopehmshgvtgesihgvthhfrdhorhhg
X-Xfinity-VMeta: sc=0.00;st=legit
Date: Sat, 13 Nov 2021 13:26:23 -0500
From: ATUL SHARMA <atulsharma@comcast.net>
To: "Holland, Jake" <jholland=40akamai.com@dmarc.ietf.org>, "msec@ietf.org" <msec@ietf.org>
Message-ID: <568586790.293075.1636827983826@connect.xfinity.com>
In-Reply-To: <C831F66E-3D94-4CBF-9968-97ED2E42638B@akamai.com>
References: <C831F66E-3D94-4CBF-9968-97ED2E42638B@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: 2601:18f:600:f00:a4be:932:7e5b:bc6e
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/msec/_5Oi_oL0POs6cd6n6BsGVoacX_8>
Subject: Re: [MSEC] Multicast Security Considerations
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 13 Nov 2021 18:26:32 -0000

Hi Jake,

Let us resurrect MSEC mailing list.

Best,
Atul

> On 11/12/2021 10:58 AM Holland, Jake <jholland=40akamai.com@dmarc.ietf.org> wrote:
> 
>  
> Hi msec,
> 
> I know this WG is shut down and the list is mostly defunct, but for
> anyone still on it:
> 
> I had a slot in secdispatch last Tuesday to talk about multicast
> security:
> - https://datatracker.ietf.org/doc/html/draft-krose-multicast-security
> - https://www.youtube.com/watch?v=vbbFgM761t4&t=1h37m51s
> - https://datatracker.ietf.org/meeting/112/materials/slides-112-secdispatch-multicast-security-privacy-considerations-00
> 
> The dispatch decision was to go to a mailing list for further discussion,
> possibly msec, or possibly a new one.
> 
> The stuff we're looking to get discussed is closely related to msec's
> prior work, but I think not fully in-scope for the old msec charter,
> mainly because (I think?) the GDOI model may not be fully applicable
> to the sort of broadcast TV scale we're aiming to support in the latest
> efforts I covered in the secdispatch presentation, as we don't anticipate
> having quite the same kind of trusted key server setup, and we aim to
> do the Authentication and Integrity constraints differently.  But with
> that said, the particulars are open for discussion.
> 
> Anyway, my first question is whether anybody objects to opening
> discussion on the topic on this list?  The other main option was to
> create a new mailing list for the new multicast security discussion, and
> I think the opinions of current msec list members would be key.
> 
> If we do it here, I'd be inviting all the interested parties I can find
> to join and discuss the draft and the plans.  I'd be trying to figure
> out if we can get to where a BoF seems useful, and if the problem space
> can get the kind of discussion and feedback that it needs to reach a
> consensus status on what it takes to deliver multicast safely with the
> modern internet's ideas of safety (specifically aiming to include Web
> traffic, against the advice of some of the web security luminaries).
> 
> Other possibly useful background includes the one review from Ekr on the
> secdispatch list and the ensuing discussion:
> https://mailarchive.ietf.org/arch/msg/secdispatch/N1jDh7MRHupuPIf1S5BiLDecGGY/
> 
> And also the discussion the next day in mboned, where some of the background
> work ahead of this has been happening:
> https://www.youtube.com/watch?v=xCl9NlRZoik&t=31m24s 
> https://datatracker.ietf.org/meeting/112/materials/slides-112-mboned-multicast-to-the-browser-update-00.pdf
> 
> Please send back opinions if you have them, else I'll assume it won't
> bother anybody to start using this list.
> 
> Best,
> Jake
> 
> 
> _______________________________________________
> MSEC mailing list
> MSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/msec