Network Analysis, Architecture and Design, Second Edition (The Morgan Kaufmann Series in Networking)

A mechanism to limit the number of calls on a network and thus control the allocation of resources.

A measure of the system's ability to transfer information (voice, data, video, combinations of these).

A written description of network performance (capacity) required for the flows that are described in the flowspec.

Overengineering bandwidth in the network to accommodate most short- and long-term traffic fluctuations. Also known as traffic engineering.

When all management data (e.g., pings, SNMP polls/ responses, traceroutes) radiate from a single (typically large) management system.

Representing how users and applications use the network to develop and understand their requirements.

Methods to duplicate measurements to verify and validate network management data.

A group of network addresses that are represented by a classless interdomain routing (CIDR) advertisement of the form (network address, mask length).

Applying predetermined mask lengths to addresses to support a range of network sizes. The result is a set of classes of addresses (A, B, C, D, and E), each of which supports a different maximum network size.

The ability to identify traffic flows as part of traffic conditioning.

The absence of class boundaries in network routing.

An architectural model that follows the client-server flow model. In this case there are obvious locations for architectural features, in particular where flows combine.

A flow model in which the flows are asymmetric and hierarchically focused toward the client.

In the distributed-computing flow model, when there are frequent transfers of information between computing devices.

In the distributed-computing flow model, when each task is dedicated to a single computing device.

The characteristics between architectural components (IP services, network management, security and privacy, and addressing and routing) that describe the relationships between these components. These characteristics are operation, interactions, dependencies, trade-offs, and constraints.

Restrictions within a component architecture or between component architectures; can even be across the entire (reference) architecture.

Requirements that one component has on one or more other components in order to function.

The requirements that each component has to communicate with other components.

Determining the mechanisms that make up each component, how each mechanism works, and how that component works as a whole.

Decision points in the development of an architecture to prioritize and choose between features and functions of each component and thereby optimize the overall (reference) architecture.

A combination of requirements from multiple applications, or of individual flows, that share a common link, path, or network.

A measure of the ability of the network to deliver data without error or loss at the design throughput.

For network management, the setting of parameters in a network element for operation and control of that element.

Traffic that is within performance boundaries as determined by metering (traffic conditioning).

When a connection is established by the technology whenever information is transferred across the network.

A network that bypassed the core of the Internet to provide better performance in delivering information to its users.

Flows that are considered more important than others in that they are higher in performance, have strict requirements, or serve more important users, applications, and devices.