-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Martin Atkins
Sent: Friday, November 10, 2006 2:41 AM
To: [EMAIL PROTECTED]
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style
Identifiers
I provide email addresses to some of my friends
Sent: Sunday, October 22, 2006 12:26 PM
To: John Panzer
Cc: Kaliya *; specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style
Identifiers
...
If we support email addresses, then the prompt may look something
like this:
email | Homesite | i-name | OpenID
Now any
with email addresses?
-Original Message-
From: Hallam-Baker, Phillip [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 4:37 PM
To: David Fuelling
Cc: specs@openid.net; [EMAIL PROTECTED]
Subject: RE: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
Please don't map
-
From: Dick Hardt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 5:06 PM
To: David Fuelling
Cc: specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
A Homesite is a new concept for users, so when they see a prompt
To: Johannes Ernst
Cc: Hallam-Baker, Phillip; specs@openid.net; general
Subject: Re: XRDS vs. DNS level identity (was RE: [PROPOSAL]
Handle http://[EMAIL PROTECTED] Style Identifiers)
I agree with Johannes here. DNS is not user accessible (for
good reason) Documents on a web server are relatively
://[EMAIL PROTECTED] Style Identifiers
On 11/9/06, David Nicol [EMAIL PROTECTED] wrote:
http://[EMAIL PROTECTED] (cool addy, btw) certainly
won't get anyone to David Fuelling's home page, now or in any likely
future.
True, http://[EMAIL PROTECTED] won't get anyone to my homepage...but it
would
# I think that all this discussion about email userid is moving us off
# track. My original proposal was that the email maps/normalizes to a
# URL of an IdP (the userid is ignored/not used).
#
# So, '[EMAIL PROTECTED]' would be treated as if the User had entered
# 'http://any.edu' (the URL of
19, 2006 9:46 PM
To: specs@openid.net
Subject: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
In meeting with a large service provider this week, an issue around end
user usability came up. The concern they expressed was that users are
know how to enter usernames or email
://[EMAIL PROTECTED] Style Identifiers
There have been several long threads in the past about using email
addresses as OpenID identifiers. The conclusion each time has been to
avoid it. I don't remember all the arguments, but among them are:
* Privacy: the last thing many users want to give
] On Behalf Of David Fuelling
Sent: Wednesday, November 08, 2006 1:40 PM
To: specs@openid.net
Subject: RE: [PROPOSAL] Handle http://[EMAIL PROTECTED]
Style Identifiers
Please see my questions/ideas enclosed...
Thanks!
David Fuelling
-Original Message-
From: [EMAIL PROTECTED
]
Sent: Wednesday, November 08, 2006 1:45 PM
To: David Fuelling; specs@openid.net
Subject: RE: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
Please don't use HTTP this way. That is not the semantics for http URLs.
A better scheme would be to use mailto:[EMAIL PROTECTED
PROTECTED]
Sent: Wednesday, November 08, 2006 1:45 PM
To: David Fuelling
Cc: specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
# So, if in a hypothetical world where we have 4 potential OpenId
# values that a user could enter, AND the goal is to reduce
PROTECTED]
Subject: RE: [PROPOSAL] Handle http://[EMAIL PROTECTED]
Style Identifiers
Hi Philip,
I'm not sure I understand Please don't use HTTP this way.
I was suggesting that the user enter an email address. The
RP then maps the email address to a URL (which would be in
the proper scheme
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Peter Watkins
Sent: Wednesday, November 08, 2006 4:21 PM
To: [EMAIL PROTECTED]
Cc: specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
Recordon, David wrote
; 'David Fuelling'
Cc: specs@openid.net; [EMAIL PROTECTED]
Subject: XRDS vs. DNS level identity (was RE: [PROPOSAL]
Handle http://[EMAIL PROTECTED] Style Identifiers)
Phillip,
Please don't shoot me -- I am just the messenger -- but a
year-long effort
(Yadis) went into the design
Fuelling
Cc: specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
Hi David
A Homesite is a new concept for users, so when they see a prompt for
it, they will know they have one or not. They are not just typing in
a random URL.
Pretty much every
; [EMAIL PROTECTED]
Subject: XRDS vs. DNS level identity (was RE: [PROPOSAL]
Handle http://[EMAIL PROTECTED] Style Identifiers)
Phillip,
Please don't shoot me -- I am just the messenger -- but a
year-long effort
(Yadis) went into the design and deployment of XRDS documents
as the discovery
: Thursday, November 09, 2006 2:05 AM
To: Johannes Ernst
Cc: Hallam-Baker, Phillip; specs@openid.net; general
Subject: Re: XRDS vs. DNS level identity (was RE: [PROPOSAL]
Handle http://[EMAIL PROTECTED] Style Identifiers)
I agree with Johannes here. DNS is not user accessible (for
good reason
Message- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Dick Hardt Sent: Sunday, October 22, 2006 5:00 PM To:
Kaliya Hamlin Cc: specs@openid.net Subject: Re: [PROPOSAL]
Handle "http://[EMAIL PROTECTED]"
Style Identifiers On 22-Oct-06, at 12:43 PM, Kaliya
Ha
On 22-Oct-06, at 11:44 AM, Praveen Alavilli wrote:
It's more of a problem with how we can accept 3rd party OpenId
users at AOL (we as an RP). Obviously for simple use cases like
leaving comments on blogs it wouldn't really matter as long as the
user is identified by someone (and someone
: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style
Identifiers
For starters please don't use Comic Sans in professional correspondence.
it is very hard to read (or take seriously)
http://bancomicsans.com/home.html
On Oct 22, 2006, at 11:44 AM, Praveen Alavilli wrote
For starters please don't use Comic Sans in professional correspondence. it is very hard to read (or take seriously) http://bancomicsans.com/home.htmlOn Oct 22, 2006, at 11:44 AM, Praveen Alavilli wrote: It's more of a problem with how we can accept 3rd party OpenId users at AOL (we as an RP).
Dick Hardt wrote:
What is different with OpenID vs email is that there is certainty
that the user actually is the user.
I'm a little confused. How is there certainty that the user actually
is the user? The viability of the identifier representing the same
user is dependent on the
[EMAIL PROTECTED] wrote:
For starters please don't use Comic Sans in professional
correspondence. it is very hard to read (or take seriously)http://bancomicsans.com/home.html
On Oct 22, 2006, at 11:44 AM, Praveen Alavilli wrote:
It's more of a problem with how we can
Dick Hardt wrote:
On 20-Oct-06, at 10:14 AM, George Fletcher wrote:
Of course, my expectation is that this syntax would be optional; the
user can always specify their full URI identifier.
I agree that this kind of an identifier is not portable, but I'm
guessing that most users wouldn't
[Please pardon me if I am spamming
the spec mailing list with general comments/issues that might have been
discussed before]
It's not the problem of just making AOL users OpenId enabled, so they
can access 3rd party RPs (use http://www.aol.com/loginId or
http://aimpages.com/loginId or
On 22-Oct-06, at 5:05 PM, George Fletcher wrote:
Dick Hardt wrote:
What is different with OpenID vs email is that there is certainty
that the user actually is the user.
I'm a little confused. How is there certainty that the user
actually is the user? The viability of the identifier
On 22-Oct-06, at 7:00 PM, George Fletcher wrote:
Dick Hardt wrote:
With OpenID, there is a presumption the user has selected a trust
worthy IdP that will only present the user's identifiers when it
really is the user.
Doesn't this imply that both the user and RP have to know which IdP's
Dick Hardt wrote:
On 22-Oct-06, at 7:00 PM, George Fletcher wrote:
Dick Hardt wrote:
With OpenID, there is a presumption the user has selected a trust
worthy IdP that will only present the user's identifiers when it
really is the user.
Doesn't this imply that both the user and RP
On 22-Oct-06, at 9:04 PM, George Fletcher wrote:
Dick Hardt wrote:
On 22-Oct-06, at 7:00 PM, George Fletcher wrote:
Dick Hardt wrote:
With OpenID, there is a presumption the user has selected a trust
worthy IdP that will only present the user's identifiers when it
really is the
# The thing is they aren't really giving them their email address.
# Rather an identifier which looks like an email address to a user and
# in some cases may also be an email address.
Isn't that likely to create a lot of confusion?
--
Jonathan Daugherty
JanRain, Inc.
Yes, potentially. It is a bit of a hybrid approach I guess.
--David
-Original Message-
From: Jonathan Daugherty [mailto:[EMAIL PROTECTED]
Sent: Friday, October 20, 2006 12:59 PM
To: Recordon, David
Cc: Drummond Reed; specs@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL
m: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On Behalf
Of Recordon, David
Sent: Thursday, October 19, 2006 6:46 PM
To: specs at openid.net
Subject: [PROPOSAL] Handle "http://[EMAIL PROTECTED]" Style Identifiers
In meeting with a large service provider this week, an
@openid.net
Subject: Re: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style
Identifiers
# The thing is they aren't really giving them their email address.
# Rather an identifier which looks like an email address to a user and #
in some cases may also be an email address.
Isn't that likely to create
# It might create some confusion depending on the audience. For the
# audience that doesn't run their own web server, or have their own
# blog, it might be confusing to enter a URI.
By confusion, I mean entering something that looks like an email but
probably isn't, and trying to figure out just
Kaliya *
wrote on 10/20/2006, 11:57 AM:
I think it is a terrible idea.
1) If you put something out into the market that looks like an e-mail
it will be used like an e-mail. I have personal experience with this.
I had a AIM handle for the Mac part of the universe [EMAIL PROTECTED] (it
On 10/20/06, John Panzer [EMAIL PROTECTED] wrote:
Kaliya *
wrote on 10/20/2006, 11:57 AM:
I think it is a terrible idea.
1) If you put something out into the market that looks like an e-mail
it will be used like an e-mail. I have personal experience with this.
I had a AIM handle
On 10/19/06, Recordon, David [EMAIL PROTECTED] wrote:
The proposal we came up with was within the spec describing what to do
if someone were to enter [EMAIL PROTECTED] in a Relying Party's OpenID
login form.
Here are the past threads that I could find about this issue:
1.
# I'm not actually proposing the IdP make an assertion about
# [EMAIL PROTECTED] It would only be used during the discovery phase
# and then an assertion for a URL be returned.
Ok, I misunderstood. But even in the case where the IdP makes an
assertion about a different identifier, that's
We actually built some code some time ago to explore this. The basic
insight was:
if we can do Yadis discovery on XRIs (which aren't rooted in DNS),
then we can do Yadis discovery on any other kind of identifier,
whether it's an e-mail address or an ISBN number or what have you --
and
@openid.net
Subject: [PROPOSAL] Handle http://[EMAIL PROTECTED] Style Identifiers
In meeting with a large service provider this week, an issue
around end user usability came up. The concern they
expressed was that users are know how to enter usernames or
email addresses to initiate the login
41 matches
Mail list logo
