> Personally, I'd rather see this solved in the underlying protocol then have > each application protocol fix it independently (and differently). leg+> Regardless, MTQP needs to specify what certificate name needs to be leg+> sent. Why "regardless"? If it is solved in the TLS protocol, why duplicate it in the MTQP protocol? Or are you assuming it will never be solved by the TLS protocol?