Multiparty Transport Overlay Control Protocol(MTOCP)
draft-kellil-sam-mtocp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christophe Janneteau , Mounir Kellil , Pierre Roux | ||
| Last updated | 2010-07-26 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
To cope with the lack of IP multicast support in today's Internet, a multiparty transport overlay architecture is presented in this document. The goal behind placing the overlay paradigm at the transport layer is to support both multicast-capable and non- multicast IP networks while providing an application-agnostic delivery service for group communications. In particular, this document specifies the Multiparty Transport Overlay Control Protocol (MTOCP) used to create, update and remove multiparty transport trees in an IP network.
Authors
Christophe Janneteau
Mounir Kellil
Pierre Roux
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)