About 6 results
Open links in new tab
  1. 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 …

  2. 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 …

  3. RFC 1438: Internet Engineering Task Force Statements Of …

    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 …

  4. RFC 5826: Home Automation Routing Requirements in Low

    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, …

  5. 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 …

  6. RFC 2683: IMAP4 Implementation Recommendations

    interoperability can not be tested in a vacuum, the final recommendation of this treatise is, "Test against EVERYTHING." Test your client against every server you can get an account on. Test …