Sure the most funny IETF RFC that I have been given to read. This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), based on HTTP, which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
]]>
]]>
Parmi les protocoles utilisés sur Internet, presque tous sont internationalisés depuis longtemps. Le dernier gros manque concernait les adresses de courrier électronique, obligées de s'en tenir à stephane@internet-en-cooperation.fr alors qu'on voudrait pouvoir écrire à stéphane@internet-en-coopération.fr. Désormais, nous avons une solution, Internationalized Email, dont les normes sont désormais effectives.
2. Enhance the existing IMAP4 message retrieval and/or message submission (RFC 2476) protocols to satisfy the requirements for forwarding a message and/or its attachments without downloading the message to the client and subsequently uploading the message to a server.
As noted above, if a connected resource does not request the roster during a session, it SHOULD never receive presence subscriptions and the associated roster pushes.
finally know why my bot was an epic failure.
]]>
Feed Paging and Archiving (nee Feed History) has finally made it to a standards-track RFC.
Who does need a web browser now?
]]>
]]>
This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document, in combination with RFC 4647, replaces RFC 3066, which RFC 1766.
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.
]]>
This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series. This memo is an upwards-compatible revision to RFC 2629.
]]>
]]>
]]>
The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This protocol is intended to control multiple data delivery sessions, provide a means for choosing delivery channels such as UDP, multicast UDP and TCP, and provide a means for choosing delivery mechanisms based upon RTP (RFC 1889).
the end of an era ... one of (the first?) RFC that breaks the all-in-text religion
]]>
]]>
This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources.