Lee, Both HTTP Boot and Redfish are very new standards. HTTP Boot got standardized as part of UEFI 2.5 in March. Redfish is still not even 1.0 (last published spec is 0.96.0a, with a target 1.0 spec sometime this month according to DMTF). It is expected that implementation will take some time to catch up to the spec. At the same time, PXE and IPMI have been there for quite some time, are implemented across the board on servers (and many clients), and are already in wide use. I do not expect them to go away anytime soon. But the goal is to switch over to HTTP and Redfish/REST over time, especially as they enable new use cases and capabilities that were not possible (or easy to do) before.
The first step though is to get the specs implemented. As Ting explained, Intel is working on UEFI 2.5 HTTP Boot implementation (that I expect will show up in EDK2. I see the header files submitted already). DMTF is also working on a Redfish mockup/simulator that can be used to exercise clients. HP ProLiant Gen9 servers already support proprietary flavors of both HTTP Boot (or "Boot from URL") and Redfish (or the "HP RESTful API"). I do not know of any other servers that implement such technologies at this time. As to your more general question, that is harder to answer. Usually, OEMs and IBVs declare standards supported in their firmware. But even then, the level of support and specific firmware versions make are not easy to pinpoint. This is the case with any new standard (UEFI/PI included) until the adoption is high and the support becomes widely available across the industry. Thanks, --Samer -----Original Message----- From: Blibbet [mailto:blib...@gmail.com] Sent: Friday, June 05, 2015 7:00 PM To: edk2-devel@lists.sourceforge.net Subject: [edk2] UEFI HTTP Boot and Redfish support? HP gave a talk at the Spring UEFI Forum event titled "Goodbye PXE and IPMI. Welcome HTTP Boot and Redfish!". But a few days ago AMI just released a new IPMI-based product, so "Goodbye IPMI" is apparently not a universally agreed upon, pehaps "Welcome to the party, pal!" is more approrpiate? :-) Besides HP, who supports UEFI 2.5 HTTP Boot? Besides HP, who supports Redfish with their UEFI implementation? DNS/DHCP/HTTP[S] servers aside, is there enough code in TianoCore to support HTTP Boot, or is additional non-TianoCore code required, including HTTPS TLS support? More generally, how do people figure out which IBV/OEMs support UEFI's various features? Except for a few OEMs, most consumer merchant pages for hardware rarely includes information about firmware, and the main consumer resource AFAICT (Consumer Reports) is also ignoring firmware in it's data. The UEFI.org pages don't have any information on this. It's hard to determine what features in the UEFI Forum spec are in Tianocore, and what are only in commercial products. I wish the UEFI Forum would work with its vendor members to help clarify the features their products include. Heck, I'd create a new page on Wikipedia or elsewhere, if I had the data. Thanks, Lee RSS: http://firmwaresecurity.com/feed ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
