Skip to main content

WAN Standards / WAN Encapsulation



2.1.3 WAN Standards
WANs use the OSI reference model, but focus mainly on Layer 1 and Layer 2. WAN standards typically describe both physical layer delivery methods and data link layer requirements, including physical addressing, flow control, and encapsulation. WAN standards are defined and managed by a number of recognized authorities.
The physical layer protocols describe how to provide electrical, mechanical, operational, and functional connections to the services provided by a communications service provider. Some of the common physical layer standards are listed in Figure , and their connectors illustrated in Figure .
The data link layer protocols define how data is encapsulated for transmission to remote sites, and the mechanisms for transferring the resulting frames. A variety of different technologies are used, such as ISDN, Frame Relay or Asynchronous Transfer Mode (ATM). These protocols use the same basic framing mechanism, high-level data link control (HDLC), an ISO standard, or one of its sub-sets or variants

 2.1.4 WAN Encapsulation
Data from the network layer is passed to the data link layer for delivery on a physical link, which is normally point-to-point on a WAN connection. The data link layer builds a frame around the network layer data so the necessary checks and controls can be applied. Each WAN connection type uses a Layer 2 protocol to encapsulate traffic while it is crossing the WAN link. To ensure that the correct encapsulation protocol is used, the Layer 2 encapsulation type used for each router serial interface must be configured. The choice of encapsulation protocols depends on the WAN technology and the equipment. Most framing is based on the HDLC standard.
HDLC framing gives reliable delivery of data over unreliable lines and includes signal mechanisms for flow and error control. The frame always starts and ends with an 8-bit flag field, the bit pattern is 01111110. Because there is a likelihood that this pattern will occur in the actual data, the sending HDLC system always inserts a 0 bit after every five 1s in the data field, so in practice the flag sequence can only occur at the frame ends. The receiving system strips out the inserted bits. When frames are transmitted consecutively the end flag of the first frame is used as the start flag of the next frame.
The address field is not needed for WAN links, which are almost always point-to-point. The address field is still present and may be one or two bytes long. The control field indicates the frame type, which may be information, supervisory, or unnumbered:
  • Unnumbered frames carry line setup messages.
  • Information frames carry network layer data.
  • Supervisory frames control the flow of information frames and request data retransmission in the event of an error.
The control field is normally one byte, but will be two bytes for extended sliding windows systems. Together the address and control fields are called the frame header. The encapsulated data follows the control field. Then a frame check sequence (FCS) uses the cyclic redundancy check (CRC) mechanism to establish a two or four byte field.
Several data link protocols are used, including sub-sets and proprietary versions of HDLC. Both PPP and the Cisco version of HDLC have an extra field in the header to identify the network layer protocol of the encapsulated data.




Comments

Post a Comment

Popular posts from this blog

Windowing

Windowing 11.1.5 This page will explain how windows are used to transmit data. Data packets must be delivered to the recipient in the same order in which they were transmitted to have a reliable, connection-oriented data transfer. The protocol fails if any data packets are lost, damaged, duplicated, or received in a different order. An easy solution is to have a recipient acknowledge the receipt of each packet before the next packet is sent. If a sender had to wait for an ACK after each packet was sent, throughput would be low. Therefore, most connection-oriented, reliable protocols allow multiple packets to be sent before an ACK is received. The time interval after the sender transmits a data packet and before the sender processes any ACKs is used to transmit more data. The number of data packets the sender can transmit before it receives an ACK is known as the window size, or window. TCP uses expectational ACKs. This means that the ACK number refers to the next packet that is...
Post a Comment
Read more

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...
Post a Comment
Read more

1.2.2 RIP V2 Features

 1.2.2 RIP V2 Features This page will discuss RIP v2, which is an improved version of RIP v1. Both versions of RIP share the following features: It is a distance vector protocol that uses a hop count metric. It uses hold down timers to prevent routing loops – default is 180 seconds. It uses split horizon to prevent routing loops. It uses 16 hops as a metric for infinite distance. RIP v2 provides prefix routing, which allows it to send out subnet mask information with the route update. Therefore, RIP v2 supports the use of classless routing in which different subnets within the same network can use different subnet masks, as in VLSM. RIP v2 provides for authentication in its updates. A set of keys can be used on an interface as an authentication check. RIP v2 allows for a choice of the type of authentication to be used in RIP v2 packets. The choice can be either clear text or Message-Digest 5 (MD5) encryption. Clear text is the default. MD5 can be used t...
Post a Comment
Read more