1. Dynamic Management for End-to-end IP QoS
From Best-effort to Personalized Services
Fayçal Bennani & Noëmie Simoni
ENST
TNC Lisbon, 23 May 2000.

2. Problematic From best-effort to multi forwarding service
From connectionless to tunneling
From per-hop to end-to-end services
From user’s flow to CoS flow
From best-effort to personalized services.
TNC Lisbon, 23 May 2000.

3. Content Problematic QoS in IP: today’s solutions QoS in IP: key points
Components to support QoS
Proposition of management components
Dynamic management for end-to-end IP QoS: a solution in five models
Conclusion
TNC Lisbon, 23 May 2000.

4. QoS in IP: today's solutions
Topology-based systems:
IP over ATM,
MPLS,
Flow-oriented solutions:
IntServ,
DiffServ.
TNC Lisbon, 23 May 2000.

5. QoS in IP: today's solutions IP over ATM
On-demand VCs with specific QoS
Various traffic classes:
CBR,
rt-VBR,
nrt-VBR,
ABR,
UBR.
TNC Lisbon, 23 May 2000.

6. QoS in IP: today's solutions MPLS
Traffic aggregates are associated with LSPs (Label-Switched Path)
The label used for switching is associated with a FEC (Forwarding Equivalent Class)
TNC Lisbon, 23 May 2000.

7. QoS in IP: today's solutions IntServ
QoS per individual flow: each application makes a reservation request for the resources it needs.
Use of signaling protocols (RSVP)
Issue of scalability
TNC Lisbon, 23 May 2000.

8. QoS in IP: today's solutions DiffServ
The DiffServ architecture defines service classes based on a classification of flows.
Repartition among edge and core devices:
peripheral nodes set the DSCP,
core nodes implement PHBs (Per-Hop Behavior) to deliver a differentiated service at the node output: (default (best effort), expedited forwarding (EF), assured forwarding (AF))
TNC Lisbon, 23 May 2000.

9. QoS in IP : key points CoS flow
A set of transfer units considered related to each others.
Packets are considered to belong to a same flow according to quantitative observations, like:
being generated by the same user,
being generated by the same application,
coming from the same originating network,
having the same destination,
requiring the same CoS.
TNC Lisbon, 23 May 2000.

10. QoS in IP: key points Per-domain organization
Domain A
Domain C
Domain B
TNC Lisbon, 23 May 2000.

11. Architectural Components to support QoS
LAN
WAN
Conditionner:
Metering
Dropping
Remarking
Contrat verification
Conditionner:
Shaping
Formating
Identification,
QoS selection
Classifier:
BA, MF
Queuing
Access and congestion management
Scheduling
TNC Lisbon, 23 May 2000.

12. Proposition of dynamic management components
Control Plane
Management Plane
Mapping
Few ms to few sec
Few sec to few min
Hours / Days
Days / Weeks
Renegotiations
Notifications
Traffic engineering
Monitoring analysis
UMD
Policy (COPS)
Signaling (RSVP)
Negotiation
Time
less than a ms
User Plane
Buffering
Conditioning
Classification
Congestion control
Retransmissions
TNC Lisbon, 23 May 2000.

13. Dynamic Management for End-to-end QoS: a solution in five models
TNC Lisbon, 23 May 2000.

14. Management organizational modelBM QB
Domain A
Domain C
Domain B
TNC Lisbon, 23 May 2000.

15. Functional Model Negotiation function Mapping function
Re-negotiation function
TNC Lisbon, 23 May 2000.

16. Architectural Model
Notifications and monitoring between a core router and its QB,
Notifications from QBs to the BM,
Anticipation strategy made by the BM
may include routing tables updates,
monitoring needed to evaluate the long term impact of the strategic anticipations made by the BM.
TNC Lisbon, 23 May 2000.

17. Relational Model
How to make relations among the various components that cooperate to grant and maintain an end-to-end QoS ?
In-band communication:
OAM flows
MPLS with its Label Distribution Protocol (LDP)
Out-band alternatives:
TMN compliant architectures (SNMP, CMIP)
TNC Lisbon, 23 May 2000.

18. Informational model: QoS
Informs about a contract
QoS evaluation through generic criteria
Requested QoS must be mapped to CoSs
Significant parameters of each visibility level
Flow characterization is domain dependent.
TNC Lisbon, 23 May 2000.

19. Conclusion QoS-enabling components time Vs planes classification
Interconnection units perform renegotiations and mapping functions
A distributed management between QBs, BM and boundary nodes.
TNC Lisbon, 23 May 2000.

20. Perspectives
Development of managing objects (for mapping and renegotiations).
Investigation of potential enhancements with new technologies
TNC Lisbon, 23 May 2000.

21. Thank you.
TNC Lisbon, 23 May 2000.