25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.4.1 Point-to-point encapsulation<br />

A summary of the PPP encapsulation is shown in Figure 2-5.<br />

Figure 2-5 PPP encapsulation frame<br />

The encapsulation fields are defined as follows:<br />

Protocol field The protocol field is one or two octets, <strong>and</strong> its value<br />

identifies the datagram encapsulated in the Information<br />

field of the packet. Up-to-date values of the Protocol field<br />

are specified in RFC 3232.<br />

Information field The Information field is zero or more octets. The<br />

Information field contains the datagram for the protocol<br />

specified in the Protocol field. The maximum length for the<br />

information field, including padding, but not including the<br />

Protocol field, is termed the Maximum Receive Unit<br />

(MRU), which defaults to 1500 octets. By negotiation,<br />

other values can be used for the MRU.<br />

Padding On transmission, the information field can be padded with<br />

an arbitrary number of octets up to the MRU. It is the<br />

responsibility of each protocol to distinguish padding<br />

octets from real information.<br />

The <strong>IP</strong> Control Protocol (<strong>IP</strong>CP) is the NCP for <strong>IP</strong> <strong>and</strong> is responsible for<br />

configuring, enabling, <strong>and</strong> disabling the <strong>IP</strong> protocol on both ends of the<br />

point-to-point link. The <strong>IP</strong>CP options negotiation sequence is the same as for<br />

LCP, thus allowing the possibility of reusing the code.<br />

One important option used with <strong>IP</strong>CP is Van Jacobson Header Compression,<br />

which is used to reduce the size of the combined <strong>IP</strong> <strong>and</strong> <strong>TCP</strong> headers from 40<br />

bytes to approximately 3-4 by recording the states of a set of <strong>TCP</strong> connections at<br />

each end of the link <strong>and</strong> replacing the full headers with encoded updates for the<br />

normal case, where many of the fields are unchanged or are incremented by<br />

small amounts between successive <strong>IP</strong> datagrams for a session. This<br />

compression is described in RFC 1144.<br />

Chapter 2. Network interfaces 37

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!