- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 03 Jan 2012 09:36:12 -0500
- To: public-xg-webid@w3.org
On 1/3/12 9:28 AM, Mo McRoberts wrote: > On 3 Jan 2012, at 14:06, Kingsley Idehen wrote: > >> On 1/3/12 7:22 AM, Henry Story wrote: >>>> What is an important point to consider re. WebID is what should be done when the CN contains URLs? >>> A Common Name is not meant to be a URL so there is nothing to do there, unless you want to do screen scraping or detective work. >> So you are claiming this is wrong then? >> >> Subject: C=US, ST=Maryland, L=Pasadena, O=Brent Baccala, >> OU=FreeSoft,CN=www.freesoft.org/emailAddress=baccala@freesoft.org > > CN=www.freesoft.org is not a CN containing a URL, for a start. A CN is effectively arbitrary, will often be used for matching (cf. clients comparing SSL server hostnames). And emailAddress is not an Address either right? What do you think www.freesoft.org is then? > > (You could add a URI as a DN attribute, though, if you know the signing entity will accept it — just pick or define an appropriate attribute OID). > > Whether *parts* of a DN should trigger special processing on the part of a receiver is a different matter. I can't recall what ITU recs have to say on the subject. I do know that a number of free personal certificate issuers mandate that the CN is a fixed string. We are using a standard representation of an info card and its semantics, to construct a protocol with its own set of semantics i.e., the WebID verification protocol. Nothing that I've stated breaks anything re. X.509 or PKI. Neither does it break WebID. Its only issue is novelty. > > M. > -- Regards, Kingsley Idehen Founder& CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Received on Tuesday, 3 January 2012 14:36:36 UTC