Minion - Wire Protocol
draft-iyengar-minion-protocol-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) | ||
https://www.ietf.org/archive/id/draft-iyengar-minion-protocol-02.txt
Abstract
Minion uses TCP-format packets on-the-wire, for compatibility with existing NATs, Firewalls, and similar middleboxes, but provides a richer set of facilities to the application, as described in the Minion Service Model document. This document specifies the details of the on-the-wire protocol used to provide those services.
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.)