The FSF campaigns against
the current IETF policy and the current policy used in several standard bodies
(notably ISO) who currently accept standards encumbered with patents, only if
they are licensed to everyone who ask for it, under “reasonable” or
“fair” licensing practices. However the acceptable licenses are not
precisely defined (at ISO, patent licensing royalties are still acceptable),
and notably this does not restrict the licensors from requiring a nominative
agreement with each licensee. Such standards do exist in ISO (notably most MPEG
related applications are covered by such restrictive licenses). However, the FSF
recognizes that, until now, the IETF was more strict about the licensing
conditions, rejecting proposals that included royalties-maker licenses and explicit
personal agreement between the licensor and the licensees (under this scheme,
if it was accepted, nothing would prevent a licensor to start charging yearly royalties
to each licensor for exercising the patented rights. But, the IETF is less
strict about RFCs that are published with “informational” status. We
do have lots of informational RFCs which are still needed and actively used,
sometimes even required (notably those in the BCP series, like the “Netiquette”
which has become a requirement for almost all ISP customers, as part of their
contract, despite they are only informational, and could change at any time after
having been replaced by another RFC replacing the older one with the same BCP
number. I do approve the FSF
campaign: if the IETF publishes a RFC, and even if it’s just
informational and still not a “BCP” recommendation, those RFCs
should really be patent free, or exempt from non-free patents requiring an explicit
license. We have already seen in the past the case where a licensor changed its
policy, and started to claim royaltees for what was initially granted for free
and licensed to any one without charge. We can accept the existence of patents
only as a way to prevent another counter-patent to be reserved by someone else
(but in a free world, such patent is normally not needed, as the copyright assignment
and its legal protection is enough to avoid this). However, the WIPO is
currently changing the game, trying to merge the two systems of copyrights and
patents into a single one with equal force, forcing those that just want a
protection of their copyright to register it at some national or international
registry to maintain the protection. This is a dangerous evolution, because it
would harm all legitimate authors that have produced valuable works, and
assigned a their copyright on these works, to protect it from claims by others:
they would now have to pay each year some fee to a registry to maintain the
protection on their own work; if they just forget to do that, someone else (richer
than the authors) will apply for a patent registration and will pay
indefinitely the registry to gain and enforce the legal protection. For this reason, we
should only accept patents that are protected with the following minimum bases:
With all these conditions,
patents are in fact not needed. We much prefer the system of copyrights which
is much simpler to protect open and free technologies. If needed, all RFCs
published by the IETF should first pass a long enough transitory period where
the RFC is published but with strong notice that it is not approved, so that
the only rile of the publication is to verify that the RFC does not violate any
rights. After this time has elapsed (2-3 years after first publication?) during
which the other patent owners have had the possibility to exercise their rights,
the RFC could be only be in an informational state, becoming a recommendation
later.
De : Lawrence Rosen
[mailto:lrosen@xxxxxxxxxxxx] To: IETF list These are statements from FSF about the issue we've
been discussing at ietf@xxxxxxxx. http://www.fsf.org/campaigns/software-patents/draft-housley-tls-authz-extns.html
and http://www.fsf.org/news/oppose-tls-authz-standard.html
The GPL does not have problems with most IETF
specifications, only those that are encumbered by non-free patents. This is an
important example of why so many of us in the open source and free software
communities believe that the IETF patent policy must be improved. |
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf