Controlled Load Service QoS Model

draft-kappler-nsis-controlledload-qosm-03.txt

Cornelia Kappler, Xiaoming Fu(Robert Hancock presenting)

IETF#65 – DallasMarch 2006

Overview

Goals Controlled load service QoSM Draft Updates Open Issues Next steps

Goals NSIS base protocol suite is in final stages Controlled-load service: a light-weight per-

flow reservation model Much simpler than guaranteed service A useful example for NSIS deployment especially

in access networks CLS QoSM is about:

How to interpret QoS parameters in conjunction with NSIS QoS signaling in a way which replicates RSVP/IntServ behaviour

CLS QoS Model

Token bucket parameters QSPEC control information

MTU not included As per Interim meeting consensus – but see

later

Traffic control rules Scheduling Excess treatment

Draft Updates

After discussions at Paris meeting: Update with detailed QOSM parameter

mappings with RFC2211 Updated Appendix: gives more

detailed QOSM for both sender-initiated reservations, and RSVP-fashion receiver-initiated

reservations

Half-Open Issues Three options for constructing QoS-NSLP-QUERY

messages like RSVP-PATH messages: Token bucket (QNE-readonly) + available bandwidth (QNE-

RW) should probably be used How exactly to interoperate with RSVP/IntServ

Basically, service translation is not a problem, but the interworking with RSVP/IntServ may need further study

The flexibility of QoS NSLP on reservation initiator can bring IntServ potentially more supporting scenarios

Some design freedom (e.g. on sender-initiated case)

Next Steps

Still some protocol fine-tuning Update following QoS-NSLP finalisation

Verify scope Is this refining the definition of CLS? Or

just providing new freedom for how to invoke it?

Start considering CL-ECN extensions? Should it be accepted as a WG item?