IPv4 Option for Somecast
draft-dhelder-somecast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Helder , Sugih Jamin | ||
| Last updated | 2000-07-11 | ||
| 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
Somecast is a multi-point delivery technology that allows a packet to be sent to a set of destinations. Somecast delivery means that the network delivers one copy of a packet to each destination listed in the packet. Somecast can be used in small multi-user sessions, such as multimedia conferences and multiplayer games, or used with endhost multicast for larger sessions. This document describes a possible implementation of somecast in IPv4. Somecast is implemented by using an IPv4 header option that includes a list of up to 9 additional destination addresses. This document also describes how somecast can be incrementally deployed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)