200 likes | 332 Views
TESTING SCENARIOS BT-UCL. Luis Velasco, Jose Luis Hilera BT-Laboratories. Our Proposal: Policy Driven Schemas. Use Enhanced Metadata to describe routing policies and express user preferences differential service. This Metadata works in a per-session basis
E N D
TESTING SCENARIOS BT-UCL Luis Velasco, Jose Luis Hilera BT-Laboratories
Our Proposal:Policy Driven Schemas • Use Enhanced Metadata to describe routing policies and express user preferences differential service. • This Metadata works in a per-session basis • XML is the technology used to wrap this Metadata allows multiple metrics... • Type of Services and Conditions required by the service can be expressed • Use Policies to Enforce QoS requirements. • LDAP to store the policies • Provide the means to share policies and populate the servers automatically
COIAS Application Satellite uplink Satellite downlink INTERNET RESOURCES ATM link Radio link Terrestrial link EUROCONTROL
Testbed Platform at BT BT Labs ATM Router A: 172.25.16.221 B: 172.25.16.130 C: 172.25.16.66 D: 172.25.16.2 E: 193.63.57.241 LearNet 172.25.16.0 / 24 A: 172.25.16.220 ISDN ISDN Cloud HUB A: 172.25.16.225 B: 172.25.16.134 C: 172.25.16.70 D: 172.25.16.6 ISDN B: 172.25.16.129 Active Node
Web Server BT-UCL Alternate Path Application Level Routing Scenario BT Labs UCL Router Active Node LDAP Server Router Active Node LDAP Server A link LearNet User 2a 1a B link 1b ISDN ISDN Cloud 2b 1c ISDN 2c ISDN C link
BT-UCL Multicast Scenario BT Labs UCL Router Active Node LDAP Server Router Active Node LDAP Server A link LearNet Users Users 2a 1a B link 1b ISDN ISDN Cloud 2b 1c ISDN 2c ISDN C link
Four mechanisms to prepare policies • Propagation of policies with inband signalling (cookies) • GET
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partner . . . . . . . . . . . . . . . . . . . . . . . Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8949017400008888 User’s DB Server’s DB AN’s DB Active Node (Web proxy) Web Server User GET (HTTP request) + cookie (with user’s policy) GET (HTTP request) + cookie (with user’s policy) Populate DB with user’s policy
Four mechanisms to prepare policies • Propagation of policies with inband signalling (cookies) • GET • GET-RESPONSE
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partner . . . . . . . . . . . . . . . . . . . . . . . Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8949017400008888 User’s DB Server’s DB AN’s DB Active Node (Web proxy) Web Server User HTTP response + cookie (with policy) HTTP response + cookie (with policy) Populate DB with policy
Four mechanisms to prepare policies • Propagation of policies with inband signalling (cookies) • GET • GET-RESPONSE • Non-propagate policies • POST (outband)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partner . . . . . . . . . . . . . . . . . . . . . . . Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8949017400008888 User’s DB Server’s DB AN’s DB Active Node (Web proxy) Web Server User POST (HTTP request) with user’s policy Populate DB with policy
Four mechanisms to prepare policies • XML - Embedded policies • Propagation of policies with inband signalling (cookies) • GET • GET-RESPONSE • Non-propagate policies. • POST (outband)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partner . . . . . . . . . . . . . . . . . . . . . . . Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8949017400008888 User’s DB Server’s DB AN’s DB Active Node (Web proxy) Web Server User HTTP response = XML policy file Populate DB with policy
Databases population USER SPACE REDIRECTION ENGINE (AN) On-going connections DB Application Decisions DB (caching) Application Redirector RMI Policy DB Analyzer Route DB Decisor XML-parser Interface DB LDAP CLIENT + INTELLIGENT ENGINE LDAP SERVER LDAP v3
Databases reading USER SPACE REDIRECTION ENGINE (AN) On-going connections DB Application Decisions DB (caching) Application Redirector RMI Policy DB Analyzer Route DB Decisor XML-parser Interface DB LDAP CLIENT + INTELLIGENT ENGINE LDAP SERVER LDAP v3
Databases reading USER SPACE REDIRECTION ENGINE (AN) On-going connections DB Application Decisions DB (caching) Application Redirector RMI Policy DB Analyzer Route DB Decisor XML-parser Interface DB LDAP CLIENT + INTELLIGENT ENGINE LDAP SERVER LDAP v3
Databases reading USER SPACE REDIRECTION ENGINE (AN) On-going connections DB Application Decisions DB (caching) Application Redirector RMI Policy DB Analyzer Route DB Decisor XML-parser Interface DB LDAP CLIENT + INTELLIGENT ENGINE LDAP SERVER LDAP v3
Computer B Computer A Demo Platform Server 2 Server 1
Questions? luis.velasco@bt.com hilerajl@drake.bt.co.uk