[AMD Official Use Only - General] Thanks and sure, I will kick off the discussion on the mailing list. Regards, Abner From: Oram, Isaac W Sent: Saturday, October 22, 2022 4:34 AM To: Chang, Abner ; Gao, Liming ; Desimone, Nathaniel L Cc: nicklew@nvidia.com; Attar, AbdulLateef (Abdul Lateef) Subject: RE: Propose the ManageabilityPkg under edk2-platform/Features Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding. Abner, >From my perspective, this looks reasonable. I think that we need to have the actual discussion on the mailing list so that our various customers can weigh in on the design and implementation. Regards, Isaac From: Chang, Abner > Sent: Wednesday, October 19, 2022 11:08 PM To: Gao, Liming >; Desimone, Nathaniel L >; Oram, Isaac W > Cc: nicklew@nvidia.com; Attar, AbdulLateef (Abdul Lateef) > Subject: Propose the ManageabilityPkg under edk2-platform/Features [AMD Official Use Only - General] Hi Liming, Nate and Isaac, This is Abner from AMD. I am writing to let you know that Nvidia and AMD is going propose a new package ManageabilityPkg under edk2-platforms/Features. We would like to provide the Feature driver, Protocol driver instance and transport implementation that includes PLDM, MCTP, IPMI and KCS industry standard under ManageabilityPkg for the server management. The concept of this package is to provide the driver stacks as shown in the below drafting, We may also pull IpmiFeaturePkg out of Intel/OutOfBandManagement folder. Thus the IpmiFeaturePkg can be referred by the edk2 driver (e.g., Modules under RedfishPkg) without the Intel folder in the INF package section or add edk2-platforms/Feature/Intel to the PACKAGES_PATH (add edk2-platform to packages path is required) for the build. We will take care the backward compatibility issues of IpmiFeaturePkg relocation, however can only cover the issues in the scope of edk2-platform. How do you think? Thanks and Regards, Abner