The IPv6 Payload Header
draft-kre-ipv6-payload-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Robert Elz , Dr. Francis Dupont | ||
Last updated | 1995-10-11 (Latest revision 1995-03-23) | ||
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 suggests a method by which many IP payload data bodies may be encapsulated in a single IPv6 datagram. New headers, designed with IPv6 in mind, will all contain a ``next header'' field, allowing headers to be chained, however older header types, inherited from IPv4, such as TCP and UDP, do not contain this field. This means that, without assistance, they would have to be the last header in any sequence, and only one such header could appear in a packet. This draft provides the mechanism to overcome this difficulty.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)