1 / 8

NSLP for Quality of Service

This document outlines the key issues discussed during the interim meetings focused on the Networked Services Layer Protocol (NSLP) for Quality of Service (QoS). It covers various topics such as receiver-initiated reservations, query mechanisms, and session binding. The discussion highlights points on message priority handling, refresh overhead reduction strategies, and the significance of the Resource Identifier Information (RII). Additionally, it delves into error handling, emphasizing the need for clear error codes. The document aims to refine the NSLP design and improve overall reservation processes.

tola
Télécharger la présentation

NSLP for Quality of Service

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. NSLP for Quality of Service draft-ietf-nsis-qos-nslp-04.txt Sven Van den Bosch (ed.) Georgios Karagiannis Andrew McDonald (et al)

  2. Issues discussed at interim • Receiver-initiated reservation • Use empty QUERY for ‘PATH’ • Receiver-initiated resv. over reduced-state domain • Session binding informative in nature • Flags made positive • Remove NO_FATE_SHARING flag • Does not explicitly provide fate sharing (can be handled by endpoints) • Refresh reduction • MRI must always be passed

  3. Issues discussed at interim • Priority • Message priority: transfer attributes • Reservation priority: QSPEC issue, one level • Use SCOPING only in QUERY/RESERVE • RII • Clarify global RII versus local RSN significance • make RII a separate object, carried in QUERY/RESERVE and RESPONSE • Object formats: TLV

  4. Closed open issues on • Priority of reservations • GIMPS Modifications for Refresh Overhead Reduction • Path state maintenance implementation at NSLP or NTLP • Resource sharing • RESERVE/COMMIT • One-sided bidirectional reservation

  5. Changes in -04 • Clarifications • Aggregation: document does not specify how to aggregate end-to-end reservation but rather how such an aggregate can be signalled for • QSPEC stacking • Made RII a separate object (outside of SCOPING) • Removed RESPONSE_REQUEST • Made SCOPING a flag rather than an object • Added object format for ERROR_SPEC object • See next slide

  6. ERROR_SPEC object format • first byte of error code indicates severity • 0x01 - Informational • 0x02 - Success • 0x03 - Protocol Error • 0x04 - Transient Failure • 0x05 - Permanent Failure • Currently defined error codes: see document +-------------+-------------+-------------+-------------+ | 0x0005 | variable length | +-------------+-------------+-------------+-------------+ | Error code | +-------------+-------------+-------------+-------------+ | | // Optional variable length error-specific information // | | +-------------+-------------+-------------+-------------+

  7. Mailing list discussions • Need for ‘OK’ error code (resolved) • Proposal to add a ‘meaning’ object to a message (open) • E.g. encode ‘TEAR’ in this object iso flag • Useful to have the concept of ‘TEAR’ [Yes] • What is the best way to encode? • In a flag [now] • In a separate ‘meaning’ object • As a separate message type

  8. Open issues • Authorization • See discussion on draft-tschofenig-nsis-qos-ext-authz-00.txt • Error codes • Include in message/object processing text, if OK

More Related