-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Andrew" == Andrew Newton <andy@xxxxxx> writes:
Andrew> Considering the IETF encourages people to communicate with
Andrew> it via mailing lists and there really has been no other ways
Andrew> offered to the FSF, I can't really blame them.
Andrew> Perhaps we ought to look forward and see how the IETF can
Andrew> better communicate with the FSF. Perhaps maybe thinking
Andrew> about a more formal relationship.
uhm, the FSF is an organization, but it's not the collective of all
people writing GPL or other-open-source-licensed software.
Mostly the people writing open source software that implement IETF
protocols are already among us ALREADY... often they don't have budgets
to attend meetings, and sometimes, their time budget limits how much
attention they can pay to the mailing lists, or to writing drafts.
(Let along contribute to our management process and structure.
The nomcom attendance requirements just to remain qualified for
instance are a barrier. Lisa Dussault is the only IESG person I know of
who lives and breaths open source while fulfilling two other fulltime jobs)
Given that almost every successful IETF protocol has had at least one
open source implementation (often two or three), the IETF really has to
do a better job of including more open source implementers.
TLS is a REALLY good example here. It took off for everything because
managers perceive that it has an API. (What you say?) Yes.
OpenSSL is the API they say is it.
I suspect that FSF cares because it has another implementation which
is pretty popular, GnuTLS.
Apparently they have ALREADY implemented this draft, PRIOR to the IPR
claim. The code is out there, and therefore the *technique* is out
there.
SURELY the IETF doesn't want to DISCOURAGE early implementation?
- --
] Y'avait une poule de jammé dans l'muffler!!!!!!!!! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@xxxxxxxxxxxxxxxxxxxxxx http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Finger me for keys
iQEVAwUBSZGWm4CLcPvd0N1lAQKV4Af/SUlhrjtGto2j0eKO12cs6/Dg2dFxQVj4
yqWV81Uy6IpIiAawY0oyFWnDH2BBVepWsVwYNXCxoOv8pGEtuhRI1khhdNOVr63Z
pHjJ75/WErK3fEeroZvWaiIDRYibHhOtpGnkgr6i27689zc6jIJMnC2G8/L/72+W
WjEjFruWJWhMUNrVBCqXiPt+8nnzxbcvkznVxtmCCONMCDHYlYM4bXAZOSkXWuAT
j1DI89HuAGLAHTzFX2f9cTMEPWmU0KcjOqebNjuElKRJQRzV9v2C/RYtc5eojCiF
kBkDgBQkPjIxGU//wKKrXP7teA0kXTHIur5YrwDMRqHtTn9iMrpJOQ==
=4tQN
-----END PGP SIGNATURE-----
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf