An Informal Management Model for Diffserv Routers

Bernet, Yoram; Blake, Steven; Grossman, Dan; Smith, Alan

doi:10.17487/rfc3290

Cited by 90 publications

(43 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Such measurement procedures are collectively referred to as "traffic conditioners". Traffic conditioners are normally built using token bucket meters, for example with a committed rate and burst size, as in Section 1.5.3 of the DiffServ Model [RFC3290]. The Assured Forwarding PHB [RFC2597] uses a variation on a meter with multiple rate and burst size measurements to test and identify multiple levels of conformance.…”

Section: Traffic Conditioningmentioning

confidence: 99%

Configuration Guidelines for DiffServ Service Classes

Chan¹,

Babiarz²,

Baker³

2006

210

170

View full text Add to dashboard Cite

Section: Traffic Conditioningmentioning

confidence: 99%

Configuration Guidelines for DiffServ Service Classes

Chan¹,

Babiarz²,

Baker³

2006

210

170

View full text Add to dashboard Cite

“…Routers implementing this specification MUST implement at least the default algorithm, which is based on the original arrival rates of the buffered packets. A maximum of 5 packets MAY be sent one after another, but all subsequent packets SHOULD use a sending rate that is determined by metering the rate at which packets have entered the buffer, potentially using smoothing techniques such as recent activity over a sliding time window and weighted averages [RFC3290]. Duplicate Address Detection (DAD) was defined in [RFC4862] to avoid address duplication on links when stateless address autoconfiguration is used.…”

Section: Koodli Standards Track [Page 17]mentioning

confidence: 99%

Mobile IPv6 Fast Handovers

2009

134

View full text Add to dashboard Cite

Mobile IPv6 enables a mobile node (MN) to maintain its connectivity to the Internet when moving from one Access Router to another, a process referred to as handover. During handover, there is a period during which the mobile node is unable to send or receive packets because of link-switching delay and IP protocol operations. This "handover latency" resulting from standard Mobile IPv6 procedures (namely, movement detection, new Care-of Address configuration, and Binding Update) is often unacceptable to real-time traffic such as Voice over IP (VoIP). Reducing the handover latency could be beneficial to non-real-time, throughput-sensitive applications as well. This document specifies a protocol to improve handover latency due to Mobile IPv6 procedures. This document does not address improving the link-switching latency.This document updates the packet formats for the Handover Initiate (HI) and Handover Acknowledge (HAck) messages to the Mobility Header Type.

show abstract

“…It also discusses how to set up the main entities in a typical DiffServ network to achieve the required service levels. The IETF DiffServ WG has also worked on standardizing a management information base (MIB) [68] for DiffServ devices and policy information base (PIB) [69] for policy management in accordance with the informal model for DiffServ routers [66]. These models are necessary for setting up policies and managing large DS domains.…”

Section: ) Per-domain Behavior (Pdb)mentioning

confidence: 99%

Evolution of the internet QoS and support for soft real-time applications

2003

View full text Add to dashboard Cite

I. INTERNET QUALITY OF SERVICEReal-time networked applications depend on network parameters such as bandwidth, delay, jitter (interpacket delay variation), and loss for their correct operation. The degree of tolerance or sensitivity to each of these parameters varies widely from one application to another. Critical applications, such as remote surgery and online trading systems, require reliability of such parameters as well as guaranteed delivery. Emerging applications such as home networking, intelligent appliances, factory supply-chain networks, as well as the vast majority of multimedia applications also require different levels of service quality from the underlying network in terms of these parameters. In traditional circuit-switched networks such as the telephone system, the quality of a connection can be measured and guaranteed in terms of connection setup delays, media quality (e.g., voice or video quality), and trunk availability. On the other hand, packet-switched networks, such as the current Internet, were not designed to provide per-connection service guarantees. As a result, packets of a particular flow can reach their destination via different paths and experience different amounts of delay, jitter, and loss along the way. This is a critical problem on the current Internet as more and more applications, originally developed for circuit-switched networks, are being migrated onto the Internet.The current Internet architecture is based on the "best-effort" service model, which has worked well for traditional applications such as e-mail, file transfer protocol (FTP), telnet, and hypertext transfer protocol (HTTP). Most of these applications are based on the transmission control protocol (TCP) suite, which provides reliable data delivery service without guaranteeing any delay and jitter bounds. On the other hand, supporting real-time and business-critical applications over a wide-area network requires classification of the application traffic and service-level guarantees from the underlying network for each class of traffic based on a number of factors. A number of proposals have been put forward to enhance the reliability and efficiency of the current Internet. A major objective of these proposals is to provide multiple service classes for either individual flows or flow aggregates with a quality that is suitable for these flows. Once implemented, such service classes will enable

show abstract

An Informal Management Model for Diffserv Routers

Abstract: Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Cited by 90 publications

References 0 publications

Configuration Guidelines for DiffServ Service Classes

Configuration Guidelines for DiffServ Service Classes

Mobile IPv6 Fast Handovers

Evolution of the internet QoS and support for soft real-time applications

Contact Info

Product

Resources

About