Enabling Byte Stuffing Transparency for RFC-1619
draft-takefman-pppext-transper-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Peter Lothberg , Robert M. Broberg , M. Takefman | ||
| Last updated | 1998-07-31 | ||
| 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
Recent Internet Draft submissions and discussion on the PPP Extensions Working Group email list have highlighted transparency issues with the PPP over SONET/SDH mapping described in IETF RFC1619 and RFC1549. The HDLC byte stuffing described by RFC1549 can result in a worst case expansion of the actual payload data by a factor of 2. An algorithm suggested below limits the expansion factor to be a maximum of 6% the actual data to be transported.
Authors
Peter Lothberg
Robert M. Broberg
M. Takefman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)