Friday, June 11, 2010

Providers of Public Networks | Environments

Now we will change gears to describe networks of an entirely different kind. Enterprise networks, covered in the preceding sections, are one factor—possibly a critical one—in the success of a business whose primary purpose is something other than networking. For a public carrier network, the network is the business—sales of network services are the primary source of revenue and the reason why everybody from the CEO to the cable splicer goes to work in the morning. The most obvious effect of this different focus is to considerably raise the stakes as far as network reliability and service quality are concerned. While there are arguably a number of other businesses that rely on telecommunications so directly that their reliability requirements may actually be similar, for a public carrier there is no denying the fact that if the network stops, the inflow of revenue stops too. It’s not possible to just spend an hour cleaning out your inbox while the phones are down! Quality is a sensitive matter as well, because along with price, customer relations, and a few other factors, it inevitably constitutes one of the basic dimensions of competition.
Add a Note HereReliability and quality requirements are among the characteristics that make public network providers stand apart, but they are not the only ones. For the largest public carriers, including the former national monopolies and their largest competitors, scale is obviously another consideration. Public networks may have hundreds or thousands of times as many end users as the very largest enterprise networks. Large scale determines the optimum choice of network architecture as well as approaches to operations and network management.
Add a Note HereRegulatory requirements also come into play for public networks. In many places, in spite of deregulation, there may be specific government-imposed metrics of service quality. Government rules may require that carriers implement certain features, and may prohibit certain classes of carriers from implementing other features. The path to deregulation itself, for example as followed in the United States, has created perhaps arcane-seeming rules about which carriers are allowed to handle which types of calls and what charges may or may not apply to them for purposes such as supporting universal service. Government efforts to open the telecommunications business to competition and foster interconnection have resulted in requirements to support specific types of open interfaces.
Add a Note HereStepping beyond technical requirements and looking at the businesses as a whole, one of the defining characteristics of public carriers as opposed to enterprise networks is that the public carriers have to incur extremely large expenditures in order to convince customers to use their services. Costs may include mass television advertising to consumers or support of large sales forces to stay in touch with the needs of business customers. An effect of these large sales and marketing expenditures is that the cost of the network and its technology, while never unimportant, may figure less in the business decisions of a public carrier than you might think. 
Add a Note HereAt one time there was just one public network provider in each country or major geographical region. Much has changed, of course, and in some places there are hundreds or even thousands of public network providers with the right to compete for business. Technology and changing government regulations have also created different types of carriers, which the following sections attempt to categorize. If you are a planner for a public carrier interested in Internet and telecommunications integration, your company should fit in one or more of the following groups loosely if not perfectly. We hope the discussion will help you think about characteristics of a public network provider that should influence your decision about whether and how to integrate Internet and telecommunications technologies.

Add a Note HereInternet Service Provider (ISP)
Add a Note HereWe will begin our survey of public network providers with one of the newest categories: Internet service providers (ISPs). The Internet service provider industry arose in the early 1990s when the U.S. government began a phased withdrawal of its direct support for the Internet and encouraged commercialization. ISP at the moment is a broad and rapidly evolving category, embracing thousands of firms ranging in size from mom-and-pop operations to some of the largest communications businesses in existence. All ISPs, however, offer services related to the Internet. Most ISPs offer points of presence for flat-rate dialup access to the Internet over local telephone lines, but services may also include providing high-speed private line access, hosting and creation of Web content, caching of Web pages, and providing a variety of proprietary information services.
Add a Note HereISPs tend to arrange themselves into a hierarchy depending on their geographic scope. Local ISPs specialize as the primary point of contact for end-user customers, deliver services, and bill customers. Backbone ISPs haul traffic across continents and around the world. In between there are levels of regional and national ISPs. These categories overlap and combine in all possible ways. For example, backbone providers often have large retail businesses and function as local ISPs as well. Consolidation in the ISP industry seems inevitable and appears to be happening, but it is not clear whether the rate of destruction yet exceeds the rate of creation of new firms.
Add a Note HereThe interest of ISPs in Internet and telecommunications integration comes from two different directions. Local ISPs are critically dependent on the local public telephone network to support dial access for their consumer business. So local ISPs need products to optimize the use of the telephone network for remote access, and technology that provides alternatives to circuit-switched access. ISPs may also be direct providers of IP telephony services. In this role, they may need to provide differentiated quality of service (QoS) over the Internet for telephony applications, and the ability to interconnect the voice over IP (VoIP) traffic with the public telephone network.

