DHCP Segmentation/Reassembly using SEAL
draft-templin-dhcpmtu-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2008-07-30 | ||
| 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
IP fragmentation has been shown to be problematic through operational experience and through studies conducted over the course of many years. Some transports (e.g., TCP) have the abilitiy to adjust their message sizes to avoid IP fragmentation, however no such capability is built into the UDP transport. UDP applications such as DHCP must therefore have a means to perform their own segmentation prior to submitting their data to UDP/IP in order to avoid IP fragmentation. This document specifies a segmentation/reassembly capability for DHCP using SEAL.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)