Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Point-to-Point Protocol
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Encapsulation=== PPP frames are encapsulated in a lower-layer protocol that provides framing and may provide other functions such as a [[checksum]] to detect transmission errors. PPP on [[serial link]]s is usually encapsulated in a framing similar to [[HDLC]], described by IETF RFC 1662. {| class="wikitable" |- ! Name ! Number of bytes ! Description |- | Flag | 1 | indicates frame's begin or end |- | Address | 1 | broadcast address |- | Control | 1 | control byte |- | Protocol | 1 or 2 or 3 | l in information field |- | Information | variable (0 or more) | datagram |- | Padding | variable (0 or more) | optional padding |- | FCS | 2 (or 4) | error check |} The Flag field is present when PPP with HDLC-like framing is used. The Address and Control fields always have the value hex FF (for "all stations") and hex 03 (for "unnumbered information"), and can be omitted whenever PPP LCP Address-and-Control-Field-Compression (ACFC) is negotiated. The [[frame check sequence]] (FCS) field is used for determining whether an individual frame has an error. It contains a checksum computed over the frame to provide basic protection against errors in transmission. This is a [[Cyclic redundancy check|CRC]] code similar to the one used for other layer two protocol error protection schemes such as the one used in Ethernet. According to RFC 1662, it can be either 16 bits (2 bytes) or 32 bits (4 bytes) in size (default is 16 bits - Polynomial ''x''<sup>16</sup> + ''x''<sup>12</sup> + ''x''<sup>5</sup> + 1). The FCS is calculated over the Address, Control, Protocol, Information and Padding fields after the message has been encapsulated.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Point-to-Point Protocol
(section)
Add topic