The IPv6 Payload Header
draft-dupont-ipv6-payload-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Francis Dupont | ||
| Last updated | 2002-03-05 | ||
| 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
This draft describes a method by which many IPv6 payload data bodies may be encapsulated in a single IPv6 datagram using a new non-terminal header will contain both a payload and necessary fields (like a ``next header'' field) allowing header chaining. This document specifies how two packets can be merged into a single one and the reverse one-step operation. But the main purpose is to provide a basis to discussions about the pros and cons of such a mechanism.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)