1 / 6

Enhancing ALSP and ULSP Concepts through Protocol Level Separation and Scalability

This presentation proposes advancements to the ALSP and ULSP frameworks based on the draft-braden-2level-signal-arch-01.txt. The concept revolves around a two-level protocol separation: transport (CSTP) and application (ALSP or ULSP). The new ALSP enhances scalability by managing different state types—per flow, per aggregate, and traffic class states—while integrating stateless operations in CSTP nodes. The goal is to elicit feedback from the Working Group on the viability and acceptance of this concept in improving protocol efficiency and reliability.

lexiss
Download Presentation

Enhancing ALSP and ULSP Concepts through Protocol Level Separation and Scalability

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. An QoS ALSP (ULSP) proposal • Georgios.Karagiannis@eln.ericsson.se

  2. Why this presentation? • Present a concept that includes additions to the concept introduced in draft-braden-2level-signal-arch-01.txt • Elicit feedback from the WG!

  3. Concept: Separation in two main protocol levels, transport (CSTP) and application (ALSP or ULSP) • Application level: • similar to the ALSP used in draft-braden-2level-signal-arch-01.txt • differences: • an ALSP that can enhance scalability and can maintain the following state management types: • per flow request =>per flow state in ALSP and CSTP; • per aggregated request=>per-aggregate state in ALSP and CSTP; • per-flow or aggregate request=> One state per traffic class in ALSP and no need for state in CSTP. A traffic class state is a state associated to an independent number of flows that are belonging to the same traffic class;

  4. Concept: Separation in two main protocol levels, transport (CSTP) and application (ALSP or ULSP) • Transport level: • similar to the CSTP used in draft-braden-2level-signal-arch-01.txt • differences (due to the requirement that CSTP has to be suitable to the proposed ALSP): • extension of CSTP to have stateless operation in a node: • CSTP stateless node: CSTP aware node that does not maintain a CSTP state but is maintaining an ALSP state per traffic class; • the detection of lost signaling messages on CSTP stateless nodes is provided by the reliable delivery procedure available on CSTP statefull nodes

  5. Architecture

  6. Discussion • Is the presented concept acceptable to the WG?

More Related