Re: msgtrk: MTQP, TLS, & SRV

leg+> Another possibility would be to add a "certificate expected" argument
leg+> to the STARTTLS command, allowing the server to choose which
leg+> certificate to return.  I believe there was discussion of this in a
leg+> working group meeting, but I don't recall what the outcome of it was.

When this was discussed for updating RFC 2487, the decision was to leave
that to the TLS working group.  As I recall, it was then brought up in that
working group and it was agreed it should be part of the TLS client hello
protocol.

Personally, I'd rather see this solved in the underlying protocol then have
each application protocol fix it independently (and differently).