Add a Note HereLong Distance and International Carrier
Add a Note HereBy law, custom, or choice, some carriers focus on national long-distance or international traffic. This category includes the U.S. long distance industry created by the breakup of the Bell System some 15 years ago (carriers include AT&T, MCI WorldCom, and Sprint) as well as some others such as KDD, the traditional international carrier of Japan. Regulatory liberalization and business mergers continue to blur boundaries, so these carriers now have local telecommunications interests—some of them quite substantial. Nonetheless, to the degree that they remain focused on long distance and/or international telecommunications, they have common characteristics that shape their needs for Internet and telecommunications integration.
Add a Note HereThe economics of voice over IP can be tricky, but, at least in the near term, the economic payoff is more obviously positive for long distance—and particularly international—traffic than for local calls—due mostly to the artificially high level of some international voice tariffs and the consequent opportunities for arbitrage. The relative lack of local infrastructure also gives these carriers an incentive to seek out new ways of establishing relationships with customers. Offering Internet-based services with less direct dependence on local telephone infrastructures is one way to attract customers. Also, the reduced embedded infrastructure per customer allows long-distance telecom companies flexibility to contemplate radical changes in technology (like using ATM or IP-based networks).
Add a Note HereA final characteristic is that the U.S.-based long distance companies have been in a highly competitive environment for a long time now and attempt to differentiate themselves by developing a wide set of IN-supported vertical services on top of the basic telephone call. Many of these services have been implemented in some form of intelligent network technology—often a proprietary flavor that does not correspond exactly to either the international standards or Telcordia requirements for IN. For carriers with a large embedded base of IN, integration of the Internet with IN is a primary challenge.

Add a Note HereNew Carrier
Add a Note HereNew carriers constitute another broad and flexible category. Here the term refers to carriers whose idea of the path to fortune for their investors is to take a clean sheet of paper and design a completely new network using the latest technology. Often these carriers intend to focus, at least as a first order of business, on long distance and international instead of local telecommunications. This focus has the advantage of reducing somewhat the enormous capital expenditures involved in building a network from scratch. Examples of such carriers are the U.S.-based firms Qwest and Level 3. Similar carriers are developing in Europe as competitors to the former national monopoly providers. Since they are open to the use of new technology, and in fact use it as a key differentiating factor, these carriers actively engage in integrating Internet and telecommunications, including use of such technology as large-scale circuit-to-packet voice gateways.

Add a Note HereIncumbent National Carrier
Add a Note HereIncumbent national carriers include most of the very large embedded telecommunications providers of the world. In most of the places where competition is being introduced into the telecommunications service industry (though not the United States—see the following sections), the former national monopoly carrier is more or less intact as an entity, though often privatized in the sense that its shares are traded on the stock market and its finances are no longer part of the national budget. This description includes giants such as Deutsche Telekom, France Telecom, and British Telecom. (It probably includes NTT of Japan as well, although the regulators in that country have made a halfhearted attempt to separate NTT into two regional subsidiaries for local service plus a long distance subsidiary.)
Add a Note HereGenerally, these incumbent national carriers are highly aware of the Internet as both opportunity and threat, and may be interested in integrating Internet and telecommunications for a number of reasons. First, most have either established or acquired ISPs, and so have the same interests as other ISPs (see the preceding ISP discussion) in efficient dial-up access as well as potential direct provision of IP telephony. Second, most are studying options for evolving part or all of their network infrastructure to be based on IP. Any such evolution, of course, would demand implementations that could operate at extreme scale and deliver services with differentiated QoS characteristics. Although not to the degree of the U.S. long distance carriers, these national carriers typically have implemented value-added services using IN, making the interworking of this IN infrastructure with VoIP an important consideration.

