90 likes | 102 Views
LQS – Lightweight QoS Signalling. Mehmet Ersü / Cornel Pampu ICM N PG SP [ST/RC] 27.8.2002. NSIS and LQS History. (03/01) NSIS (Next Steps in Signalling) BOF in IETF #50
E N D
LQS – Lightweight QoS Signalling Mehmet Ersü / Cornel Pampu ICM N PG SP [ST/RC] 27.8.2002
NSIS and LQS History • (03/01) NSIS (Next Steps in Signalling) BOF in IETF #50 • (08/01) In ‚Long-Term IETF Standardization Strategy‘ project workshop with LoB‘s „Lightweight QoS Signalling“ has been detected as one of the Top 3 IP issues in ICM N • (10/01) Nokia initiated the new NSIS WG • (10/01) Sabbatical project proposal “Lightweight QoS Signalling for MM Scenarios“ accepted by Prof. Schulzrinne • (11/01) A joint team started work on NSIS requirements draft with limited resources from several projects and LoB‘s: Masa/NEC, MIND/RMR/Uni Ulm, SeQoMo/TU Berlin, CT IC, LoB U SE, PG SP RC, PG SP ST • (01/02) Siemens/NEC req. draft becomes WG item because of completeness, UMTS scenarios and a strong security chapter • (03/02) Successful presentation and discussion of the framework draft at IETF #53 • (06/02) Start of the sabbatical project LQS • (07/02) Acceptance of the 2nd FW draft, NSIS Threats, RSVP Security Properties as WG items and Multicast Analysis as part of a WG item ICM templ-1-o-example.ppt 12/07/2001
Lightweight QoS Signalling for Mobile Multimedia Scenarios (LQS) • Overall project theme: „Design of a technology independent Lightweight QoS Signalling protocol for access networks“ • Joint Project with members of CT, ICN and ICM together with Prof. Henning Schulzrinne • In parallel to the joint activity in IETF WG NSIS (Next Steps In Signalling) with members from RMR, CT, ICM, NEC, TU Berlin, Univ. of Ulm • Project Management: Mehmet Ersü (ICM N PG SP ST A 1) • Technical Project Lead:Dr. Cornelia Kappler/Cornel Pampu (ICM N PG SP RC AP) ICM templ-1-o-example.ppt 12/07/2001
LQS Project Team • Core Team: • Technical Leadership and Guidance:Prof. Schulzrinne (Columbia University, NY) • Hannes Tschofenig (CT IC 3) • Jochen Eisl (ICM N PG SP RC PC) • Xiaoming Fu (TU Berlin) • Review partner: • Robert Hancock (Roke Manor Research) • Other project members: • Hans-Peter Huth (CT IC 2) • Joachim Sokol (CT IC 2) • Changpeng Fan (ICM N PG SP RC AP) • Rudolf Brandner (ICN M SR 1) • Karl Schrodi (ICN WN CS FP 1) ICM templ-1-o-example.ppt 12/07/2001
LQS: Why are existing solutions insufficient? • inter-domain signaling • out-of-path signaling • signaling other than end-to-end • bi-directional signaling • mobility support • multicast support usually not needed • interworking with policy, security, TE, ... ICM templ-1-o-example.ppt 12/07/2001
LQS Milestones • Milestone 1: 27.6. • Requirements gathering and analysis based on ICM N priorities • Analysis of the Protocol-Candidates • Milestone 2: 23.7. • Definition of the Scenarios • Design of the "very light" version (LQS kernel) • Milestone 3: 13.8. • Design of LQS-sub-packages with priorities • Milestone 4: 27.8. • Final Internet Draft(s) • White Paper: LQS Design Considerations ICM templ-1-o-example.ppt 12/07/2001
LQS: Where to use? • QoS Signalling • Configuration of middleboxes • Topology discovery • Measurement data collection • MPLS label distribution • ACTIVE NETWORKS • ….. ICM templ-1-o-example.ppt 12/07/2001
LQS: Why now?(I) • Signalling solution needed: • In 3GPP for inter-domain signaling • Between bandwidth-brokers • In conjunction with mobility • IETF NSIS (Next Steps In Signaling) WG chartered in Nov. 2001 • generates wide interest • most active participants - mobility community (Siemens, NEC, Ericsson, Nokia, Alcatel) • closely followed and supported by „RSVP inventors“ ICM templ-1-o-example.ppt 12/07/2001
LQS: Why now? (II) • Siemens contribution to NSIS: • Requirements I-D: Marcus Brunner (NEC) as the editor, 3 main contributors from Siemens in I-D • Framework I-D: Robert Hancock (RMR) as the editor • The only securitycontributions: Hannes Tschofenig (CT) as the editor • Analysis I-D: Xiaoming Fu (TU Berlin) contributor with SeQoMo results => Siemens solution for NSIS Protocol • CASP (Cross Application Signaling Protocol) • CASP QoS Client: A Per-Flow Resource Allocation Client for CASP ICM templ-1-o-example.ppt 12/07/2001