Die RFC's der Internet Engineering Task Force (IETF) sind eine beeindruckende Sammlung - auch von Kuriositäten:
RFC 2324 vom 1. April 1998 (!)
Auszug:
This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. 1. Rationale and Scope [...]The demand for ubiquitous appliance connectivity that is causing the consumption of the IPv4 address space. Consumers want remote control of devices such as coffee pots so that they may wake up to freshly brewed coffee, or cause coffee to be prepared at a precise time after the completion of dinner preparations. [...] 2. HTCPCP Protocol The HTCPCP protocol is built on top of HTTP, with the addition of a few new methods, header fields and return codes. All HTCPCP servers should be referred to with the "coffee:" URI scheme (Section 4). 2.1 HTCPCP Added Methods 2.1.1 The BREW method, and the use of POST Commands to control a coffee pot are sent from client to coffee server using either the BREW or POST method, and a message body with Content-Type set to "application/coffee-pot-command". A coffee pot server MUST accept both the BREW and POST method equivalently. However, the use of POST for causing actions to happen is deprecated. Coffee pots heat water using electronic mechanisms, so there is no fire. Thus, no firewalls are necessary, and firewall control policy is irrelevant. However, POST may be a trademark for coffee, and so the BREW method has been added. The BREW method may be used with other HTTP-based protocols (e.g., the Hyper Text Brewery Control Protocol).
Zu guter Letzt noch ein Taschenspielertrick, der die Rolle von Client und Server etwas auf den Kopf stellt: HostYoSelf.
Oder zurück zum Ausgangspunkt, wenn es genug für heute ist.