On 17-Mar-06, at 7:28 AM, Robert Yates wrote:
1. The space owner adds a new member to the space. The new member
is e-mailed a url link to the space along with a welcome message
from the space owner.
2. Members of the space need to authenticate before being allowed
access to the space. Their id is checked against the list of
members allowed into a particular space.
3. The spaces membership list is available to all members of the
space. This list also makes available the contact details of the
members so that other members can contact them easily. This
includes contact information such as business telephone, e-mail and
jabber id.
4. All postings to the space display who made the posting.
5. Members keep track of activity in the space by subscribing to
the space's feed.
Some observations of these requirements and dmd1.
Requirements 2 and 4 are met by dmd1
Requirements 1 and 3 cannot currently be met by dmd1. There's a
couple of interesting point here. Namely that it is the
enterprise, not the individual that makes the decision about
whether to release certain attributes about an individual. It also
determines to whom (i.e. which partners) those attributes can be
released. Also, the individuals contact details needs to be
available prior to the individual logging into the space. As soon
as an individual is added to the membership list their contact
information should be available to other members in the space.
Requirement 5 is not met by dmd1 as "Rich Clients" are presently
not in scope.
Personally, I think that a goal of DIX would be to provide the basis
for your to solve your problem above. Some of the aspects are part of
your application, rather then the protocol. From what I gather from
the problem statement, an email address is likely the easier
identifier for identifying users. A SAML assertion linking the email
address and the persona-url could be made by a third party, either
the server at the domain of the email address or a trusted 3rd party.
This allows the space owner to add email address to the space. The
new member gets the email, and logs in proving they own they email by
providing the SAML assertion and their persona-url. I think this
covers (1) above. (3) is covered by the application displaying the
list of email addresses of the members.
(5) would be nice to solve real-soon-now. Not sure what is
appropriate or standard within IETF for setting up a subgroup to work
on that. We still don't have a WG for the core stuff in DIX.
-- Dick
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
