- From: Thomas Roessler <tlr@w3.org>
- Date: Thu, 18 Dec 2008 14:01:02 +0100
- To: Mary-Ellen Zurko <mzurko@us.ibm.com>, Tyler Close <tyler.close@hp.com>
- Cc: WSC WG <public-wsc-wg@w3.org>
Mez, Tyler, I notice that we've seen the return of the petnames proposal into the specification (as resolved on 5 November, reversing a decision made at the face-to-face). > For TLS-secured pages, the user agent MAY allow the user to assign > the authenticated entity a [Definition: petname]. This assignment > MUST create a binding between the petname and the base domain of the > site hosting the page. > - What's the "site hosting the page"? Is that the provider's domain name, or is it one taken from the URI that was dereferenced? - Can we please throw out the base domain notion? There is no reference here, and there is no stable reference or algorithm in existence that is guaranteed to last longer than 2010 [1]. I don't think that referencing a service that is being offered by one vendor is appropriate. I guess I can live with saying "implementations can pick some suffix of their choosing" (as we're doing for the identity signal already), as that gives clear warning that this feature includes implementation- defined behavior. Related to this one, we seem to have skipped over the petnames-related piece of Ian Griggs's comment (LC-2094, [2]) when discussing that one at the face-to-face, based on the notions that petnames would go: > Promoting Petnames would be a substantial improvement in UI > practices. This document more or less supports them, but, unlike > its promise, does not describe why they are so useful, and > importantly when to use them (suggest to user) rather than > anyalternate. We are very far away from useful guidance. > In contrast to petnames, there is little commentary on key > continuity management. These are very close to petnames, is the > point that we may as well just implement petnames? I suppose there still needs to be an answer drafted to this piece of the comment. 1. http://icann.org/en/topics/new-gtld-program.htm 2. http://www.w3.org/2006/02/lc-comments-tracker/39814/WD-wsc-ui-20080724/2094 Regards, -- Thomas Roessler, W3C <tlr@w3.org>
Received on Thursday, 18 December 2008 13:01:12 UTC