On 11-Apr-06, at 10:08 AM, Tom Doman wrote:
I have a question about use case B3.
Hmm, it's a bit brief isn't it. Maybe it needs to be beefed up.
It should probably suggest that geekdate.com verifies that
Beth does in fact own the identifier she provides.
What is the "Identifier" being requested by geekdate.com and how
did Beth provide it? She gave consent and the "data" was sent but,
what data?
The data is the identifier... and maybe whatever additional data is
needed to verify that identifier.
Maybe you're trying to be a bit vague here as in the "Identifier"
in B5, B6, etc. to leave it more open but could you perhaps provide
some examples of some of Beth's "Identifiers"?
Well there's are multiple possible solutions.
On the list, both URLs and email addresses have been suggested.
draft-merrells-dix suggests URLs, such as:
http:/www.home.com/beth
I think that would clarify this for me. I'm assuming that these
"Identifiers" are becoming "personas" in later use cases, is this
correct?
Yes, B7 introduces this:
Beth wants to have multiple identifiers, for different aspects of
herself, her personas.
She wants to have a 'home' persona for identity data that she
releases to her personal sites, such as geeknews.com.
She wants to have a separate 'work' persona for identity data that
she releases to work-related sites, such as helpdesk.com.
She wants some of her identity data to be the same for her different
personas, and other data to be different.
John
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
