An QoS ALSP (ULSP) proposal

1
An QoS ALSP (ULSP) proposal

• Georgios.Karagiannis_at_eln.ericsson.se

2
Why this presentation?

• Present a concept that includes additions to the
  concept introduced in draft-braden-2level-signal-a
  rch-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-si
  gnal-arch-01.txt
• differences
• an ALSP that can enhance scalability and can
  maintain the following state management types
• per flow request gtper flow state in ALSP and
  CSTP
• per aggregated requestgtper-aggregate state in
  ALSP and CSTP
• per-flow or aggregate requestgt 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-si
  gnal-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?