1. 1 “A QoS Model for Signaling IntServ Controlled-Load Service with NSIS” draft-kappler-nsis-qosmodel-controlledload-01.txt cornelia.kappler at siemens.com

2. 2 What is IntServ Controlled-Load Service? qIntServ Controlled Load Service is (in NSIS terms) a QoS Model vRFC 2210 specifies how to signal for Ctrld Load using RSVP vThis ID specifies how to signal for Ctrld Load using NSIS qControlled-Load Service (RFC 2211) vProvides approximately service of an unloaded best-effort network vQoS parameters signaled are Token Bucket and MTU vImplemented per “network element”, i.e. per-router or per-subnet –Can be used for Reserving resources per-flow per-router Admission control at edge of DiffServ domains Admission control into MPLS clouds qWhat is Controlled Load specific, what is RSVP specific? vOnly Controlled Load specifics need to be reflected in this ID –“extra features” compared to RSVP are in green

3. 3 How to signal for Controlled-Load Service with NSIS qRole of QNEs vOne or more QNE per “network element” vStateless QNEs? –“Provide approximately service of an unloaded best-effort network” may also be possible with stateless QNEs qQoS-model specific Control Information v ? –Even if don’t implement Ctrld Load, all QNEs must be able to interpret all parameters because all parameters for Ctrld Load are mandatory parameters v may be included qQSPEC Procedures vNo restriction, i.e. sender-ini, receiver-ini with all combination of QSPEC objects

4. 4 How to signal for Controlled-Load Service with NSIS qQSPEC objects: =, ( ) = (,,, ), = OR, ( ) = vOf these, only and will be used in all procedures –E.g. for sender-initiated reservation can use only vMay include to provide for DiffServ domains vIn QoS Available, are there because this is how RSVP does it. Usage unclear –For admission control? vFor parameters appearing in QoS Available and/or Minimum QoS can accept downgrade vIn all QSPEC objects, additional parameters may be included

5. 5 How to signal for Controlled-Load Service with NSIS qHow to deal with MTU? vIn sender-ini procedures, if reservation fails… –E.g. because of too big (Max packet size)? …how can receive meaningful feedback? –When reservation fails only receive feedback up to failure point vCould include lower bound for in to avoid failure of reservation because of MTU problem – is not necessarily supported by all QNEs vXiaoming: “I would prefer to remove it from IntServ discussion; instead, PMTU discovery or out-of-band MTU information exchange should be another process instead inside QoS signaling itself.”