Add a Note HereIncumbent Local Exchange Carrier (United States)
Add a Note HereWhile incumbent local exchange carriers are a unique product of the path taken by regulation and deregulation in the United States, this category includes a number of very large companies, namely the regional Bell operating companies (RBOCs) like Bell Atlantic, SBC, BellSouth, and USWest and, in a rather different regulatory position, GTE. All of these companies have their assets heavily concentrated in local telecommunications, and, in the case of the RBOCs, they are currently still legally restricted in their ability to offer long distance, having just barely begun to overcome the legal hurdles defined in the Telecom Act of 1996. Nonetheless, they are all developing plans for eventual long distance services, and it is partly as potential deployers of substantial amounts of new long distance infrastructure that they loom large in the picture of Internet and telecommunications integration.
Add a Note HereOn the more traditional end of their business—local access—local exchange carriers (LECs) are also interested in providing dial-up access to ISPs. Here, the unusual traffic characteristics presented by dial-up (large volumes of long-holding-time calls, where ISPs serve almost exclusively as terminators rather than originators of calls) have caused the LECs to reengineer their networks, purchase and deploy capacity upgrades to their existing circuit-switched infrastructures sooner than anticipated, and actively seek more technologically advanced solutions. IN interworking with VoIP is also a concern of the LECs; the larger LECs have made significant investments in IN infrastructure, even though a smaller percentage of calls access an IN SCP compared to calls in a U.S. long distance provider’s network.

Add a Note HereCompetitive LEC
Add a Note HereCLECs are the new carriers of the LEC market. What makes them different from the new carriers described earlier is a focus on the local (as opposed to long distance and international) market. Because CLECs are deployers of new infrastructure and competitors in search of a technological edge over the incumbent LECs, integrating Internet and telecommunication has great appeal, although competitive LECs should take a hard look at costs relative to more traditional solutions in their environment.

Add a Note HereCellular/Wireless
Add a Note HereProviders of cellular and wireless communications are having their own experience of spectacular growth, which seems to be continuing unabated. A commonly held belief is that a crossover of wired and wireless access will occur early in the twenty-first century. This means that much VoIP traffic will be wireless voice over IP, which makes wireless a big factor in the integration of Internet and telecommunications technologies. In addition, there is strong interest from consumers and service providers in enabling wireless access to the Internet for Web, e-mail, and similar applications, so that IP voice in a wireless environment is likely to be one component of a multimedia mix.

Add a Note HereCable Network
Add a Note HereCable TV networks have long been recognized as a potential alternative means of access for consumers to communications services that go beyond one-way transmission of TV signals. This potential is finally being actualized due to developments such as the upgrading of cable systems with two-way fiber trunks and the deployment of cable modems. Business moves such as the acquisition of TCI by AT&T are also accelerating developments in this sector. Since second-line voice and Internet access are both key components of the service mix being contemplated by the cable companies, interest in integrating the Internet and telecommunications is natural.

Monday, June 7, 2010

Enterprise Networks | Environments

