1. 25 January 2001TEQUILA Workshop Amsterdam1 Describing, Negotiating & Providing value-added IP services www.ist-tequila.org/ danny.goderis@alcatel.be

2. 25 January 2001TEQUILA Workshop Amsterdam2 Presentation Outline The Tequila Project The Tequila Functional Architecture Describing value-added IP services (SLS) Negotiating value-added IP services Report from the IEFT

3. 25 January 2001TEQUILA Workshop Amsterdam3 Part 1 : The Tequila Project consortium objectives & assumptions some interim achievements

4. 25 January 2001TEQUILA Workshop Amsterdam4 Tequila consortium Industrial Partners –Alcatel, Antwerp, Belgium –Algosystems S.A., Athens, Greece –France Telecom-R&D, Paris, France –Global Crossing, UK Universities –UCL - University College London, UK –NTUA - National Technical University Athens, Greece –UniS - The University of Surrey, Guildford, UK Research Institutes –IMEC, Ghent, Belgium –TERENA, Amsterdam, Netherlands

5. 25 January 2001TEQUILA Workshop Amsterdam5 Tequila objectives Develop architectures, algorithms and protocols for enabling negotiation, monitoring and enforcement of Service Level Specifications (SLS) between customer/ISP and ISP/ISP Develop a functional model of co-operating components, algorithms and protocols offering a intra-domain traffic engineering solution for meeting the contracted SLSs Develop a scaleable approach for inter-domain SLS negotiation and QoS-based routing for enforcing E2E QoS across the internet” Validate the Models & Contribute to standardization

6. 25 January 2001TEQUILA Workshop Amsterdam6 Enterprise Network TEQUILA system Host Application RSVP Path/Resv VPN/LL Manager H.323 GK Host Application SIP server/proxy Tequila network SLS Public IP-based, DiffServ (PHB)-enabled Network IPv4, Unicast, single addressing space SLS describes the traffic characteristics of IP services & the QoS guarantees offered by the network

7. 25 January 2001TEQUILA Workshop Amsterdam7 Interim achievements Theoretical Work –Functional Architecture and Top Level Design (public deliverable D1.1) –Algorithms & Protocol specification (D1.2) Contribution to IETF standardisation (SLS) –SLS parameters & semantics internet draft draft-tequila-sls-00.txt –SLS and Usage Framework internet draft draft-manyfolks-framework-00.txt –Service Level Specification & Usage BoF session San Diego 15 December 2000 - 350 attendees –SLS Public Mailing list : sls@ist-tequila.org Papers, conferences,...

8. 25 January 2001TEQUILA Workshop Amsterdam8 Part 2 The TEQUILA functional model Tequila Subsystems Service Management Traffic Engineering Traffic Forecasting & Aggregation

9. 25 January 2001TEQUILA Workshop Amsterdam9 Tequila Subsystems Service description through SLS template => Customer awareness Service provisioning through Traffic Engineering => QoS Class awareness VPN/LL Manager H.323 GK Host Application Service Management Traffic Engineering Monitoring Policy Management Data Plane QoS classes SLS

10. 25 January 2001TEQUILA Workshop Amsterdam10 Service Management Network Dimensioning Service Subscription Service Invocation Traffic Forecast Traffic Conditioning Service Subscription Service Invocation Data Transmission “Management Plane” “Data Plane” “Control Plane” CustomerISP Dynamic Route Management SLS-aware

11. 25 January 2001TEQUILA Workshop Amsterdam11 Subscription & Invocation Service Subscription –negotiating the right to invoke transport (IP) services ensures the customer resource availability –between ISP-Customer allows the ISP to provision & dimension his network Service Invocation –actual negotiation for (allocating) resources in-band or out-of-band explicit (e.g. by RSVP) or implicit (e.g. automatic by subscription) –between ISP-users –may be at a later time than SLS subscription –may be a N-to-1 relation with subscription –must be in-range with SLS subscription (provider policy)

12. 25 January 2001TEQUILA Workshop Amsterdam12 Traffic Engineering Network Dimensioning Dynamic Route Management Dynamic Resource Management Routing PHB configuration Network Planning Traffic Forecast Service Invocation Service Subscription QoS-class aware Traffic Conditioning

