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

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

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...
Post a Comment
Read more

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.
Post a Comment
Read more