RSS
|
||||
  Implementing Prioritization On IP Networks | ||||
|
By Eric Hall With the introduction of the 802.1Q and 802.1p drafts, you can now prioritize Ethernet traffic on your network. Using simple rules-based policies, administrators can dictate that their networks' switching infrastructures give precedence to Lotus Notes and e-mail traffic rather than to the RealAudio streams that are sucking up all of the bandwidth. This is a real boon for Ethernet technology (see "Bringing Prioritization Services to Ethernet" at www.networkcomputing.com/914/914ws1.html). Yet, while the drafts' advances provide prioritization services to the most popular Layer 2 topology, they do not necessarily provide end-to-end prioritization across your entire network. In particular, 802.1Q and 802.1p won't help you prioritize the Layer 3 IP traffic traveling across your low-speed WAN and ISP connections--the points in your overall infrastructure where bottlenecks usually occur. To handle network congestion across your entire network, you must first provide for the prioritization of IP traffic. Doing this effectively raises a series of design questions. Does your internal network support IP-prioritization services? Does your WAN equipment? What about your Internet service provider? What about the infrastructure at the other end of the connection? If any device between two systems cannot provide IP-prioritization services, you won't be able to implement an end-to-end solution. The Basics of IP Prioritization Unlike Ethernet, IP has had prioritization capabilities ever since version 4 was first published in 1981. Every IP packet has an 8-bit field--called the ToS (Type of Service) byte--that consists of two subfields. These subfields consist of a 3-bit precedence field used for prioritization as well as a 4-bit field for the specific ToS desired by this packet (the remaining bit is unused). By using 3 bits for precedence, IP has the same eight levels of prioritization--0 through 7--as 802.1p, 802.1Q and most of the other LAN topologies. By implementing a cross-mapping service, it becomes feasible to provide a one-to-one mapping between 802.1Q Ethernet frames and the IP precedence, letting you build a network that carries prioritization from one Ethernet LAN to another across an IP-based WAN or ISP connection. Many router vendors say they will be implementing this functionality in the coming months as they roll out their 802.1Q-compliant products. The remaining 4 bits of ToS information let administrators implement per-packet routing based on the characteristics of the packet's data. Thus, an NNTP (Network News Transfer Protocol) packet that carries UseNet news traffic can be marked as a low-cost service, while a telnet packet can be marked as a low-latency service . Originally, only three types of services were defined in RFC 791, the original basis of the IP standard. These services were identified with unique bits that were either on or off, depending on whether the specific ToS was desired. However, this setup was modified by RFC 1349, which added a fourth service to the mix; it also stated that the bits were to be numerically additive rather than distinct entities. Because they were additive, the four bits provided for a maximum of 16 possible values--0 through 15. Network managers handling complex networks with multiple routing paths can use these ToS flags in conjunction with ToS-based routing protocols such as OSPF to provide specific routing services across their networks.
|
|
|
|
The IP-Packet Format and IP Service Options graphics, in Acrobat format.
Slicing Through the Hype of IP Switching March 15, 1998 IPSec For Communities Of Interest April 1, 1998 Casting Off Old Myths With IP Multicast June 1, 1998 AppleShare Plays Nice With Windows August 1, 1998 IPSec-Compliant VPN Solutions: Virtualizing Your Network August 1, 1998  Print This Page E-mail this URL |
 |
||||
Best of the Web
Data deduplication: Declawing the clones
Data deduplication is emerging as a critically important new arrow in the storage administrator's quiver to answer hard questions about the increasing problem in storage growth costs.
Compression, Encryption, Deduplication, and Replication: Strange Bedfellows
One of the great ironies of storage technology is the inverse relationship between efficiency and security: Adding performance or reducing storage requirements almost always results in reducing the confidentiality, integrity, or availability of a system.
WAN Optimization Whitelists and Blacklists
Optimization is a fantastic way of saving money and creating really happy customers at the same time, but it doesn't work flawlessly for all applications.
WAN Optimization as a Managed Service: It's Not About the Cost
This insight examines how organizations outsourcing their WAN optimization initiatives to a third-party go about achieving their goals for application performance, reducing operational costs, and streamlining enterprise infrastructure.
