Differentiated Services Quality of Service Policy Information Base

Chan, K.; Sahita, Ravi; Hahn, Scott; McCloghrie, K.

doi:10.17487/rfc3317

Cited by 49 publications

(12 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, the strategy for defining the policy model and the implementation framework differs in some important aspects. Considering the vendors efforts to follow the recent IETF standards, translating business level policies to a diffserv PIB [11], and distributing the configuration information using the COPS-PR [5] protocol is certainly a logical approach for a QoS management tool. None of the works reviewed in this section follows this approach altogether.…”

Section: Related Work and Discussionmentioning

confidence: 99%

“…The DLPC "existence" is conceptually defined by the IETF framework, in the provisioning approach. The device-dependent configuration is expressed in terms of a diffserv PIB, which general structure is defined by the IETF [11]. Because network devices can support different mechanisms for implementing diffserv actions, the DLPC must also receive the "device capabilities" as an input parameter.…”

Section: Related Work and Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Defining Reusable Business-Level QoS Policies for DiffServ

2004

View full text Add to dashboard Cite

Abstract. This paper proposes a PBNM (Policy Based Network Management) framework for automating the process of generating and distributing DiffServ configuration to network devices. The framework is based on IETF standards, and proposes a new business level policy model for simplifying the process of defining QoS policies. The framework is defined in three layers: a business level policy model (based on a IETF PCIM extension), a device independent policy model (based on a IETF QPIM extension) and a device dependent policy model (based on the IETF diffserv PIB definition). The paper illustrates the use of the framework by mapping the information models to XML documents. The XML mapped information model supports the reuse of rules, conditions and network information by using XPointer references.

show abstract

Section: Related Work and Discussionmentioning

confidence: 99%

Section: Related Work and Discussionmentioning

confidence: 99%

Defining Reusable Business-Level QoS Policies for DiffServ

2004

View full text Add to dashboard Cite

show abstract

“…That is, if the CE attempts to instruct the FE to set up some specific behavior it cannot support, the FE will return an error indicating the problem. Examples of similar approaches include Diffserv PIB RFC 3317 [RFC3317] and framework PIB RFC 3318 [RFC3318].…”

Section: Fe Capability Model and State Modelmentioning

confidence: 99%

Forwarding and Control Element Separation (ForCES) Forwarding Element Model

Halpern¹

2010

View full text Add to dashboard Cite

This document defines the forwarding element (FE) model used in the Forwarding and Control Element Separation (ForCES) protocol. The model represents the capabilities, state, and configuration of forwarding elements within the context of the ForCES protocol, so that control elements (CEs) can control the FEs accordingly. More specifically, the model describes the logical functions that are present in an FE, what capabilities these functions support, and how these functions are or can be interconnected. This FE model is intended to satisfy the model requirements specified in RFC 3654. Status of This Memo This is an Internet Standards Track document.This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5812.

show abstract

“…There are many options for conveying the MPEG-7 motion activity descriptor to the network nodes. For instance, the motion activity could be carried as differentiated services (DiffServ) code points in the individual packets [26]. Another option could be to convey the motion activity level in real-time control protocol (RTCP) packets [27] to the intermediate nodes.…”

Section: Prioritization Of Video Packetsmentioning

confidence: 99%

Adaptive Video Transmission Schemes Using MPEG-7 Motion Intensity Descriptor

Lotfallah

Reisslein

Panchanathan

2006

IEEE Trans. Circuits Syst. Video Technol.

View full text Add to dashboard Cite

Abstract-A variety of error resilience and scalable coding techniques have recently been proposed to facilitate the delivery of video over best-effort networks; a common drawback of these techniques is reduced compression efficiency. Also, MPEG-7 descriptors have recently been developed for the purpose of indexing. In this paper, we propose to employ MPEG-7 descriptors to improve the quality of the video delivered over best-effort networks. In particular, we propose a video transmission system that uses the motion activity descriptors to ensure robust video transmission. A novel motion activity extraction technique is proposed, which relies on a neural network approach. By considering several low-level visual features, our proposed extraction approach achieves high consistency with subjective evaluations of motion activities. In order to demonstrate the benefits of the proposed transmission system, we develop a selective packet dropping scheme that can be applied in case of network congestion. Simulations demonstrate that the reconstruction quality of the proposed congestion scheme can surpass conventional schemes by 1.2 dB. The network performance of the proposed transmission system when video sequences are coded into single layer or scalable layers is presented. We also present a transcoding scheme that achieves the optimal reconstructed quality by exploiting the motion activities of the underlying video sequence.

show abstract

Differentiated Services Quality of Service Policy Information Base

Cited by 49 publications

References 21 publications

Defining Reusable Business-Level QoS Policies for DiffServ

Defining Reusable Business-Level QoS Policies for DiffServ

Forwarding and Control Element Separation (ForCES) Forwarding Element Model

Adaptive Video Transmission Schemes Using MPEG-7 Motion Intensity Descriptor

Contact Info

Product

Resources

About