Self-Synchronous Scramblers For PPP Over Sonet/SDH: Some Analysis
draft-ferguson-pppsonet-selfsync-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dennis Ferguson , Ravi Cherukuri | ||
| Last updated | 1997-11-03 | ||
| 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
The use of a self-synchronous scrambler to minimize the possibility that a carefully chosen PPP over SONET/SDH payload can cause a long sequence of zero bits to be transmitted is examined. It is pointed out that, while self-synchronous scramblers have some attractive properties for the application, the x^43 + 1 scrambler used by ATM for the same purpose has some unfortunate interactions with the 16-bit CRC Frame Check Sequence which is the PPP default FCS. It is suggested that adding a third term to the self-synchronous generator polynomial might improve its behaviour, and that inverting the scrambler bit ordering so it is applied to the data in the same bit order as the PPP CRC FCS algorithms are defined for may eliminate any remaining effect such scramblers have on either PPP FCS.
Authors
Dennis Ferguson
Ravi Cherukuri
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)