RE: Note from the past re. x.509 certs, Subjects, and DNs

You are quoting something talking about the  v2 cert (that never saw the light of day). At some point, working on a certain agencies problems, the folks in DEC going for an A1 certification (i.e. formal proofs for everything) hit a "little probem". Peter Williams might be fired, having hogged a DN (in the proof model, for every). ANother Pete Williams might be rehired, wanting a DN being hogged by someone no longer in the system. Hence, for NAME re-assignment purposes (a bit like gender re-assignment but presumably less painful), the uniqueSubkectId was identified. So, too, while they were at it, was the issuer name similarly addressed. Then the web struck, and we got SANs as the ISO response. At that point it was go design your own name scheme. See how well you do (and the story is one of legend).  
 > Date: Sat, 7 Jan 2012 19:54:19 -0500
> From: kidehen@openlinksw.com
> To: public-xg-webid@w3.org
> Subject: Note from the past re. x.509 certs, Subjects, and DNs
> 
> All,
> 
> Digest: http://www.imc.org/ietf-pkix/old-archive-97/msg00342.html
> 
> -- 
> 
> 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
> 
> 
> 
> 
> 
>