Content deleted Content added
Guy Harris (talk | contribs) →Framing: Use {{cite IETF}} for an RFC. |
m avoid unnec redirect |
||
Line 1:
{{context|date=February 2013}}
In [[
When packets of varying length are sent, it is necessary to have an instantly recognizable packet-end delimiter. When a continuous stream of fixed-length frames are sent, a synchronized receiver can in principle identify frame boundaries forever. In practice, receivers can usually maintain synchronization despite transmission errors; [[bit slip]]s are much rarer than [[bit error]]s. Thus, it is acceptable to use a much smaller frame boundary marker, at the expense of a lengthier process to establish synchronization in the first place.
Line 16:
Common frame synchronization schemes are:
;Framing bit: A common practice in [[
;Syncword and flag sequence framing: Rather than a single bit, some systems use a multi-bit [[syncword]] in each frame, or a '''flag sequence''' that marks the beginning and end of each frame. [[High-Level Data Link Control]] and similar systems use flag sequences.<ref>{{Cite IETF |rfc=1662 |title=PPP in HDLC-like Framing |last=Simpson |first=William A. |date=July 1994 |publisher=Internet Engineering Task Force}}</ref>
;CRC-based framing: Some telecommunications hardware uses [[CRC-based framing]], where correct framing is verified when almost all frames have valid CRCs.
|