Ripcord
Senior Lurker
Today the Internet Society released RFC 3751, detailing the requirements of the Omniscience Protocol.
The protocol is designed to meet the requirement of Orrin Hatchs call for a method to allow law enforcement, large software vendors, media conglomerates, and other bodies in or controlling the US government, to allow remote destruction of computers found to be involved in performing illegal activity, like sharing music and nuclear launch codes.
Such a protocol paves the way for legislation allowing such activity. Law enforcement and corporations would have a method of detecting and disabling bad guys, clearing the ever-more-seedy Internet from the bad element, and making it once again clear to carry important data such as adult entertainment and spam.
The protocol includes requirements for strong encryption, anti-spoofing mechanisms, and the ability to install itself and operate on systems even while not connected to the Internet.
The RFC can be found at any RFC archive site, or specifically here:
http://mirror.switch.ch/rfc/3751.txt
or http://www.faqs.org/rfcs/rfc3751.html
The protocol is designed to meet the requirement of Orrin Hatchs call for a method to allow law enforcement, large software vendors, media conglomerates, and other bodies in or controlling the US government, to allow remote destruction of computers found to be involved in performing illegal activity, like sharing music and nuclear launch codes.
Such a protocol paves the way for legislation allowing such activity. Law enforcement and corporations would have a method of detecting and disabling bad guys, clearing the ever-more-seedy Internet from the bad element, and making it once again clear to carry important data such as adult entertainment and spam.
The protocol includes requirements for strong encryption, anti-spoofing mechanisms, and the ability to install itself and operate on systems even while not connected to the Internet.
The RFC can be found at any RFC archive site, or specifically here:
http://mirror.switch.ch/rfc/3751.txt
or http://www.faqs.org/rfcs/rfc3751.html