Actually, it is based on the industry standard CIM schema with AMT extensions. It may even implement some standard SMASH profiles from the DMTF as well, but I can't seem to find documentation of that.
What a consumer of this interface actually programs to is the schema, not the protocol. -- mark Garrett D'Amore wrote: > Mark A. Carlson wrote: >> David, >> >> I would like to see the AMT and CIM Schema exported by this project >> listed as a Committed interface in the interface table. > > Hmm... I'm not sure how stable they are from Intel. Committed Volatile? > > Again, this project is just an HTTP proxy in what it passes. The HTTP > *content* is beyond the projects control, as it is supplied by Intel > firmware. > > -- Garrett >> >> Thanks, >> >> -- mark >> >> David Chieu wrote: >>> As you know, we've submitted PSARC 2007/601 Intel AMT case about a >>> month ago. There were a barrage of interested questions asked >>> immediately, so we've taken our case off of the fast-track and >>> started to prepare a more detailed documentation. With gracious >>> helps from some of the PSARC members, we've generated a "spec.txt" >>> which is numbered/initialed with detailed answers of already asked + >>> expected questions. We also have broken this doc into major >>> pertinent areas of Intel's AMT: intro, admin/config, security, >>> network, use cases, driver, proxy, virtualization, FMA, and >>> potential customers. Please see the case directory for either >>> spec_amt_draft_v.1.6.pdf or spec_amt_draft_v.1.6.sxw. >>> >>> Please note, the luminary index for Q&A: >>> >>> Garrett D'Amore = (gd) >>> James Carlson = (jc) >>> Bill Sommerfeld = (bs) >>> Nicolas Williams = (nw) >>> Paul Jakma = (pj) >>> Gary Winiger = (gw) >>> Randy Fishel = (rf) >>> >>> The timer for this case is now set to 12/05/2007 >>> >>> -- The Solaris AMT team >
