1 / 7

Controlled Load Service QoS Model <draft-kappler-nsis-controlledload-qosm-05.txt>

Controlled Load Service QoS Model <draft-kappler-nsis-controlledload-qosm-05.txt>. Cornelia Kappler Xiaoming Fu Bernd Schloer. Overview. Quick review Controlled Load Service QoSM Draft Update 04 -> 05 Interoperation with RSVP/IntServ. 2 69th IETF - Chicago, IL, USA. Review.

italia
Download Presentation

Controlled Load Service QoS Model <draft-kappler-nsis-controlledload-qosm-05.txt>

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Controlled Load Service QoS Model<draft-kappler-nsis-controlledload-qosm-05.txt> Cornelia Kappler Xiaoming Fu Bernd Schloer

  2. Overview • Quick review • Controlled Load Service QoSM • Draft Update 04 -> 05 • Interoperation with RSVP/IntServ 2 69th IETF - Chicago, IL, USA

  3. Review • Controlled-load service: a light-weight per-flow reservation service (compared with guaranteed service) in the IntServ model • A useful use example for per-flow NSIS QoS signaling especially in access networks • CLS QoSM: • Bandwidth is signaled in form of a <TMOD> parameter • provides approx. end-to-end service of an unloaded best-effort network • Reserving resources per-flow 3 69th IETF - Chicago, IL, USA

  4. Draft Update 04 -> 05 • Updated section about interoperation with RSVP-CLS • Included additional bit-level examples, e.g. Resource QUERY • Adapted terminology and content to latest version of QSPEC (v17), e.g. removed QOSM ID, removed MTU,.. 4 69th IETF - Chicago, IL, USA

  5. Interoperation with RSVP/IntServ • RSVP: • The sender populates a Path message including Sender Tspec (Token Bucket) and an ADSpec (Bandwidth and MTU). • The Receiver sends a Resv with a FlowSpec (Token Bucket). • Sender confirms the reservation with a ResvConfirm. 5 69th IETF - Chicago, IL, USA

  6. Interoperation with RSVP/IntServ • QoS NSLP: • The sender populates a QUERY message including <QoS Desired> and <QoS Available> • The Receiver sends a RESERVE with <QoS Desired> and <QoS Available> • Sender confirms the reservation with a RESPONSE including <QoS Reserved> • (all QSPEC objects carry the <TMOD> parameter)‏ 6 69th IETF - Chicago, IL, USA

  7. Current Status and Next Steps • This doc is fairly stable • Reviewed by a number of WG members • Addressed several IETF meeting comments • Also revised based on implementation experiences • Implementation: finished and working (will be included in next NSIS release)‏ • As a WG item? 7 69th IETF - Chicago, IL, USA

More Related