2006
DOI: 10.17487/rfc4594
|View full text |Cite
|
Sign up to set email alerts
|

Configuration Guidelines for DiffServ Service Classes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

2
170
0
1

Year Published

2006
2006
2017
2017

Publication Types

Select...
4
4
2

Relationship

0
10

Authors

Journals

citations
Cited by 210 publications
(180 citation statements)
references
References 23 publications
2
170
0
1
Order By: Relevance
“…This traffic should be forwarded with a PHB that is appropriate for transiting NC service class traffic [RFC4594] in the receiving domain, e.g., AF31 as specified by this document. As an example, GSMA IR.34 recommends an Interactive class / AF31 to carry SIP and DIAMETER traffic.…”
Section: Treatment Of Network Control Traffic At Carrier Interconnectmentioning
confidence: 99%
“…This traffic should be forwarded with a PHB that is appropriate for transiting NC service class traffic [RFC4594] in the receiving domain, e.g., AF31 as specified by this document. As an example, GSMA IR.34 recommends an Interactive class / AF31 to carry SIP and DIAMETER traffic.…”
Section: Treatment Of Network Control Traffic At Carrier Interconnectmentioning
confidence: 99%
“…Services are categorized by relating them to a type of SLS [16,17]. According to recommendations from [18], ITU Y.1541 and 3GPP standards, current service types include: real-time services, multimedia services, data services, and default traffic service.…”
Section: Multiservice Network Ontologymentioning
confidence: 99%
“…In each network along the end-to-end heterogeneous session path, flows of multi-user sessions with similar QoS requirements must be mapped into the appropriated service class. However, static approaches of QoS mapping between session requirements and network service classes or even guidelines for IP QoS mapping [2] alone, are not sufficient to assure the quality level of sessions. This is mainly due to the emergence of sessions with new QoS requirements and QoS models with different configurations and classes of service.…”
Section: Introductionmentioning
confidence: 99%