At 5:32 PM -0700 9/14/05, Michael Thomas wrote:
Ned Freed wrote:
Such a third party would act as a repository for update information
provided by
vendors. Applications would then "call home" to one of these repositories
rather than directly to the vendor. Various anonymyzing tricks could be
employed to minimize information leakage even if the third party was
compromised.
You mean we could invent Bitorrent? :)
BitTorrent (note the spelling) does a lot of very nice things, but
not those. For those interested, the BitTorrent protocol is described
at <http://www.bittorrent.com/protocol.html>.
Mike, doesn't it strike others as odd
that ietf is completely outside of the
p2p bizness?
In this case, there is no advantage to the developer of the protocol
to have it worked on in the IETF, nor even published as an RFC. It
came out of one person's head, he was able to experiment with it live
on the net, and he retains the ability to tweak the specs whenever he
feels like it. It has worked remarkably well, given the variety of
clients and servers available for the protocol, and the huge amount
of traffic that is moved daily over it.
--Paul Hoffman, who shares a lot of legal music and OSs with BitTorrent
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf