RFC 3751:Omniscience Protocol Requirements
RFC-Ref

requirement


Click on the red underlined text to get to the source

... Garratt v. Dailey] Because it can be quite difficult to establish a person's intent lawmakers have, in some cases, reduced the requirement for prosecutors to establish intent and mere possession is now proof enough of intent. ...
... enough of intent. This memo proposes a set of requirements for a new protocol to be used by prosecutors to determine a person's intent, thus reducing the ...
... new protocol to be used by prosecutors to determine a person's intent, thus reducing the need to dilute the historical legal requirement to show intent and by groups such as the MPAA and RIAA to be sure they are dealing with ...


... Omniscience Protocol Requirements ...
... For the purpose of these requirements, I will assume that the OP is implemented using a client-server model, where the OP client ...
... referred to as a miscreant) is in full control of a computer and that OP Servers will generally be operated by "Good guys." (See Functional Requirements FR5-7 for requirements to ensure that the latter is the case.) In the context ...
... OP Servers will generally be operated by "Good guys." (See Functional Requirements FR5-7 for requirements to ensure that the latter is the case.) In the context of this memo, "evil-doer" and ...
... Operational Requirements ...
... the network, the OP must be able to continue to communicate, even under these circumstances. Meeting this requirement may require that the OP client be able to reconfigure the user's ...
... Functional Requirements ...
... updated if the laws change or the computer is moved to a location where the laws are different. Note that this requirement also implies that the OP client knows where its OP server is located to know if the client and server ...



Google
Web
RFC-Ref