Enterprise networks are used by businesses to accomplish the everyday functions essential to their success. They are characterized by requirements for features, functionality, and scale that go far beyond typical consumer needs for telecommunications services. Enterprise networks can be very large, spanning the entire globe and operating with multimillion-dollar annual budgets, or they can be much more modest in scale, conforming to the needs of a small business operating in a distinct geographical area.
No matter how large or small, one defining characteristic of an enterprise network is that in almost all cases it is a means to another end. That is, the company that pays for and supports the network is not primarily in the communications business, but rather is in some other business supported by the network. Salespeople make calls to customers and to the home office. Product planners on opposite sides of a continent or an ocean hold weekly conference calls supported by high-quality graphics. A call center takes customer orders or provides support to users of the firm’s products. Remote workers dial in to the company network for e-mail and voice mail. All of these activities are essential to conducting the firm’s business, and some may place critical and demanding requirements on the network, but they are not in themselves the reason why the firm is in business or the sources of its revenue.
The degree to which the network is managed and operated by the firm itself, or to which these functions are outsourced to another company, varies from firm to firm. In the one case, you as the network manager may have a staff of employees that you hire, compensate, and coach in performing tasks to keep the network up and running and expand and extend it to keep pace with user demand. In the other case, you may be primarily responsible for managing the relationship with an outsourcing vendor who in turn performs these tasks. Either way, one of your central concerns is likely to be the costs of network operations, and managing these costs within a budget may be a major function of your job.
Enterprise networks often differ in scale and geographical scope, as mentioned previously. You must consider size and scale when you evaluate your Internet and telecommunications integration needs. Since cost savings is an important goal, it is essential to understand how scale and geographical scope can affect IP telephony costs, including the effects of government regulation in different jurisdictions.
The following sections introduce some possible enterprise network environments. As noted previously, you may find that your own environment is some combination of these, or that it is somewhat different from any of them. Nonetheless, they should provide a framework for thinking about the applicability of Internet and telecommunications integration to your business.

Small Office/Home Office (SOHO)
A SOHO environment can be a small office in a business location, a small office located in a private home, or even a home office setup designed primarily to support a remote worker for a large business. There may be several workers in the office with voice and data communication needs, or there may be just one. In either case, needs for communication within the office are likely to be minimal; the most demanding need is for communication outside the office with customers and suppliers, and, in the remote worker case, with other employees and centralized facilities of the large business. Depending on the nature of the business, the scope of communication may be local, regional, national, or international.
To support voice communications, the most readily available traditional options will be based on switched telephone service from the local telephony provider, possibly augmented by relatively simple premises telephone equipment (an electronic key system or the like) to help manage multiple lines. Connections to Internet service providers (ISPs) or the internal network of a large business can also most readily be supported on a dial-up basis. Depending on the locality, you may have other options such as cable modems or digital subscriber line (DSL) technology.

Medium to Large Business—Single Building or Campus
The medium to large business with a single building or campus category can span locations with less than a dozen to more than 1000 employees. A defining characteristic is a significant need to provide communication among the colocated employees (for example, at an R&D site or large professional office) and/or to manage high-volume incoming or outgoing communications (as at a call center).
Traditionally, voice communications for a single campus location would be handled by a digital private branch exchange (PBX) supported by a substantial in-building twisted pair wiring infrastructure. In a minority of cases (usually governmental organizations or other institutions with a limited ability to raise capital for buying things like PBXs), the same functions may be provided by Centrex service from a telephone company. For call center operations, a special feature of PBX called automatic call distribution (ACD) may be in use, possibly along with computer telephony (CT) capabilities to optimize the flow of calls and connect agents with customer information databases and other information systems. Data communications would be provided by local area network (LAN) technology, probably running over the same twisted pair infrastructure as the telephone system, using networking technology like switches and routers. Depending on the scale of the operation, you may have a hierarchy of departmental and backbone LANs.
Communications outside the building or campus may use a combination of local, regional, national, and international services, depending on the nature of the business. If the building or campus is part of a larger business, a substantial amount of off-premises voice and data traffic may flow over private facilities such as leased circuits or specialized carrier services like software defined networks (primarily for voice) or frame relay service (traditionally for data). Switched business lines from the local telephony provider are available as the ultimate default.

