designs/mctp/mctp.md

7 Currently, we have a few different methods of communication between host and
9 side-channels, like hiomap. On OpenPOWER hardware at least, we've definitely
10 started to hit some of the limitations of IPMI (for example, we have need
15 platforms provide. Then, on top of MCTP, we have the opportunity to move to
16 newer host/BMC messaging protocols to overcome some of the limitations we've
23 these; we currently have BT and KCS (both defined as part of the IPMI 2.0
37 functionality that we may want to implement for OpenBMC. The DSP numbers
53 covered in detail much; we will propose those parts in separate design efforts.
72 - Allow different hardware channels, as we have a wide variety of target
103 longer under active development, we would likely end up with a large amount of
111 (for example, OpenPOWER). It's possible that we could run a simplified Redfish
120 duplicate the work we have in IPMI handlers.
122 We'd want to keep IPMI running in parallel, so the "upgrade" path should be