Home > Articles

SLA Support in the ISP Environment

Supporting SLAs in ISP environments can be done by means of multiple technologies. One of the possible ways to provide SLA support is by operating different physical networks. Another approach is to use a technology such as DiffServ.

SLA Support by Operating Multiple Networks

When different service levels are implemented as different networks, the structure of the operator's network looks like Figure 4.3. Packets belonging to different service levels are directed to different networks. This function is also known as alternate routing. With this approach, the core network is effectively split into two core subnetworks.

Figure 4.3
Parallel Physical Subnetworks for SLA Support

The responsibility of identifying the correct service level to which a packet belongs and routing it to the corresponding core subnetwork belongs to the access router. The access router is typically the place where many customers connect to the ISP network. The access router needs to classify packets into the different service levels on the basis of any combination of IP and TCP/UDP headers. Some fields that can be included in this combination are the source and destination IP addresses and the protocol field in the IP header, and the source and destination port numbers in the transport header.

The choice of the exact fields that are needed to support SLAs depends on the granularity at which SLAs are defined. Consider the case in which different performance requirements are offered at the granularity of a customer organization (in other words, all traffic from a single customer organization is offered the same performance bounds). In this case, the classification can be done simply on the basis of the source IP addresses of the packets. You can alternatively do the classification on the basis of the adapter on which an incoming packet is received. When each customer organization is mapped to a different service level, it is as if each has a separate intranet of its own. They simply happen to share the same access router.

An alternative approach is to assign different service levels to different applications. Each core subnetwork is used to carry a different set of applications. In this case, the classification of packets would be done using a combination of the IP source and destination addresses and the TCP or UDP port numbers used by the applications.

As an example, consider the case of an enterprise that used to operate a Systems Network Architecture (SNA) network and that has decided to migrate to an IP-based network. The legacy SNA applications are encapsulated in IP using the data-link switching protocol (DLSw). The SLAs for SNA applications typically require a much higher availability. In order to prevent interference among the DLSw traffic and other IP traffic, one of the core networks is used to carry DLSw traffic, and the second core subnetwork is used to carry all other IP traffic. DLSw uses TCP as the transport protocol and typically uses the port numbers 2065 and 2067. The access routers determine the packets that use TCP (the protocol field in the IP header is 6) on ports 2065 or 2067 as source or destination port numbers and direct them to specific core subnetworks.

The identification of applications using only port numbers is best done when applications are run on standard well-known ports or on ports that are used universally within the network. In this case, the port numbers can be used to identify applications. If an application is run on a server at a different port number than the standard one, you have to introduce additional rules specifying the server and the nonstandard port to identify the application. If port numbers are not managed properly, the number of rules required to identify an application can become large.

Running different networks for different service levels has several advantages. Traffic in each service level is insulated from the other traffic. Thus, the idiosyncrasies of one type of traffic do not interfere with the other types of traffic. As an example, voice packets typically happen to be small (less than 100 bytes) and require low jitter in the network. Data packets can potentially be large (a size of 4096 bytes for file transfer is typical). These large packets can cause a significant amount of jitter in the congested nodes. Imagine a voice packet stuck behind a few bulk transfer packets at a queue in the network. Separating the two types of packets into different networks insulates them from each other. This is assuming that the separation point (the access router) is itself not congested and that the interference between the two types of packets at the access router is negligible.

The same arguments hold true for networks that are used to support two different customers' organizations. If a customer requires low delays, its packets can be routed on a subnetwork consisting of faster links. If a customer requires higher availability, you can design a subnetwork that is a more dense mesh of lower-speed links. Other customers can be routed on networks with different characteristics.

The low-level policy issues when running multiple subnetworks relate mostly to the access routers that connect the customer's routers to the different core subnetworks. They have to be configured with the routing rules that direct customers' packets to the right subnetwork. The routers that make up the subnetworks have no significant policy issues to " consider.

SLA Support with DiffServ in the ISP Environment

Although running parallel networks simplifies the task of providing different SLAs, it is a relatively expensive solution. It would be much cheaper to combine the different networks into a single network. If the distinction between the multiple physical networks were mostly related to performance, you could use DiffServ to partition the overall network into two logical ones. Each logical network would be specified by a specific Per-Hop Behavior (PHB) as defined by the DiffServ specification.

The model of supporting different service levels using DiffServ is shown in Figure 4.4. The figure shows two PHBs supported at each link in the network. Assume that one of these PHBs is a higher-priority forwarding class (with a DS field of 110000) and the other one is the default forwarding class (with a DS field of 000000). The physical network is essentially divided into two logical networks sharing the same physical links. Figure 4.4 shows each link as consisting of two virtual sublinks (one of which is shaded and the other is not). Each of the virtual sublinks corresponds to one of the PHBs used within the network. The bandwidth on each link is allocated among the different virtual PHB-based sublinks in a manner determined by the network operator.

Figure 4.4
SLA Support Using DiffServ

Assume that the allocation of bandwidth along the two priority classes shown is done so that 40 percent of each link's capacity is reserved for the higher-priority class, and the other 60 percent is used for default forwarding. In order to ensure that the DiffServ network meets the desired SLAs, the access router and the core routers must perform specific functions.

The various access routers, as shown in Figure 4.4, must perform the following functions in order to obtain a split into two logical networks:

  • Upon receiving a packet, examine the fields in the packet header to determine the packet's service level.

  • Determine the rate limits associated with the specific service level, and enforce those limits.

  • Determine the correct PHB to be used for the service level, and change the Type of Service field in the IP header to the correct code point for the PHB.

  • Keep counters measuring the number of bytes and packets belonging to each service level, and collect any information needed to estimate network performance.

The definition of service levels, how each service level is mapped onto a specific DiffServ header field code point, and the rate limits associated with each service level constitute the low-level policies for the access router supporting the DiffServ function.

Another policy item is the action to be taken on an IP packet when rate limits are exceeded. The packet could be delayed until it conforms with the rate limit, or it could be discarded. If the packet is delayed, it occupies buffers at the access router. The limit on how many buffers can be occupied by packets belonging to a specific service level is also part of the low-level policy for the access router.

The core router needs to implement the queuing behavior that supports the different DiffServ PHBs within the network. Each PHB is associated with a specific scheduling behavior, such as defining the queuing priority level, an absolute limit on bandwidth to be used, or relative ratios in which bandwidth needs to be allocated. The definitions of the priorities, the rate limits, and the action to be taken when the limits are exceeded constitute the low-level policies for the core routers in the network.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020