Medium to Large Business—Multiple Campuses
The medium to large business with more than one campus is a generalization of the preceding category. All of the same characteristics are present. The new factor is that there are substantial traffic flows between two or more buildings/campuses. As a result, there will often be significant use of private facilities or specialized carrier services to connect the multiple large locations. Distances between pairs of buildings/campuses, of course, can vary enormously, from a few miles/kilometers to intercontinental distances, and may have a great impact on the specific services available for interconnection as well as on the relative economics of different options.

Medium to Large Business—Single or Multiple Campuses with Small Remote Locations
Many medium to large organizations fall in the category of medium to large businesses with single or multiple campuses with small remote locations. Not only are there possibly multiple large buildings or campuses with substantial traffic flows among them, but there are very important communication flows to and from a relatively large number of small locations. These small locations may be similar in character to the small office/home office environments described previously, or they may be a bit larger, more like the lower end of the single-campus category. All of the communication options described in the preceding two categories may be in place, and in addition the small remote offices present important communication requirements that may need to be satisfied by a combination of switched business lines, specialized carrier services, and, if traffic densities are high enough and the economics work out, leased lines like T1s or cable-based circuits.
The limiting case of the small remote office is probably the single nomadic worker who needs to stay in touch with the business through whatever combination of e-mail, voice mail, and fax he or she can manage. Communications options for this increasingly important case are typically based on dial-up from wired or wireless telephones into corporate voice networks and/or remote access servers for corporate data networks.

Interenterprise Networks and Extranets
All of the preceding categories include some amount of communication between the enterprise in question and other businesses, including suppliers, distributors, and business customers. The default communication mechanism for such communication flows is the public telephone network, whether employed for voice or fax transmission, or maybe the post office, or, in a small but growing number of instances, the public Internet. However, for high-volume transactions between companies that are regular, long-term partners, intercompany private networks or industry-wide jointly managed networks are sometimes employed. Examples are the use of electronic data interchange (EDI) for functions like ordering and invoicing, and electronic funds transfers in the banking industry. Internet technology is often adapted to interenterprise uses in the form of an extranet—an IP-based network that is neither public nor strictly private and that is used by two or more businesses with a long-term relationship.

Thursday, June 3, 2010

Multihoming | Remote Access


One important detail affecting the design of access servers (which, for example, may contain the LAC function) is that their routers are typically located at the borders of enterprise or ISP networks. The servers then act as gateways to their respective networks. Three applications —remote dial-in, VPN, and IP telephony—deal with the IP packets that can traverse more than one network. For this reason, the remote access products that support the VPN service and IP telephony gateways benefit from the implementation of Border Gateway Protocol (BGP) version 4 (RFC 1771).
Add a Note HereAlthough the subject of routing algorithms is outside of the scope, a short discussion of BGP is warranted. You may notice that some issues (such as policing) inherent in BGP are very similar to—and, in some cases, even the same as—those pertinent to the QoS standards addressed. BGP is the means of realizing multihoming (that is, maintenance of connections to multiple ISPs or enterprise networks). Thus, BGP is of considerable importance to dial-in access and VPN applications. The IETF has paid much attention to the BGP development, which dates back to ARPANET and then was pursued in the Inter-Domain Routing (idr) working group (www.ietf.org/html.charters/idr-charter.html ) over several years. Four versions of BGP have been released. In the latest series of RFCs, RFCs 1771 and 1772 have achieved the status of Draft Standards. Informational RFCs 1773 and 1774, respectively, document experiences with BGP-4 and provide an analysis.
Add a Note HereRFC 1771 defines an autonomous system (AS) as “a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASs.” ISPs and enterprise networks are two typical examples of ASs.
Add a Note HereWhereas interior nodes are concerned with making the best effort at delivering IP packets, exterior nodes have to deal with many other tasks. One task is to decide whether certain packets should be admitted to the AS; the other is to maintain the appearance of a coherent interior routing plan (which is not necessarily the case in practice). As RFC 1771 says: “The use of the term Autonomous System here stresses the fact that, even when multiple IGPs and metrics are used, the administration of an AS appears to other ASs to have a single coherent interior routing plan and presents a consistent picture of what destinations are reachable through it.”
Add a Note HereThere are two aspects to packet admission: Some packets may actually be destined to terminate in the AS, whereas others should be allowed to traverse it in order to get to other ASs.
Add a Note HereIn the world of the exterior nodes, which is significantly cozier than the world of all routers—if only because it is much smaller—the ASs are somewhat selfishly viewed as the means of connecting the exterior nodes. As far as transit through ASs is concerned, BGP provides the following taxonomy (illustrated in Figure 1):

