From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jikos@kernel.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C55D11113
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Sun, 23 Sep 2018 18:54:34 +0000 (UTC)
Received: from mx1.suse.de (mx2.suse.de [195.135.220.15])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B896EA8
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Sun, 23 Sep 2018 18:54:32 +0000 (UTC)
Date: Sun, 23 Sep 2018 20:54:29 +0200 (CEST)
From: Jiri Kosina <jikos@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
In-Reply-To: <20180923183407.GA2774@thunk.org>
Message-ID: <nycvar.YFH.7.76.1809232052170.15880@cbobk.fhfr.pm>
References: <alpine.LRH.2.21.1809220709090.19240@namei.org>
	<20180922131640.pxjwukrckggxtg3s@mwanda>
	<nycvar.YFH.7.76.1809231518440.15880@cbobk.fhfr.pm>
	<20180923183407.GA2774@thunk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Security
List-Id: <ksummit-discuss.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/>
List-Post: <mailto:ksummit-discuss@lists.linuxfoundation.org>
List-Help: <mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=subscribe>

On Sun, 23 Sep 2018, Theodore Y. Ts'o wrote:

> > 3) there simply is a need for CRD process for the kernel (which pretty 
> >    much by definition is not happening publicly). Currently, security@ 
> >    serves that purpose, so if you make that public, you have to 
> >    instantiate some other process to deal with CRDs.
> 
> Can you expand the acronym "CRD".

"Coordinated release date" across the various affected vendors.

-- 
Jiri Kosina
SUSE Labs