Bicast packet identification header
draft-petander-mipshop-bicasthdr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Henrik Petander | ||
| Last updated | 2006-10-17 | ||
| 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
Bicasting or multicasting of traffic can be used to reduce the impact of a handoff by allowing a Mobile Node to receive a stream via multiple paths simultaneously. However, receiving of multiple copies of the packets may have a negative impact on applications which cannot distinguish duplicate packets. This holds true for all applications using TCP which mistakes the packet duplication from bicasting with congestion and reduces the sending rate drastically. This document specifies an IPv6 destination option header which can be used to identify and discard duplicate copies of bicasted packets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)