§  Add a Note HereStub AS. An AS that has only a single connection to one other AS. Naturally, a stub AS only carries local traffic.
§  Add a Note HereMultihomed AS. An AS that has connections to more than one other AS, but refuses to carry transit traffic.
§  Add a Note HereTransit AS. An AS that has connections to more than one other AS and is designed (under certain policy restrictions) to carry both transit and local traffic.


Figure 1: The AS classification.
Add a Note Here
Add a Note HereStub and multihomed ASs do not need to employ BGP at their border nodes, but transit ASs do. The responsibilities of the border gateways involve, among other things, policing the incoming traffic.
Add a Note HereThis situation is strikingly similar to what used to happen at the borders of the Iron Curtain countries in Europe before the fall of the Curtain. In particular, the German Democratic Republic—the former East Germany—which had a piece of the free world (West Berlin) within its territory, was well equipped for dealing with transit traffic at its borders, where the cars queued up amid many uniformed men and women with automatic rifles and barking dogs. Unless all present in a car were citizens of East Germany or had prearranged visas for visiting specific places in the country, they were issued—for a fee—time-stamped transit visas that indicated a particular border point at which the car had to exit the country. The choice of destination border point belonged to the driver, but could not be changed once it was written in the visa. Furthermore, the car was supposed to reach its destination border point by (1) always staying on the East German highway network, (2) following the shortest path through this network, and (3) obeying all the laws of the country, which in this case were of course effectively reduced to the traffic laws. With that, the car was virtually tunneled through the country, its passengers seeing not much more than other cars and trucks—including many police cars—and vast fields on both sides of the highway. At the destination border checkpoint, more armed men and women with dogs were waiting. One of the many checks they performed was that of the initial time stamp. If the elapsed time indicated that the car had clearly spent more time in the country than it would have had it taken the shortest path, some specific policies applied, with the actual consequences (fines? imprisonment?) fortunately unknown to these authors. Another—and, alas, often unexpected—effect of time-stamping was discovered by those drivers whose traveling time was too short for the distance, which was a clear proof of speeding. The offense was punished by a large on-the-spot fine to be paid in cash and in hard currency. The latter policy example, however, is more illustrative of QoS rather than border gateway policies.
Add a Note HerePolicy-based routing is an essential job of the routers that serve as border gateways. Policy specification is a job of network administrators rather than of the protocol itself, but BGP routers do make routing decisions based on these policies.
Add a Note HereIn a deviation from other Internet routing protocols, BGP uses TCP (instead of a link layer protocol) as a reliable data transport for routing messages. The actual routing algorithm belongs to the so-called distance vector routing family, which operates by maintaining within each router a table of distances (costs) to all reachable routers and exchanging this information with other routers. The most lamented deficiency of the distance vector routing is that the “bad news,” (that is, loss of a link between two routers or router flop) propagates through the network extremely slowly. BGP differs from other distance vector routing protocols in that the routers maintain—and share with one another—full paths to the nodes reachable from them. That fixes the problem of spreading the bad news, because the routers notice all the nodes disappearing from neighbors’ paths as soon as they get the change information. Note that being reachable is not simply a matter of connectivity but also of active policies.
Add a Note HereIn an example of RFC 1772, a multihomed AS may actually act as a transit AS for some ASs by advertising to them paths to foreign gateways; on the other hand, a transit AS may restrict access to some ASs by never advertising paths to them (that is, declaring them unreachable). In the example of Figure 2, AS D is reachable to AS A through AS C, but AS B is not.