13. 25 January 2001TEQUILA Workshop Amsterdam13 Tequila QoS Classes QoS class = [OA | delay | loss ] –Ordered Aggregate ~ PHB scheduling class EF, AFx, BE –delay edge-to-edge maximum delay worst case or probabilistic (percentile) delay classes (min-max intervals) –loss edge-to-edge packet loss probability

14. 25 January 2001TEQUILA Workshop Amsterdam14 Traffic Forecast TM = [pipe] [QoS class | ingr-egre | min-demand - max-demand] –minimum - maximum range interval allows for over-subscription (statistical multiplexing) allows for new SLSs between two TE cycles E2E NC = [pipe] [QoS class | ingr-egre | min-demand - sustainable load] –sustainable load = effective (long-term) reserved capacity –calculated by Traffic Engineering algorithms Network Dimensioning Traffic Forecast Service Subscription Edge-to-Edge Network Configuration E2E NC Traffic Matrix - TM SLS Subscriptions

15. 25 January 2001TEQUILA Workshop Amsterdam15 Traffic Forecast Forecast algorithm Service mapping algorithm SLS monitoring SLS subscription Traffic forecast module over-subscription policy QoS-class ingress min-In max-In {egress min-Out max-Out} SLS load QoS-class ingress In-demand {egress Out-demand} Aggregation algorithm QoS-class ingressminIn maxIn {egressminOut maxOut}

16. 25 January 2001TEQUILA Workshop Amsterdam16 TEQUILA Functional Architecture SLS management Traffic Engineering Data Plane Monitoring Policy Management Interdomain SLS Policy Consumer Pol. Mgt tool SLS Subs SLS invoc. Traffic Forecast DRsM DRtM Routing PHBTC ND SLS Repos. Network M.SLS M. Node M.

17. 25 January 2001TEQUILA Workshop Amsterdam17 Part 3 Describing value-added IP services Service Level Specifications IP Transport Services Examples

18. 25 January 2001TEQUILA Workshop Amsterdam18 Providing Transport Services DiffServ top-down view Service Level Agreement (SLA) Transport Service Service Level Specification (SLS) QoS class Per Domain Behaviour (PDB) Per Hop Behaviour (PHB) Traffic Conditioning Block Scheduler (e.g. WFQ) Algorithmic Dropper (e.g. RED) - implementation - Non-technical terms & conditions - technical parameters :{SLS}-set - IP service traffic characteristics - offered network QoS guarantees - Network QoS capabilities - DiffServ edge-to-edge aggregates - Router QoS capabilities - DiffServ core & edge routers

19. 25 January 2001TEQUILA Workshop Amsterdam19 SLS - Parameters IP Flow Descriptor Traffic Envelope & Conformance Performance Guarantees & Excess Treatment SLS = a set of parameters making up an IP flow contract Four basic parameter groups Scope = (ingress, egress)

20. 25 January 2001TEQUILA Workshop Amsterdam20 Flow Descriptor IP Flow = stream of IP packets sharing at least one common characteristic –DSCP information (set of) DSCP value(s) | any –Source information (set of) source addresses | (set of) source prefixes | any –Destination information (set of) destination addresses | (set of) prefixes | any –Application information protocol number,...

21. 25 January 2001TEQUILA Workshop Amsterdam21 Scope Scope = the geographical region over which the QoS is to be enforced Scope = (Ingress, Egress) –Ingress : (set of) interface addresses | any –Egress : (set of) interface addresses | any IP-addresses | L2-link identifiers Scope models –Pipe or one-to-one model : (1,1) –Hose or one-to-many|any model : (1, N| any) –Funnel or many|any-to-one model (N|any,1)

22. 25 January 2001TEQUILA Workshop Amsterdam22 Traffic Envelope Traffic Envelope = set of (conformance) parameters describing how the packet stream should look like to get performance guarantees Traffic Conformance testing is the set of actions allowing to identify in- & out-of-profile packets –Example: token bucket Excess treatment –drop | shape | remark

23. 25 January 2001TEQUILA Workshop Amsterdam23 Performance Guarantees The performance parameters describe the transport guarantees the network offers to the customer –for the packet stream identified by Flow descriptor –over the geographical region defined by Scope Four (measurable) parameters –delay | optional quantile –jitter | optional quantile –packet loss –throughput

