Here is what I'm getting from your text:
DIX provides a standardized basis, for client-based interfaces:
1) to interact with the user and the user's environment,
2) to acquire a collection of information related to the user, based on
requests from servers, and
3) selectively provide this data to the requesting servers, based on
user permissions and contextual aggregations specific to the
relationship between the user and a particular service
A few more thoughts have occurred to me:
User contact with remote services often requires that the user supply a variety
of information. The information might be appropriate to supply to many
different services or it might be specific to a particular relationship between
that user and a single service.
The DIX effort will define:
a) a common framework for representing user-specific information, based on an
attribute/value model (identity-related attribute format)
b) an initial set of attribute definitions
c) one or more means (protocols) for requesting and exchanging user-specific
attributes on behalf of the user.
d/
--
Dave Crocker
Brandenburg InternetWorking
<http://bbiw.net>
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