Figure 2: Access restriction.
Add a Note Here
Add a Note HereInitially, a BGP router sends its whole routing table to its neighbors, which are supposed to keep it until the connection is closed because from now on they will receive only incremental updates. Even though TCP is used for transport, BGP still uses its own KeepAlive messages to ensure that the connection is open. The connection is closed whenever an error condition (such as nonreception of KeepAlive messages) is encountered. In addition to incremental updates, BGP-4 has added the concept of route aggregation so that information about groups of networks may be represented as a single entity.
Add a Note HereBGP-4 has also addressed the problems of (1) the exhaustion of class B address space and (2) threatening growth of the routing tables. In listing the differences between BGP-4 and previous versions of BGP, RFC 1771 notes: “BGP-4 is capable of operating in an environment where a set of reachable destinations may be expressed via a single IP prefix. The concept of network classes, or subnetting, is foreign to BGP-4. . . . New text has been added to define semantics associated with IP prefixes.”

Saturday, May 29, 2010

Internet Protocol Security (IPsec)

The work on the IP security suite protocol (IPsec) is carried out in the ipsec working group (www.ietf.org/html.charters/ipsec-charter.html) in the security area of the IETF. We strongly recommend Kaufman and Newman (1999) if you would like a detailed treatment of the subject and its business applications.
Add a Note HereRFC 2401 defines the design goal of the IP security (IPsec) protocol as the means to provision interoperable, high-quality, cryptography-based security for both versions of IP protocol—IPv4 and IPv6. In a nutshell, the IPsec suite provides privacy (through encryption) and authentication services at the IP layer (which, among other things, means that application and transport security as well as data link layer security are outside of the scope of the IPsec suite). The services provided by the suite include access control, connectionless integrity, confidentiality, and protection against replays (that is, reuse of snooped messages).
Add a Note HereTo provide these services, first, two traffic security protocols are defined:

§  Add a Note HereAuthentication Header (AH) (RFC 2402). Provides connectionless integrity, data origin authentication, and an (optional) antireplay service.
§  Add a Note HereEncapsulating Security Payload (ESP) (RFC 2406). Provides one of the two sets of services:
1.  Add a Note HereConfidentiality and limited traffic flow confidentiality.
2.  Add a Note HereIntegrity, data origin authentication, and an antireplay service.
Add a Note HereEach of these protocols can be used in either transport mode (where transport protocols are protected) or tunnel mode (where the IP itself is protected). Tunnel mode is particularly important to VPN services in connection with IPIP (RFC 2003).
Add a Note HereSecond, algorithms for encryption and authentication as well as automatic key management schemes (such as RFC 2408 and RFC 2409) are defined, each in a separate RFC. The informational RFC 2411 provides guidelines for specifying new encryption and authentication algorithms and explains the interrelationship of all the protocols and algorithms in the IPsec suite.
Add a Note HereThe interrelationship of the elements of the IPsec architecture is demonstrated in Figure 1. The ESP and AH protocol documents cover the packet format and general issues of these protocols. They also define the default and mandatory values (as, for example, specified in RFC 2407) that are fed into the domain of interpretation (DOI) document, which deals with assigned values. The ESP protocols can use various encryption algorithms (for example, those specified by RFC 2405 and RFC 2451) as well as authentication algorithms (for example, those specified by RFC 2403 and RFC 2404). The authentication algorithms are also used by the AH protocol.


Figure 1: IPsec architecture.
Add a Note Here
Source: RFC 2411.

