[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: End-Entity Certificate Policies



I would like to add my/our voice(s)in support of Dave's and Mack's responses.

We strongly resist the idea of restrictions.  Our community has some deployed 
infrastructure and proposed services that absolutely rely upon multiple 
policy OIDs.  In some cases it is helpful, in many other cases it is 
imperative that they be supported.  (full disclosure-some of my projects 
require this as well)

After a painful, but terribly productive last two days at the ANSI X9F5 
meeting at the ABA's offices it was discomforting to see the first parts of 
this thread.

I was very pleased to see that the response from the banking community.  
Historically it has been extremely helpful to many folk involved in policy 
making and standards setting to review the concrete requirements from 
communities such as Identrus, SWIFT, and ABAecom as well as the deployed 
infrastructures run by financial institutions in the wild.  Having those 
requirements accessible directly or through participation in discussions like 
these is essential to finding solutions that actually work and meet real 
needs.  

I would encourage everyone to take great care to determine whether proposals 
would cause already deployed systems to become unsupported or render them 
noncompliant.

I have more specific arguments if anyone would like to hear them.

...Kawika Daguio...