The ANDROID Project

Peter T. Kirstein
University College London

14.3.02 ANDROID for IPv6 Concertation 1

 Partners in ANDROID

UPM

MEDIASEC

6WINIT EURO6IX 6NET

14.3.02 ANDROID for IPv6 Concertation 2

 The Nature of ANDROID
• An Active Network Technical Development
• In NGI area
• Planning to migrate all services to IPv6
• 28 Months from 1.6.99
• Project Cost 4.2 M Euro (EC 7.1M Euro)
• 643 man months
• 7 partners

14.3.02 ANDROID for IPv6 Concertation 3

 Project Overview
• ANDROID will prove the feasibility of
– a managed, scalable, programmable infrastructure
based on application layer active networking
• Technical approach
– Application Layer Active Networking
• existing system (FunnelWeb) is starting point
– Dynamic VPNs
• Cisco, 6WIND, Netcelo
– Management, Flexibility, Modelling to assess
scalability

14.3.02 ANDROID for IPv6 Concertation 4

 Main Activities
• Active Services Infrastructure
• Active Server Implementation
• Active Router Service implementation
• Application Components
• Modelling
• Integration and Testing
• All activities first in IPv4, then ported to IPv6
14.3.02 ANDROID for IPv6 Concertation 5
 Active Infrastructure
• Application Level Active Nets (ALAN)
– FunnelWeb is an implementation
• Network contains Execution Environment
for Proxylets (EEPS) - in end-systems
– Which may be active servers or routers
• EEPS use Application level framing
• Proxylets are loaded from web server
– May itself be an HTTP cache
– Are driven by policies written in XML

14.3.02 ANDROID for IPv6 Concertation 6

 Schematic of System

14.3.02 ANDROID for IPv6 Concertation 7

 System Schematic of A/Ss
NODE MONITORING/MANAGEMENT

AA
DEPOSITORY
A/S
CLIENT EDGE POLICY
NET
DEPOSITORY

ER

CORE SERVER
NET

14.3.02 ANDROID for IPv6 Concertation 8

 Active Server Overview
Control I/F Control I/F

Control I/F AA PM
AA PM
AA PM POLICY
AA
DEPOSITORY
DEPOSITORY
EEAA
CLIENT
SERVER

Node Management/Monitoring
14.3.02 ANDROID for IPv6 Concertation 9
 Funnelweb Overview
• Adhoc project name
• Produced Java-based Execution Environment
for Active Applications (EEAA)
• Active Applications are “in between” Applet
and Servlet
• EEs loads other Active Applications with
interface:
– Load, start, modify, stop

14.3.02 ANDROID for IPv6 Concertation 10

 Active Applications
• Active Applications are loaded from Web servers
which we showed as AA Depository
– These can be via cache servers
– They can ensure that AA code can be shared
– They can ensure trustworthiness of code
• Active Applications may be self-contained, or a
control for other Active Applications
– These may include dynamic protocol stacks
• Developing Mechanisms for storing and dis-
tributing policies, shown as Policy Depository
14.3.02 ANDROID for IPv6 Concertation 11
 Active Applications
• ‘Routing’ AA split in separate AAs
Applications:
– A Scaleable node discovery AA
– Develop various routing AA
• Self organising Transcoding Active Gateway
– Called ‘TAG’
• Application level and reliable multicast
• Watermarking of streams (e.g. use in VPNs)
• Media Record/replay including CDNs

14.3.02 ANDROID for IPv6 Concertation 12

 End User Applications
• Use as applications to stress system Mbone
multimedia conferencing
– Applications multicast in local environment
• Environment to run conferences VPN
– VPNs are set up dynamically
– VPNs Unicast tunnels between local environments
• Hence requires Transcoding Active Gateway
– Does Unicast-Multicast Relay
– Some media adaptation

14.3.02 ANDROID for IPv6 Concertation 13

 TAG Functions
• Automatic configuration of a multicast
session using the secure conference store
• Use of active networking for locating and
positioning a reflection point
• Re-multicasting reflecting streams to a client
• Modular approach to media relay proxylets
• Operation based on XML policies, generate
XML events

14.3.02 ANDROID for IPv6 Concertation 14

 TAG Architecture
WEB Server
EEP
TAG proxylets
TAG server
RMI session
Reflector
Discovery MBone
session
TAG client
Reflector
Discovery Discovery
session EEP
EEP

Media tool

14.3.02 ANDROID for IPv6 Concertation 15

 6WIND Active Router
• Can set up Unicast VPNs based on Active Code
• Runs IPv4 and IPv6 Stacks
• Can support also Mobile IPv6

Correspondent Node
Router

IPSec VPN
Mobile Node
Home agent

14.3.02 ANDROID for IPv6 Concertation Mobile IPv6 components 16

 TAG - VPN mode
SPAR
events
config VPN
Manager
TAG client MID
EEP tunnel config
Reflector Router unicast stream(s)

Router
multicast registration
stream(s)

Mbone Tool Reflection Reflector

Manager
local site remote site
14.3.02 ANDROID for IPv6 Concertation 17
 Other ANDROID Parts
• Policies for TAG and VPNs written in JML
• Policies and Active Server code stored in
replicated directories
• The set of replicated directories becomes a
Content Distribution Network (CDN)
• Need Neighbour Discovery to find Directory
• Whole thing written in JAVA
• Work on Mobility, security management,
resource management, network management
14.3.02 ANDROID for IPv6 Concertation 18
 Major Demonstration
UCL-EE
UCL-CS

6WIND

LEARnet 6-Bone
BT

Internet

-Host + VIC
NTUA
-VPN Manager
-VPN Configure
-AS + TAG -VPN Query/Reply
-VPN Join
-6Wind
-Unicast data
-Router -Multicast data Netcello
14.3.02 ANDROID for IPv6 Concertation 19
•
IPv6 Migration
Non-Java Applications like Mbone tools have
APIs re-written to meet IPv6 stacks
• All applications have addresses well
separated from rest of system
• Use of JAVA 1.4 JDK now allows Java
portion to be fairly easily ported to IPv6
• Use IPv6 PKI-enabled from U of Murcia
• 6WIND routers, hosts, servers all dual stack
• NETCELO management system still IPv4
– Can control IPv6 streams over IPv4 control path
14.3.02 ANDROID for IPv6 Concertation 20
 Conclusions
• ANDROID is developing major applications
– Which are useful broadly in real environments
like wireless
• While initially developed in IPv4, all is being
ported to IPv6
• By suitable policies, can be used directly in
the 6WINIT environment
• The porting will teach us much for 6LINK
– Will use in 6WINIT, 6NET and possibly Euro6IX

14.3.02 ANDROID for IPv6 Concertation 21