MIF API consideration
draft-liu-mif-api-extension-06
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuri Ismailov , Ted Lemon , Dapeng Liu , Zhen Cao | ||
| Last updated | 2012-04-18 (Latest revision 2011-10-31) | ||
| Replaced by | draft-ietf-mif-api-extension | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mif-api-extension | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Ted Lemon
Dapeng Liu
Zhen Cao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)