chris  i am sort of of the mind that having only two tests here to begin with speaks to insufficient coverage of the capability and paints us into a corner with respect to procedure  e g  what if tempest just flat out had a bug that broke these two tests this is something we should bring up with the committee  in the interim i would like to look and see if there are not other tests that could be added for the capability  but unfortunately they would have to go through the advisory cycle first and will not really help for ish i will also note that there is a  potential  loophole should we feel the need to invoke it  the bylaw states that  vendors  may not request flagging all tests for a capability  refer to community review  vendor self test c c for the actual wording so if  for example  the foundation  through it is interoperability engineer  presumably  or perhaps folks acting on behalf of the board  like  say  the co chairs of the defcore committee  though i will note one of them has a potential conflict of interest in this particular instance as she is employed by the same vendor  were to request it  that would not violate the bylaw  in the interim  you are right  we cannot accept dropping all the tests for a capability at a vendor s request  so i am still  i am going to look into whether there are additional tests we should be including so that they can start the advisory phase sooner rather than later 