we may want a form of GET-PARAMS which fetches session-independent server 
information. One way to do this is to define a MRCPv2-frag content type (like we 
have with sipfrag). That way a SIP OPTIONs to an MRCPv2 server can return an 
MRCP-specific body with all that interesting information about server 
capabilities.

See http://www.ietf.org/mail-archive/web/speechsc/current/msg01387.html for 
discussion