Y. Bernet, D. Durham, and F. Reichmeyer. Requirements of Diff-serv Boundary Routers. Internet Draft, November 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....(DiffServ) framework [8] supports network quality of service using a simple network core that treats packets belonging to one of a small number of service classes in the same way . Traffic is policed at the entry points to the network according to service level agreements (SLAs) The SLA [8, 7, 3] between the customer (user or another service provider) and the service provider defines the traffic contract and the guarantees that the customer should receive from the network based on the customer s needs and the provider s policies. 10 Simple SLAs require only static enforcement of the ....

Y. Bernet, D. Durham, and F. Reichmeyer. Requirements of Diff-serv Boundary Routers. Internet Draft, November 1998.

....the SLA could be addressed to the BB. B. Traffic Conditioning Traffic conditioning is performed at the boundary node of the DS domain. Traffic conditioning is made based on the TCAs. Traffic conditioning consists of a traffic classifier, marking, metering, and policing shaping, see Figure 3. 11][14] Figure 3. Traffic Conditioning Types Traffic classifier can run in two modes, in a multi flow (MF) classifier mode, or in a bandwidth aggregate (BA) classifier mode. 15] In the MF mode (Fig. 3c) the edge node classifies microflows or traffic streams and marks the DS field according to the ....

....is used for two separate customers then the expanded BA mode (Fig. 3b) is preferable since MF classification is more costly than BA classification. In this case the MF classification granularity is very low. It only differentiates the traffic from the two subnets based on the source IP addresses. [14] The marker sets the DS codepoint (PHB) and thus adds the packet to a particular DS behavior aggregate. 11] A meter measures the rate of the packet stream selected by the classifier against the TCA. The meter indicates to other conditioning functions whether each individual packet is in or ....

[Article contains additional citation context not shown here]

Bernet Y., "Requirements of Diff-serv Boundary Routers", Internet Draft <draft-bernet-diffadge-00.txt>, Microsoft, July 1998

....treat all packets equally. The vigorous interest in quality of service (QoS) issues within the Internet community is evidenced by the rapid development of two IP standards in the last few years the RSVP signaling (IntServ RSVP) approach [6] and the differentiated services (DiffServ) approach [8,9]. Integrated services with RSVP signaling approach attempts to provide per flow QoS assurances with dynamic resource reservation. A flow is defined by the 5 tuple consisting of source IP address, destination IP address, transport protocol, source port, and destination port. In this context, there ....

....on bilateral communication for exchanging policy 10 information between independent domains. This section describes the enforcement of inter domain QoS policies using bilateral mechanisms called bandwidth brokers (BB) 2] and the related network architecture based on policy aware edge devices [9]. Each domain is placed under the administrative control of a bandwidth broker. Adjacent domains negotiate in order to determine the nature and extent of traffic that will traverse across their common boundaries. As part of this process, each domain describes its requested level of service to its ....

Y. Bernet, D. Durham and F. Reichmeyer, Requirements of Diff-serv Boundary Routers. Internet Draft, November, 1998. URL: http://www.ietf.org/internetdrafts /draft-bernet-diffedge-01.txt.

....service classes and their PHB s, a continued focus remains on exploring how various components within the framework can together meet the end to end quality of service requirements of network applications. Towards that end, there have been proposals on the architecture of DiffServ access boxes [DIFFEDGE] as well as discussion of how differentiated services can inter operate with integrated services and signaled quality of service (QoS) DIFFEDGE] RSVPDIFF] Stub Transit Stub Network Network Network Tx ....

....quality of service requirements of network applications. Towards that end, there have been proposals on the architecture of DiffServ access boxes [DIFFEDGE] as well as discussion of how differentiated services can inter operate with integrated services and signaled quality of service (QoS) [DIFFEDGE] [RSVPDIFF] Stub Transit Stub Network Network Network Tx ER1 BR1 BR2 ER2 Rx ....

Y. Bernet, D. Durham and F. Reichmeyer, "Requirements of Diff-Serv Boundary Routers", Internet Draft draft-bernet-diffedge-01.txt, November 1998, Work in progress.

.... between the various DiffServ router types is that in an egress router, we usually have BA classification only while first hop or ingress routers have BA MF classification because they are connected to external customers, which have negotiated SLAs with the provider of the DiffServ domain [11]. Figure 5 shows the architecture of the Assured Service Handler which is an implementation of the three color marking concept [1] Token buckets support the decision, whether the dropping precedence of a packet must be modified before forwarding to the Assured Service queuing system. The High ....

Y. Bernet, D. Durham, and F. Reichmeyer, "Requirements of Diff-Serv Boundary Routers", Internet Draft draft-bernet-diffedge-01.txt, Nov. 1998.

....DS packets. This must include edge routers, and may include other (non edge, or internal) routers. The management of a DS router involves the configuration and control of the various Traffic Conditioning (TC) components within the router. Specific details concerning TC components are included in [DIFFEDGE] and [RFC2475] and are listed here for completeness. TC components include: Internet2 Qbone BB Advisory Council August , 1999 BB Requirements, v 0.7 29 Classifiers Meters Markers Shapers Droppers The data elements required to configure these components is listed in the following ....

Y. Bernet, D. Durham, F. Reichmeyer, Requirements for Diff-serv Boundary Routers, IETF draft-bernet-diffedge-01.txt, November, 1998.

No context found.

Y. Bernet, D. Durham, and F. Reichmeyer. Requirements of Diff-serv Boundary Routers. Internet Draft, November 1998.

No context found.

BERNET, Y., DURHAM, D., AND REICHMEYER, F. Requirements of Diffserv Boundary Routers, draft-bernet-diffedge-01.txt. November 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC