MIF API consideration
draft-liu-mif-api-extension-06
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2012-04-18 (latest revision 2011-10-31) | ||
| Replaced by | draft-ietf-mif-api-extension | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
|
||
| Stream | Stream state | (No stream defined) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-mif-api-extension | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-liu-mif-api-extension-06.txt
Abstract
This document describes an abstract API that provides the minimal functionality required for a program to communicate effectively with peers and services on the network while running on a host that has more than one active network interface. This API is abstract: we describe the functionality that must be provided, not the bindings that should be used to provide that functionality. The functionality described here provides the building blocks from which higher-level APIs might be built, and is not intended to be used directly by typical applications.
Authors
Yuri Ismailov
([email protected])
Ted Lemon
([email protected])
Dapeng Liu
([email protected])
Zhen Cao
([email protected])
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)