
RFC 7282: On Consensus and Humming in the IETF
vote, nor do we want decisions to be made in a vacuum without practical experience. Instead, we strive to make our decisions by the consent of all participants, though allowing for some dissent (rough …
RFC 1438: Internet Engineering Task Force Statements Of Boredom …
However, once everyone has approved the document by falling asleep over it, the process ends and the document is discarded. The resulting vacuum is viewed as having the technical approval of the IETF, …
RFC 6707: Content Distribution Network Interconnection (CDNI) …
fact that the CDNI interfaces need not be created in a vacuum and that reuse or leverage of existing protocols is likely possible. The four CDNI interfaces (CDNI Control interface, CDNI Request Routing …
RFC 5826: Home Automation Routing Requirements in Low ... - RFC …
unresponsive if using more than 0.5 seconds to, e.g., pause the music. On more rare occasions, receiving nodes may also have moved. Examples include a safety-off switch in a clothes iron, a …
This includes security systems, robotic vacuum cleaners, or anyone taking a picture with a camera. Such systems may store the picture(s) in such a way that a future viewer of the image will be able to …
RFC 3467: Role of the Domain Name System (DNS)
expedient compromises typical with prototypes. If they prove useful, the nature of the network permits very rapid dissemination (i.e., they fill a vacuum, even if a vacuum that no one previously knew …