1 / 35

Describing, Negotiating & Providing value-added IP services

Describing, Negotiating & Providing value-added IP services. www.ist-tequila.org/ danny.goderis@alcatel.be. Presentation Outline. The Tequila Project The Tequila Functional Architecture Describing value-added IP services (SLS) Negotiating value-added IP services Report from the IEFT.

colton-hatfield
Download Presentation

Describing, Negotiating & Providing value-added IP services

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. Describing, Negotiating & Providing value-added IP services www.ist-tequila.org/ danny.goderis@alcatel.be TEQUILA Workshop Amsterdam

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

  3. Part 1 : The Tequila Project consortium objectives & assumptions some interim achievements TEQUILA Workshop Amsterdam

  4. Tequila consortium • Industrial Partners • Alcatel, Antwerp, Belgium • Algosystems S.A., Athens, Greece • France Telecom-R&D, Paris, France • GlobalCrossing, 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 TEQUILA Workshop Amsterdam

  5. 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 engineeringsolution formeeting the contracted SLSs • Develop a scaleable approach for inter-domain SLS negotiation and QoS-based routingfor enforcing E2E QoS across the internet” • Validate the Models & Contribute to standardization TEQUILA Workshop Amsterdam

  6. SLS VPN/LL Manager Enterprise Network H.323 GK SIP server/proxy TEQUILA system Host Application SLS RSVP Path/Resv Host Application SLS Tequila network • 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 TEQUILA Workshop Amsterdam

  7. 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 & semanticsinternet 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,... TEQUILA Workshop Amsterdam

  8. Part 2The TEQUILA functional model Tequila Subsystems Service Management Traffic Engineering Traffic Forecasting & Aggregation TEQUILA Workshop Amsterdam

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

  10. Service Management Customer ISP SLS-aware Traffic Forecast Network Dimensioning Service Subscription Service Subscription “Management Plane” Service Invocation Service Invocation Dynamic Route Management “Control Plane” Data Transmission Traffic Conditioning “Data Plane” TEQUILA Workshop Amsterdam

  11. Subscription & Invocation • Service Subscription • negotiating the righttoinvoke 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) TEQUILA Workshop Amsterdam

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

  13. 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 TEQUILA Workshop Amsterdam

  14. SLS Subscriptions Traffic Forecast Traffic Matrix - TM Service Subscription Network Dimensioning Edge-to-Edge Network Configuration E2E NC 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 TEQUILA Workshop Amsterdam

  15. SLS load SLS Traffic monitoring forecast Service mapping module algorithm SLS subscription QoS -class ingress In-demand {egress Out-demand} over-subscription Aggregation policy algorithm QoS -class ingress minIn maxIn {egress minOut maxOut } Forecast algorithm QoS -class ingress min-In max-In {egress min-Out max-Out} Traffic Forecast TEQUILA Workshop Amsterdam

  16. TEQUILAFunctional Architecture Policy Management Pol. Mgt tool SLS Repos. Policy Consumer SLS management Interdomain SLS ND Traffic Forecast SLS Subs DRtM DRsM SLS invoc. Routing Traffic Engineering SLS M. Network M. Node M. Data Plane TC PHB Monitoring TEQUILA Workshop Amsterdam

  17. Part 3Describing value-added IP services Service Level Specifications IP Transport Services Examples TEQUILA Workshop Amsterdam

  18. 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) Providing Transport ServicesDiffServ top-down view - 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 - implementation TEQUILA Workshop Amsterdam

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

  20. FlowDescriptor • 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,... TEQUILA Workshop Amsterdam

  21. 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) TEQUILA Workshop Amsterdam

  22. TrafficEnvelope • 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 TEQUILA Workshop Amsterdam

  23. PerformanceGuarantees • 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 • packetloss • throughput TEQUILA Workshop Amsterdam

  24. PerformanceGuarantees • 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 TEQUILA Workshop Amsterdam

  25. IP Transport ServicesExamples • 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 Aout) TEQUILA Workshop Amsterdam

  26. SSS Service Subscription Service Subscription ISP customer SIS Service Invocation Service Invocation user Data Transmission data Traffic Conditioning application IP Transport ServicesFormal Description • SSS = Service Subscription Structure • SIS = Service Invocation Structure TEQUILA Workshop Amsterdam

  27. IP Transport ServicesFormal 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) TEQUILA Workshop Amsterdam

  28. TEQUILA System Customer Service Subscription Customer Premises Access Router SLS Subscription SLS Subscription AS Core Router AS Edge Router Policy - configuration RSVP Autonomous System CPE CPE Invoked IP flows employees Server ExampleIP VPN Services TEQUILA Workshop Amsterdam

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

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

  31. Subsc . SSM SSM SSM SSM TFM User broker Broker SSM ND SSM SIM SIM Router Router Router SIM SIM SIM Router Router Router Router SIM SIM SIM SIM Tequila Service ManagementEngineering Model & Protocols SSM Service Subscription Module SrNP SrNP SIM Service Invocation Module out-of-band invocation in-band invocation RSVP TEQUILA Workshop Amsterdam

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

  33. SLS-I SLS-I SLS-I SLS-I Admitted Request Admitted Request RSVP PATH RESV PATH RSVP PATH RSVP RESV RSVP RESV RSVP RESV RSVP - IntServ/DiffServ scenarioReminder Tequila Network User A Ingress A Egress B User B sender receiver Admission Admission Is executed first Control Control RSVP RSVP RSVP RSVP TEQUILA Workshop Amsterdam

  34. Tequila Network User A Ingress A Egress B User B sender receiver Admission Admission Control Control SLS-I SLS-I SLS-I SLS-I Request Admitted Request Admitted RSVP PATH RSVP PATH RSVP RSVP RSVP RSVP RESV RSVP RESV data RSVP - Service InvocationUni-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 withSSS - subscription - resource availability TEQUILA Workshop Amsterdam

  35. RSVP - Service InvocationBi-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 TEQUILA Workshop Amsterdam

More Related