24. 25 January 2001TEQUILA Workshop Amsterdam24 Performance Guarantees Delay & jitter –indicate the maximum packet transfer delay and delay variation from ingress to egress can be deterministic (worst case) or probabilistic (quantile) guarantee for in-profile packets (only) Packet loss –the ratio of the lost and the sent (in-profile) packets sent packets at ingress lost packets between (and including) ingress/egress Throughput guarantee –the packet rate measured at egress counting all packets identified by Flow Id

25. 25 January 2001TEQUILA Workshop Amsterdam25 IP Transport Services Examples Bi-directional services (e.g. VLLs) –bi-directional VLLs = combination of 2 SLSs Virtual Private Networks –combination of multiple hose & filter SLSs –guaranteed throughput from ingress to all egress –maximum allowed rate towards a customer side (e.g A out )

26. 25 January 2001TEQUILA Workshop Amsterdam26 IP Transport Services Formal Description Service Subscription Service Invocation Traffic Conditioning Service Subscription Service Invocation Data Transmission SSS customer ISP user SIS data application SSS = Service Subscription Structure SIS = Service Invocation Structure

27. 25 January 2001TEQUILA Workshop Amsterdam27 IP Transport Services Formal Description Service Subscription Structure –Subscriber id & credentials –Service = {SLS} set –Service Schedule (Start time, End time) –{user ids, credentials} –Invocation method (permanent | on-demand - protocol-id) –Grade of Service (blocking probability of invocations) Service Invocation Structure –SSS_reference handle –{user id, credential} –Service = {SLS-set} –Atomic Invocation (yes/no)

28. 25 January 2001TEQUILA Workshop Amsterdam28 Example IP VPN Services Customer Premises Access Router AS Core RouterAS Edge Router Autonomous System SLS Subscription TEQUILA System Policy - configuration SLS Subscription Customer Service Subscription CPE Server employees RSVP Invoked IP flows

29. 25 January 2001TEQUILA Workshop Amsterdam29 Example Connecting Residential Gateways IP H323/SIP/... Gatekeeper/ Proxy Server COPS, SNMP Service Subscription Tequila System RG SLS Invocation - RSVP Service Subscription = contract between the VoIP & Transport Provider

30. 25 January 2001TEQUILA Workshop Amsterdam30 Part 4 Negotiating value-added IP services Service Management Engineering Model Service Subscription Protocol - SrNP Service Negotiation Protocol - RSVP

31. 25 January 2001TEQUILA Workshop Amsterdam31 Tequila Service Management Engineering Model & Protocols SSM Broker SIM Router SIM Router SIM Router SIM Router SIM Router SIM TFM ND Router SIM Router SIM User broker SIM Subsc. SSM Service Subscription Module SIM Service Invocation Module out-of-band invocation in-band invocation SrNP RSVP SrNP

32. 25 January 2001TEQUILA Workshop Amsterdam32 Service Negotiation Protocol - SrNP Client-server based Form-fill oriented Messaging is content- independent Protocol stacks TCP/IP HTTP,SMTP,IIOP XML SrNP TCP/IP SrNP

33. 25 January 2001TEQUILA Workshop Amsterdam33 RSVP - IntServ/DiffServ scenario Reminder User A sender User B receiver Ingress AEgress B Tequila Network SLS-I Request RSVP PATH RSVP RESV RSVP SLS-I Admitted Admission Control Admission Control RSVP RESV RSVP PATH RSVP RESV RSVP SLS-I Request SLS-I Admitted RESV PATH Is executed first

34. 25 January 2001TEQUILA Workshop Amsterdam34 User A sender User B receiver Ingress A Admission Control Egress B Admission Control Tequila Network SLS-I Admitted SLS-I Request SLS-I Admitted SLS-I Request RSVP PATH RSVP RESV RSVP PATH RSVP RESV RSVP data RSVP - Service Invocation Uni-directional service PATH message contains (new-defined) SIS object class with 1 SLS Admission Control executed by Service Invocation Module at edges –Ingress A -> network resources –Egress B -> access link resources to receiver B Admission Control - AA user credentials - in range check with SSS - subscription - resource availability

35. 25 January 2001TEQUILA Workshop Amsterdam35 RSVP - Service Invocation Bi-directional service PATH message contains SIS object class with 2 SLSs Admission Control at node A –network resources for the stream from A to B –access link resources for the stream from B to A