From: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: Ed Tanous <edtanous@google.com>
Subject: RDE Enablement
Date: Thu, 10 Jun 2021 20:26:21 +0000 [thread overview]
Message-ID: <DF4PR8401MB0634B89E3FF275E28FB590CC8F359@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM> (raw)
Greetings,
I'm am interested to know if there has been any organized discussion or development on Redfish Device Enablement (RDE - DMTF DSP0218) for moving encoded Redfish data across PLDM/MCTP interfaces. We are interested in promoting this standard and are willing to lead a reference implementation for OpenBMC if there is not yet something in progress. If there is something in progress, can you point me at the work because I would love to see it.
What is the normal sequence for proposing, debating and finalizing major new features? Would I submit something in Gerrit for review (e.g. a markdown file for the docs/designs repo?) We could probably get something started fairly soon.
Thanks.
Mike
next reply other threads:[~2021-06-10 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 20:26 Garrett, Mike (HPE Server Firmware) [this message]
2021-06-10 20:32 ` RDE Enablement Ed Tanous
2021-06-10 20:59 ` Garrett, Mike (HPE Server Firmware)
2021-06-10 23:06 ` Andrew Jeffery
2021-06-11 6:53 ` Deepak Kodihalli
2021-06-11 13:31 ` Garrett, Mike (HPE Server Firmware)
2021-08-09 13:50 ` Garrett, Mike (HPE Server Firmware)
2021-07-21 14:16 ` Ed Tanous
2021-07-21 8:34 ` Deepak Kodihalli
2021-07-21 14:23 ` Ed Tanous
2021-07-26 13:53 ` Garrett, Mike (HPE Server Firmware)
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=DF4PR8401MB0634B89E3FF275E28FB590CC8F359@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM \
--to=mike.garrett@hpe.com \
--cc=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
/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).