Add a Note HereBoth the encryption and authentication algorithms may also specify values for the DOI (for example, the values that identify these algorithms). Finally, the key management documents specify the IETF standards-track key management schemes, which also define the values for DOI. The IPsec DOI also supports negotiation of IP compression (as specified in RFC 2393); this function may be necessary because the encryption of IP payload prevents compression at lower layers. For example, a message containing a string of 50 octets filled with 0s could have been successfully compressed to something much smaller than 50 octets had it not been for the encryption, which—by design—not only changed 0s to other values but also eliminated the pattern.
Add a Note HereOverall, IPsec provides security services at the IP layer by selecting (1) appropriate security protocols, (2) algorithms to be used with these protocols, and (3) appropriate cryptographic keys. The major function of the Internet Key Exchange (IKE) protocol (RFC 2409) is to establish and manage security associations (SAs), a function supported by both AH and ESP.
Add a Note HereThe concept of SAs is fundamental to IPsec. RFC 2401 defines an SA as a simplex connection that affords security services to the traffic carried by it. These services can be afforded by either AH or ESP, but in the case where both are to be employed, two SAs need to be established. An SA is uniquely identified by the following triplet:
1.  Add a Note HereSecurity parameter index (SPI).
2.  Add a Note HereIP destination address. Although this can in principle also be a broadcast or multicast address, only the unicast address is presently supported by the IPsec management mechanism.
3.  Add a Note HereSecurity protocol identifier (that is, AH or ESP).
Add a Note HereRFC 2401 defines two types of SAs—transport mode SA and tunnel mode SA—to support the AH and ESP modes of operation, respectively. As Figure 2 demonstrates, the transport mode SA is an association between two hosts. The double arrows are used only to indicate the nodes between which the SAs are established, not to imply by any means that that the SAs are duplex! The tunnel mode SA, however, may be established between:
§  Add a Note HereTwo security gateways. A security gateway is defined in RFC 2401 as an intermediate system that acts as the communications interface between two networks.
§  Add a Note HereA host and a security gateway.
§  Add a Note HereTwo hosts.

Figure 2: Two types of security associations (SAs).
Add a Note Here
Add a Note HereAny SA that supports tunneling (that is, an SA between a host and a security gateway or two security gateways) must be a tunnel mode SA, but an SA between two hosts may be either a transport mode SA or tunnel mode SA. The modes define the order and selection of appropriate headers. RFC 2401 provides several interesting examples of how SAs can be combined to satisfy complex, nesting security policies, and introduces into the model the notions of the security policy database (which specifies the policies that determine the disposition of IP traffic) and the security association database (which specifies the parameters of each active SA). Finally, RFC 2401 studies four cases of security associations, of which the fourth—depicted in Figure 3—is specifically relevant to the topic of dial-in access to an enterprise network. 

Figure 3: Remote host reaching an enterprise server.
Add a Note Here
Source: RFC 2401, Case 4.

Add a Note HereIn Figure 3, a remote host (dialing into an access concentrator) uses the Internet to reach an enterprise’s firewall (a security gateway) and then a particular host (a server). Only tunnel mode is required for an SA between the remote host and the firewall, while an SA between the remote host and the server can be either a transport or tunnel mode SA.
Add a Note HereWe have mentioned how IPsec standards relate to access and, particularly, VPNs, but so far we have not said anything about IPsec’s relation to IP telephony. The general feeling in the IP telephony community[2] is that AH and ESP can be used in a standalone IP telephone, but the complexities of key exchange through IKE and the Internet Security Association and Key Management Protocol (ISAKMP) are too much to be handled by a client in a small standalone telephone.
Add a Note HereKaufman and Newman (1999) report that “early generations of IPsec products have proven to be suboptimal for many VoIP installations” and recommend deploying IPsec and voice over Internet Protocol (VoIP) separately and “experiment[ing] with integration only when you have debugged both installations.” In addition to technical reasons, the same monograph brings up an important regulatory consideration: In some circumstances, there are regulations that restrict voice encryption.