[Extracted from Blair Dillaway's email to the list.]

This document is a good start, but is too high-level and unfocused to properly motivate and justify the mechanisms 
developed in the other specifications.  Ideally, the use-cases should reflect functionality the target audience for 
these specification deems critical and requiring interoperable solutions. I believe more detail will be required to 
achieve that goal. Of course, it would be best to get input, and/or incorporate already documented use-cases, from 
groups such as HPC Profile, ByteIO, etc..

 

The use-case discussion should also highlight the specific functional requirements that drive the mechanism in the draft
 specs. In particular: why is a discovery mechanisms for authN and communication security requirements  needed; what 
authN mechanisms are required ; what protocols must be supported; why are message integrity and encryption mandatory; is
 communications security only needed point-to-point or  must it span processing intermediaries? The current doc is quite
 weak in this area.