Minion - Service Model and Conceptual API
draft-iyengar-minion-concept-02

Document Type Expired Internet-Draft (individual)
Authors Jana Iyengar  , Stuart Cheshire  , Josh Graessley
Last updated 2014-04-24 (latest revision 2013-10-21)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-iyengar-minion-concept-02.txt

Abstract

Minion uses TCP-format packets on-the-wire, to provide full compatibility with existing NATs, Firewalls, and similar middleboxes, but provides a richer set of facilities to the application. Minion's richer facilities include a message-oriented API rather than TCP's unstructured byte-stream service model, multiplexing of multiple messages (or message streams) on a single connection, interleaving of multiplexed messages (to eliminate head-of-line blocking), message cancellation, request/reply support, ordered and unordered messages, superseding messages, chained messages, multiple priority levels with byte-granularity preemption, and DTLS Security. Minion can be implemented entirely as a user-level library, without waiting for any special support from OS vendors, and provides immediate benefits to application developers. Additionally, Minion is able to take advantage of some simple kernel extensions to provide enhanced services that go beyond what is possible with traditional TCP. These kernel extensions are optional, and even without them, Minion offers worthwhile benefits to application developers.

Authors

Jana Iyengar (janardhan.iyengar@fandm.edu)
Stuart Cheshire (cheshire@apple.com)
Josh Graessley (jgraessley@apple.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)