standards / principles for secure, free RTC software?

[Daniel Pocock]

I've had a look at the FSF info about the campaign for a Skype replacement

http://www.fsf.org/campaigns/priority-projects/priority-projects/highpriorityprojects#Replaceskype

While it specifies that existing solutions have shortcomings, it
doesn't specify what the final solution should look like. In other
words, a developer aiming to build such a solution won't know when
they cross the finish line.

Has anybody done any policy work, possibly similar to the Debian Free
Software Guidelines, to define the essential attributes of a solution?

Looking at it from another angle, Debian also provides a set of tests
to determine if a license is really free:

http://people.debian.org/~bap/dfsg-faq.html#testing

and it may be useful to define a similar set of tests for evaluating a
communications application.