Peter T Kirstein University College London

1. Services in Next Generation InternetsPresentation at ICC2001Helsinki May 17, St Petersburg May 18, 2001 Peter T Kirstein University College London

2. Contents of Talk • Services in the NGI • IST activities towards the NGI • Two Typical NGI Projects • ANDROID • 6WINIT • NGI Testbeds • The Future

3. The Service Model • Will concentrate on service requirements • Will map onto areas being examined in EC IST • Will pay specific attention to factors which improve the Quality of Service (QoS) • Meaning of QoS depends on the application • Includes many functions often called different • Mapping often not clear in actual proposals

4. Next Generation Internet Services • Provide services to maximum population • Carry total telephone traffic • Be bearer for total mobile traffic (data & mm) • Carry most entertainment traffic • Carry essential service traffic • Electric Power Control • Defence and emergency services • Total financial transactions • Large-scale utility monitoring

5. Some Implications • Address Requirements frighteningly large • Often confidentiality of data required • Often also of addressees, with end-end confidentiality • Distributed Denial of Service defences improved • Distributed active services, Virtual Private Networks • Quality of service must be optimised • Within the constraints of bandwidth available • Probably requiring active services inside networks • Network infrastructure must be fortified • Security of network infrastructure components • Automated configuration

6. Implications of Requirements • Address requirements imply IPv6 • Could be met by IPv4 NATs, but features not sufficiently standardisd and hard to manage • Security at different levels helped by IPv6 • However security must also be at different levels • Quality of service helped by IPv6 Flow labels • But not meeting all QoS needs • Active processing inside net or at boundaries often vital • IPv6 Auto-configuration will help deployment • IPv6 aids to renumbering also vital • IPv4 projects could meet these, IPv6 more uniform

7. Composable Services • Some have attempted to provide high value high level composable services • Example is DARWIN/BEAGLE from CMU • NINJA from UCB • Requires a clearly thought-through architecture • Composable units at each level with useful properties • Depositories to store and retrieve the components • Resource Management at each level • Policies to determine how to do the composition

8. Key Issues being discussed • Fair (and hence unfair) share of resources • Secured services – data, addressees and infrastructure • Multimedia services – both interactive and streamed • Mobile services – including, but not only, wireless • Location services – integrity, authenticity and privacy • Heterogeneous services – with widely differing B/ws • Often services require different ways of working and parameters for different purposes • Clearly many real services are a combination of these • Policy-driven services will increase re-usability

9. IST Projects towards NGI • Many IST project are directed at new Services in the Next Generation Internet • One indicator is the use of IPv6 - though many such projects ignore IPv6 for now • Many such projects are first targeting novel services or network technologies • They consider the IPv6 element can be considered later, when its timing is clearer • We start with considering IPv6 Projects • but will quickly to two with novelty and IPv6

10. Many IST Projects Address IPv6 • 6INIT - Introduction of IPv6 services in Europe • 6WINIT- Wireless counterpart • ANDROID- Management of Active Networks • WINE - Wireless Internet Networks • LONG - Laboratories over NGNs • GCAP -Global Communication Architecture and Protocols • NETGATE - Advanced Network Adapter for NextGeneration of mobile and IP based Networks • AQUILA - Adaptive resource control for QoS Using an IP-based Layered Architecture

11. More IPv6 IST Projects • SEQUIN - End-to-end approach to QoS • DRIVE - Cellular/broadcast IP inter-working at IP WINE GLASS - IP mobility for UMTS-WLAN’s • MOBY DICK - IPv6 micro-mobility on Wnets • BRAIN - Seamless handover between heterogeneous Wnets • MIND - Mobile IP based Network Developments • SUITED - IPv6 over the EuroSkyways satellite • GEOCAST - Multicast Over Geostationary EHF Satellites

12. ANDROID and 6WINIT • Two EC IST IPv6-oriented projects illustrate future networks: • ANDROID • Provides management technology and applications of Active Networks • 6WINIT • Considers applications testbeds for wireless Internet – with special emphasis on clinical

13. ANDROID OBJECTIVES • Objective is to develop complete technology for Application-level Active Networks • Show how the Active networks can be managed • Validate the mechanisms with some complete system-level applications • All in the context of IPv6 networks

14. ANDROID SCHEMATIC • Application-level active components inside network • Both at router and server level • Using applications such as multimedia conferences, watermarking flows, content distribution networks, and VPNs • Whole system IPv6 capable

15. ANDROID Components • Client and/or Servers for Applications • Active Servers and/or Active Routers at or near domain boundaries • Wireless Network (WLessNet) • Show Active Server (AS) near wireless boundary • Boundary Router (BS) at wireless boundary • Active Application Code Server (AA Depository) • Policy Depository

16. NODE MONITORING/MANAGEMENT AA DEPOSITORY AS CLIENT WLESS NET POLICY DEPOSITORY BR SERVER CORENET System Schematic of ASs

