Aggregation of Diffserv Service Classes

Babiarz, Jozef; Baker, Fred; Chan, K.

doi:10.17487/rfc5127

Cited by 26 publications

(21 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The choice of which DSCP is most suitable for a given PCN-domain is dependent on the nature of the traffic entering that domain and the link rates of all the links making up that domain. In PCN-domains with sufficient aggregation, the appropriate DSCPs would currently be those for the Real-Time Treatment Aggregate [RFC5127]. It is suggested that admission control could be used for the following service classes (defined in [RFC4594] CS5 is excluded from this list since PCN is not expected to be applied to signalling traffic.…”

Section: Appendix a Choice Of Suitable Dscpsmentioning

confidence: 99%

Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)

Moncaster¹,

Menth²,

Briscoe³

2012

View full text Add to dashboard Cite

The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. The overall rate of PCN-traffic is metered on every link in the PCNdomain, and PCN-packets are appropriately marked when certain configured rates are exceeded. Egress nodes pass information about these PCN-marks to Decision Points that then decide whether to admit or block new flow requests or to terminate some already admitted flows during serious pre-congestion.

show abstract

Section: Appendix a Choice Of Suitable Dscpsmentioning

confidence: 99%

Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)

Moncaster¹,

Menth²,

Briscoe³

2012

View full text Add to dashboard Cite

show abstract

“…The choice of which DSCP is most suitable for a given PCN-domain is dependent on the nature of the traffic entering that domain and the link rates of all the links making up that domain. In PCN-domains with sufficient aggregation, the appropriate DSCPs would currently be those for the Real-Time Treatment Aggregate [RFC5127]. The PCN working group suggests using admission control for the following service classes (defined in [RFC4594] CS5 is excluded from this list since PCN is not expected to be applied to signalling traffic.…”

Section: A1 Choice Of Suitable Dscpsmentioning

confidence: 99%

Baseline Encoding and Transport of Pre-Congestion Information

Moncaster¹,

Menth²,

Briscoe³

2009

View full text Add to dashboard Cite

The objective of the Pre-Congestion Notification (PCN) architecture is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. It achieves this by marking packets belonging to PCN-flows when the rate of traffic exceeds certain configured thresholds on links in the domain. These marks can then be evaluated to determine how close the domain is to being congested. This document specifies how such marks are encoded into the IP header by redefining the Explicit Congestion Notification (ECN) codepoints within such domains. The baseline encoding described here provides only two PCN encoding states: Not-marked and PCN-marked. Future extensions to this encoding may be needed in order to provide more than one level of marking severity.

show abstract

“…In the past few years, work on the Internet Protocol for providing QoS has resulted in two dominant models, i.e., the Integrated Services (IntServ) [1] and the Differentiated Services (DiffServ) [2] models. IntServ tries to provide hard QoS guarantees on a per flow basis, to which end it uses the signaling protocol known as the Resource Reservation Protocol (RSVP).…”

Section: Related Workmentioning

confidence: 99%

“…DiffServ [2] was invented to circumvent the scalability problem of IntServ by providing QoS provisioning on class based granularity. The DiffServ model has defined three main types of traffic classes: Expedited Forwarding (EF) [4]; Assured Forwarding (AF) [5]; and best effort forwarding.…”

Section: Related Workmentioning

confidence: 99%

Differentiated Services Based Admission Control and Multi Path Routing Algorithm for IPv6

Farooq¹,

Aziz²

2009

Journal of Information Processing Systems

View full text Add to dashboard Cite

Abstract:In this paper we propose a Differentiated Services Based Admission Control and Routing Algorithm for IPv6 (ACMRA). The basic DiffServ architecture lacks an admission control mechanism, the injection of more QoS sensitive traffic into the network can cause congestion at the core of the network. Our Differentiated Services Based Admission Control and Routing Algorithm for IPv6 combines the admission control phase with the route finding phase, and our routing protocol has been designed in a way to work alongside DiffServ based networks. The Differentiated Services Based Admission Control and Routing Algorithm for IPv6 constructs label switched paths in order to provide rigorous QoS provisioning. We have conducted extensive simulations to validate the effectiveness and efficiency of our proposed admission control and routing algorithm. Simulation Results show that the Differentiated Services Based Admission Control and Routing Algorithm for IPv6 provides an excellent packet delivery ratio, reduces the control packets' overhead, and makes use of the resources present on multiple paths to the destination network, while almost each admitted flow shows compliance with its Service Level Agreement.

show abstract

Aggregation of Diffserv Service Classes

Cited by 26 publications

References 9 publications

Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)

Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)

Baseline Encoding and Transport of Pre-Congestion Information

Differentiated Services Based Admission Control and Multi Path Routing Algorithm for IPv6

Contact Info

Product

Resources

About