90 likes | 261 Views
QoS-NSLP QSpec Template. draft-ash-nsis-nslp-qspec-01. Jerry Ash, Attila Bader, Chuck Dvorak, Yacine El Mghazli, Cornelia Kappler, Georgios Karagiannis, Andrew McDonald, Al Morton, Percy Tarapore, Lars Westberg. Motivated by IDs on QSMs draft-ash-nsis-nslp-qos-sig-proof-of-concept-01
E N D
QoS-NSLP QSpec Template draft-ash-nsis-nslp-qspec-01 Jerry Ash, Attila Bader, Chuck Dvorak, Yacine El Mghazli, Cornelia Kappler, Georgios Karagiannis, Andrew McDonald, Al Morton, Percy Tarapore, Lars Westberg Motivated by IDs on QSMs • draft-ash-nsis-nslp-qos-sig-proof-of-concept-01 • draft-bader-rmd-qos-model-01 • draft-kappler-nsis-qosmodel-controlledload-00
Outline • Updates to draft • QSpec Template • Example QSpecs • IntServ Controlled Load Service • IntServ Guaranteed Service • Open Issues • Recommendation: propose document as NSIS WG draft
Updates to the Draft • Focus on generic parameters • Based on DiffServ & IntServ QoS signaling models (QSMs) • Optional parameters supporting other QSMs to be provided later • Simplified overall structure • Clearer definition of sub-objects • Examples given of IntServ guaranteed service & controlled load service
QSpec Template • QSpec Template defines generic parameters & optional parameters • Generic Parameters • MUST be understood by any QNE • SHOULD be used for QSpecs if applicable • Based on DiffServ & IntServ QSMs • Optional Parameters • SHOULD be used for QSpecs if applicable • To be provided later as required by other QSMs • Parameters can be mutable or immutable
QSpec Template • QSpec = <QSM Specific Control Info> <QoS Description> • <QSM Specific Control Info> = <Hop Count> <Service Schedule> • <QoS Description> = <QoS desired > <QoS Available> <QoS Reserved> <Minimum QoS> • QoS Description sub-objects were proposed to satisfy sender and receiver initiated signaling
Example QSpecs • QSpec for IntServ Controlled Load Service • <QoS Desired> = <token bucket> • <QoS Available> = <non IS hop> <IS hops> <Available BW> <Min latency> <M> • <QoS Reserved> = <token bucket> • QSpec for IntServ Guaranteed Service • <QoS Desired> = <token bucket> • <QoS Available> = <non IS hop> <IS hops> <Available BW> <Min latency> <M> <Ctot> <Dtot> <Csum> <Dsum> • <QoS Reserved> = <token bucket> <R> <S>
Open Issues • QSM guideline is needed in addition to QSpec template • Specify ‘generic’ message processing rules • Extend those already present in QoS-NSLP (e.g. RESERVE-RESPONSE, QUERY-RESERVE-RESPONSE) • Clarify relationship of Common NSLP Processing, QSM-specific NSLP Processing and Resource Mgmt. Fct. • May a node compose a QSpec containing more parameters than defined in the QSM it is signaling for later use by other nodes?
Open Issues • Optional parameters proposed to support other QSMs, need to discuss for inclusion in QSpec template • <Transfer Delay>, <Delay Variation>, <Packet Loss Ratio>, & <Packet Error Ratio> • Generalize priority parameter: <Priority> = <Reservation Priority> <Setup Priority> <Holding Priority> • <Priority> is part of <QoS Desired>, <QoS Reserved> or <Minimum QoS > • <Setup Priority> & <Holding Priority> specified in RFC 3209 • Do we need an explicit Traffic Specification, or is <QoS Desired>, which may not exactly describe the issued traffic, acceptable? • Should <Service Schedule> be optional?
Recommendation • Propose draft as NSIS working group draft