Transcript No Slide Title

Describing, Negotiating & Providing
value-added IP services
www.ist-tequila.org/
[email protected]
25 January 2001
TEQUILA Workshop Amsterdam
1
Presentation Outline
• The Tequila Project
• The Tequila Functional Architecture
• Describing value-added IP services (SLS)
• Negotiating value-added IP services
• Report from the IEFT
25 January 2001
TEQUILA Workshop Amsterdam
2
Part 1 : The Tequila Project
• consortium
• objectives & assumptions
• some interim achievements
25 January 2001
TEQUILA Workshop Amsterdam
3
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
25 January 2001
TEQUILA Workshop Amsterdam
4
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
25 January 2001
TEQUILA Workshop Amsterdam
5
Tequila network
Enterprise
Network
VPN/LL Manager
H.323 GK
SIP server/proxy
TEQUILA system
SLS
Host Application
Host Application
RSVP Path/Resv
SLS
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
25 January 2001
TEQUILA Workshop Amsterdam
6
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 :
• [email protected]
• Papers, conferences,...
25 January 2001
TEQUILA Workshop Amsterdam
7
Part 2
The TEQUILA functional model
• Tequila Subsystems
• Service Management
• Traffic Engineering
• Traffic Forecasting & Aggregation
25 January 2001
TEQUILA Workshop Amsterdam
8
Tequila Subsystems
Policy Management
VPN/LL Manager
Service
Management
H.323 GK
QoS
classes
Host Application
Traffic
Engineering
Data Plane
SLS
Monitoring
Service description
through SLS template
=> Customer awareness
25 January 2001
TEQUILA Workshop Amsterdam
Service provisioning
through Traffic Engineering
=> QoS Class awareness
9
Service Management
Customer
ISP
SLS-aware
Traffic
Forecast
“Management
Plane”
Service
Subscription
Service
Subscription
“Control Plane”
Service
Invocation
Service
Invocation
“Data Plane”
Data
Transmission
Traffic
Conditioning
25 January 2001
TEQUILA Workshop Amsterdam
Network
Dimensioning
Dynamic Route
Management
10
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)
25 January 2001
TEQUILA Workshop Amsterdam
11
Traffic Engineering
Traffic
Forecast
Service
Subscription
Service
Invocation
Network
Dimensioning
Dynamic
Route
Management
Network
Planning
Dynamic
Resource
Management
Routing
QoS-class aware
Traffic
Conditioning
25 January 2001
PHB
configuration
TEQUILA Workshop Amsterdam
12
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
25 January 2001
TEQUILA Workshop Amsterdam
13
Traffic Forecast
SLS
Subscriptions
Traffic
Forecast
Traffic Matrix - TM
Service
Network
Subscription
Dimensioning
Edge-to-Edge Network Configuration
E2E NC
• 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
25 January 2001
TEQUILA Workshop Amsterdam
14
Traffic Forecast
SLS
monitoring
SLS load
SLS
subscription
over-subscription
policy
Service mapping
algorithm
Traffic
forecast
module
QoS -class ingress In-demand
{egress Out-demand}
Aggregation
algorithm
QoS -class ingress minIn maxIn
{egress minOut maxOut }
Forecast
algorithm
QoS -class ingress min-In
max-In {egress min-Out max-Out}
25 January 2001
TEQUILA Workshop Amsterdam
15
TEQUILA
Functional Architecture
Policy Management
Pol. Mgt
tool
SLS Repos.
Policy
Consumer
Interdomain
SLS
SLS management
ND
Traffic
Forecast
SLS Subs
DRtM
DRsM
SLS invoc.
Routing
Traffic Engineering
SLS M.
Network M.
Node M.
TC
Data Plane
PHB
Monitoring
25 January 2001
TEQUILA Workshop Amsterdam
16
Part 3
Describing value-added IP services
• Service Level Specifications
• IP Transport Services
• Examples
25 January 2001
TEQUILA Workshop Amsterdam
17
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)
25 January 2001
- 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
18
SLS - Parameters
• SLS = a set of parameters making up an IP flow contract
• Four basic parameter groups
Traffic Envelope &
Conformance
IP Flow Descriptor
Scope = (ingress, egress)
25 January 2001
Performance
Guarantees
&
Excess Treatment
TEQUILA Workshop Amsterdam
19
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,...
25 January 2001
TEQUILA Workshop Amsterdam
20
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)
25 January 2001
TEQUILA Workshop Amsterdam
21
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
25 January 2001
TEQUILA Workshop Amsterdam
22
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
25 January 2001
TEQUILA Workshop Amsterdam
23
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 January 2001
TEQUILA Workshop Amsterdam
24
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 Aout)
bout
ain
Network
Networ
k
B
bin
cin
A
C
aout
c out
din
dout
25 January 2001
TEQUILA Workshop Amsterdam
D
25
IP Transport Services
Formal Description
customer
Service
Subscription
user
Service
Invocation
application
Data
Transmission
SSS
SIS
data
Service
Subscription
ISP
Service
Invocation
Traffic
Conditioning
• SSS = Service Subscription Structure
• SIS = Service Invocation Structure
25 January 2001
TEQUILA Workshop Amsterdam
26
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)
25 January 2001
TEQUILA Workshop Amsterdam
27
Example
IP VPN Services
Customer Service
Subscription
SLS
Subscription
TEQUILA System
SLS
Subscription
Policy - configuration
Autonomous System
CPE
CPE
Invoked IP flows
employees
Customer Premises Access Router
25 January 2001
RSVP
AS Core Router
TEQUILA Workshop Amsterdam
Server
AS Edge Router
28
Example
Connecting Residential Gateways
Gatekeeper/ Proxy Server
Service Subscription
Tequila System
H323/SIP/...
COPS, SNMP
IP
RG
RG
SLS Invocation - RSVP
RG
RG
RG
RG
Service Subscription =
contract between the VoIP & Transport Provider
25 January 2001
TEQUILA Workshop Amsterdam
29
Part 4
Negotiating value-added IP services
• Service Management Engineering Model
• Service Subscription Protocol - SrNP
• Service Negotiation Protocol - RSVP
25 January 2001
TEQUILA Workshop Amsterdam
30
Tequila Service Management
Engineering Model & Protocols
Subsc.
SSM
SrNP
SSM
SSM
SSM
SSM
Service Subscription Module
TFM
SrNP
User broker
SIM
Broker
SSM
SSM
SIM
ND
SIM
Service Invocation Module
out-of-band
invocation
in-band
invocation
Router
SIM
Router
SIM
Router
SIM
Router
SIM
Router
SIM
Router
SIM
Router
SIM
RSVP
25 January 2001
TEQUILA Workshop Amsterdam
31
Service Negotiation Protocol - SrNP
Client
Client
Server
Server
SessionInit
Accept
Proposal
Revision
• Client-server based
• Form-fill oriented
• Messaging is contentindependent
• Protocol stacks
Proposal
SrNP
XML
ProposalOnHold
HTTP,SMTP,IIOP
AcceptToHold
TCP/IP
AgreedProposal
SrNP
Accept
25 January 2001
TCP/IP
TEQUILA Workshop Amsterdam
32
RSVP - IntServ/DiffServ scenario
Reminder
Tequila Network
User A
sender
Ingress A
Egress B
Admission
Control
Admission
Control
SLS-I
Request
SLS-I
Admitted
RSVP PATH
RSVP
SLS-I
Request
RSVP RESV
25 January 2001
Is executed first
SLS-I
Admitted
RESV PATH
RSVP
User B
receiver
RSVP PATH
RSVP
RSVP RESV
TEQUILA Workshop Amsterdam
RSVP
RSVP RESV
33
RSVP - Service Invocation
Uni-directional service
Tequila Network
User A
sender
Ingress A
Egress B
Admission
Control
Admission
Control
SLS-I
Request
RSVP PATH
RSVP
SLS-I
SLS-I
Request
Admitted
RSVP PATH
RSVP
RSVP RESV
User B
receiver
SLS-I
Admitted
Admission Control
- AA user credentials
- in range check with
SSS - subscription
- resource availability
RSVP
RSVP RESV
data
• 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
25 January 2001
TEQUILA Workshop Amsterdam
34
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
25 January 2001
TEQUILA Workshop Amsterdam
35