Q. Is there a concept of an owner/administrator of a mesh?
A. Yes, you can have roles in a mesh.

Q. Is there a way to kick someone out of a mesh?
A: Currently, the only way to kick someone out of a mesh is to create another mesh without this member. Clearly, this may work with small groups, but not with larger groups. With larger groups, we currently do not have a means to revoke a person from a mesh.

Q: What are the differnet optimizations that are done on the mesh, and how do these work?
A: Meshes are dynamically shaped for optimizing data delivery to all nodes, and meshes are very difficult to get partitioned. If they do get partitioned, some of our offerings have ways in which these can be repaired. To read on details on how the mesh algorithms work at a high level, please take a look at this white paper http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/p2pintro.mspx under the section of graphing. Please note that we use the words graphing, grouping, peer channel and mesh interchangeably just to keep things confusing :)

Q: Is there a way in which data sent in the mesh can be signed so that it is not tampered?
A: Yes, data sent in the mesh can be signed and encrypted.

Q: Are there any message patterns/protocols being standardized on top of the mesh?
A: WCF (aka Indigo) provides a means by which services/protocols can be composed on top of existing channels. I don't have information on whether any of these message patterns built on top of the peer channel would get standardized or not at this stage.

Q: Are there constraints to the clients on how much data can be sent?
A: There are limits on how much data can be flooded around to prevent obvious DoS attacks.

Q: What are the plans with standards body alignment?
A: At this stage, I don't have anything concrete to tell you all. Please stay tuned in this space.

Q: When would I use grouping vs the peer channel?
A: Grouping is a win32 API that enables multiparty replication/synchronization on a small scale (in the hundreds). If you have the need to maintain a history for what has happened in a mesh, then the grouping technology would suit you best. Peer Channel on the other hand is a multiparty messaging system (with no backing store for the data sent) that is intended for larger scale scenarios (where number of participants is in the thousands). Clearly, you could use either technology depending on what your needs are. If you want data replication in the peer channel, you would have to maintain your own store. If you want messaging in grouping, you would need to send short lifetime records that are replicated. It depends on the scenario. If you want managed API, and are already building a WCF application, then the peer channel may be the way to go. If you already have a win32 application that you are enhancing, then grouping could be the way to go. We are providing different options for you to pick from.

Q: How do the contact certs in question get deployed on the various machines?
A: This is out of band of our infrastructure, and admittedly, is a little hard. We are making it as simple as emailing the Me contact which is located in the WAB, but it is still a manual step outside of our infrastructure. Do you think this is actually that hard? I am interested in hearing your feedback on how we could make this easier if this is a hard problem.