17. POLICY DEPOSITORY AA DEPOSITORY EEAA CLIENT AA PM AA PM SERVER AA PM Node Management/Monitoring Architectural Overview of ASs

18. Applications Considered • Several Applications • Content Distribution Networks • Multimedia Conferencing • Virtual Private Networks • Watermarking flows for IPR • All need Active Applications near Boundary • Need Code & Policies loaded from Depository • Strongly need security, policies & management

19. ANDROID Features for NGN • Much more complex architecture at boundaries – with Policy driven modules • Active actions required to provide QoS at gross discontinuities of parameters • E.g. Multicast <-> Unicast • Transcoding or filtering for lower bandwidth • Reliable multicast for content distribution • VPNs • The actions often two features: the actual code and the policies on how the code is used

20. Reactive Loading • Present Internet based on limited services • NGN will have many more complex ones • Means not all will be resident at all boundaries • Both code and Policies may need to be loaded dynamically • NGN will have much graver discontinuities – yet real-time services - than current Internet • E.g. GSM versus Optical – (10**6) • Requires loading on demand – with security, and policies that may depend on users

21. Policies for different Purposes • Security, QoS, Fairness, Mobility • Number of different Policy constituents • How used • How triggered • At what level • Static or Dynamic • In ANDROID, the technology is being thought through – without Wireless • In 6WINIT, more complex testbed applications are being developed with real wireless nets

22. Different levels of Policy • Different levels of Policy • Application, User, Class, Path • Different Policy Components • Enforcement Point • Decision Point • Depository • IETF Policy Framework Definition Language • Restricts access, controls routing

23. Lessons from ANDROID • This type of architecture, with policy driven modules inside the net, allows powerful services tailored both to applications and groups • Using IPv6 will eventually provide a defined set of underlying services, superior to those guaranteed in IPv4 • Use of a high level language such as XML allows a very flexible expression of the services

24. 6WINIT Objectives • Validate introduction of Wireless Internet • Based on IPv6 + GPRS and UMTS/3GPP • Validate integration of these protocols • In real application with whole testbeds • Ensure implementations are generic • Ensure testbeds not too tied to application • Maintain international perspective • Felt we wanted wide partnership

25. RUS Partners

26. Focus of 6WINIT Wireless Testbed • Procedures for IPv6-2G-3G Nets • Including IPv4/IPv6 network and application integration • Investigate problems providing a trans- national wireless delivery service • Early IPv6-ready applications testing • Implement handsets and edge devices

27. Testbed Aims • Carry out in-depth applications in the clinical domain, in hospitals: • Whittington (UK), Tubingen (DE), John Paul II (PL), U. of Basel (CH) • Validate specific non-clinical apps • Road Warrior, Seamless wandering, Streaming Media, Weather station access, M-commerce activities

28. Specifically Not-Addressed • Redefinition of air interface • Technologies for the home like ADSL • Re-definition of higher-level applications e.g. HTTP • Development of complete applications • Development of complete IPv6 Stacks • WAP

29. Some 6WINIT Applications • Road Warrior • VPN Extended to mobile users • Problems with security, accounting and addressing with dynamic addresses • Seamless Wandering • Resource and address discovery, navigation aids, content adaptation, location awareness

30. Clinical 6WINIT Applications • Exact applications will be identified during first few months, but may be: • Remote Access to Haematology database for anticoagulant clinical management • Ambulance to base communications including A/V and vital data • Remote booking and reservation systems

31. IST NGI Testbed Actions • Have ported some tools over to IPv6 • e,g, secured Mbone tools (RAT,VIC, NTE, SPAR) • High Quality Digital Video tools from CRL • Still do not use underlying features such as QoS • Have started setting up IPv6 Testbeds • Will show Japanese WIDE - European MBS link • Now connects French Renater with Japanese IPv6 WIDE • MCI WorldCom offered to link in their IPv6 testbed • Are planning to introduce active tools • e.g. those from ANDROID and others • Mobile ones from 6WINIT and others

32. COIN-15/IPv6 Forum Session

33. Some Areas Not Yet Tackled • Most IETF protocols for advanced services still being formulated in IPv4 context • IPv6 activities still only paying lip service here • 3G Bodies have agreed to move to IPv6 • Still unresolved how far and deep to go • There are still conflicts with IETF principles • Next Generation Networks Services starting • Internet2 and NTON ones in the US, IPv4 • Large IPv6 ones in Japan, smaller in Korea • Smaller IPv6 testbeds are starting in Europe

34. The Future • Initiatives like the IPv6 Task Force (and NGN-I) will tackle how to progress the move to NGN Services on a larger scale • Achieving QoS on small-scale fairly easy • The problem is in finding solutions which: • scale in size of network and speed • Apply for many applications, enough to justify H/W implementations in Silicon • Large scale Pilot Problems Essential here • Hope that these come from current initatives

35. Great Progress is being made Much Remains to be done