The entire process will certainly have an impact on the organization,
even if "certification" is never revoked. The process of developing
test specifications is slow, tedious, and about as alluring as the
prospect of writing a MIB. It tends to attract relatively few people
As I said... no test specifications. Just $100, say you are
complying, boom you have the logo and the "trust" of IETF.
It's up to an IETF working group to challenge that trust and
threaten to yank the logo, which is the "one true mark" of that
trust.
No one wants to be bogged down with bureaucracy, but I don't
mind filling out an application, sending in $100, and getting
the logo. If I become a bad vendor, then people in an IETF
WG can move to yank my logo. There should be a process for
the "yanking" of the logo that is very fair, and arguably
should happen over a period of time, be pretty lenient
and give vendors more than ample time to "do the right thing."
The goal here isn't to punish vendors, rather, to promote
standards, and created a trusted "one true mark" that says
you have the trust of the IETF. CIOs can use that mark
as a differentiator with products and can choose to not
buy from vendors that lose that trust...
Kyle Lussier
AutoNOC LLC