linux-cxl.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Manzanares <a.manzanares@samsung.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Lukas Wunner <lukas@wunner.de>, Ira Weiny <ira.weiny@intel.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	"ben@bwidawsk.net" <ben@bwidawsk.net>,
	"linuxarm@huawei.com" <linuxarm@huawei.com>,
	"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
	"Box, David E" <david.e.box@intel.com>,
	"Chuck Lever" <chuck.lever@oracle.com>,
	Krzysztof Wilczy??ski <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	Joerg Roedel <joro@8bytes.org>
Subject: Re: (SPDM) Device attestation, secure channels from host to device etc: Discuss at Plumbers?
Date: Wed, 29 Jun 2022 16:01:57 +0000	[thread overview]
Message-ID: <20220629160149.GA1039216@bgt-140510-bm01> (raw)
In-Reply-To: <20220624153241.000055e2@Huawei.com>

On Fri, Jun 24, 2022 at 03:32:41PM +0100, Jonathan Cameron wrote:
> On Fri, 24 Jun 2022 16:15:31 +0200
> Lukas Wunner <lukas@wunner.de> wrote:
> 
> > On Fri, Jun 24, 2022 at 12:08:30PM +0100, Jonathan Cameron wrote:
> > > I've put this in for now:  
> > 
> > Perfect!  For me as a non-native English speaker, it would have been
> > a lot more difficult to write up such an excellent description,
> > so thanks for doing this.
> 
> It always feels a bit like cheating when you get to write these
> things in your first language!
> > 
> > > Hence this proposal for a BoF rather than session in 
> > > either PCI or CXL uconf.  
> > 

I am planning to be attending plumbers in person and am quite interested in 
this BOF.


> > I think this has overlap with the Confidential Computing uconf as well,
> > so that might be another potentially interested audience.
> > 
> > (Link encryption is by its very nature "confidential computing",
> > and attestation is explicitly mentioned on the CC uconf page:
> > https://urldefense.com/v3/__https://protect2.fireeye.com/v1/url?k=10369d39-71bd8872-10371676-74fe485fb305-1ce6f2197c6a68d6&q=1&e=6639a8eb-2d66-432f-a3d9-760b3e8def9f&u=https*3A*2F*2Flpc.events*2Fevent*2F16*2Fcontributions*2F1143*2F__;JSUlJSUlJSU!!EwVzqGoTKBqv-0DWAJBm!UGKGabNBEqfdQU-FrF-bEnhwu9mRW4PRGa1LoMvehedU3XRfsZzuoHGUZUVWHVD3p26pNa-le6OwJPQwMs7wV4kiu9GUb9ld$  )
> > 
> > Thanks,
> > 
> > Lukas
> > 
> 
> Good point. That is an area in which we need dance around what we
> can an can't say (i.e. what is public from various standards orgs) but they 
> may well still be interested.
> 
> Added 
> - Confidential compute community
> to list of people who might be interested.
> 
> +CC Joerg so he knows this proposal exists and can perhaps drag in anyone
> else who might be interested.
> 
> https://urldefense.com/v3/__https://lore.kernel.org/all/20220624120830.00002eef@Huawei.com/__;!!EwVzqGoTKBqv-0DWAJBm!UGKGabNBEqfdQU-FrF-bEnhwu9mRW4PRGa1LoMvehedU3XRfsZzuoHGUZUVWHVD3p26pNa-le6OwJPQwMs7wV4kiu68CJwlU$ 
> for abstract.
> 
> Thanks,
> 
> Jonathan
> 

  reply	other threads:[~2022-06-29 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 11:47 (SPDM) Device attestation, secure channels from host to device etc: Discuss at Plumbers? Jonathan Cameron
2022-06-09 14:22 ` Ira Weiny
2022-06-17 10:21   ` Jonathan Cameron
2022-06-20 16:52     ` Lukas Wunner
2022-06-22 11:46       ` Jonathan Cameron
2022-06-24 11:08         ` Jonathan Cameron
2022-06-24 14:15           ` Lukas Wunner
2022-06-24 14:32             ` Jonathan Cameron
2022-06-29 16:01               ` Adam Manzanares [this message]
2022-09-06 11:59                 ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220629160149.GA1039216@bgt-140510-bm01 \
    --to=a.manzanares@samsung.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=ben@bwidawsk.net \
    --cc=bhelgaas@google.com \
    --cc=chuck.lever@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=david.e.box@intel.com \
    --cc=hch@infradead.org \
    --cc=ira.weiny@intel.com \
    --cc=joro@8bytes.org \
    --cc=kw@linux.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lukas@wunner.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).