Removing Trust Models and including "Mutual Trust"
"Jim Pinkerton" <[email protected]>
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <E6564B8F86852D46A4E98C485FB33B8F067BD63F@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> |
Per the last IETF meeting, the Trust Model concept has now been moved to the Appendix. The document now focuses on whether a resource is shared or not, and assumes the Remote Peer is untrusted. An interesting side-effect of this is that the definition for "Partial Trust" goes with it. And the document in general assumes the Remote Peer (and Unprivileged Local Peer) are simply "untrusted". This semantic is unfortunately not rich enough, however. I've started editing the document to more directly address security concerns in a client/server environment. As part of that editing, it seems worthwhile to introduce a new concept Sara Bitan and I are calling "partial mutual trust" (Sara is now an author on the document, specifically working on the Security Services for RDMAP/DDP section). This more acurately describes the "session" concept that some applications have. And then one can talk about how two Streams do not share "mutual trust" and thus are subject to a specific attack and need X countermeasure - so we can now define a server that has multiple sessions (each with potentially multiple Streams) to individual clients, and individual clients do not trust each other. Feedback on this model would be appreciated. Here's my tentative definition of "partial mutual trust": Partial Mutual Trust - a collection of RDMAP/DDP Streams are willing to assume that the other Streams will not perform malicious attacks against any of the Streams in the collection. Jim